By the DenverSEO.io team · 2026-10-10
Crawled, currently not indexed is a Search Console status meaning Google fetched the page but decided not to add it to the index for now. Google says it may or may not be indexed later and there is no need to resubmit it. The usual causes are duplicate or near-duplicate content, thin pages, weak internal linking and rendering problems. Fix the page and its signals, then let Google recrawl it.
Open the Page indexing report in Google Search Console and you will usually find a reason list under “Why pages aren't indexed.” Two entries cause more confusion than all the others: Crawled, currently not indexed and Discovered, currently not indexed. They sound similar. They point to different problems.
Google's help text for the first one is short: the page was crawled by Google but not indexed; it may or may not be indexed in the future; there is no need to resubmit the URL for crawling. That last clause matters. Google already has the page. It looked, and for now it decided the page did not earn a place in the index.
Crawled versus discovered
| Status | What happened | Usual problem |
|---|---|---|
| Discovered, currently not indexed | Google knows the URL exists but has not fetched it yet. | Crawl scheduling: server capacity, too many low-value URLs competing for attention, weak links to the page. |
| Crawled, currently not indexed | Google fetched the page and chose not to index it. | The page itself: duplication, thin or unhelpful content, conflicting signals, or content that did not render. |
If you remember one thing: discovered is mostly about getting crawled; crawled is mostly about being worth indexing.
First, decide whether it is a problem
Not every URL in this bucket deserves to be indexed. Before fixing anything, export the list and sort it into three piles:
- Pages that should never be indexed: tag archives, internal search results, filtered views, paginated duplicates, thank-you pages, feeds. These belong out of the index. Stop linking to them where you can, and use
noindexor canonical tags as appropriate. - Old or retired pages: if a page is gone, return a 404 or 410, or redirect it to a true equivalent.
- Pages you need indexed: service pages, location pages, product pages, guides. Only this pile needs the work below.
On many small sites the first two piles are most of the list, and the honest fix is to stop generating those URLs.
The engineering checks, in order
1. Inspect the URL and look at what Google rendered
Use the URL Inspection tool and run a live test. Check the rendered HTML and screenshot. If the main content is missing, replaced by a loading spinner, a consent wall or an error, Google evaluated an empty page. That is a rendering or blocking problem, not a content problem. Common culprits are content injected by JavaScript after a slow API call, blocked script or API files in robots.txt, and bot-detection services that challenge crawlers. Our JavaScript SEO page covers the fixes.
2. Check for duplicates and canonical conflicts
Look at the canonical Google selected versus the one you declared. If several URLs carry nearly the same content, such as location pages that differ only by city name, product variants on separate URLs, or HTTP and HTTPS or trailing-slash versions, Google may index one and leave the rest. Consolidate true duplicates, make canonicals consistent, and make sure internal links and the sitemap use the same canonical URL. Conflicting signals, like a canonical pointing one way and the sitemap listing another, make the choice harder.
3. Be honest about the content
Thin pages are the most common reason we see. A 150-word service page that repeats the homepage, a city page made from a template, or a product page with only a manufacturer description gives Google little reason to keep it. Ask whether the page answers a real question better than what is already indexed, including other pages on your own site. Add specifics only you can provide: process, pricing ranges, photos of real work, local details, FAQs from actual customers. Our guide to schema markup mistakes also matters here, because markup should describe content that is genuinely on the page.
4. Strengthen internal links
A page linked only from the XML sitemap tells Google you consider it unimportant. Link to it from relevant, frequently crawled pages with descriptive anchor text. Pages more than three clicks from the homepage often struggle. Our free internal link graph shows orphan and deep pages quickly.
5. Check speed and server health
Slow or error-prone servers affect crawling more than indexing, but they compound everything else. If your server logs show crawlers receiving timeouts or 5xx errors, fix that first.
What not to do
- Do not spam Request Indexing. Google's own text says resubmitting is unnecessary. A single request after a substantial improvement is reasonable; repeating it on an unchanged page achieves nothing.
- Do not mass-produce more of the same pages. If template pages are not being indexed, more template pages will not help.
- Do not panic over small numbers. Some fluctuation is normal. Pages move in and out of this status as Google re-evaluates sites.
- Do not use third-party “instant indexing” services for ordinary pages. Google's Indexing API is documented only for specific content types such as job postings and livestream events.
A typical pattern, worked through
Here is the shape we see most often on service-business sites. The site has a strong page for its main service, then twenty city pages built from one template: same three paragraphs, city name swapped, same stock photo. Search Console shows the main page indexed, two or three city pages indexed, and the rest crawled but not indexed.
The instinct is to blame Google or to add more city pages. The fix runs the other way. Keep city pages only for areas the business genuinely serves and can say something specific about: response times from the nearest crew, local permit quirks, projects completed there, the neighborhoods and housing types involved. Merge or retire the rest, redirect the retired URLs to the closest real page, and link the survivors from the main service page. The result is fewer pages, each with a reason to exist, and that is what tends to move out of this status.
How long until it changes?
After you improve a page, Google needs to recrawl and re-evaluate it. That can take days for frequently crawled sites and several weeks for small or rarely updated ones. Track it in the Page indexing report and with URL Inspection rather than daily site: searches, which are not a reliable measure of indexing.
When it is a site-wide signal
If a large share of your important pages sit in this status, the problem is usually broader than any single page: a site built from near-identical templates, a migration that left duplicate URL versions live, or a rendering setup that hides content from crawlers. That is when a full technical SEO audit pays for itself. We look at rendering, canonicals, internal linking and content duplication together, then give you a ranked list of fixes, most of which your developer or ours can ship in days.