Your site isn't getting indexed: the most common causes and how to check them in Search Console

"My site doesn't show up on Google" is probably the sentence we hear most often from people writing to us for the first time. The problem is almost never a ranking issue: it's that the site, or some of its pages, aren't even indexed yet — meaning Google hasn't added them to its index, so they can't appear in any search, at any position. These are two different problems and need to be diagnosed in a different order: check indexing first, and only then does it make sense to talk about ranking.

The first thing to do: verify, don't assume

Before hunting for causes, confirm the symptom with real data, not a mental "I can't find it on Google". In Search Console (free, connects to any site in a few minutes) the Coverage › Pages section shows exactly how many URLs are indexed and how many aren't, with a reason for each excluded one. For a single page, the URL Inspection tool (top of the page, paste the full address) tells you in real time whether that specific page is in Google's index or not, and if it isn't, explains why. This is the first step of any serious diagnosis, and it's free: skipping it to jump straight to guesswork is the most common way to waste time on a problem you can actually see in ten seconds.

The most common technical causes

In the order worth checking them, because the first three cover the large majority of the real cases we see:

• A robots.txt block. A Disallow: / line (often left over by mistake from a site still in development, or a misconfigured plugin) stops crawlers from reading the entire site or whole sections of it. You can check this in one second by opening yoursite.com/robots.txt in a browser.
• A forgotten noindex tag. This happens very often after a hosting move or a switch from a staging site to the live one: the <meta name="robots" content="noindex"> directive stays active even in production. Many WordPress themes and plugins have a "discourage search engines from indexing this site" option that must be switched off manually at launch — and that nobody ever double-checks afterwards.
• A site too young or pages too isolated. Google has to discover a page before it can index it, and it discovers pages by following links — from the sitemap, from other pages on the site, from external sites. An orphan page, with no internal link pointing to it, can stay invisible for months even without any technical block.
• Duplicate or too-thin content. Pages nearly identical to one another (product variants that differ only by colour, city pages with the same text copied and pasted) push Google to index only one of them and drop the rest as duplicates or low-quality.
• No XML sitemap, or one that was never submitted. It isn't mandatory for getting indexed, but it's the most direct way to tell Google "here are all the pages I have, go look at them". Without a sitemap submitted in Search Console, discovery depends only on links, and it's slower.
• A canonical tag pointing elsewhere. A rel="canonical" tag set by mistake to point at a different URL (this happens with some misconfigured SEO plugins or after a migration) explicitly tells Google "the original is this other page, ignore this one": the page stays out of the index even if it's perfectly valid.
• A server-side or firewall block. A WAF, a security plugin or a Cloudflare rule set up to block "suspicious" traffic sometimes ends up blocking Googlebot too, perhaps only on certain URLs or at certain times of day. In Search Console this shows up as intermittent server errors rather than an explicit block, and it's one of the hardest causes to spot because the site, viewed from a normal browser, works perfectly fine.

How to read the reasons Search Console gives you

In the Pages section, Google lists excluded pages with a specific label for each one. The most common ones to understand right away: "Blocked by robots.txt" and "Excluded by 'noindex' tag" are explicit blocks, intentional or not — they should be removed if unintended. "Discovered, currently not indexed" means Google knows about the page but hasn't yet decided to add it to the index, often for perceived quality reasons or crawl budget on very large sites. "Page with redirect" or "Duplicate, Google chose different canonical than user" usually aren't errors: they're expected behaviours that Search Console still flags in the list anyway. Telling apart "issue to fix" from "normal behaviour being reported" is where most time gets wasted, and it's also the point where an experienced technical read makes a real difference over just reading the label.

A quick way to get an automated first check on many of these points — free, no sign-up — is our free SEO analysis tool: it checks robots.txt, meta robots, sitemap and other technical signals within seconds and returns an action plan ranked by impact.

How long it realistically takes

After removing a block (robots.txt, noindex, a wrong canonical) and submitting or updating the sitemap, Google doesn't recheck the page instantly. For a site with already established authority, the new crawl can happen within a few days; for a new site or one with few inbound links, it can take several weeks. The "Request indexing" button inside Search Console's URL Inspection tool speeds up the crawl of that single page, but it doesn't guarantee a fixed timeframe, and it has a daily request limit: using it on dozens of URLs in the same day doesn't work better than using it on three or four genuinely priority pages.

When the problem isn't technical

If the page is technically clean — no blocks, correct sitemap, correct canonical — but stays "discovered, not indexed" for weeks, the most likely cause is perceived content quality: pages too similar to others already indexed, automatically generated and repetitive text, or a site overall too young to have earned trust yet. In these cases a technical fix isn't enough: the content itself needs a rethink, which sits more within an overall SEO strategy than in a checklist.

In short

Before talking about ranking, verify indexing with real data: Coverage and URL Inspection in Search Console. The most common technical causes are robots.txt, a forgotten noindex tag, a wrong canonical, orphan pages and duplicate content — all checkable within minutes. If the page stays out of the index for weeks after the fix, the problem is almost always content quality, not the technical side.

Want a free check on your site before chasing rankings? Try the free SEO analysis, or get in touch if the problem is still unclear after the checks.