Yoast Compatibility

Actually, this isn’t perfect, as the snippet is showing an extra trailing slash for the URL, but I’m not sure how to correct that…

There is a new update for Yoast SEO and this fix can’t help anymore. Any ideas?

No – I have no idea what the problem or fix is at this point, either. Because sometimes the Yoast metabox will display the correct, changed, URL, minus the trailing slash (that’s odd, too).

Sometimes it looks like it’s displaying the first URL the page was published with, not the current (changed) URL. That’s kind of scary.

Why would you want to change permalinks via this plugin when you can do that via Yoast?

Seriously? *shocked look*

I didn’t realize that was possible with Yoast.

Ok, so I deactivated the Custom Permalinks plugin to test this theory, because I did see that the Yoast meta box allows you to customize the URL.

1) Deactivate the Custom Permalinks plugin.
2) Create new child page and edit.
3) WP Editor shows child page URL as domain.com/parent/child/, while Yoast meta box shows the URL as domain.com/child/
4) Yoast breadcrumbs are automatically assigned the WP URL for pages: domain.com/parent/child/
5) Default URLs still exist and are NOT redirecting to custom URLs.

So, I am going to have to re-activate the Custom Permalinks plugin. So, you’re right, Yoast DOES allow you to customize the URL, but it doesn’t handle it very well. If for no other reason than to avoid potential conflicts of duplicate content and duplicate URLs for my site. At least with the Custom Permalinks plugin, when I customize a page’s URL, the default WP URL is 301 redirected to the customized URL.

The downside to this is that there is no way to back up those permalink changes or redirects. As soon as the plugin is deactivated, all of the custom URLs revert to WP defaults and all of the 301s are effectively rendered useless then.

Also – It looks like with the most recent version of Yoast, my original issue has been corrected and the fix mentioned in my original post (which was no longer working) is no longer necessary.

Thus, marking this topic as closed.