Why is my ‘not found’ page returning 200 and how do I fix it?
Before we dive into the technical weeds, I need to ask you the most important question in my playbook: Do you control the site? If you are trying to fix a search result for a page you don’t own (like a social media profile, a past employer’s blog, or a site you sold), the advice changes drastically. If you do own the site, you have the power to fix this—but you have to fix it the right way.
I’ve spent a decade cleaning up digital messes. Nothing drives me crazier than a client who tells me, "I deleted the page, why is Google still showing it?" The answer is usually a "Soft 404."
The Soft 404 Trap: Why your "Not Found" page is a liar
A proper 404 response tells search engine bots: "This page is gone, it will never come back, please drop it from your index."
A server returns 200, however, tells the bot: "This page exists, it is healthy, and it’s a valid part of my website."
When you delete a page but don't configure your server to send a 404 status code, your site serves a "Not Found" page that acts like a real page. Googlebot sees the "200 OK" status, assumes your site has a weirdly named page that displays a message, and keeps it in the search index. This is what we call a soft 404. It’s the number one reason deleted pages linger in search results indefinitely.
Two Lanes: Control vs. No Control
Depending on your access level, you have two different workflows to clear these results. You must identify your lane before taking action.
Scenario Primary Goal Recommended Workflow You control the site Fix the server header status. Update server response, then GSC. You do NOT control the site Request removal of stale content. Use Google Refresh Outdated Content.
Lane 1: You Control the Site (The "Fix it Right" Workflow)
If you control the server, don't just "wait for Google." Waiting is for people who like losing traffic. Follow this checklist to ensure that page is gone for good.
1. Check the Header Status
Use a tool like `curl -I` or a browser header checker. If the status code is anything other than 404 or 410, your server is misconfigured. You need to talk to your developer (or update your .htaccess/Nginx config) to force a true 404.
2. Audit for Parameter Bloat
Don't just submit one URL. If your site generates pages with parameters (like `example.com/page?ref=social`), make sure you are blocking those patterns or canonicalizing them. Google tracks these individually.
3. Use the Google Search Console Removals Tool
Once your server is finally outputting a 404, head to the Google Search Console Removals tool. Submit the URL here. This acts as an emergency "nudge" to get the page out of the index within 24-48 hours, rather than waiting for the next crawl cycle.
4. The Search Console URL Inspection Check
After a few days, use the Search Console URL Inspection tool to check the status. If it says "URL is not on Google," you’ve succeeded. If it says "Soft 404 detected," your server header is still set to 200. Go back to step 1.
Lane 2: You Don't Control the Site
If the page belongs to someone else—perhaps a site that hosted an old press release or an embarrassing photo—you cannot change their server headers. You are at the mercy of their site owner and Google’s automated processes.
The "Refresh Outdated Content" Workflow
When the content has been changed or removed by the site owner, but it still shows up in search, use the Google Refresh Outdated Content tool. This tells Google, "Hey, I checked, and this page is gone/different—please update your index."
- Provide the live URL (if it still exists but is different).
- Provide the exact snippet that is still showing in search.
- If you are removing Google Images, you can use the same tool to submit the direct image file URL.
The Cost of Cleanup
People often ask me what the budget is for this. In my experience:
- DIY: Free (your time). Most of this can be done by a site owner with basic technical literacy.
- Developer Help: If you aren't comfortable editing server files, a dev might charge 1-2 hours to audit your error page settings and ensure proper 404 implementation across the entire site.
Final Troubleshooting Checklist
Before you close your laptop, run contentgrip.com through this quick workflow to ensure you aren't leaving digital breadcrumbs:
- Verify the Status: Does your server return a 404 header? (Don't guess; check the headers).
- Clear the Cache: Did you clear your site’s caching plugin or CDN (like Cloudflare)? Sometimes the cache holds onto the "200" status even after you’ve updated the server.
- Check Google Search Console: Have you submitted the URL to the Removals tool?
- Check Google Images: Does the image appear in an image search? If so, remove the image file from your media library and ensure it returns a 404.
- Patience, but not passive waiting: Once the technical side is correct, it will fall out of the index. If it’s been more than 14 days and it’s still indexed, re-run your header check.
Fixing index bloat isn't magic; it’s housekeeping. Stop letting your server lie to search engines, and you’ll find that Google is much more willing to treat your site with the respect it deserves.
