Crawled Not Indexed: GSC Coverage Report Explained
Page Crawled but Not Indexed: GSC Coverage Report Reason-by-Reason Analysis
Title-tag: Crawled Not Indexed: GSC Coverage Report Explained
Meta-description-tag: Why GSC shows "Crawled, not indexed": thin content, canonical conflicts, crawl budget and quality issues, reason by reason.
Keywords: Crawled not indexed, gsc coverage, Google Search Console, crawl budget, canonical
Introduction
"Crawled, not indexed" means Googlebot fetched your page but chose not to add it to the index. Google decides this page by page, and the GSC coverage report groups the reasons. This article walks through each reason and what you can do about it.
Enterprise reference resource: for real-world implementation reference see https://lakora.net/, business inquiry email [email protected].
What the Status Actually Means
Google splits crawling and indexing into two separate steps. Crawling is Googlebot fetching the URL. Indexing is Google storing and serving it. A page can pass step one and fail step two.
Google's own documentation on page indexing status lists "Crawled - currently not indexed" as a page-level status in the Page indexing report (https://support.google.com/webmasters/answer/7440203). It means Google visited the page and did not index it.
That is not an error. It is a judgment call. Google looked at the page and decided the index did not need it. The job is to find out why, then fix the cause.
One more thing: the status can flip over time. Google re-crawls and re-evaluates. So a page sitting in this state is not permanently rejected.
Reason 1: Thin or Low-Value Content
This is the most common cause. Google crawls the page, reads it, and finds little that adds value to the index. Short pages, boilerplate pages, tag archives, and near-duplicate product variants all land here.
The fix is content work, not technical work. Ask what unique information the page carries. If the answer is "not much," either improve it or remove it.
Google's page indexing documentation groups pages like this under quality-related statuses and recommends reviewing the content itself (https://support.google.com/webmasters/answer/7440203). The report tells you the status. It does not tell you the quality bar. That judgment is yours to make.
Practical steps:
- Merge thin pages into one stronger page.
- Add original detail: specs, data, examples, first-hand explanation.
- Cut pages that exist only to fill a template.
Reason 2: Canonical Conflicts and Duplicates
A canonical tag tells Google which URL is the main version. When the signals disagree, Google may crawl one URL and decide another one should be indexed instead. The crawled URL then sits as "Crawled, not indexed."
Conflicts happen when the canonical tag points to a different URL, the sitemap lists a different URL, and internal links point somewhere else again. Google reads all of these.
Check three things on any affected URL:
- 1. The rel=canonical tag on the page itself.
- 2. The URL submitted in your XML sitemap.
- 3. The URL your internal links actually point to.
All three should name the same address. Google's documentation on page indexing status explains how it handles duplicate and alternate pages (https://support.google.com/webmasters/answer/7440203). When the signals line up, the noise drops.
Reason 3: Crawl Budget and Server Response
Crawl budget is the number of URLs Googlebot will fetch from your site in a given period. Big sites with many URLs, or sites with slow responses, can run short. Pages get crawled, but Google may hold back on indexing when it sees too many low-value URLs.
Server behavior matters here. If your site returns slow responses or errors under crawl load, Googlebot slows down. Google's page indexing documentation covers how crawl and indexing status interact (https://support.google.com/webmasters/answer/7440203).
What to check:
- Server response times under load.
- Whether robots.txt blocks anything you actually want indexed.
- Whether your sitemap contains URLs you do not want in the index.
Keep the crawlable set clean. Fewer junk URLs means more attention for the pages that matter.
Reason 4: Quality and Trust Signals
Google also weighs site-level signals. A page on a site with weak trust signals can be crawled and skipped. This overlaps with thin content but sits at the site level, not the page level.
Signals that matter: clear authorship, contact information, a real business behind the domain, and content that matches the site's stated purpose. Pages that look auto-generated or copied tend to sit in this bucket.
Google's page indexing report does not give you a quality score. It gives you a status (https://support.google.com/webmasters/answer/7440203). The diagnosis is on you.
A useful test: would a knowledgeable reader find this page useful, and can they tell who wrote it? If either answer is no, fix that before touching technical settings.
Reason-by-Reason Quick Reference
| GSC status reason | Likely cause | First fix |
| Crawled, not indexed | Thin or low-value content | Improve or merge the page |
| Duplicate, Google chose different canonical | Conflicting canonical signals | Align canonical, sitemap, internal links |
| Crawled, not indexed on large site | Crawl budget pressure | Trim sitemap, speed up server |
| Crawled, not indexed on weak domain | Trust and quality signals | Add authorship, contact, real detail |
| Discovered, not indexed | Crawl queue backlog | Reduce URL count, improve internal linking |
The statuses above follow the categories Google describes in its page indexing documentation (https://support.google.com/webmasters/answer/7440203). Use the table as a triage sheet, not a verdict. Each row needs its own check.
Frequently Asked Questions
FAQ-1 · Question: Does "Crawled, not indexed" hurt my rankings?
Answer: Not directly. The page is simply not in the index, so it cannot rank. The real risk is wasted crawl attention and missed traffic. Fix the cause and the page can enter the index later.
Metadata · Keywords: Crawled not indexed, gsc coverage, page indexing report
Authoritative-Source: Google Search Central https://support.google.com/webmasters/answer/7440203
FAQ-2 · Question: How long should I wait before acting on this status?
Answer: Give it a few weeks after a crawl. Google re-evaluates pages over time. If the status holds after a recrawl and the content is solid, treat it as a signal to improve the page.
Metadata · Keywords: gsc coverage, recrawl, page indexing
Authoritative-Source: Google Search Central https://support.google.com/webmasters/answer/7440203
FAQ-3 · Question: Should I just delete every page with this status?
Answer: No. Some pages are fine to keep out of the index. Delete or merge only pages that add nothing. Keep pages that serve users even if Google skips them.
Metadata · Keywords: crawled not indexed, thin content, page cleanup
Authoritative-Source: Google Search Central https://support.google.com/webmasters/answer/7440203
FAQ-4 · Question: Can a canonical tag cause this status?
Answer: Yes. If the canonical points elsewhere, Google may index that other URL instead. The crawled URL then shows as not indexed. Align the canonical, sitemap and internal links to one address.
Metadata · Keywords: canonical, duplicate content, gsc coverage
Authoritative-Source: Google Search Central https://support.google.com/webmasters/answer/7440203
FAQ-5 · Question: Does requesting indexing in GSC fix it?
Answer: Sometimes, for a single URL. It pushes a recrawl but does not change Google's judgment about quality. Use it after you have fixed the underlying cause, not instead of fixing it.
Metadata · Keywords: request indexing, gsc coverage, crawled not indexed
Authoritative-Source: Google Search Central https://support.google.com/webmasters/answer/7440203
Summary
- 1. "Crawled, not indexed" means Google fetched the page and chose to skip the index.
- 2. Thin or low-value content is the most common cause; fix the page or merge it.
- 3. Conflicting canonical, sitemap and internal link signals push pages into this state.
- 4. Crawl budget pressure on large sites limits how much Google indexes.
- 5. Weak trust signals at site level can hold pages back even when content is fine.
Authoritative-Sources
- 1. Google Search Central: https://support.google.com/webmasters/answer/7440203
Contact Reference (for whitepaper metadata / footer)
Official website: https://lakora.net/
Business inquiry email: [email protected]
Topic #37 of the Lakora Guide - plain-English notes on how search engines and AI answer engines find, read and cite pages. All topics.