Why your pages are not showing up in Google

A page that is not in the index cannot rank, no matter how good it is. It sounds obvious, and it is still the single most common thing we find on a first review — sites with months of content investment where a meaningful share of the pages were never eligible to appear at all.

It is worth ruling out before you spend anything on rewriting.

How to check in two minutes

Search for site:yourdomain.co.uk in Google. The result count is approximate and should not be taken literally, but if it returns twelve results and you have two hundred pages, you have found your problem.

For a real answer, use the URL Inspection tool in Google Search Console on a specific page. It tells you whether the page is indexed, when it was last crawled, and if it was excluded, why. The Pages report does the same job across the whole site and groups the reasons, which is where to start if you have more than a handful.

The causes, roughly in order of how often we see them

Blocked in robots.txt

Usually left over from a staging site. A Disallow: / that was correct before launch and never removed will keep an entire site out. Check yourdomain.co.uk/robots.txt and read it properly — this takes thirty seconds and has explained more than one site's total absence.

A noindex tag

Same origin, same story: a meta robots noindex applied during development, or applied by a plugin setting nobody remembers changing. Worth checking on the actual live page source rather than in the CMS, because they sometimes disagree.

Canonical tags pointing elsewhere

A canonical tag tells search engines the real version of a page is somewhere else. When these are set wrongly — often site-wide by a misconfigured plugin, all pointing at the homepage — every page politely asks not to be indexed in its own right.

The page is genuinely thin

Crawled, assessed, and judged not worth including. This is common with templated pages generated in bulk where only a variable changes. If that describes a chunk of your site, the fix is fewer and better pages rather than a technical change.

Nothing links to it

Orphan pages — reachable only if you know the URL, with no internal link anywhere. They get crawled late or not at all. Being in the sitemap helps but does not substitute for an actual link from a page that matters.

It is simply new

Sometimes there is no fault. New pages on a low-authority site can wait weeks. Requesting indexing in Search Console occasionally helps and is worth one attempt, not ten.

The one that catches people out

"Crawled — currently not indexed" in Search Console is not a technical error. It means the page was fetched, considered, and left out. There is no tag to fix and no setting to change.

It is a quality judgement, and the honest response is to make the page substantially better or to accept it will not rank. Requesting indexing repeatedly on a page in this state achieves nothing, which does not stop it being the most common reaction.

What to do about a large number of them

If hundreds of pages are excluded, resist fixing them one at a time. Group them by the reason Search Console gives, find the systemic cause — a plugin setting, a template, a bulk-generation process — and fix that. Almost always a handful of causes account for nearly all of it.

It is also worth asking whether all those pages should exist. Sites carrying thousands of near-identical pages are usually better off consolidating, both for indexing and for the crawl budget spent reaching the pages that matter.

Once they are indexed

Being in the index is the floor, not the goal — it makes a page eligible to rank, nothing more. But it is the right first check, because every hour spent on content and links for a page that was never eligible is an hour wasted, and finding that out after six months is an expensive way to learn it.