What it means
A 200 response says the request hit no errors and the response body contains the requested resource. For a GET request that is a page, image or API data; for a POST it is usually the result of the operation. The code itself says nothing about whether the content is correct, complete or useful.
Most common causes
- The page exists and loaded without errors.
- The app shows an error as a normal page but returns 200 (a “soft 404”).
- A CDN or cache serves a stale copy that is still a 200.
- A blank or near-blank page caused by a JavaScript error, while the server still returns 200.
What you can do as a visitor
- If the page looks normal, there is nothing wrong with the response.
- If the page is blank, try a hard refresh (Ctrl+F5) or another browser. The problem may be scripts or extensions.
What the site owner or developer should do
- Return 404 or 410 for URLs that don't exist, not a 200 with a “not found” message.
- Make sure key content is in the HTML itself, not only rendered after JavaScript runs.
- Check the canonical, title and meta robots. A 200 page with noindex is still dropped from the index.
- Monitor “Soft 404” reports in Google Search Console.
Impact on SEO and Google
Google only indexes pages that return 200 (directly or after a redirect that ends in 200). Soft 404s, 200 responses carrying an error message, waste crawl budget and show up as errors in Search Console.
Frequently asked questions
Does a 200 mean the page is in Google?
No. 200 only means the response succeeded. Indexing also depends on robots rules, noindex, the canonical and content quality.
What is a soft 404?
A page that tells the user the content doesn't exist while the server returns 200. The correct response is 404 or 410.