Fix Crawled but Not Indexed in Search Console - Mergeflo

Fix Crawled but Not Indexed in Search Console - Mergeflo

Short Answer

Short answer: In Search Console, crawled but not indexed means Google fetched your URL but did not add it to the index due to duplicate or low-value content, conflicting canonicals, noindex directives, unstable HTTP status, rendering gaps, or weak internal links. Fix those signals, confirm a clean indexable 200, then re-request indexing.

Why It Happens and How to Prove It

Most crawled but not indexed cases come from signal conflicts or thin duplication. Start with URL Inspection in Google Search Console: compare User-declared vs Google-selected canonical, confirm Indexing allowed, and review the HTML under View crawled page to ensure your primary copy actually rendered.

Use Screaming Frog or Sitebulb to surface noindex tags, soft 404 patterns, unstable 200/3xx/4xx flips, and orphaned URLs. Align rel=canonical, internal links, sitemaps, and redirects to the same canonical URL. If content is JavaScript-driven, ensure key copy (H1, intro, product terms) exists in the HTML Google renders.

“Crawled - currently not indexed means the page was crawled but not indexed; it might be indexed in the future.” Source: Page Indexing Report

Hero diagram showing multiple duplicate pages and signals funneling into one highlighted canonical page with indexable 200 status.
URL Inspection signals and canonical alignment diagram

• Page Indexing Report: https://support.google.com/webmasters/answer/7440203
• JavaScript SEO fundamentals: https://developers.google.com/search/docs/crawling-indexing/javascript

When It Is Normal: New Sites and Quality Gates

Some crawled but not indexed URLs on a new domain are common and do not always point to a fault. A new site has little trust history, so Google tests pages and holds back URLs until they show unique value. When several URLs say the same thing, Google tends to index the strongest one and hold back the rest.

Read the two statuses separately. Crawled - currently not indexed means Google fetched the page and paused inclusion, so look at quality, duplication and canonical signals. Discovered - currently not indexed means Google has not fetched it yet, so look at discovery: internal links and sitemap placement.

Diagnostics to Fixes: a Quick Map

Map the exact Search Console symptom to one small, shippable fix and retest on a short cycle. Use the table to decide your next move, then verify via URL Inspection and the Page Indexing report before scaling the fix across templates.

Symptom In GSC What To Check Fastest Fix
Crawled - currently not indexed + Duplicate, Google chose different canonical rel=canonical, internal links, sitemaps, hreflang targets Set a single canonical, update internal links to the canonical, 301 variants
Crawled - currently not indexed + Discovered but not indexed Orphaned URL, low internal PageRank, sitemap coverage Add contextual internal links from indexed pages; include only canonicals in sitemap
Crawled - currently not indexed + Soft 404 Thin template, wrong status, missing primary copy Return 200 with substantive content or 410/404 if non-canonical; remove thin variants
Indexed, though blocked by robots (or not indexing allowed) meta robots noindex, X-Robots-Tag, robots.txt Remove noindex/X-Robots on canonicals; unblock critical resources
Page fetch/render issues Blocked JS/CSS, client-only content, timeouts Allow JS/CSS, server-render primary content, stabilize TTFB
International alternates suppressed hreflang points to non-canonical or mismatched Make hreflang reciprocal between canonicals; avoid pointing to noindex
Flowchart branching from a URL Inspection result into specific diagnostic paths with icons for canonical, internal links, content, robots, rendering, and hreflang.
Decision flow: choose diagnostic based on URL Inspection output

Operational tradeoff: consolidating overlapping URLs boosts indexing and ranking signals but sacrifices some long-tail coverage. Keep the canonical that already has impressions in GSC, 301 the duplicates, and migrate internal links. Indexing consistency matters more than sheer URL count.

Start with Coverage. For Crawled currently not indexed, pull a sample of URLs, check server logs for Googlebot visit and 200 status, then inspect main content length; treat pages with very little unique content as thin in triage. Add internal links from relevant hubs and resubmit sitemap. For Duplicate without user-selected canonical, verify only one rel=canonical, no conflicting canonicals in HTTP headers, and no parameterized variants in sitemaps. Keep redirect chains to two hops max, fix soft 404s to return 200 with content or 404 with a helpful template, and keep robots.txt from blocking CSS or JS.

From Fixes to a System You Can Run

Indexing stabilizes when signals stay consistent at publish speed across templates, sitemaps, and internal links. Ship segmented sitemaps with only 200-status, canonical, indexable URLs and accurate lastmod. Exclude faceted parameters. Reuse strong templates but add unique copy above the fold, entity-rich FAQs, and contextual internal links per page. Add Article/Product schema as appropriate.

Mergeflo supports the content side of this workflow. It finds search gaps and buyer questions, drafts briefs and articles in your brand voice for review, and publishes approved articles to Webflow. Canonicals, sitemaps and rendering stay in your own stack, so keep them on your checklist. If you need a deeper playbook on page-level indexing, read the sibling post: Why Is My Google Search Console Page Not Indexed.

Semi-isometric illustration of a content-to-index pipeline with checkpoints for sitemaps, canonicals, internal links, rendering, and an index confirmation.
blog illustration

Stop publishing pages that stall at crawled but not indexed. Mergeflo tracks Google positions, flags pages losing impressions so you can see which pages need work, and writes a refresh brief when you press Refresh.

Start free

Operationalize with a weekly loop. Export your canonical URL list from the CMS, the live XML sitemaps, and the Index coverage via the Search Console API. Diff the three to surface gaps by template. Parse seven days of access logs, filter Googlebot by user agent and reverse DNS, and report percent 2xx, median TTFB, and average HTML bytes by template. Set targets for your own site, for example a high share of 2xx responses and a low TTFB (web.dev rates 0.8 seconds or less as good). Queue fixes by owner: dev for canonicals and headers, content for thin pages, ops for links and sitemaps. Regenerate sitemaps when the URL list changes.

Frequently Asked Questions

Should I Use Request Indexing After Every Fix?

Use Request Indexing only after the URL serves a clean, indexable 200 with aligned canonicals and internal links. It can speed recrawl for one-off pages, but it will not override weak content or conflicting signals. For batches, resubmit sitemaps and add internal links; avoid spamming the tool.

How Many Internal Links Are Enough to Push a URL Into the Index?

Add contextual links from already-indexed, relevant pages. Prioritize in-body anchors near matching terms over footer/sidebar links. Confirm source pages are indexed and recrawled in GSC, then wait a few weeks before reassessing, since Google says crawling can take anywhere from a few days to a few weeks (Google Search Central). Ahrefs’ Internal Link Opportunities report helps you find anchors at scale.

When Does Programmatic Content Fail to Index?

Programmatic pages stall when templates are near-duplicate and lack unique entity coverage or user value. Add unique intros with problem framing, page-specific data points, and tailored FAQs. At scale, watch GSC for soft 404 spikes and prune or 410 pages that never earn impressions after a fair test window.

How Do I Monitor This at Scale Without Drowning in Errors?

Segment sitemaps by section, crawl weekly with Screaming Frog, and track GSC Page Indexing by folder. Set alerts for canonical mismatches and status flapping (200↔302↔404). Maintain a weekly checklist: ship fixes, resubmit sitemaps, re-run URL Inspection on a sample of URLs, and document outcomes in a spreadsheet for trend visibility.

Does Publishing More Pages Help a New Site Index Faster?

Volume without quality signals slows indexing. Publish more only when each template can ship unique sections, entity-rich FAQs, and links from indexed hubs. Stabilize a small set of templates, confirm their pages get indexed, and then scale.

How Do I Tell if This Is a Quality Issue or a Crawl Budget Issue?

If Google fetched the page and paused, the cause is usually quality or duplication. If the URL stays at Discovered - currently not indexed, raise its priority with internal links and sitemap placement. Crawl budget limits are rare on small sites unless robots rules, noindex tags or slow responses get in the way.