Why Isn’t My Page Indexed? A Diagnostic Walkthrough

You published it three weeks ago. It's good. And it isn't in Google.

The temptation at this point is to start changing things — resubmit it, add some links, rewrite the intro, submit the sitemap again. Most of that does nothing, because you haven't yet established which problem you have.

There are about seven reasons a page isn't indexed. They need completely different fixes, and one of them isn't technical at all. Here they are in the order that finds yours fastest.

The short version

Start with URL Inspection in Search Console. Paste the URL and read what it says — the status tells you which branch to follow.

Then work down:

1. A noindex tag — the most common and the most embarrassing
2. A robots.txt block — and the trap where blocking prevents removal
3. A canonical pointing elsewhere — you told Google to index a different page
4. No internal links — Google never found it
5. "Discovered – currently not indexed" — found, not prioritised
6. "Crawled – currently not indexed" — found, read, judged not worth storing
7. It's simply too new — genuinely just wait

Step 0 — Confirm it's actually not indexed

Two checks, thirty seconds.

Search site:yourdomain.com/your-page-url in Google. Nothing returned means not indexed.

Then URL Inspection in Search Console, which tells you why rather than just whether.

Worth ruling out the boring explanation first: a page can be indexed and simply ranking so poorly that you never see it. If site: returns the page, it's indexed and you have a ranking problem, not an indexing one. Different article.

Step 1 — Check for a noindex tag

The most common cause, and it usually isn't deliberate.

View source and search for noindex. You're looking for:

<meta name="robots" content="noindex">

Or an X-Robots-Tag: noindex HTTP header, which is invisible in the source and catches people out — check it in your browser's network tab or with curl -I.

Where these come from:

• WordPress's Settings → Reading → Discourage search engines checkbox, which is genuinely the single most common cause of a site not being indexed. It gets ticked during development and survives launch.
• SEO plugin settings applied per-post-type or per-page
• Staging environment configuration that made it to production
• Page builder or theme options

Fix it, then request indexing in URL Inspection.

Step 2 — Check robots.txt

Visit yourdomain.com/robots.txt and read it properly.

You're looking for anything blocking your URL's path. The catastrophic version is:

User-agent: *
Disallow: /

Here's the trap that traps everyone: Disallow blocks crawling, not indexing. Those aren't the same thing, and confusing them causes two opposite failures.

A blocked page can still appear in results — Google can't see the content, so it shows a bare listing with no description. And if you block a page that has a noindex tag, Google can never crawl it to see the noindex, so it stays indexed indefinitely.

To remove a page: use noindex and let Google crawl it. Blocking is the opposite of what you want. The five robots.txt errors.

Step 3 — Check the canonical

View source and look for:

<link rel="canonical" href="...">

Does it point at this page, or somewhere else?

If it points elsewhere, you've explicitly told Google "don't index this, index that instead" — and Google obliged. This happens through plugin misconfiguration, duplicated templates, or a site-wide canonical someone set to the homepage.

URL Inspection also shows you Google's chosen canonical, which may differ from your declared one. When Google picks a different canonical than you declared, it's telling you your signals contradict each other — usually your internal links and sitemap point somewhere your canonical doesn't.

Step 4 — Check it's actually linked

Google finds pages by following links. A page with no internal links pointing at it is an orphan, and orphans get discovered late or never.

Being in your sitemap helps but isn't sufficient — a sitemap is a suggestion, and a URL with zero internal links looks unimportant regardless of what your sitemap claims.

The fix: add contextual links from two or three relevant existing pages, ideally established ones with their own traffic. Finding orphans.

Step 5 — "Discovered – currently not indexed"

Google knows the URL exists and hasn't got round to crawling it.

This means one of three things:

Crawl priority. Google doesn't think the page is important enough to spend a crawl on yet. Internal links from established pages are the strongest available signal here.

Server capacity. If your site responds slowly, Google throttles its crawl rate to avoid overloading you. Check your response times.

Site-wide quality signals. On sites with lots of thin or duplicate content, Google gets conservative about crawling new URLs generally.

The fix is usually internal links plus patience. Requesting indexing helps a little; it's a nudge rather than a command.

Step 6 — "Crawled – currently not indexed"

The status that generates the most confusion, so let me be blunt about what it means.

Google reached your page, read it, and decided not to store it.

That's not a technical failure. It's an editorial judgement, and it usually means one of:

Thin or low-value content. Not enough substance to justify a slot in the index.

Duplicate or near-duplicate. Substantially similar to something already indexed, from you or someone else.

No demonstrated purpose. Tag archives, thin category pages, paginated URLs, auto-generated pages.

Site-level quality. If a lot of your site is thin, Google applies more scepticism to all of it.

The fix is content, not technical. Make the page substantially better — add original material, real depth, something it uniquely offers — then request indexing again. Resubmitting an unchanged page is a way to feel busy.

The uncomfortable version some people need to hear: sometimes the right answer is that the page shouldn't exist. Thin tag archives and near-duplicate posts are better consolidated or removed than fixed.

Step 7 — It might just be new

New pages on established sites typically index within a few days. New pages on new sites can take weeks.

If a page is under a week old, everything is fine and you can stop reading.

Requesting indexing in URL Inspection is worth doing once. Doing it repeatedly on the same URL achieves nothing — it doesn't queue-jump, and there's no evidence that spamming it helps.

Can you force Google to index a page?

No. And it's worth understanding why, because a lot of money gets spent on services claiming otherwise.

Indexing is a decision Google makes about whether a page warrants a slot. You can request, signal, and make the case — with internal links, a sitemap entry, external links, and content worth storing. You can't compel.

What genuinely helps, in rough order:

1. Internal links from established pages
2. Content substantial enough to warrant indexing
3. A sitemap entry
4. Requesting indexing, once
5. An external link, if you have a legitimate way to get one

What doesn't help: repeated indexing requests, indexing services, or pinging tools.

Frequently asked questions

What does "crawled – currently not indexed" mean?
Google reached your page, read it, and chose not to store it in the index. That's an editorial judgement rather than a technical fault — it usually indicates thin content, near-duplication of something already indexed, or a page with no clear purpose like a thin tag archive. The fix is improving the content substantially, not resubmitting the same page.

How long does indexing take?
New pages on established sites usually index within a few days. New pages on new sites can take several weeks, since Google has no history to justify prioritising the crawl. If a page is less than a week old and has internal links pointing at it, waiting is the correct action. If it's been three weeks with no status change, work through the diagnostic above.

Can I force Google to index a page?
No. Indexing is Google's decision about whether a page warrants a slot in the index. You can request indexing in URL Inspection — once, usefully — and improve your case with internal links from established pages, a sitemap entry, and content substantial enough to justify storage. Repeated requests and third-party indexing services don't change the outcome.

What to do next

Run URL Inspection on the page and read the exact status. That single string tells you which of the seven causes you're dealing with, and they need completely different responses.

If it says "crawled – currently not indexed," stop looking for a technical fix. Google read your page and wasn't convinced — which is a harder problem than a stray meta tag, but at least you now know which problem you have.

Free: The SEO audit checklist.

---

Related guides

• Technical SEO: what actually breaks rankings — the wider audit
• robots.txt mistakes — noindex versus disallow, properly explained
• Search Console: the 5 reports that matter — monitoring indexation at scale
• Internal linking and topic clusters — fixing orphan pages