What does “Crawled — currently not indexed” actually mean?

Google fetched the page, read it, and decided not to add it to the index. It is a quality decision, not a crawl error. When it applies to a handful of thin pages it is normal housekeeping; when it applies to most of your new pages, Google is telling you something about how it rates the whole domain.

How is “Discovered — currently not indexed” different?

Discovered means Google knows the URL exists but has not spent the crawl budget to fetch it yet. That usually points to crawl capacity or perceived value: too many low-value URLs competing for attention, or a domain Google is not motivated to crawl deeply.

How long does it stay that way?

There is no fixed window. Pages can sit there indefinitely. If a page has been stuck for more than a few weeks and nothing about it changed, waiting longer is not a strategy — the page needs to become materially better, get consolidated into a stronger page, or be removed.

Does requesting indexing in Search Console help?

It helps Google discover a URL sooner. It does not override a quality decision. If you have requested indexing on the same URL more than once and nothing changed, more requests will not change the outcome.

Why does Bing index my pages when Google will not?

Because the engines apply different thresholds. If Bing and DuckDuckGo both show your page on a site: search and Google does not, robots.txt, hosting, and rendering are almost certainly fine. That narrows the problem to how Google specifically judges your content.

Does AI-written content cause non-indexation?

AI assistance is not the trigger by itself. The trigger is content that adds nothing distinguishable — the same structure, phrasing, and claims already sitting in the index thousands of times over. Templated city pages built from one prompt are the clearest example.

Should I delete pages that will not index?

Consolidate first, delete second. Merge overlapping thin pages into one page that genuinely deserves to rank, redirect the old URLs to it, and remove or noindex parameter URLs and dead tag archives. Every crawl should land on something worth indexing.

Crawled — Currently Not Indexed: Google's New Indexing Threshold

By Susan Dutcher · 10 min read · Updated August 2026

You publish a page, request indexing, and nothing happens for weeks. That is rarely a bug in your setup. Google is now using indexation itself as a quality gate on your whole domain — here is how to tell which problem you actually have.

Disclosure: this post contains affiliate links for Semrush. If you start a trial or buy through my links I may earn a commission at no extra cost to you. Semrush is the platform I use on client audits, and I hold two Semrush certifications.

The Pattern: Crawled, Currently Not Indexed — For Weeks

If you run a local service business in Metro Detroit or anywhere in Michigan, you have probably seen this: you publish a new page, request indexing, and nothing happens. The URL sits in “Crawled — currently not indexed” or “Discovered — currently not indexed” for weeks while your technical setup looks perfectly fine.

That is not a random glitch in Search Console. It is Google delivering a verdict on the quality of your domain — and it now delivers that verdict at the indexing layer, before rankings are ever calculated.

Google has said plainly that when it has strong concerns about a site’s overall quality, it will deliberately reduce how much of that site it crawls and indexes. That is how you end up with a growing stack of URLs stuck in a non-indexed status indefinitely.

What This Means for Michigan Service Businesses

For a law firm in Troy, a medspa in Birmingham, or a contractor serving Ann Arbor and Plymouth, the practical consequences look like this:

If Google does not trust the domain, new local content may never enter the index at all.
Pages can report as “Indexed” in Search Console and still be invisible in live results for your core service plus city keywords.
A site can lose Google visibility while Bing and DuckDuckGo keep indexing it normally.
Your indexation rate is now a running scorecard on content quality — not just on technical SEO.

Indexation Used to Be a Formality. It Is Not Anymore.

For years the local SEO playbook was: submit a sitemap, request indexing, run a technical audit, wait for rankings to follow. That sequence assumes indexation happens by default and only rankings have to be earned.

In 2026 that assumption is the problem. “Crawled — currently not indexed” is rarely a queue you can push harder on. It is a signal to interpret, and it usually reflects site-wide content concerns rather than a short-term crawl delay.

Google is using indexation itself as a quality gate. Fall below the threshold and your new pages do not rank badly — they never enter the index to rank at all.

First: Figure Out Which Problem You Actually Have

Before changing anything, spend twenty minutes separating a technical issue from a quality verdict. These four checks do that faster than any full audit.

1. Read the exact status, not the summary

In Search Console, open the URL Inspection tool on a stuck page. “Crawled — currently not indexed” and “Discovered — currently not indexed” are different problems. The first is a judgment on the page. The second is a judgment on how much crawl attention your domain earns.

2. Cross-check the other engines

Run a site: search for the same URL in Bing and DuckDuckGo. If they have it and Google does not, stop auditing robots.txt, hosting, and rendering. You are looking at a Google-specific quality assessment, and no technical fix will resolve it.

3. Verify “Indexed” actually means visible

A page can report as indexed and still return nothing for your service plus city terms — or even for a quoted sentence from its own copy. Search a distinctive sentence in quotes. If the page does not come back, treat it as functionally unindexed regardless of what the report says.

4. Count what Google is excluding

Look at the ratio of excluded to indexed URLs in the Pages report. When excluded dwarfs indexed, the issue is usually volume: filter combinations, parameter URLs, duplicate tag archives, and pages published “just in case” are absorbing crawl attention that your real service pages need.

Three outcomes come out of this: a genuine technical fault, a domain-level quality problem, or crawl budget being spent on pages that were never going to earn their place. Each needs a different response, and guessing wrong costs months.

Three Things Driving Mass Non-Indexation

1. The Search Console trust gap

Practitioners keep reporting a mismatch between what Search Console shows and what live results show: pages marked indexed that never surface for branded or unbranded queries, impression counts that shift after the fact, and domains vanishing from Google while remaining fully indexed elsewhere.

If Search Console is your only diagnostic surface, you can miss a serious indexation problem until the phone has already stopped ringing.

2. Template footprints from scaled AI content

Google has been explicit that AI-generated content lacking unique or valuable insight can be refused indexing outright. In the audits I run, the pattern is consistent: a business ships dozens or hundreds of near-identical location pages — “best [service] in [city]” across Metro Detroit and the Midwest — each built from the same prompt, with thin local proof. Google reads the footprint at scale and filters large sections of the site at the indexing layer.

The question is not whether AI content is allowed. It is whether your content is distinguishable from every other site running the same workflow.

3. Crawl budget quietly draining

The third driver hides in site architecture: faceted navigation and filter combinations, duplicate location tags, parameter URLs, and thin pages kept around just in case. On larger sites these multiply into thousands of low-value URLs competing for the same crawl attention.

What shows up in reports is a huge excluded count against a small indexed count, a flat indexing pipeline that stays flat for months, and no obvious errors anywhere. The issue is not that Google cannot crawl the site. It is that Google no longer sees enough unique value to keep crawling it deeply.

Rebuilding Around Quality: A Different Order of Operations

Step 1: Quality-check before you publish, not after

Before shipping a service page or a city page, run it through three questions:

If I deleted the city name, would this page still be specific — or could it describe any competitor in any market?
Does it contain real evidence: local case studies, before-and-after numbers, neighborhood examples, photos, process detail?
Would someone in Troy, Birmingham, or Ann Arbor recognize their own reality in it?

Structurally: a title and H1 that name the service and the geography, short paragraphs carrying one idea each, and local angles generic content cannot fake — zoning, regulations, seasonal patterns, landmarks. If the page reads like thousands of documents already in the index, it is not ready.

Step 2: Prune the site and clean up your local entity

Non-indexed pages are not bugs to force through. They are a signal that your content footprint needs a reset.

Consolidate. Merge overlapping thin pages into stronger service hubs — several “roof repair in [suburb]” posts become one substantial Metro Detroit roofing page with genuine localized sections.
Prune. Remove or noindex parameter URLs, duplicate tag archives, and old posts that never earned an impression.
Align the entity. Keep name, address, phone, and service areas identical across your site, Google Business Profile, and the major directories.
Mark it up. Use LocalBusiness, Service, and FAQ schema so engines can state who you are, what you do, and where you work in Michigan.

The goal is simple: every crawl should land on something that obviously deserves to be indexed.

Step 3: Audit across engines and AI platforms

Your buyers are not only using ten blue links. Discovery now runs through Google and Bing results, Google AI Overviews and AI Mode, and answer engines like ChatGPT, Perplexity, and Gemini that cite sources inside generated answers. A cross-engine audit is what separates a true technical fault from a Google-specific quality problem — and from an AI visibility gap where competitors are cited and you are not.

The Tooling I Use for This

When indexation becomes a quality gate, you need two views at once: whether the site is technically crawlable, and whether the content clears the bar. I run both in Semrush.

Site Audit surfaces the thin content, canonical conflicts, and crawl-budget waste behind non-indexation. Position Tracking catches visibility drops tied to indexing changes, often before Search Console data catches up. AI Visibility reports show whether ChatGPT, Perplexity, and Gemini are citing you at all — the layer Search Console cannot see. Semrush One bundles the SEO and AI Visibility toolkits together, which is what makes the cross-engine comparison practical.

Because templated content is what triggers indexing refusals, the Content Toolkit is worth adding if you publish regularly. SEO Writing Assistant scores drafts for originality and readability before they ship, and Topic Finder keeps you from publishing duplicative pages just to hit a quota.

Try Semrush One (affiliate link)Try the Semrush Content Toolkit (affiliate link)

From “Index Faster” to “Earn Indexation”

The useful question is no longer how to get pages indexed faster. It is how to build pages that earn a place in the index at all.

Three reframes worth carrying into your next content decision. “Crawled — currently not indexed” is a verdict, not an error message, and it is fixed with strategy and pruning rather than more sitemap submissions. Template footprints are detectable at scale, so your content has to reflect experience you actually have. And if Bing indexes what Google will not, the problem is Google’s read on your quality — which is exactly the diagnosis most local sites never make.

Frequently Asked Questions

What does “Crawled — currently not indexed” actually mean?: Google fetched the page, read it, and decided not to add it to the index. It is a quality decision, not a crawl error. When it applies to a handful of thin pages it is normal housekeeping; when it applies to most of your new pages, Google is telling you something about how it rates the whole domain.
How is “Discovered — currently not indexed” different?: Discovered means Google knows the URL exists but has not spent the crawl budget to fetch it yet. That usually points to crawl capacity or perceived value: too many low-value URLs competing for attention, or a domain Google is not motivated to crawl deeply.
How long does it stay that way?: There is no fixed window. Pages can sit there indefinitely. If a page has been stuck for more than a few weeks and nothing about it changed, waiting longer is not a strategy — the page needs to become materially better, get consolidated into a stronger page, or be removed.
Does requesting indexing in Search Console help?: It helps Google discover a URL sooner. It does not override a quality decision. If you have requested indexing on the same URL more than once and nothing changed, more requests will not change the outcome.
Why does Bing index my pages when Google will not?: Because the engines apply different thresholds. If Bing and DuckDuckGo both show your page on a site: search and Google does not, robots.txt, hosting, and rendering are almost certainly fine. That narrows the problem to how Google specifically judges your content.
Does AI-written content cause non-indexation?: AI assistance is not the trigger by itself. The trigger is content that adds nothing distinguishable — the same structure, phrasing, and claims already sitting in the index thousands of times over. Templated city pages built from one prompt are the clearest example.
Should I delete pages that will not index?: Consolidate first, delete second. Merge overlapping thin pages into one page that genuinely deserves to rank, redirect the old URLs to it, and remove or noindex parameter URLs and dead tag archives. Every crawl should land on something worth indexing.