Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
The current orthodoxy is that noindex will lead to (an effective) nofollow tag after some time.(if you believe this).
I feel like you deserve some kinda congratulatory trophy for defeating a black and white animal very publicly.@F5K7, they are technically "errors." Google expected content it knew about and got a 404 error instead. This is fine and not really an error, it's just where they place them in the Coverage Report.
After starting this thread I ended up talking about this issue in various places on the forum. Here's two posts you'll find of interest:
You asked what you can do to make Google know it's on purpose. You can throw a 410 error instead of a 404. You can think of a 404 error as "Missing" and a 410 as "Gone" (as in, yes, there was content here and we purposefully have removed it).
- https://www.buildersociety.com/threads/Ω-→-∞-surrender-supremacy.446/post-41818
- https://www.buildersociety.com/threads/Ω-→-∞-surrender-supremacy.446/post-41926
I never did the 410 method simply because I didn't want to deal with writing code for it. But with the 404 you may have to get the pages crawled a couple of times before Google says "okay, we get it, it's gone and we'll deindex it." Most pages will drop out pretty quickly and the final stragglers will take months.
There was a few times, since I had so many URLs, that I ended up filtering the temporary sitemap down to what was left so I could get a fresh look in the Coverage Report. This also helped get those URLs crawled again.
_____
UPDATE
I never really updated what happened with this mini-project, but removing the 147 low quality posts, fixing a few indexation errors with categories, and then fixing around 700 blank URLs being indexed due to robots.txt... I got a full recovery as far as I can tell so far. I became convinced it was a Panda problem and treated it as such and it took about 11 months after the fixes were deployed to finally pop back up in the SERPs:
I never did the 410 method simply because I didn't want to deal with writing code for it. But with the 404 you may have to get the pages crawled a couple of times before Google says "okay, we get it, it's gone and we'll deindex it." Most pages will drop out pretty quickly and the final stragglers will take months.
What do you think about serving a 410 for all 404 pages. That would be pretty easy to do and I don't see the downside.
I'm not sure if this was mentioned already, but I was just doing something similar due to an affiliate link cloaking plugin. Old search console has a URL removal tool. I used it today and the URLs were out of the index in just a few hours. The downside is that it may only be temporary (90 days). You can do all urls that start with a specific prefix in one shot too.
I use the redirection plugin to monitor my 404s and every few days check and manually redirect anything to the correct (or next best) content.What do you think about installing a plugin that redirects any 404s to closely related pages, if available.
If you delete huge amounts of content, there is a good chance that what was discredit as an irrelevant link adds up. This way you wouldn't lose any backlinks. Obviously that's only a solution for big sites where individual 301 redirects aren't feasible.
What do you think about installing a plugin that redirects any 404s to closely related pages, if available.
If you delete huge amounts of content, there is a good chance that what was discredit as an irrelevant link adds up. This way you wouldn't lose any backlinks. Obviously that's only a solution for big sites where individual 301 redirects aren't feasible.
I use the redirection plugin to monitor my 404s and every few days check and manually redirect anything to the correct (or next best) content.
I wouldn't trust a plugin to determine which page is most relevant. I prefer to setup the redirect right when I delete the post.
If your worried about your .htaccess file getting too long and bloated, this does PHP redirects. You still have to create each one individually (is that your concern?)
Oh god yes, this. So much this.This was one of those stupid, vague, cryptic statements that another Google employee debunked on the same day, but the debunking never outpaces the #fakenews. John Mueller sometimes plays the same old ego game Matt Cutts used to play: "I know something you don't know, not because I'm smarter, but because I have access. But if I state it like a wise old sage where you have to unravel the riddle, then you'll think I'm smart."
Old != Low Quality
Yeah, I went through and removed all internal links to the deleted posts, and I redirected the deleted posts back to their parent categories. I don't want 404's for users or Google. I truly believe that most of Tech SEO is about doing Google the favor of not costing them wasted resources, and they return the favor back to you.Prior prunes, I just deleted the posts outright (safest). However then you have potentially bad user experiences and 404 links on your other posts (like if you had linked to a post you pruned from a still live post).
The only thing to consider is that noindex pages will still play a role in Google's new "user experience" Core Web Vitals page speed stuff like Cumulative Layout Shift, Largest Contentful Paint, First Input Delay, etc. (readers can learn more here). So they still need to be up to snuff. Could create a maintenance issue that you could dodge by deleting the posts, redirecting them, and deleting internal links (as to not have a redirect chain or bad user experience).Anyway, I think I will go to the effort of noindexing my pruned posts this time. Anyone have any thoughts on why delete vs noindex might be better?