Why Isn’t My Website on Google? 9 Checks to Make

Start with the affected URL in Google Search Console’s URL Inspection tool, then use the Page indexing report to compare other affected pages. A search for site:yoursite.co.uk can provide a quick spot check, but Google says the site: operator does not return every indexed URL. A missing result does not prove a page is unindexed, and finding some pages does not establish that the whole site is indexed.

If you have not connected Search Console, our plain-English setup guide walks through it. Keep the inspection date, last crawl and Google-selected canonical with each finding. The indexed view describes Google’s stored information; a live test checks the current page but cannot prove that Google will index it. Some report statuses identify a specific block, while others need further investigation.

Check 1: Has Google discovered the page?

Links and sitemaps help Google discover URLs. “URL is unknown to Google” and “Discovered – currently not indexed” describe different states: the latter means Google knows the URL but has not yet crawled it. Check discovery evidence and crawl access before assuming the page needs rewriting. Google’s Page indexing report guide explains the status definitions.

• Verify the site in Search Console, then submit your sitemap under Indexing → Sitemaps (usually yoursite.co.uk/sitemap.xml — WordPress, Wix, Squarespace and Shopify all generate one automatically).
• For a few new or materially changed public pages, use URL Inspection to check the URL and request indexing once. For many URLs, submit a sitemap. Neither action guarantees crawling or indexing.
• Link to important pages from relevant, accessible pages on your own site. Keep legitimate business profiles and relevant partner links accurate; do not buy links to try to force discovery.

Check 2: Is noindex excluding an intended public page?

A noindex rule in an HTML meta tag or X-Robots-Tag HTTP header tells Google to exclude the page after it reads the rule. It can remain on a public page accidentally after launch. Crucially, noindex is not access control and does not make staging or customer information private: protect private content with authentication. Google documents the noindex rule and its crawl requirements.

Look for noindex exclusions in Page indexing and inspect the affected URL. Check both the HTML and response headers. Remove the rule only when that specific page should appear in search; keep intentional exclusions. Google must be able to crawl the page to see either the rule or its removal.

Check 3: Is robots.txt blocking the crawl?

Your robots.txt file tells compliant crawlers which paths they may fetch. Disallow: / can block all paths for the user-agent group it applies to. Check the complete rule set for the affected URL and Googlebot; more-specific user-agent groups and Allow rules can change the result.

Robots.txt controls crawling, not privacy or guaranteed exclusion from search. Google may know a blocked URL from links even when it cannot read its content. Allow crawling of pages intended for search while preserving deliberate restrictions, and use authentication for private content. Google’s robots.txt guide explains these limits.

Check 4: What does “Crawled – currently not indexed” establish?

“Crawled – currently not indexed” establishes that Google crawled the URL but has not indexed it. The status alone does not prove a quality penalty, a duplicate-content problem or a particular technical fault. Google says the page may or may not be indexed later and does not require resubmission simply because it has this status. This differs from “Discovered – currently not indexed”, where a crawl has not yet happened.

Inspect the recorded crawl, current HTTP response, rendered content and canonical evidence. Then review whether the page serves a distinct purpose and adds useful first-hand detail rather than repeating another page. Use real examples and verified business facts, with contextual links where they help readers. These are checks to guide a correction, not guaranteed cures for the status. Our internal linking guide shows how to make those paths useful.

Check 5: Are duplicate and canonical signals consistent?

If equivalent content lives at several URLs, Google can select one canonical URL to represent it. An alternate URL being excluded can be expected behaviour. Compare your declared canonical with Google’s selection and confirm which version should appear in search before treating a duplicate status as a fault.

• Pick one canonical version of your domain (https plus either www or not) and 301-redirect every other variant to it.
• Use self-referencing canonicals for distinct canonical pages; point deliberate duplicates to their chosen equivalent. Keep redirects, internal links and sitemap URLs consistent with that choice.
• Replace placeholder or copied text with information that helps your customer make a decision. Consolidate pages when they serve the same purpose and have no useful reason to remain separate.

Check 6: Is there a manual action or security issue?

Rare, but worth thirty seconds: check Security & Manual actions in the Search Console menu. A manual action means a human reviewer at Google penalised the site — usually for spammy links or hacked content — and the report says exactly why and how to request reconsideration. A security issue (malware, phishing injections) can get a site filtered or flagged with a browser warning. Both screens should read “No issues detected”. If they do not, that finding outranks every other fix on this page; Google’s manual actions report guide explains the recovery process.

Check 7: Is the indexed page getting search impressions?

If URL Inspection reports the intended canonical as indexed, examine that page in Performance → Search results. Check impressions, queries, clicks and average position over a useful date range. Indexing alone does not guarantee an impression for the search you tried, and a sitewide average can hide very different page and query results.

Prioritise pages with relevant impressions and a clear unmet reader need. A page ranking below stronger competitors might benefit from more useful detail, clearer titles or better internal links, depending on the evidence. Our guide to quick wins in your Search Console data explains the filters; how long SEO takes discusses why outcomes vary.

Check 8: Does the page answer the searches you want to serve?

A technically accessible page can still be unclear or poorly matched to a customer’s question. A title such as “Bespoke Solutions for Discerning Clients” explains less than a specific service description. Consider the service, customer type and real area served, without assuming that a narrower phrase will be easy to rank for.

Look at the Queries tab in your Performance report and compare the reported searches with real customer questions. An empty query list can reflect limited or withheld data, so it is not proof of no demand. Use verified customer language and service areas when improving titles and headings. Our industry SEO guides provide sector examples to review against your own evidence.

Check 9: Are technical failures preventing a reliable crawl?

Repeated server errors and inaccessible content can prevent reliable crawling. Check Crawl stats, URL Inspection and your server logs for the affected time and URL; investigate the cause before replacing your hosting. Compare the crawled HTML with a live test if JavaScript rendering may be involved. Google’s technical requirements cover access, working responses and indexable content.

Work the list in order

1. Inspect affected URLs in Search Console and record their status, canonical and last crawl. Treat site: results as an incomplete spot check.
2. Compare the Page indexing reasons and current page checks. Separate confirmed blocks from questions that still need evidence.
3. Make the correction supported by those findings and record what changed and when. Review overlapping content before adding another URL.
4. For a few materially changed URLs, request indexing once; use a sitemap for larger batches. Repeated requests do not speed crawling. Reinspect later and keep publication, crawling, indexing and search performance separate.

Google’s recrawl guidance makes clear that requests do not guarantee inclusion. VantageRank agents check connected Search Console evidence on their scheduled runs and propose work for review. Missing or incomplete evidence should produce a next step to investigate, rather than a claimed diagnosis or a promise of indexing.