At what point is a “not indexed” page a content problem vs a domain-trust problem?
- Published November 6, 2026
- Linked from 1 answer
- In a cluster of 5
Count how far the problem reaches before deciding. If one page or a small group is not indexed while comparable pages on the same site are, the cause sits with those pages. If indexing is poor across most of the site, including simple, useful pages that should be easy to accept, look at the site as a whole. “Domain trust” is shorthand here, not a Google metric; Google publishes no such score, though it does describe crawl capacity limits that apply to a site as a whole.
How to measure the spread
Use Search Console, not a site: search. Google’s site: operator documentation warns that it “doesn’t necessarily return all the URLs that are indexed under the prefix specified in the query”, so it is the wrong tool for counting indexed pages. The Page indexing report gives you the indexed and not-indexed totals and the reason for each excluded URL, and you can filter it to the URLs in a sitemap. The status names do not give the cause: Google’s Page indexing report documentation says Crawled – currently not indexed “doesn’t necessarily indicate an issue that needs attention”, and for important pages it points to URL Inspection to diagnose site issues first.
| What the report shows | Possible level | First move |
|---|---|---|
| A few pages Crawled – currently not indexed, the rest indexed | Page | Inspect the URLs: Google-selected canonical, HTTP status, rendered HTML; then compare them with indexed siblings: are they thinner, newer, or near-duplicates? |
| One section or template not indexed, other sections fine | Template or section | Look for a shared cause: a noindex in the template, duplicate content across the section, or thin pages built from one pattern |
| A large share of the site Discovered – currently not indexed | Crawling at the site level | Check server health in Crawl Stats and look for junk URLs competing for crawls |
| A large share Crawled – currently not indexed, across sections | Possibly site-wide quality | Rule out shared technical causes on a sample first (canonical choices, rendering, server responses), then review the site's content, starting with the weakest and the repetitive pages |
Why the level changes the fix
A page-level problem has a page-level fix: make the page distinct, more complete, or merge it with its twin. A section-level problem can be one template mistake repeated many times, which one change can solve. A site-level pattern takes longer, because the remedy is to reduce the proportion of weak pages and improve what remains; for the point at which weak pages start to affect the rest of a site, see how many low-value indexed pages it takes to drag a site down.
A check that cuts both ways
Pick two pages: the weakest page that is indexed and the strongest page that is not. If the strong page is not indexed while weaker pages are, look for a technical cause on that page before anything else, because the comparison suggests quality is not the whole story. If the indexed pages all share something the excluded ones lack, such as internal links from the homepage or original content, that difference is the lever.
Whichever level the count points to, fix that level first; a site-wide content program will not repair a single misplaced noindex, and a single-page rewrite will not change a pattern that runs across hundreds of URLs.
Add a comment