What should you do when GSC shows “Crawled - currently not indexed”?

Conclusion

This status means Google fetched the page, but decided not to index it (yet). The fix is usually uniqueness + prioritization, not repeated indexing requests.

Practical order:

1. confirm you’re not signaling the wrong canonical (or duplicates)
2. reduce near-duplicate/template signals (especially above the fold)
3. add a uniquely useful section per page (examples, decisions, pitfalls)
4. build prioritization with hubs + related links
5. request indexing only for hubs + top pages, then wait 7–14 days

Explanation

Google already discovered and crawled the URL. If it still isn’t indexed, it’s usually one of:

• canonical/duplicate conflicts
• page looks like a near-duplicate (template pages)
• weak intent signals (title/intro/headings)
• low site-level prioritization (no hubs/structure)

The cure is structural, not “click Request indexing again”.

Practical Guide

Step 1: confirm you’re not asking Google to index the wrong URL

Check:

• user-declared canonical vs Google-selected canonical
• trailing slash / casing / parameter variants
• cross-language duplication

Fix canonical conflicts first.

Step 2: diagnose the 3 most common causes

Cause A: near-duplicate/template feel

• identical headings and intro text
• same layout with only small substitutions
• templated titles/descriptions

Fix:

• rewrite above-the-fold to match unique intent
• add one unique example or decision point

Cause B: thin for the query intent

Fix:

• add 1–2 sections users need:
  • pitfalls
  • edge cases
  • checklists
  • primary sources

Cause C: low prioritization

Fix:

• create hubs per category
• add related links per page (3)
• ensure key pages are within ~3 clicks

Step 3: strengthen intent signals on-page

• title: clear outcome, not just a label
• description: who it’s for + what it solves
• headings: show depth

Step 4: reduce index bloat

Indexing often improves when you stop asking Google to index everything.

• consolidate near-duplicates
• avoid pages that differ only by an ID

Step 5: when to use Request indexing

Use it for:

• homepage
• hubs
• top pages (5–10)

Then wait 7–14 days and reassess.

Pitfalls

• repeatedly requesting indexing instead of fixing signals
• leaving boilerplate dominating above the fold
• no hubs/related links (no site-level prioritization)
• canonical drift across URL variants

Checklist

• [ ] Canonical conflicts are resolved (user vs Google)
• [ ] URL variants are normalized (slash/casing/params)
• [ ] Cross-language duplication is handled (canonical/hreflang)
• [ ] Above-the-fold is unique per page (not boilerplate)
• [ ] Each page has at least one unique section (example/decision/pitfall)
• [ ] Titles/descriptions are not templated
• [ ] Category hubs exist and are linked prominently
• [ ] Related links exist per page (3)
• [ ] Thin/duplicate pages are consolidated
• [ ] Request indexing is used only for hubs + top pages
• [ ] Reassessment window is set (7–14 days)

FAQ

Q1. Why doesn’t “Request indexing” solve this?

Because Google already crawled the page. The decision is about indexing priority and perceived value/uniqueness.

Q2. What’s the fastest fix for template-heavy sites?

Hubs + related links + unique above-the-fold intent per page. Micro-tweaks rarely beat structural fixes.

Q3. How do I tell if it’s a canonical problem vs a quality problem?

Use URL Inspection. If Google-selected canonical differs, fix canonical/normalization first. If canonicals match, focus on uniqueness and prioritization.

Internal links

• Parent hub: Indexing: start here
• Related:
  • Discovered but not indexed checklist
  • Google Search Console setup (Next.js + Vercel)
  • Canonical + hreflang pitfalls (Next.js i18n)

Disclaimer

Indexing is probabilistic. You can improve signals, but you cannot force Google to index every URL.