Why isn't my website showing on Google?
A practical Google Search Console sequence for UK small businesses when a site or page is missing: robots, noindex, status, canonicals, redirects and sitemaps.

“We’re not on Google” usually means one of three different problems:
- Google has not indexed the site or page at all.
- The page is indexed, but ranks too weakly to appear for the searches you tried.
- You are looking at the wrong URL (http vs https, www vs non-www, or a duplicate Google chose as canonical).
Those need different fixes. Guessing “we need more SEO content” before you check indexing wastes time.
A missing Google Maps pin is a fourth, separate problem: it is about the Business Profile for that location, not whether the website is indexed. See Why isn’t my business showing on Google Maps?.
Google Analytics 4 does not control indexing. GA4 measures visits from people (and some other traffic). Google Search discovers, crawls and indexes the web through other systems. A quiet Analytics property does not prove you are absent from Search — and a busy one does not prove every important URL is indexed.
Start with Search Console URL Inspection
The authoritative check is Google Search Console’s URL Inspection tool. Open Google Search Console, select the correct property, and paste the exact URL you care about.
URL Inspection tells you whether Google could crawl the URL, whether indexing is allowed, what canonical Google selected, and whether the URL is currently on Google. That report should drive your diagnosis.
A site: search in Google can be a rough clue:
- Whole site:
site:yourdomain.co.uk - Specific path:
site:yourdomain.co.uk/exact-page
If results appear, the URL or site is at least partly in the index — ranking is then a separate conversation. If nothing useful appears, that does not prove the page is unindexed. site: results are incomplete, can lag, and can miss URLs that URL Inspection still shows as on Google. Treat Search Console as the source of truth.
New pages can take time. Google’s guidance is to allow at least a week after submitting a sitemap or an indexing request before assuming a problem, and crawling can take from a few days to a few weeks depending on many factors.
The diagnostic sequence
Work through the URL Inspection report in this order.
1. Can Google crawl it? (robots.txt)
“Crawl allowed?” should be yes for public pages you want in Search.
robots.txtcontrols crawling. It is not, by itself, a complete way to keep a page out of the index.- Google notes a page blocked by robots.txt might still appear in results in limited form if discovered via links — but Google will not fetch the full page while blocked.
- If you want a public page kept out of Google Search results, Google’s documented approach is to allow crawling and use a noindex directive, rather than relying on robots.txt alone.
- If you want a public page in Search, remove the disallow rule that blocks Googlebot, then retest.
Also check your host or CDN firewall is not presenting Googlebot with a challenge or block page.
2. Is indexing allowed? (noindex)
“Indexing allowed?” should be yes for public marketing pages you want found.
Look for:
- A
noindexmeta robots tag in the HTML - An
X-Robots-Tag: noindexHTTP header - CMS “discourage search engines” or staging settings left on after launch
If noindex is present on a page you intend to be public in Search, remove it from the live URL, confirm with Test live URL, then request indexing if appropriate.
Do not remove noindex from pages that should stay out of Search — for example draft, staging, thank-you, internal or otherwise non-public URLs. For content that must stay private, authentication or other access control is the right protection; noindex only affects search indexing of a URL Google can already fetch, and is not a secrecy mechanism.
If robots.txt blocks the crawl, Google may not see a noindex directive on the page. Fix crawl blocks carefully so you do not leave a public page both blocked and half-visible.
3. Does the URL return a healthy status?
The page needs to be fetchable. Common failures:
- Soft 404s (URL returns 200 but “page not found” content)
- Hard 404 / 410 on URLs you still promote
- 5xx server errors or long timeouts when Google tried to fetch
- Login walls or geo blocks for crawlers on pages you want indexed
Fix the live response, then inspect again.
4. Canonical: which URL does Google treat as the main one?
URL Inspection shows:
- User-declared canonical (what your page/sitemap signals)
- Google-selected canonical (what Google chose)
If Google selected a different URL, Search results will tend to point there. Causes include duplicate http/https or www variants, parameter URLs, thin copies, or a canonical tag pointing elsewhere.
Align:
- Preferred host (https, www or not) with redirects
- Self-referencing or correct
rel=canonicalon the preferred URL - Internal links and sitemap entries that all point to that preferred URL
Google may still choose a different canonical; clear, consistent signals help.
5. Redirects and site moves
If you recently changed domain, folded www, or moved to https, broken or chained redirects often explain why older URLs stop appearing as expected.
Google’s missing-page help recommends proper 301 redirects for permanent moves and checking that both old and new variants are understood in Search Console. Follow Google’s site-move guidance rather than deleting the old property and hoping.
6. Sitemaps and discovery
A sitemap helps Google learn which URLs you consider important. Google’s crawling FAQ is clear that a sitemap does not guarantee indexing or improve ranking.
Still do the basics:
- Submit an XML sitemap that lists only canonical, indexable URLs that return success responses
- Remove deleted or redirected URLs promptly
- Ensure important pages are reachable via ordinary links from the homepage and key landing pages — Google discovers many URLs through links, not only sitemaps
If you also care about Bing discovery, Bing Webmaster Tools and Bing’s own sitemap guidance are the parallel place to look once Google issues are understood.
7. Manual actions, security issues and removals
In Search Console, check Manual actions, Security issues, and Removals (including temporary removals you or a previous owner requested). Inherited domains sometimes carry old problems. Fix what those reports document before you assume a ranking mystery.
Indexed vs ranking: do not confuse them
| Situation | What it usually means | What to do next |
|---|---|---|
| URL Inspection: not indexed / blocked | Crawl, noindex, status, canonical or discovery issue | Work the sequence above |
site: shows little or nothing | Incomplete clue only — confirm with URL Inspection | Do not treat absence in site: as proof |
| URL Inspection: “URL is on Google” but you don’t see it for “best X Brighton” | Indexing worked; relevance, competition or query choice differs | Improve content and local relevance; check GBP basics if local |
| Wrong variant ranks | Canonical/redirect confusion | Consolidate URLs |
| AI features don’t cite you | For Google AI Overviews/AI Mode, the page must be indexed and snippet-eligible first | Fix indexing; see How to appear in Google AI Overviews and ChatGPT / AI search notes |
Requesting indexing submits a URL for consideration. Google’s recrawl documentation states that a request does not guarantee inclusion in results instantly — or at all — and that systems prioritise useful content. Quotas apply; repeating the same request does not make Google faster.
New site checklist
If the whole site is new:
- Search Console property verified for the exact preferred host (and consider Domain property coverage)
- Homepage returns 200 over https
- No sitewide noindex or “discourage search engines” on public pages
- robots.txt allows Googlebot on public content
- Sitemap submitted with key public URLs
- Homepage indexing requested once blockers are clear
- Important pages linked from the homepage so Google can discover them
- Wait and re-check with URL Inspection rather than rebuilding the site every two days
Fix crawl and index blockers before you commission a pile of new blog posts. Content only helps once Google can fetch and consider the pages you already have.
What GA4 can and cannot tell you
Use GA4 for:
- Whether real users arrive from organic search once tagging is correct
- Landing pages and conversions after clicks happen
Do not use GA4 for:
- Index coverage
- Canonical selection
- Crawl permission
- Proof that Google “approved” your site
Search Console’s Page indexing report and URL Inspection are the right tools for presence in Google Search.
Short Q&A
I clicked Request indexing. Why is nothing happening?
Requests enter a queue. Google may take days or weeks, and may decline to index. Fix availability and quality issues first; then be patient and monitor URL Inspection.
Does a sitemap force Google to index everything?
No. It helps discovery. Indexing is separate and not guaranteed.
We’re on Google for our brand name but not for services — are we “not showing”?
Usually you are indexed. That is a ranking and relevance problem, not a missing-site problem.
Next step
If URL Inspection shows blockers you cannot clear — or the site is indexed but chronically misconfigured — a technical SEO health check focuses on crawl, indexation and canonical clarity.
Sources
- Why is my page missing from Google Search? — verification steps; new pages; common blockers; sitemap/linking discovery
- URL Inspection tool — crawl allowed, indexing allowed, canonicals, fetch, sitemaps
- Page indexing report — robots.txt vs noindex; duplicates/canonicals
- Ask Google to recrawl your URLs — request timing and limits
- FAQ: Google Search crawling and indexing — timing; sitemaps and indexing/ranking
- AI features and your website — AI Overviews/AI Mode need indexed, snippet-eligible pages
- Bing Webmaster Guidelines — discovery, sitemaps, robots vs noindex for Bing eligibility