If Google reports a page as 'Crawled - currently not indexed', Google has fetched the page but chosen not to add it to its search index. That is not a bug and not a penalty. Google saw the page and set it aside, usually because it judged the page too thin, too duplicative or too weakly linked to earn a place in the index.
The fix is rarely 'request indexing again'. The fix is to change the signal the page sends: make it more distinct, link to it better, and give it a clear canonical. Below is the pipeline, the common misconceptions, and a checklist you can run on a small site this week.
Crawl, index and serve are three separate stages, and a 200 response only proves the first one
Google's own documentation separates these stages, and mixing them up is the root of most bad fixes.
Crawl is when a bot fetches a URL and reads the response. Index is when Google stores and processes that page so it can be retrieved later. Serve is when Google returns the page as a result for a query. A page can pass crawl, fail index, and never reach serve. That is the state Search Console calls 'Crawled - currently not indexed'.
Put simply: crawl is a fetch, index is a decision, serve is a ranking outcome. They are not the same event.
Each stage leaves a different trace, so check the trace instead of guessing
| Stage | What it means | Where to check it | Typical wrong fix |
|---|---|---|---|
| Discovered | Google knows the URL exists but has not fetched it yet | Search Console Page indexing report, 'Discovered - currently not indexed' | Resubmitting the sitemap repeatedly |
| Crawled | Google fetched the page | URL Inspection tool, 'Crawled' status; server logs show the bot hit | Assuming the page is live in search |
| Indexed | Google stored the page and can retrieve it | URL Inspection, 'Page is indexed'; site: query returns the URL | Confusing 'indexed' with 'ranking well' |
| Served | Google returned the page for a query | Search Console Performance report, Queries tab | Expecting traffic the moment indexing lands |
The URL Inspection tool is the authoritative check for a single URL. The Page indexing report is the aggregate view. The Performance report is the only place that shows serve. If a page is indexed but has zero impressions, it is indexed and not served. That is a relevance and ranking question, not an indexing one.
Most 'crawled but not indexed' pages fail on one of four checks: thin content, duplication, a wrong canonical, or a stray noindex
Google's own guidance on page indexing lists the reasons a crawled URL is left out. On a small site, the common ones are: the content adds little unique value, the page duplicates another URL, the canonical points elsewhere, or a noindex directive is present.
A canonical is an HTML link tag that tells search engines which URL is the preferred version of a page. A noindex is a meta tag or HTTP header that tells search engines not to include the page in results. Both are instructions, not requests, and both get set by accident: a staging tag left in a template, a CMS default, or a plugin that adds canonicals pointing at the homepage.
Before changing content, check the response. Fetch the URL with a tool that shows headers, or use the URL Inspection 'View crawled page' option. Look for a noindex in the HTML head or the X-Robots-Tag header. Look at the canonical. If either is wrong, fixing content will not help.
The second check is duplication. If two URLs return the same or near-same content, with and without a trailing slash, with tracking parameters, or a print version, Google may crawl both and index neither. Pick one canonical and make the other redirect or point to it.
On a small site, consolidation beats addition: merge thin pages and link the survivors
Small sites have a specific problem. Fewer pages means each page carries more weight, and a handful of thin pages can drag the whole set. The fix is consolidation, not addition.
Start with the pages that have the least unique text. If two pages cover the same service in the same city, merge them into one stronger page and redirect the weaker one. If a page exists only to hold a form or a thank-you message, set it to noindex deliberately and keep it out of the sitemap.
Then check internal links. A page that no other page links to is a page Google has little reason to prioritise. Add contextual links from related pages using descriptive anchor text. On a small site, the homepage and the main service pages should link to every page you actually want indexed.
Boilerplate is the other trap. A long company description or a standard disclaimer that appears on every page does not make each page unique. Trim it or move it to a single page and link to it.
Sort the unindexed list by business value, and leave some URLs out on purpose
Not every unindexed URL deserves a fix. Some should stay out of the index on purpose.
Sort the unindexed list into three groups. First, pages you need in search: service pages, product pages, key articles. Fix these first. Second, pages that should not be indexed: tag archives, filtered views, internal search results, staging copies. Set noindex or block them in robots.txt and remove them from the sitemap. Third, pages you are unsure about: leave them for two to four weeks and check again before spending time.
Work top-down by business value, not by the order the report lists them. One strong service page indexed is worth more than twenty tag pages fixed.
Internal links are the main signal a small site controls, and the sitemap is only a discovery aid
Google's crawl is driven by links, and a page with no internal links is effectively orphaned even if it is in the sitemap.
Keep the click depth low. A page three clicks from the homepage is easier to find than one six clicks deep. Build a flat structure: homepage, main sections, leaf pages. Link from the main sections to the leaf pages with anchor text that describes the target.
The XML sitemap is a discovery aid, not a promise of indexing. The sitemaps.org protocol defines the format; it does not promise indexing. Submit the sitemap, keep it accurate, and remove URLs you do not want indexed.
If your site is new, expect crawl activity to grow over the first weeks. There is no public figure that applies to every site.
After a fix, verify the signals and then wait: recrawl takes days to weeks and 'Request indexing' only queues a check
Indexing is not instant. After a fix, Google has to recrawl the URL before the status can change. The URL Inspection tool has a 'Request indexing' button, but Google's documentation is clear that it is a request, not a command.
To verify a fix, compare the URL Inspection result before and after. Check that the canonical now points to the intended URL, that no noindex remains, and that the page returns a 200. Then wait. A recrawl can take days to weeks depending on the site. There is no public figure for an assured turnaround.
Pressing 'Request indexing' over and over does not force the outcome. It queues a check. If the underlying signal has not changed, the result will not either.
Review indexing monthly with a simple log, because a flat count is not the same as a healthy one
Set a monthly review, not a daily one. Open the Page indexing report, note the count of 'Crawled - currently not indexed', and compare it with last month. A flat number is not necessarily bad if the site is stable. A rising number on new pages is the signal to look closer.
Keep a simple log: URL, date crawled, status, fix applied, date rechecked. This is the only reliable way to tell whether a change helped. Without a log, you are guessing.
For AI answer engines, the same pipeline applies in principle. A page that is not indexed by a search engine is unlikely to be retrieved by a system that depends on search-style retrieval.
Key Facts at a Glance
- 'Crawled - currently not indexed' means Google fetched the page but chose not to store it.
- Crawl, index and serve are three separate stages; a 200 response only proves crawl.
- The URL Inspection tool is the single-URL check; the Page indexing report is the aggregate view.
- Check
noindex, canonical and duplication before changing content. - 'Request indexing' queues a check; it does not force a result.
- Internal links and a flat site structure are the main signals a small site controls.
What does 'crawled but not indexed' actually mean?
Google fetched the page and read it, but decided not to add it to the search index. The page can still be reached by direct URL. It will not appear in search results until Google indexes it.
Does requesting indexing ensure the page gets indexed?
No. Google's documentation describes it as a request that queues a recrawl. If the page still looks thin, duplicate or blocked, the result will not change.
How long does indexing take after a fix?
There is no fixed number. It depends on crawl frequency, site size and how much the page changed. Days to weeks is common.
Why are my small site's pages slow to index?
Small sites have fewer internal links and less crawl history. Fewer signals mean Google has less reason to revisit quickly. Consolidating pages and linking them well is the main lever.
How do I check if a page is indexed or served?
Use URL Inspection for indexed status. Use the Performance report for served status. A page can be indexed and still get zero impressions.
Data sources: Google Search Console documentation (Page indexing report, URL Inspection tool, Performance report) and the sitemaps.org protocol.
Sources (checked 2026-10-27): Google Search Central: Consolidate duplicate URLs (canonicalization) ยท sitemaps.org: Sitemap protocol.