Indexability
Indexability is the ability of a web page to be included in a search engine's index. A page can be crawlable but not indexable if it has a noindex tag, canonical pointing to another URL, or other indexation blockers.
Reviewed by Alexander Yarovenko · Updated: 2026-09-18
What is Indexability?
Indexability refers to whether a web page can be included in a search engine's index. Indexability is distinct from crawlability: Googlebot can crawl a page but still choose not to index it due to various signals. A page must be both crawlable AND indexable to have any chance of ranking.
Why Pages Fail to Be Indexed
| Cause | Signal | Intentional or error? |
|---|---|---|
| noindex meta tag | <meta name="robots" content="noindex"> | Usually intentional |
| Canonical tag pointing elsewhere | <link rel="canonical" href="[other URL]"> | Usually intentional |
| robots.txt disallow | Cannot crawl → cannot index | May be error |
| Thin/low-quality content | Google chooses not to index | Quality issue to fix |
| Duplicate content | Google consolidates duplicates; non-canonical not indexed | Architecture issue |
| Soft 404 | Page returns 200 but has near-no content | Error |
| Discovered but not indexed | Google aware but hasn't indexed yet, or chose not to | May be quality issue |
How to Check Indexability
- GSC Coverage report → "Not indexed" section shows all unindexed pages and the reason
- URL Inspection Tool → enter any URL to see its index status, last crawl date, and blocking reasons
- site: operator →
site:yourdomain.com/specific-pageshows whether Google has indexed it - Screaming Frog → check for noindex meta tags and canonical issues at scale
Crawlability vs Indexability
| Crawlable | Indexable | |
|---|---|---|
| robots.txt blocked page | No | No (can't crawl, can't index) |
| noindex page | Yes | No |
| Canonical to another URL | Yes | No (this URL) |
| Normal page | Yes | Yes |
How to use this concept in SEO
Indexability requires more than a 200 response: Google must be allowed to crawl the page, see meaningful rendered content, identify a coherent canonical, and judge the page useful enough to store.
Audit checklist
- Confirm that the implementation matches the page purpose and the user task.
- Check the HTTP response, rendered HTML, canonical, robots rules, and internal links together.
- Use Search Console and analytics to verify the result instead of relying on one crawler signal.
- Test a representative URL on mobile and desktop after deployment.
- Document the expected outcome so regressions can be detected in the next audit.
Practical example
How to validate the result
Record the current crawl, indexation, performance, and traffic state before changing anything. Recheck the affected template and a representative URL after deployment, then monitor Search Console over the following crawl cycle. A technical change is complete only when the live response and Google’s observed state agree.