Knowledge base v2.13.0 · Community edition · data through 2 October 2026
Thing · Status code
The HTTP status code for success: the server returns the page, and its content can be considered for indexing.
Documented in
Google's JavaScript SEO guide says Googlebot sends every page with a 200 HTTP status code to the rendering queue, whether or not it contains JavaScript, unless a robots meta tag or header tells Google not to index it, and Google uses the rendered HTML to index the page.
Google Search Central · Day 2 · Lightning session D: Rendering and JavaScript
Google's JavaScript SEO basics says every page with a 200 status code is queued for rendering, whether or not it uses JavaScript, unless a robots meta tag or header says not to index it; for non-200 pages such as 404 error pages, rendering might be skipped.
Google Search Central · Day 2 · What is Google friendly JavaScript
Google's Search Central post on CDNs says that if Google cannot recognise an error message served with a 200 status as an error, all pages showing the same message may be dropped from the index as duplicates, and recovery can be slow because Google has little incentive to recrawl duplicates. For bot-verification interstitials it recommends sending crawlers a 503 status.
Search Central blog (24 December 2024) · Day 2 · Handling web duplication
Slide and stage claims that name it, the ones Google’s documentation does not cover first.
An HTTP 200 OK status only means that the server believes it managed to do what the client asked for.
Gary Illyes · Day 1 · How crawling works
CDN captcha challenges often return HTTP 200; Googlebot does not solve them and sees only content with a 200 status, which indexing then classifies as a soft 404, reported as an error in Search Console.
Gary Illyes · Day 1 · How crawling errors affect Search
The fix for a client-side soft 404 is to make a missing page end with a real HTTP 404 status code instead of 200.
Rebecca Yu · Day 2 · Lightning session D: Rendering and JavaScript
A community speaker warned that HTTP 200 responses across a new domain show only that the URLs work, not that the content users came for is still there, so after launch the redirect map becomes the test.
David Carrasco Pamies · Day 2 · Lightning session E: Managing Duplicates and Site Moves
When a crawler's request returns 200, the page, file or other resource that comes back is eligible for indexing.
Cherry Prommawin · Day 1 · How crawling errors affect Search
A soft 404 is a 404 in disguise: the page returns 200 but its content says something like 'page not found', information the site should have sent as the HTTP status.
Cherry Prommawin · Day 1 · How crawling errors affect Search
In single-page apps, a missing page often shows a custom 404 page while the server returns HTTP 200, because the front-end router, not the server, handles the 404.
Rebecca Yu · Day 2 · Lightning session D: Rendering and JavaScript
Google's slide defined a soft 404 in a JavaScript application as a page that serves a 'Not Found' message but returns a 200 HTTP status code.
Erin Sparling · Day 2 · What is Google friendly JavaScript
In JavaScript single-page apps, soft 404s typically arise because the server returns the app with a 200 status for every URL, so when the app shows a 'not found' message for a URL that does not exist, no error is reported.
Erin Sparling · Day 2 · What is Google friendly JavaScript
A soft 404 is a page that should return an error status code but returns HTTP 200; from a crawling point of view it looks indexable, but because it has no real content Google throws it out of the index.
Gary Illyes · Day 2 · Understanding what's on a page
An audience member asked whether a product detail page that is out of stock for two to three months should keep returning 200 with links to similar products, or be 302-redirected to a similar product or to its parent product listing page.
From the audience · Day 2 · Welcome to indexing day!
A community speaker listed four common but often overlooked JavaScript rendering mistakes: non-crawlable link markup, error pages that return HTTP 200 in single-page apps, content behind user interaction, and JavaScript or API resources blocked in robots.txt.
Rebecca Yu · Day 2 · Lightning session D: Rendering and JavaScript
For temporary blocks return 503 or 429, never a 200 page with a captcha or error message, which becomes a soft 404 and can replace real content in the index. Verify Googlebot by reverse DNS, not by user agent.
Ibrahim Anjro · Day 1 · How crawling errors affect Search
Day 1 said a CDN captcha page served with HTTP 200 becomes a soft 404, while Day 2 (D2-C374, D2-C375) said such challenge pages are hard to recognise as errors and can be clustered as duplicates; Google's CDN post describes both outcomes, and in both the real pages drop out of Search.
Ibrahim Anjro · Day 1 · How crawling errors affect Search
Keep a product page that is out of stock for a few months live with a 200 status, show its availability on the page and in Product structured data, and offer pre-ordering where possible when users would wait for the product. Redirect it only when users would rather switch to a similar product than wait.
Ibrahim Anjro · Day 2 · Welcome to indexing day!
The stage remark that content indexable without JavaScript can pass through without rendering does not mean such pages skip rendering, because Google's guide queues every 200 page for rendering; read it as: content already in the raw HTML does not depend on the slower rendering pass.
Ibrahim Anjro · Day 2 · Lightning session D: Rendering and JavaScript
After moving to real paths, set the server or hosting rewrite rules so a direct request to every valid path returns 200 with the content (ideally server-rendered) and an unknown path returns a 404 status, which removes client-side soft 404s at the source.
Ibrahim Anjro · Day 2 · What is Google friendly JavaScript
Return real error status codes for error states, 404 or 410 for missing content and 503 for outages such as a failed database connection, also in single-page apps; a 200 page whose main content is only an error message is treated as a soft 404 even when header and navigation look normal.
Ibrahim Anjro · Day 2 · Understanding what's on a page
Check what your CDN or bot protection serves to verified Googlebot and to the AI agents you want to allow; if crawlers must get a challenge page, return it with a 503 status as Google recommends, never as a 200 page across many URLs, which Google may cluster as duplicates.
Ibrahim Anjro · Day 2 · Handling web duplication
The stage doubt that every URL gets rendered sits beside Google's JavaScript guide, which says every page with a 200 status is queued for rendering unless a robots rule blocks indexing: queued is not the same as rendered, so do not rely on rendering for critical content.
Ibrahim Anjro · Day 3 · How long does it take to..?
Kit items about 200: their own words name it, or several of the claims they rest on do.
Return a real 404 for unknown routes in single-page apps, or use a documented client-side fallback
Rests on 7 claims, 5 of them naming 200; its own words name 200
Never serve error states, empty results or failed data loads with a 200 status
Rests on 10 claims, 5 of them naming 200; its own words name 200
Never serve bot challenges or error pages to crawlers with a 200 status
Rests on 7 claims, 4 of them naming 200; its own words name 200
Server-render the main content and everything indexing depends on (SSR, static generation or hybrid)
Rests on 11 claims, 2 of them naming 200; its own words name 200
Answer planned maintenance and short outages with 503, for a day or two at most
Rests on 11 claims, 2 of them naming 200; its own words name 200
Redirect an old URL only to a page with the same intent, and return 404 or 410 when there is none
Rests on 7 claims, 1 of them naming 200; its own words name 200
Keep temporarily out-of-stock product pages live with 200 and their current availability
Rests on 5 claims, 1 of them naming 200; its own words name 200
Point every canonical directly at a final URL that returns 200, is indexable and is linked
Rests on 8 claims, 0 of them naming 200; its own words name 200
Keep robots.txt reachable on every host: 200 with rules, or 404 if there are none
Rests on 4 claims, 0 of them naming 200; its own words name 200
Also inglossary terms Single-page app (SPA), Soft 404
Things named in the same claim, with the number of claims they share.