Fastest fix: a submitted sitemap only tells Google your URLs exist — it never guarantees indexing. Run URL Inspection on one stuck page in Search Console. If it says Crawled - currently not indexed, it’s a content-quality problem (fix the page). If it says Discovered - currently not indexed, Google hasn’t crawled it yet (a crawl-budget / site-authority problem, often just time). Those two statuses point to completely different fixes, so read them first.
This is the single most common “my new site won’t show up” situation, and it almost always reduces to one of the six causes below.
Step 0 — Confirm the sitemap actually parsed
Open Search Console → Indexing → Sitemaps and click your sitemap row. You want:
- Status:
Success - Discovered pages: roughly your real URL count (not 0, not wildly inflated)
- Last read: a recent date
If the status is Couldn't fetch, Has errors, or it discovered 0 pages, the sitemap file itself is broken — wrong URL, blocked by robots.txt, returning a non-200, or malformed XML. Fix that first; the rest of this article assumes the sitemap reads cleanly. (Note: the old google.com/ping?sitemap=... ping URL was deprecated in 2023 and now returns 404 — submitting in Search Console or listing the sitemap in robots.txt is the only supported path as of June 2026.)
Which bucket are you in?
Run URL Inspection (top search bar in Search Console) on one representative stuck page, then read the status:
| URL Inspection says | What it means | Most likely cause below |
|---|---|---|
Crawled - currently not indexed | Googlebot fetched the page and chose not to index it | #1 content quality (almost always) |
Discovered - currently not indexed | Google knows the URL but hasn’t crawled it yet | #2 new-domain lag, #3 weak internal links, #5 depth/authority, #6 crawl budget |
Excluded by 'noindex' tag / Duplicate, Google chose a different canonical | A directive on the page is blocking it | #4 noindex / canonical |
URL is unknown to Google | Google never discovered it at all | sitemap not read, or page unlinked — recheck Step 0 and #3 |
You can see all of these aggregated under Indexing → Pages → “Why pages aren’t indexed”, which lists every non-indexed reason with a count and the affected URLs.
6 reasons your indexed count stays low
In rough order of frequency.
1. Thin or low-value content (the #1 cause of Crawled - currently not indexed)
When Googlebot has already crawled a page and still won’t index it, it’s a quality call, not a technical one. These get judged not worth indexing:
- Pages under ~300 words of real content
- Many pages off one template with only a few words different (thin/duplicate)
- Translated or lightly paraphrased third-party content
- Unedited bulk AI output
- “City × keyword” / “tool × use-case” template farms
How to confirm: URL Inspection shows Crawled - currently not indexed. This is the tell — Google saw it and passed.
Fix: make the page genuinely substantive (aim ~800–1500 words of original material), add a viewpoint, a worked example, a table, or first-hand data that isn’t on ten other pages. Then request indexing on that one page and check back in a week. Note that since the March 2026 Core Update, a wave of sites reported pages flipping back to Crawled - currently not indexed — if that’s you, this cause is where to focus.
2. New-domain evaluation lag
Brand-new domains get weeks to months of cautious evaluation before Google indexes freely. It isn’t a penalty — Google is deciding you’re not spam. Pages sit at Discovered - currently not indexed during this period.
Tell-tale signs: domain registered < 3 months ago, no prior backlinks, no prior traffic.
Fix:
- Wait it out (typically 4–12 weeks)
- Publish consistently (2–3 articles/week signals a live site)
- Earn 1–2 real backlinks (a community share, a peer’s blog) — this is the single biggest accelerator
- Don’t spam-resubmit the sitemap; monthly is plenty
3. Sparse internal linking — the crawler has no path
The sitemap tells Google a URL exists, but crawl and indexing priority come from internal links. A page with zero inbound internal links reads as unimportant and gets deprioritized, often stuck at Discovered.
Tell-tale signs:
- The article is reachable only from the sitemap
- No “Related articles,” no prev/next
- Homepage and category pages never link to it
Fix:
- Link the homepage and category pages to recent articles
- End every article with 3–5 contextual internal links
- Surface important articles in navigation so they’re 1–2 clicks from the homepage
4. The page has noindex, or its canonical points elsewhere
The URL is in the sitemap, but the page’s own <head> countermands it. Google honors these directives and won’t index:
<meta name="robots" content="noindex">Or a canonical pointing at a different URL (so Google indexes that one instead):
<link rel="canonical" href="https://otherdomain.com/page" />How to confirm: in URL Inspection, look for Excluded by 'noindex' tag or Alternate page with proper canonical tag / Duplicate, Google chose a different canonical. Or right-click the live page → View Source → search for noindex and canonical. Watch for these being injected by a CMS/theme/staging flag you forgot.
Fix:
- Remove
noindex(or setindex, follow) - Make the canonical self-referential (point to the page’s own URL)
- After fixing, use URL Inspection → Test Live URL to confirm the directive is gone before requesting indexing
5. Site too deep, or homepage authority too low
If an article is 5+ clicks from the homepage, Google may never prioritize crawling it. And if the homepage itself has no traffic and no backlinks, the whole site’s authority is low, so Google indexes conservatively across the board.
Fix:
- Surface important articles directly from the homepage
- Keep click depth to
<= 3levels - Earn external links: a relevant Reddit/forum post, a community share, a friendly cross-link from a related site
6. Crawl budget burned on junk URLs
If your site auto-generates many tag, search, filter, or pagination URLs, Googlebot can spend its limited crawl budget on those instead of real articles — leaving real content at Discovered - currently not indexed.
Fix:
- Add
noindexto tag / search / filter pages - Disallow the junk URL patterns in
robots.txt - Keep them out of the sitemap entirely (the sitemap should list only canonical, indexable URLs)
Shortest path to fix (ROI order)
- URL Inspect 3 stuck pages. If
Crawled - currently not indexed→ expand each to ~1500 words of original content; recheck in a week. - Add 3–5 internal links into every important article and link them from the homepage.
- Show latest articles on the homepage so the crawler fans out from a high-priority page.
noindexor remove thin tag/filter pages, and drop them from the sitemap.- Earn one real backlink — this moves the needle more than any on-site tweak for a new domain.
How to confirm it’s fixed
- Re-run URL Inspection on the page → Test Live URL → it should report indexable with no blocking directive.
- Click Request Indexing for that single page (quota is roughly 10–12 URLs/day per property on a rolling 24-hour window as of June 2026 — use it on priority pages, not in bulk).
- After a few days to a week, the status flips to
URL is on Google, and Indexing → Pages shows the indexed count rising. Don’t expect it to be instant; even after a fix, recrawl-and-index can take days.
When it isn’t your fault
- New domain (
< 3 months) still in evaluation - A Google Core Update in progress — pages legitimately move in and out of the index around these (the March 2026 update was a notable example)
- A YMYL niche (finance / health / law) where Google’s quality bar is higher
- Normal indexing lag — discovery to indexing routinely takes days, sometimes weeks, even on healthy sites
Common misjudgments
- “Sitemap status: Success, so I’m done.” That only means the XML file parses — it says nothing about whether pages get indexed.
- “
Discovered - currently not indexedis a bug.” It’s a queue/priority signal, not an error. - “Resubmitting the sitemap more often speeds indexing.” It doesn’t; monthly is enough. Internal links and backlinks do the actual lifting.
- “IndexNow / Bing submission will help Google.” It won’t — Google still does not participate in IndexNow as of June 2026. It speeds up Bing, Yandex, and Naver only.
Prevention checklist
- Plan internal linking from day one — don’t bolt it on after indexing stalls
- Feature new articles on the homepage for their first 1–2 weeks
- Launch with 3–5 substantive articles, not 50 thin ones
- Watch the Pages report and keep an eye on the
Crawled - currently not indexedcount - Keep the sitemap clean: canonical, indexable URLs only, with accurate
lastmoddates (Google leans onlastmodnow that ping is gone)
FAQ
Q: How fast should indexing start after I submit a sitemap? A: Established domains: 2–7 days. New domains: 2–12 weeks. Zero indexing after 3 months on a new domain is a real problem worth investigating.
Q: My sitemap lists 100 URLs but only 20 are indexed. Is that normal? A: Yes. Google never indexes 100% of a site. Strong sites land around 60–80%; new sites often sit at 10–30% early on.
Q: Should I ping Google after updating the sitemap?
A: No — the google.com/ping?sitemap=... endpoint was deprecated in 2023 and returns 404. Just keep the sitemap referenced in robots.txt and submitted in Search Console; Google rechecks it on its own schedule.
Q: Is “Request Indexing” in URL Inspection worth using? A: Yes for a handful of high-priority pages. There’s a daily quota (~10–12 URLs/property as of June 2026), and it nudges crawl priority — it doesn’t override a quality problem.
Q: One big sitemap, or split by topic? A: Under ~1,000 URLs, one sitemap is fine. Over 50,000 URLs (or 50 MB), you must split and use a sitemap index. Splitting by topic helps your management and lets you see indexed-rate per section in Search Console — it doesn’t speed indexing.
Q: Will adding an RSS/Atom feed help? A: Marginally. Some crawlers consume feeds for discovery, but for Google the real levers are internal links, content quality, and backlinks.
Related articles
- Why Your New Website Is Not Showing Up on Google
- How to Fix Crawled Currently Not Indexed
- How to Fix Firebase Hosting Route 404
- noindex vs robots.txt: When to Use Which
Tags: #SEO #Google #Search Console #Sitemap #Indexing #Debug