 Today's question comes from San Francisco. What should I do with 404s in Search Console that are from ancient versions of my site? So sites evolve over time, URLs change, you add redirects, redirects get dropped over the years, sometimes URLs are just no longer needed. These URLs end up returning 404. So they show up in Search Console as crawl errors, but what does that mean? When an invalid URL is opened, it's the right thing for a server to return a 404 page not found error. When doing a restructuring of your website, we recommend redirecting from old URLs to the new ones and updating the links that go to the old URLs to point to the new ones directly. However, over time, you might decide to drop those redirects, maybe because of the maintenance overhead, or just maybe you forgot about them. These URLs are now 404s in Search Console. In your server logs or analytics, check for traffic to those URLs. If there's no traffic, that's great. In Search Console, check for links to those URLs. Are there no relevant links? That's great too. If you see nothing special in either the links or the traffic, having those pages return 404 is perfectly fine. If you do see traffic to those URLs, or see links pointing at those URLs, check where they're coming from, and have those links point at the new URLs instead. Or if it looks like a lot of traffic or links are going to those URLs, perhaps putting a redirect back in place would be more efficient. That works for a few crawl errors, but what if you have a ton of 404 errors? Search Console makes this easy. It prioritizes crawl errors for you. If the top errors in the report are all irrelevant, you can rest assured that there's nothing more important further down on the list. Crawl errors for 404s that you don't want to have indexed don't negatively affect the rest of your site in Search. So take your time to find a good approach that works for you. If you found that useful, please like and comment on the video so that we know to make more of them.