Royking Niba

Crawled – Currently Not Indexed: Google Read the Page and Passed. Here Is How to Find the Template Causing It

· Royking Niba

Stock photograph of a data centre corridor lined with server racks. It is a generic stock image and not a photograph of Google's infrastructure or any client system.

Crawled – currently not indexed is a Page Indexing status in Google Search Console meaning Googlebot fetched the URL, read it, and decided not to add it to the index for now. Unlike “Discovered – currently not indexed”, this is not a queue: Google has seen the page and passed on it. The fix is almost never to resubmit the URL. It is to find which template is producing pages Google does not want, and either make those pages worth indexing or stop producing them.

What Google actually says

From the Page Indexing report help page, checked on 2 October 2026:

The page was crawled by Google but not indexed. It may or may not be indexed in the future; no need to resubmit this URL for crawling.

Google Search Console Help, Page Indexing report

Two phrases in that definition do most of the work. “May or may not be indexed in the future” means the status is a current decision, not a permanent verdict. “No need to resubmit” means the Request Indexing button is not the lever: Google already has the page. The same help page groups this status under pages that “have not been indexed, but not necessarily because of an error”, and it is blunt about the wider point: “Google doesn’t guarantee that all pages everywhere will make it into the Google index.”

Google’s How Search Works page says the same thing from the other side: “Indexing isn’t guaranteed; not every page that Google processes will be indexed.” It then lists the common reasons, and the first one is the one that usually applies here: “The quality of the content on page is low”. The other two it names are robots meta rules that disallow indexing and a site design that makes indexing difficult.

How it differs from the statuses next to it

StatusHas Google fetched the page?What it meansWhere the fix lives
Discovered – currently not indexedNoThe URL is known and waiting in the crawl queueCrawl capacity or crawl demand, see the backlog model
Crawled – currently not indexedYesGoogle read the page and declined to index it for nowThe page, and more often the template that produced it
Duplicate without user-selected canonicalYesGoogle judged it a duplicate and picked another URLCanonical signals, see the duplicate triage
Soft 404YesThe page says “missing” to a human while returning 200The status code, see soft 404s
Excluded by noindex tagYesYou told Google not to index itYour own robots rules

The 1,000-row ceiling, and why the export misleads

The help page states that “the list of example URLs in the report is limited to 1,000 items, and isn’t guaranteed to show all URLs in a given status, even when less than 1,000 items.” On a site with 2,301 URLs in this status, the export can show at most 1,000 of them, 43.5 percent, and nothing guarantees those 1,000 are a fair cross-section. Teams that sort the export, read the top fifty URLs and rewrite those fifty pages are fixing whatever happened to be at the top of a partial list.

The way round it is to stop treating the report as a list of pages and treat it as a rate per template. You know every URL your site generates, because your CMS or crawler can list them. Group them by template, match the report’s examples against those groups, and use URL Inspection on a handful from each group to confirm the status holds across it.

A worked example: the template ratio

This is an illustrative model, built to show the method, not a client’s data. An 8,000-URL store with six templates has 2,301 URLs reported as Crawled – currently not indexed, 28.8 percent of everything it publishes. Here is the same number broken out by template, with the “excess” column counting URLs above an assumed 5 percent baseline, a modelling choice that allows even a healthy template a few stragglers.

TemplateURLs publishedCrawled, not indexedRateExcess over 5% baseline
Product pages4,0001604.0%0
Category pages300124.0%0
Blog posts600549.0%24
Paginated category pages1,00029029.0%240
Tag archives1,20091276.0%852
Internal search results90087397.0%828
Total8,0002,30128.8%1,944

Read it from the right. 1,944 of the 2,301 URLs, 84.5 percent, sit above baseline, and two templates account for 1,785 of them, 77.6 percent of the whole report: tag archives and internal search results. Neither of those is a content quality problem you can write your way out of. They are pages the site should not be offering to Google in the first place. The product pages, which are the ones that earn money, are fine at 4 percent. The fix for this site is two template decisions, not 2,301 page rewrites.

Paginated category pages at 29 percent are the interesting middle case. Deep pages in a long series often carry little that the first page does not, so a share of them going unindexed is expected. What matters is whether the products they list are reachable and indexed on their own, which is the subject of the pagination arithmetic.

Cause, evidence and action

Likely causeEvidence you can checkActionWhat not to do
A template produces low-value pages (tags, internal search, empty filters)Rate far above the site baseline for one templateStop generating or linking the URLs; use noindex where they must exist, and keep them crawlable so the rule is seenRewrite individual pages from that template
Near-duplicate of a page Google has indexedContent overlaps heavily with another live URLConsolidate with a redirect or rel=canonical, which Google rates as strong signalsBlock the duplicate in robots.txt, which Google says not to use for canonicalization
Thin or low-value page on an otherwise good templateLow rate on the template, the page itself adds littleImprove it, merge it, or retire itPad it with words; there is no length threshold, see thin content
Recently published pageFirst crawl date is recentWait, and keep it linked from strong pagesResubmit it repeatedly; Google says there is no need
Main content depends on JavaScript that did not renderURL Inspection rendered HTML is missing the contentServer-render the primary content, see JavaScript SEOAssume Google saw what your browser shows
Page is effectively empty but returns 200Empty listings, “no results” statesReturn a 404, see soft 404sLeave it on 200 and hope

The audit, in order

  1. Export the status from the Page Indexing report and note the total count, not just the rows you can download.
  2. List every URL your site publishes from the CMS or a full crawl, grouped by template.
  3. Match the export against those groups and compute a rate per template, as in the table above.
  4. For each template above baseline, run URL Inspection on five to ten URLs to confirm the status and check the rendered HTML.
  5. Decide per template: stop producing, consolidate, noindex, improve, or leave alone.
  6. Ship the template change, then validate the fix in Search Console. Google says validation “typically takes up to about two weeks, but in some cases can take much longer”.
  7. Re-run the rate table after a month. The number to watch is the excess column, not the raw total.

Where this sits in a recovery

A rising Crawled – currently not indexed count is often the first visible symptom of a site producing more pages than it can justify, which is the same pattern behind index bloat and many of the traffic drops that get misdiagnosed as penalties. If the count jumped at the same time as rankings fell, start with the diagnosis sequence in Google penalty recovery before touching individual pages.

Related reading

Leave a Reply

Your email address will not be published. Required fields are marked *