Wordpress-seo: Snippet editor doesn't reflect permalink consistently

[Rarst]

Different cases observed.

Nested page

Actual permalink example.com/parent-page-name/child-page-name
Snippet editor: example.com/child-page-name

Custom post type

Actual permalink example.com/dev-blog/article-name
Snippet editor: example.com/article-name

[AskKim]

Please inform the customer of conversation # 97000 when this conversation has been closed.

[Pcosta88]

Please inform the customer of conversation # 114428 when this conversation has been closed.

[dpardes]

This is currently an issue on my production site. I'd love to know when it's fixed but am curious about the workaround others are using.

[AskKim]

Please inform the customer of conversation # 97000 when this conversation has been closed.

[AskKim]

Please inform the customer of conversation # 107999 when this conversation has been closed.

[monbauza]

Please inform the customer of conversation # 131884 when this conversation has been closed.

[Kizzycocoa]

Can anyone confirm, is this purely visual on the page, or does this actually affect the URL Google etc. display?

[Rarst]

This should be purely visual. URL handling is still left to core, editor is only for the purposes of editing slug part.

[Kizzycocoa]

Ah, excellent! Thanks a lot. I don't know much of these things, so I was worried that I'd need to switch SEO. Thanks for clarifying!

[Pcosta88]

Please inform the customer of conversation # 149335 when this conversation has been closed.

[monbauza]

Please inform the customer of conversation # 151066 when this conversation has been closed.

[Pcosta88]

Please inform the customer of conversation # 159222 when this conversation has been closed.

[iamazik]

Please inform the customer of conversation # 159366 when this conversation has been closed.

[iamazik]

Please inform the customer of conversation # 172900 when this conversation has been closed.

[monbauza]

Please inform the customer of conversation # 182009 when this conversation has been closed.

[Pcosta88]

Above user provides the following images to illustrate the issue

[bmihajlovski]

i am experiencing not only a snippet display problem but search engine results errors too. for example, although my default urls are domain.com/product/product-name and domain.com/category/subcategory yoast changes them to domain/product-name and domain/subcategory on google, and when clicked on google you get invalid (404 page) destination, because the link that is displayed on google is not existing.
Please help me.

[thulshof]

Please inform the customer of conversation # 177580 when this conversation has been closed.

[iamazik]

Please inform the customer of conversation # 187315 when this conversation has been closed.

[monbauza]

Please inform the customer of conversation # 188844 when this conversation has been closed.

[monbauza]

Please inform the customer of conversation # 193018 when this conversation has been closed.

[Pcosta88]

Please inform the customer of conversation # 196322 when this conversation has been closed.

[Pcosta88]

Please inform the customer of conversation # 195778 when this conversation has been closed.

[amboutwe]

Please inform the customer of conversation # 200236 when this conversation has been closed.

[zameer85]

I have the same problem... the permalink url shows up domain.com/shop/category/product-name however on the seo snippet preview it shows domain.com/product-name. Strange thing is that both urls work!!!! How to fix this?

[zameer85]

@amboutwe So i assume this issue has not been resolved yet? Thanks for your support!

[monbauza]

Please inform the customer of conversation # 205471 when this conversation has been closed.

[Pcosta88]

Please inform the customer of conversation # 205983 when this conversation has been closed.

[iamazik]

Please inform the customer of conversation # 206027 when this conversation has been closed.

[zameer85]

Sorry, but someone please clarify if this issue has been resolved or not? I have just updated the plugin to the latest version but i still i have the same issue.

[Pcosta88]

@zameer85 Hi,

We can confirm that the issue is still an open one. We have it marked for future release. You can view the tracking of the progress in the top right of the screen under milestone

[monbauza]

Please inform the customer of conversation # 211465 when this conversation has been closed.

[devnihil]

Please inform the customer of conversation # 215051 when this conversation has been closed.

[ghost]

Same issue here. If my pages can't display the correct URL in search engines, I'm considering deactivating the plugin until it's fixed. I definitely don't want my visitors to be getting 404s. Any way you guys could have the slug display the default URL (if "Stop words in slugs" is set to "keep")?

[jcomack]

We discovered that this only happens when creating new posts and that this is purely a visual thing in the snippet preview. This has no impact on the actual permalink structure whatsoever.
Once you save the post, the page reloads and the new / proper permalink structure is displayed.

Because we're in the process of moving towards a Gutenberg compatible implementation, I'll reference that issue to ensure it stays on the radar.

Related https://github.com/Yoast/yoast-components/issues/195

[Pcosta88]

Please inform the customer of conversation # 250751 when this conversation has been closed.

[monbauza]

Please inform the customer of conversation # 253983 when this conversation has been closed.

[Pcosta88]

Please inform the customer of conversation # 255551 when this conversation has been closed.

[Pcosta88]

Please inform the customer of conversation # 255335 when this conversation has been closed.

[iamazik]

Please inform the customer of conversation # 273769 when this conversation has been closed.

[Pcosta88]

Please inform the customer of conversation # 279865 when this conversation has been closed.

[jdevalk]

@CarolineGeven This really needs fixing, given the amount of complaints about it, making a queue-candidate.

[iamazik]

Please inform the customer of conversation # 302405 when this conversation has been closed.

[Pcosta88]

Please inform the customer of conversation # 302582 when this conversation has been closed.

[gezquinndesign]

Is this fixed?

[rmarcano]

Please inform the customer of conversation # 308925 when this conversation has been closed.

[iamazik]

Please inform the customer of conversation # 326119 when this conversation has been closed.

[kurniaoone]

Is this fixed?

[jdevalk]

@kurniaoone nope, then the issue would be closed ;-)

[sadam7777]

i have similar cases. I am using TOTAL wp theme and use the Post type editor function. The problem is the permalinks is different from the snippet yoast.

it do effect the SEO in search engine. the search engine will crawl the permalink instead of snippet yoast. i did a experiment using post and pages, the google crawl the yoast snipper, ONLY the post editor type function google dont crawl.

this make my blog reach lower than it suppose to be. any solution will be helpful

[mayada-ibrahim]

Please inform the customer of conversation # 346152 when this conversation has been closed.

[moorscode]

As we are currently in the progress of moving the Snippet Editor to React, this can be solved without having to refactor a lot of code that is currently present.

This problem is in context while building the newer version of the editor.

[Raymondstanley02]

Once same issue on www.MP3blends.com

[sadam7777]

@moorscode can you explain? i dont really understand. do you mean we can solve this problem?

[moorscode]

We are aware of the problem, but due to how the code has been set up currently, we cannot easily fix this problem.

We are in the process of rebuilding this feature of the plugin, but that is a complex project that will take some time to complete. The problem will be addressed in that project and will be resolved whenever we are ready to release the new code.

So to answer your question, this is not something _you_ can solve, but something we can (and will) solve.

[zameer85]

Is there an ETA for solving this problem? This thread of complaint has started in 2015, it's ironic how a SEO plugin can ignore such big permalink problem? It may be complex to fix but shouldn't it be the priority?

[iamazik]

Please inform the customer of conversation # 358726 when this conversation has been closed.

[rmarcano]

Please inform the customer of conversation # 368178 when this conversation has been closed.

[mariusghitulescu]

Please inform the customer of conversation # 372708 when this conversation has been closed.

[monbauza]

Please inform the customer of conversation # 375597 when this conversation has been closed.

[Pcosta88]

Please inform the customer of conversation # 375956 when this conversation has been closed.

[mariusghitulescu]

Please inform the customer of conversation # 377527 when this conversation has been closed.

[amboutwe]

Please inform the customer of conversation # 382931 when this conversation has been closed.

[iamazik]

Please inform the customer of conversation # 89570 when this conversation has been closed.

[iamazik]

Please inform the customer of conversation # 429705 when this conversation has been closed.

[Pcosta88]

Please inform the customer of conversation # 442636 when this conversation has been closed.

[Pcosta88]

Please inform the customer of conversation # 446931 when this conversation has been closed.

[Xyfi]

Instead of trying to construct the permalink ourselves, we should simply use the Gutenberg permalink. This can simply be retrieved using wp.data.select( "core/editor" ).getPermalink(). This way we don't have to construct the permalink ourselves.

This means the permalink will still be broken in the classic editor, but will lead to a lot less bugs because building the permalink is handled by Gutenberg instead of us.

If this is implemented the changes in Yoast/yoast-components#790 can be undone.

[atimmer]

@Xyfi Will that allow for realtime editing of the slug using the snippet editor?

How should other platforms expect to use this when they implement the SnippetEditor component into their version of Yoast SEO?

Edit: I am not opposed to doing it like that, but I prefer that this decision be taken with all the relevant context taken into account.

[IreneStr]

Change of plans: we're going for the implementation described in #11537.

[vetlaser]

After I created subcategory for post in admin area, YOAST snippet permalink shown doesn't include parent category snug, only subcategory snug, is this resolved? right now for each category page, I have two different permalink that both works, but I need to eliminate #1:

/MySubCategory
/MyCategory/MySubCategory

[Pcosta88]

Please inform the customer of conversation # 522449 when this conversation has been closed.

[Pcosta88]

subpages also fail to appear

[Pcosta88]

Please inform the customer of conversation # 559828 when this conversation has been closed.

[iamazik]

Please inform the customer of conversation # 568416 when this conversation has been closed.

[priscillamc]

Please inform the customer of conversation # 580636 when this conversation has been closed.

[rmarcano]

Please inform the customer of conversation # 581381 when this conversation has been closed.

[Pcosta88]

Primary Category fails to be outputted into the permalink part of the Snippet Preview

[Pcosta88]

Please inform the customer of conversation # 587481 when this conversation has been closed.