Technical SEO
Crawled - Currently Not Indexed: Causes and Fixes That Work
Google visited the page, read it and decided not to keep it. That's frustrating, but it's also useful information: the status tells you exactly where to look.

"Crawled - currently not indexed" in Google Search Console means Google fetched the page but decided not to add it to the index, at least for now. The most common causes are thin or low-value content, near-duplicate pages, weak internal linking that signals low importance, and technical conflicts such as canonical or rendering problems. The fix is to make the page clearly worth indexing and clearly important within your site, then request indexing.
I check this status on every technical SEO audit. Sometimes it reveals a serious problem with key pages. Often it's just Google declining to index pages that shouldn't be indexed anyway. The skill is telling the two apart.
What the status means
Google's indexing process has stages: discover a URL, crawl it, process and render it, then decide whether to index it. Two statuses in the Pages report sound similar but sit at different stages:
| Status | What happened | Usual meaning |
|---|---|---|
| Discovered - currently not indexed | Google knows the URL but hasn't crawled it yet | Crawl budget, server load or low perceived priority |
| Crawled - currently not indexed | Google crawled the URL and chose not to index it | Quality, duplication, importance or technical issues |
"Crawled - currently not indexed" is a decision about the page. Google read it and, for now, didn't think it was worth storing and showing. "Currently" matters: the decision can change after the page or its context changes.
First, decide which URLs actually matter
Open the Pages report, click the status and export the examples. Then sort them into groups:
- Important pages: service pages, product pages, key articles. These need fixing.
- Pages that shouldn't be indexed anyway: tag and author archives, internal search results, parameter URLs, attachment pages, old spam URLs. These can stay excluded, and some should be noindexed or removed.
- Pages you're unsure about: thin category pages, old blog posts. These may be candidates for improving, merging or removing.
On a hacked site, this list can be full of spam URLs. Those should return 404 or 410, not be pushed into the index. My recovery process is in removing hacked spam pages from Google.
Cause 1: thin or low-value content
The most common reason. The page exists but adds little that isn't available elsewhere, on your site or on the web.
Signs:
- Very short pages with generic text.
- Product pages that only repeat the manufacturer's description.
- Location pages that swap the city name and keep everything else identical.
- Blog posts that summarize what dozens of other posts already say.
Fixes:
- Add something only you can say: first-hand experience, original data, specific examples, real photos, prices and processes.
- Answer the questions people actually ask, clearly and directly. The AEO guide explains the format.
- Merge thin pages into one stronger page and 301 redirect the others.
- Remove pages that can't be improved and have no traffic or links.
Cause 2: duplicate or near-duplicate content
If a page is very similar to another URL, Google may index one and skip the other.
Common sources:
- URL variations: with and without trailing slash, http and https, www and non-www, parameters.
- Faceted navigation producing many filter combinations of the same product list.
- Printer-friendly or AMP versions without proper canonicals.
- Similar products or services with nearly identical descriptions.
- Syndicated content published on several sites.
Fixes:
- One canonical version of every page, with redirects from the others.
- Canonical tags pointing to the preferred version.
- Unique descriptions for similar items, focusing on what's actually different.
- Parameter and filter URLs controlled with canonicals, noindex or crawl rules.
Cause 3: weak internal linking
Google uses internal links to judge how important a page is within your site. A page linked only from the sitemap, or from one obscure page, looks unimportant.
In a New York studio audit, 45 pages had only one internal link pointing to them (case study). Pages like that are prime candidates for this status.
Fixes:
- Link to important pages from your navigation, hub pages and related content.
- Add contextual links from relevant articles with descriptive anchor text.
- Keep important pages within three clicks of the homepage.
- Remove nofollow from internal links. One e-commerce store I audited had 141 internal links wrongly set to nofollow (case study).
Cause 4: technical conflicts
Sometimes the content is fine but technical signals confuse Google:
- Canonical pointing elsewhere: the page says another URL is the main version.
- Rendering problems: main content loads through JavaScript that fails or times out, so Google sees an empty or thin page.
- Soft 404s: the page looks like an error or empty result.
- Blocked resources: CSS or JavaScript blocked in robots.txt, so the page renders badly. In one audit, 252 internal resources were blocked this way.
- Very slow pages: extreme load times can affect how reliably content is processed. See the Core Web Vitals guide.
How to check: run URL Inspection, then Test live URL, and open View tested page to see the rendered HTML and screenshot. If the main content isn't in the rendered HTML, you've found the problem.
Cause 5: site-wide quality or trust signals
If a large share of a site is low quality, spammy or recently hacked, Google may be more selective about indexing new pages. A site recovering from a hack, or one that has published hundreds of thin pages quickly, can see more pages left out.
Fixes take longer: remove or improve low-quality sections, clean up hacked content and build genuine authority. Individual page fixes won't fully work until the overall picture improves.
Cause 6: it's new and Google hasn't decided yet
Brand-new pages sometimes sit in this status briefly before being indexed. If a page is new, strong, well linked and technically sound, give it a little time before overhauling it.
Step-by-step fix process
For each important page in this status:
- Inspect the URL and run a live test. Check indexability, canonical, rendering and page fetch.
- Compare it honestly with the pages that rank for its main query. What do they offer that it doesn't?
- Improve the content: unique information, clear answers, specifics, updated facts.
- Check for duplicates on your own site and consolidate if needed.
- Strengthen internal links from relevant, well-linked pages.
- Make sure it's in the sitemap with an accurate lastmod date.
- Request indexing in URL Inspection.
- Wait and re-check after a couple of weeks.
Requesting indexing without improving anything often gets the page indexed briefly, then dropped again. The improvement is the fix; the request just asks Google to look again.
When to leave pages out of the index
Not every page should be indexed. I'm comfortable leaving these excluded, or deliberately noindexing them:
- Internal search results and filter combinations.
- Tag, author and date archives with no unique content.
- Thank-you pages, login pages, cart and checkout.
- Thin attachment pages created automatically for images.
- Old spam URLs after a hack (return 410 instead).
A smaller index of strong pages is better than a large index of weak ones. It also helps Google spend its crawling on what matters.
Related statuses worth knowing
- Duplicate without user-selected canonical: Google found duplicates and chose a canonical itself. Add explicit canonicals.
- Duplicate, Google chose different canonical than user: your canonical tag disagrees with Google's choice. Check whether the pages are really distinct.
- Excluded by noindex tag: intentional or accidental noindex. Check templates and plugins.
- Blocked by robots.txt: Google can't crawl the URL. Fine for private areas, a problem for content.
- Soft 404: the page looks empty or like an error.
A triage example
Here's how a typical export looks when I sort it, using the kind of mix I see on small business sites:
| Group | Example URLs | Action |
|---|---|---|
| Important, thin | A service page with 150 words and no FAQs | Rewrite with specifics, add internal links, request indexing |
| Important, duplicate | Two pages targeting the same service with similar text | Merge into one, 301 the other |
| Archives | /tag/seo/, /author/admin/, /2023/05/ |
Noindex or remove from sitemap; leave excluded |
| Parameters | ?sort=price, ?color=blue |
Canonical to the main category; no action in Search Console |
| Old spam | Casino or pharma URLs from a past hack | Return 410; ignore in this report |
Usually only a handful of URLs fall in the first two groups, and those are where all the effort should go. On a site with dozens of excluded archive and parameter URLs, the report can look alarming while the important pages are fine.
Indexing and AI search
Pages that Google doesn't index can't be used in AI Overviews or AI Mode, which draw on Google's index. The same logic applies to other engines and their indexes. If a page you want cited by AI assistants is stuck in this status, fixing indexing comes before any answer-first rewriting or GEO work.
It's also worth checking Bing Webmaster Tools, which has its own indexing reports. A page can be indexed in one engine and not the other, and several AI assistants draw on Bing's index.
Quick checklist for each stuck page
- [ ] Live test passes: page fetched, indexable, canonical is itself
- [ ] Rendered HTML contains the main content
- [ ] Offers something the ranking pages don't
- [ ] No near-duplicate on the same site
- [ ] Linked from navigation, a hub page or several related pages
- [ ] Listed in the sitemap with an accurate lastmod
- [ ] Indexing requested after the improvement, with the date noted
Prevention: publishing pages that get indexed
The best way to deal with this status is to avoid it for pages that matter. Before publishing anything important, I check:
- Does it have a clear job? One topic, one intent, one primary question it answers better than anything else on the site.
- Is it linked on day one? New pages go live with links from the navigation, a hub page or at least two related pages, not just the sitemap.
- Is it substantial? Not long for its own sake, but complete: the main answer, the follow-up questions, examples and proof.
- Is it distinct? If it overlaps heavily with an existing page, improve the existing page instead.
- Is it technically clean? Self-referencing canonical, indexable, fast, with content in the HTML.
When I built the case study and service sections of my own site, each new page went live already linked from its hub, the navigation or footer, and related pages, and every one was listed in the sitemap the same day. That's the simplest way to tell Google a page is important from the start.
Publishing in volume is the other risk. Launching hundreds of thin pages at once, such as auto-generated location pages, is one of the most reliable ways to fill this report. Fewer, stronger pages get indexed faster.
How long fixes take
After improving pages and requesting indexing, many sites see changes within one to four weeks. Site-wide quality improvements take longer, often several months, because Google needs to recrawl and reassess many pages.
The short version
If an important page is crawled but not indexed, assume Google isn't convinced it's worth keeping. Make it clearly useful, clearly distinct and clearly important within your site, then ask Google to look again.
Frequently asked questions
Is 'Crawled - currently not indexed' a penalty?
No. It's not a manual action or penalty. It means Google crawled the page and decided not to index it for now, usually because of quality, duplication, importance or technical reasons. Improving the page and its internal links usually changes the decision.
Should I keep clicking Request Indexing?
Requesting indexing once after a real improvement is useful. Requesting repeatedly without changing the page rarely helps, and if the page is indexed it may be dropped again later. Fix the underlying reason first, then request indexing.
What is the difference between discovered and crawled but not indexed?
Discovered - currently not indexed means Google knows the URL but hasn't crawled it yet, often because of crawl capacity or low priority. Crawled - currently not indexed means Google has fetched the page and chosen not to index it. The first is about crawling, the second about the page itself.
Can low-quality pages hurt my whole site?
They can affect how Google sees the site overall. A site with many thin, duplicate or spammy pages may find Google more selective about indexing. Improving, merging or removing weak pages helps your strongest pages get crawled and indexed more reliably.
Why are my old spam URLs listed as crawled but not indexed?
That's normal after a hack cleanup. Google crawled them, saw they shouldn't be indexed or found them gone, and left them out. As long as they return 404 or 410 and aren't in your sitemap, they'll eventually drop out of the report.