301 redirect missing?

Why removing the 301 redirect?
How do I can redirect parent page to child page?

This was a terrible decision… Like Craig Bailey, I am a paying member and I feel like this type of thing is forcing me to pay for the plugin on more sites. I will find an alternative and never pay again for SEO Yoast. God… I really hate decisions like this that hurt the user just to try and squeeze more $ into your pockets. Well… you lost my $. Let me know if you change this back. Bye.

Hey @tacoverdo

Regarding your comment below:

Your redirects aren’t lost. They’re safely stored in your database and if you decide to switch to Yoast SEO Premium, all of them will be automatically important in the redirects-module.

My old redirects have not been imported yet ??

I’m doing a massive restructure at the moment and I’m stuck.

Still would’ve been nice to have some advance notice from the Yoast team …

btw @diywebmastery – excellent blog post. Thanks for that work.

Best,
Frank @ MFJLabs

@mfjlabs – Thanks and no problem.

If anyone happens to use a Genesis theme, we updated our free Genesis Club Lite plugin and it
a) copies all the Yoast redirects out if you have them
b) puts them into a list that you can paste into your .htaccess at the click of a button, or
c) keeps them in the Genesis Club plugin where you can always see a full list of all your redirects.
d) allows you to redirect on a page and post basis and maintains a fully visible lists of all redirects whether you previously used Yoast SEO for these or not.

Liz

I understand wanting to discourage people from continuing to do redirects like this but it’s disappointing you didn’t leave a way to remove ones that have already been set.

@bigj9901 – You can check out my blog post. It will help you get the ones you have out.

Thanks @diywebmastery . I did reference your post.

One caveat from your post. The redirects your script outputs only work if your pages are in the root. It does not use the complete path for subpages or blog posts that use category. It was still very helpful though. Thanks again

This makes two useful features that have been recently removed from the advanced tab… First, “exclude from the XML sitemap” was removed, forcing users to navigate to the XML sitemaps section, go to the exclusions tab and exclude by post ID, and now we’ve lost easy redirects. In my opinion, both changes are much less efficient…

Regardless of the reason given by Yoast I still find this a bizarre move. By all means explain the reason not to do redirects in this way, but ultimately it’s down to us whether we want to take the hit over speed or not. Using htaccess is fine if your a developer but I can’t ask my clients to do that. having the option to do this on page was extremely useful. This just feels like a money making exercise which is disappointing.

The last version I can see that still has the 301 redirect feature is 1.7.4. i’ll be sticking to that for the time being.

Bad move removing a feature we’ve become accustomed to having without notification. Is there another plugin for a redirect?

Yep, @mikegood — it was mentioned previously, but it’s easy to miss in this thread:

The Redirection plugin has served me well for quite a long time now. I had only recently started to think of using this feature inside of Yoast…

Hope this helps!

So what if we need to remove existing redirects? Do you have to upgrade to remove them? I suppose we could install an old version of the plugin just to remove the redirect, then update again..

@davidjs – If you had already added a 301 to a page, then the box remains in place so you can edit or delete. You could also read the post by @diywebmastery mentioned above – Regardless, I still think this is a pointless change, and I absolutely hate it…

Thanks @scott. @davidjs – I just updated my post in response to your comment.