What breaks indexing when the page looks perfectly fine?
- Published November 6, 2026
- Linked from 1 answer
- In a cluster of 77
What breaks it is something you cannot see by reading the page: an instruction in the code, a response from the server, or a version of the page that differs from the one in your browser. The fastest way to find it is to stop reading the page and inspect what Google received, using the URL Inspection tool in Search Console.
The checks, in the order to run them
| Check | What goes wrong | Where to look |
|---|---|---|
| noindex | A robots meta tag or <!–INLINECODE0–> header tells Google not to index the page, which can come from a template, a plugin setting, or a staging configuration that reached production | Page source, HTTP response headers, Page indexing status URL marked ‘noindex’ |
| Canonical | The canonical points to another URL, so Google treats this page as a duplicate of it | Page source; the canonical Google selected in URL Inspection |
| robots.txt | A disallow rule stops Google from fetching the page, so it cannot read the content or any noindex on it | robots.txt report in Search Console; test the URL against the file |
| Status code | The server returns an error or a redirect to Googlebot while the page loads for you | Response code in URL Inspection's live test |
| Rendering | The main content depends on JavaScript that does not run or loads only after a click | Rendered HTML in URL Inspection |
| Soft 404 | The page returns 200 but looks empty or like an error page to Google | Page indexing status Soft 404 |
| Duplication | The page is nearly the same as another, so Google shows the other one | Duplicate statuses in the Page indexing report |
Google’s JavaScript SEO guidance explains that Googlebot queues pages with a 200 status for rendering “unless a robots meta tag or header tells Google not to index the page”, which is one reason a stray noindex is worth checking first: it stops the process before rendering begins.
Mobile adds a twist. Google indexes the mobile version of a site’s content, so a mobile template that drops text, links, or markup can hide content that the desktop page you are looking at still shows. Google’s mobile-first indexing guidance also notes that Google won’t load content that requires user interactions such as clicking or typing to load.
How to work through it
Start with the cheapest checks, noindex and canonical, because each takes a minute in the page source. Then run a live test in URL Inspection and compare its rendered HTML and response with what you expect. The live test does not cover every indexing issue; Google notes it does not test whether a page is a duplicate or alternate, so read the indexed view and the Page indexing report for that part.
If every technical check passes and the page still is not indexed, content becomes the main suspect, though not the only one: a new page may still be in processing, and Google does not index every page it can. Compare the indexed view with the live test, then judge the page’s usefulness; what to do first when a page says crawled, currently not indexed picks up from there. Fix one cause at a time and re-inspect after each change, so you know which one was blocking the page.
Add a comment