What is indexability?
Indexability is a page's eligibility for the index. A page is indexable when a search engine can reach it, can read its content, and has not been told to leave it out. That makes it a chain of conditions rather than a single switch: the URL has to return a success code, it cannot be blocked from crawling in robots.txt, it cannot carry a noindex directive in its meta tags or HTTP headers, its canonical tag has to point at itself rather than at another page, and the content has to be visible to the crawler once the page is rendered.
It is often paired with crawlability, and the two are different. Crawlability is whether the crawler can get to a page; indexability is whether, having got there, it is allowed to keep it. A page can be crawlable and not indexable, and that combination is the most common way good content disappears.
Why it matters
Why indexability matters
Because an unindexable page has no search presence at all. It does not rank low; it does not rank. Every hour spent on its content, its design and its links is wasted until the directive that keeps it out is found. And those directives are easy to set by accident: a noindex left on from the staging site, a plugin setting applied to a whole post type, a canonical tag pointing every page at the homepage, a redirect that loops. Launches are lost this way with some regularity.
It matters in the other direction too. Deliberately making a page unindexable is how a site keeps checkout steps, thank-you pages, internal search results and duplicate variants out of the results, so indexability is a control to be used, not only a fault to be avoided.
In practice
How indexability works in practice
- 01
The check is a short list, and it is run on every important page before launch and after any template change. Does the URL return 200? Is it allowed in robots.txt? Does the page's meta robots tag or X-Robots-Tag header say index, or say nothing? Does the canonical point to this URL? Does the content appear in the rendered HTML rather than only after a script runs? Is the page linked from somewhere the crawler already knows, and is it in the sitemap? The URL Inspection tool in Search Console answers all of these for a single page in one screen.
- 02
At scale the same questions are asked by a crawler such as Screaming Frog or Sitebulb across the whole site, which flags every page that is non-indexable and why. The report is read against intent: pages that should be out and are out are fine, pages that should be in and are out are the bugs.
Watch out
What people get wrong about indexability
Assuming the sitemap decides it. Listing a page in the sitemap is a request; a noindex tag on the page is an instruction, and the instruction wins. The other mistake is blocking a page in robots.txt to keep it out of the index, which prevents Google reading the noindex tag and can leave the page indexed as a bare URL. The third is forgetting rendered content: a page whose text loads only after a client-side script may be indexable in theory and empty in practice, because what the crawler stores is what it managed to render.
