Yoast creating redirect for the front page.
locksmithunit opened this issue · comments
Hello everyone, how are you doing?
I’m using the Memsmerize Theme Pro, and I noticed that the front page actually has a slug.
I contacted the theme support, and they told me it’s connected to Yoast and the Gutenberg editor.
Here are screenshots from our emails:
The theme developer also uploaded a video demonstrating the issue:
Just for the record, even when the slug is empty, there’s still a redirect:
“yourdomain.com/mesmerize-pro” to the front page (yourdomain.com)
As you can see in the video, before activating the Gutenberg editor (the default WordPress editor), the slug is empty. However, even when the slug is empty, there’s still a redirect:
“yourdomain.com/mesmerize-pro” to the front page (yourdomain.com)
On my website, I’ve temporarily changed it to get rid of the mesmerize-pro URL. (i changed that to “/cerrajero-barcelona” to git rid of the “/mesmerize-pro”)
But this behavior doesn’t seem right; the front page shouldn’t have any weird redirects.
I’ll also try to post this issue on your WordPress.org to see if we can find a solution. If you have any ideas on why this happened or how to fix it, I’d appreciate hearing about it.
Regards,
Nadav
Thanks for using the Yoast SEO plugin and for creating the issue.
Quick answer: When you set a page as a Front page or Homepage within the WordPress Dashboard > Settings >Reading >Homepage, the respective page won't load the slug you have added to it before when viewing on the browser. It's an expected behavior on WordPress, and it's not a redirect by the Yoast SEO plugin.
It is expected that when you set a static page to be the homepage of your site, WordPress hides it from the URL. It is also expected that when you check your homepage slug from the Quick Edit option or if you use the block editor, you will still see the slug of the homepage.
So whatever you set as the slug for your homepage will reflect that, but when it loads for a user, it will just appear without the slug or just as your top-level domain name. In that sense, we can say slug remains hidden, so we don't treat this as an issue of concern.
Closing this issue as it's not related to a bug and is an expected behavior.