{"id":338,"date":"2026-09-11T19:13:45","date_gmt":"2026-09-11T18:13:45","guid":{"rendered":"https:\/\/www.webfort.co.uk\/blog\/?p=338"},"modified":"2026-09-11T19:13:45","modified_gmt":"2026-09-11T18:13:45","slug":"why-website-not-showing-on-google","status":"publish","type":"post","link":"https:\/\/www.webfort.co.uk\/blog\/why-website-not-showing-on-google\/","title":{"rendered":"Why Is My Website Not Showing on Google? A UK SEO Guide"},"content":{"rendered":"<p>If you are asking <strong>why is my website not showing on Google<\/strong>, the short answer is usually one of two things: either Google has not indexed your site yet, or it has indexed the site but is not ranking it highly enough for anyone to notice. Those are very different problems with very different fixes, so the first job is working out which one you have.<\/p>\n<p>Being indexed means Google has crawled a page, understood it and stored it in its search index, so it is eligible to appear in results. Ranking well means Google chooses to show that page near the top for a particular search. Indexing is a technical gate. Ranking is a competition. You can pass the gate and still finish nowhere, and plenty of UK small-business sites are indexed perfectly well while sitting on page four for the terms that matter to them.<\/p>\n<figure style=\"max-width:100%\"><img decoding=\"async\" src=\"https:\/\/images.pexels.com\/photos\/13628541\/pexels-photo-13628541.jpeg?auto=compress&#038;cs=tinysrgb&#038;fit=crop&#038;h=627&#038;w=1200\" alt=\"Google Search Console and website indexing dashboard for SEO troubleshooting\" style=\"max-width:100%;height:auto\" \/><figcaption>Google Search Console is the fastest way to find out what Google actually thinks of your site.<\/figcaption><\/figure>\n<h2>What&#8217;s in this post<\/h2>\n<ul>\n<li><a href=\"#indexed-check\">Check whether Google has indexed your site<\/a><\/li>\n<li><a href=\"#url-inspection\">Use URL Inspection and the Page indexing report<\/a><\/li>\n<li><a href=\"#accessible\">Check the site is publicly accessible and returns HTTP 200<\/a><\/li>\n<li><a href=\"#robots-noindex\">Check robots.txt and noindex rules<\/a><\/li>\n<li><a href=\"#sitemap\">Check your XML sitemap and internal links<\/a><\/li>\n<li><a href=\"#speed-mobile\">Check mobile usability, speed and Core Web Vitals<\/a><\/li>\n<li><a href=\"#content\">Improve the page itself<\/a><\/li>\n<li><a href=\"#how-long\">How long indexing takes and what to do after fixes<\/a><\/li>\n<li><a href=\"#checklist\">Troubleshooting checklist<\/a><\/li>\n<li><a href=\"#final\">Final thoughts<\/a><\/li>\n<\/ul>\n<h2 id=\"indexed-check\">1. Check whether Google has indexed the site or page<\/h2>\n<p>Start with the cheapest test. Type this into Google, replacing the domain with your own:<\/p>\n<ul>\n<li><code>site:yourbusiness.co.uk<\/code> shows roughly which pages of your domain are in the index.<\/li>\n<li><code>site:yourbusiness.co.uk\/services\/boiler-repair<\/code> checks one specific page.<\/li>\n<li><code>\"your exact business name\" yourtown<\/code> checks whether you appear for your own brand.<\/li>\n<\/ul>\n<h2 id=\"url-inspection\">2. Use URL Inspection and the Page indexing report<\/h2>\n<p>Search Console gives you two tools that answer most indexing questions outright.<\/p>\n<h3>URL Inspection<\/h3>\n<p>Paste any URL from your verified property into the search bar at the top of Search Console and it will tell you whether that exact page is on Google. The <a href=\"https:\/\/support.google.com\/webmasters\/answer\/9012289\" rel=\"noopener nofollow\" target=\"_blank\">URL Inspection tool<\/a> reports the page&#8217;s index status, when it was last crawled, which sitemap referred it, and whether Google found any blocking rules.<\/p>\n<p>Read the status line carefully, because the wording is specific:<\/p>\n<table>\n<thead>\n<tr>\n<th>What you see<\/th>\n<th>What it usually means<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>URL is on Google<\/td>\n<td>Indexed. Any visibility issue is about ranking, not indexing.<\/td>\n<\/tr>\n<tr>\n<td>URL is not on Google: indexing errors<\/td>\n<td>Google tried and was blocked or hit an error. Fix the cause below.<\/td>\n<\/tr>\n<tr>\n<td>Discovered, currently not indexed<\/td>\n<td>Google knows the URL exists but has not crawled it yet. Often a crawl budget or perceived value issue.<\/td>\n<\/tr>\n<tr>\n<td>Crawled, currently not indexed<\/td>\n<td>Google looked and chose not to index. Usually a content quality or duplication signal.<\/td>\n<\/tr>\n<tr>\n<td>Excluded by noindex tag<\/td>\n<td>You are telling Google to stay out. See the robots and noindex section.<\/td>\n<\/tr>\n<tr>\n<td>Duplicate, Google chose different canonical<\/td>\n<td>Google treats another URL as the main version of this content.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>Page indexing report<\/h3>\n<p>For the whole site view, open the <a href=\"https:\/\/support.google.com\/webmasters\/answer\/7440203\" rel=\"noopener nofollow\" target=\"_blank\">Page indexing report<\/a>. It splits your URLs into indexed and not indexed, and groups the not indexed pages by reason. This is the single most useful screen in Search Console for diagnosing why is my website not showing on Google at scale, because it turns a vague worry into a list of named causes with counts against them.<\/p>\n<p>Work down that list from the largest group. If 200 pages are excluded by noindex and three have server errors, fix the noindex first.<\/p>\n<h2 id=\"accessible\">3. Check the site is publicly accessible and returns HTTP 200<\/h2>\n<p>Google can only index what it can reach. Before touching anything clever, confirm the basics.<\/p>\n<p>If the site is unreliable, start with our <a href=\"https:\/\/www.webfort.co.uk\/blog\/website-down-checklist-small-business\/\">website down checklist for small businesses<\/a>. For domain and DNS faults, see <a href=\"https:\/\/www.webfort.co.uk\/blog\/dns-problems-why-website-wont-load\/\">why a website will not load<\/a>.<\/p>\n<h3>What status code does it return?<\/h3>\n<p>A healthy public page returns HTTP 200. Codes to watch for:<\/p>\n<ul>\n<li><strong>301 or 302 redirects.<\/strong> Fine in moderation, but long redirect chains and redirect loops waste crawl effort and can stop indexing entirely. Aim for one hop.<\/li>\n<li><strong>403 Forbidden.<\/strong> Often a firewall, bot protection rule or security plugin blocking Googlebot. Check whether your WAF is rate limiting or challenging crawler traffic.<\/li>\n<li><strong>404 Not Found.<\/strong> The URL genuinely does not exist, or a broken internal link is pointing at a typo.<\/li>\n<li><strong>500 or 503.<\/strong> Server errors. Repeated 5xx responses will slow crawling and can get pages dropped.<\/li>\n<\/ul>\n<p>You can check any URL&#8217;s status code with a browser&#8217;s developer tools network tab, or with <code>curl -I https:\/\/yourbusiness.co.uk<\/code> from a terminal.<\/p>\n<p>Google&#8217;s own <a href=\"https:\/\/developers.google.com\/search\/docs\/essentials\/technical\" rel=\"noopener nofollow\" target=\"_blank\">Search technical requirements<\/a> are short and worth reading in full. They set out the minimum bar: the page must not be blocked, Googlebot must get a successful response, and the page must have indexable content.<\/p>\n    <aside class=\"wf-blog-cta wf-blog-cta--check\">\n      <div class=\"wf-blog-cta__inner\">\n        <span class=\"wf-blog-cta__kicker\">Free Tool<\/span>\n                <p class=\"wf-blog-cta__title\">Is your website holding your business back?<\/p>\n        <p class=\"wf-blog-cta__body\">Run our free 30-second health check - no signup required. Check speed, security, and SEO issues instantly.<\/p>\n        <a class=\"wf-blog-cta__btn\" href=\"https:\/\/www.webfort.co.uk\/free-website-check\/\">\n          Check My Website          <svg class=\"wf-blog-cta__arrow\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2.5\" stroke-linecap=\"round\" stroke-linejoin=\"round\" aria-hidden=\"true\"><path d=\"M5 12h14M13 6l6 6-6 6\"\/><\/svg>\n        <\/a>\n      <\/div>\n    <\/aside>\n    \n<h2 id=\"robots-noindex\">4. Check robots.txt and noindex rules<\/h2>\n<p>These two get mixed up constantly, and the distinction matters.<\/p>\n<p><strong>robots.txt controls crawling.<\/strong> It sits at <code>yourbusiness.co.uk\/robots.txt<\/code> and tells crawlers which paths they may request. <strong>noindex controls indexing.<\/strong> It is a meta tag or HTTP header on the page itself telling Google not to include that page in search results.<\/p>\n<p>The trap: if you block a page in robots.txt, Google cannot crawl it, which means it cannot see your noindex tag either. A page blocked in robots.txt can still appear in results as a bare URL with no description, because Google knows it exists from links but is not allowed to look at it. If you want a page out of the index, allow crawling and use noindex. Google&#8217;s <a href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/block-indexing\" rel=\"noopener nofollow\" target=\"_blank\">documentation on blocking indexing<\/a> explains this properly.<\/p>\n<h3>What to look for<\/h3>\n<p>Open your robots.txt in a browser. A blanket block looks like this and will keep your whole site out:<\/p>\n<pre><code>User-agent: *\nDisallow: \/<\/code><\/pre>\n<p>That line is standard on staging servers and sometimes survives a launch. It is one of the most common single causes of a site vanishing.<\/p>\n<p>Then check for noindex. View the page source and search for <code>noindex<\/code>. You are looking for:<\/p>\n<pre><code>&lt;meta name=\"robots\" content=\"noindex\"&gt;<\/code><\/pre>\n<p>Or the header equivalent, <code>X-Robots-Tag: noindex<\/code>, which is invisible in the page source and easy to miss. URL Inspection will flag both.<\/p>\n<p>Most site platforms have a &#8220;discourage search engines&#8221; setting somewhere in their options. If a developer or agency switched it on during a build and nobody switched it off, that single checkbox is your answer.<\/p>\n<h2 id=\"sitemap\">5. Check your XML sitemap and internal links<\/h2>\n<p>A sitemap is a list of the URLs you want Google to know about. It does not force indexing, but it helps Google discover pages, particularly on larger sites or ones with weak internal linking.<\/p>\n<p>Your sitemap usually lives at <code>\/sitemap.xml<\/code> or <code>\/sitemap_index.xml<\/code>. Submit it through the <a href=\"https:\/\/support.google.com\/webmasters\/answer\/7451001\" rel=\"noopener nofollow\" target=\"_blank\">Sitemaps report<\/a> in Search Console, then check back for parse errors and the count of discovered URLs.<\/p>\n<p>Good sitemap hygiene:<\/p>\n<ul>\n<li>Include only canonical, indexable URLs that return 200.<\/li>\n<li>Remove noindexed pages, redirects and 404s. A sitemap full of dead URLs erodes trust in the file.<\/li>\n<li>Use absolute URLs on your canonical domain and protocol.<\/li>\n<li>Reference the sitemap from robots.txt with a <code>Sitemap:<\/code> line.<\/li>\n<\/ul>\n<h3>Internal links matter more than the sitemap<\/h3>\n<p>Google largely finds pages by following links. A page with no internal links pointing to it is an orphan, and orphans are frequently the ones sitting in &#8220;Discovered, currently not indexed&#8221; limbo.<\/p>\n<p>Check that every important page is reachable within a few clicks of your homepage, that your main navigation uses real <code>&lt;a href&gt;<\/code> links rather than JavaScript handlers, and that service pages link to each other where it makes sense. If your key pages are only reachable through a search box or a filtered listing, Google may never get to them. The <a href=\"https:\/\/developers.google.com\/search\/docs\/fundamentals\/get-started-developers\" rel=\"noopener nofollow\" target=\"_blank\">Search Central guide for developers<\/a> is a good reference if your site relies heavily on client side rendering.<\/p>\n<figure style=\"max-width:100%\"><img decoding=\"async\" src=\"https:\/\/images.pexels.com\/photos\/12969403\/pexels-photo-12969403.jpeg?auto=compress&#038;cs=tinysrgb&#038;fit=crop&#038;h=627&#038;w=1200\" alt=\"Website SEO audit and Google indexing checks on a laptop\" style=\"max-width:100%;height:auto\" \/><figcaption>Work through the technical checks in order before spending money on content or links.<\/figcaption><\/figure>\n<h2 id=\"speed-mobile\">6. Check mobile usability, page speed and Core Web Vitals<\/h2>\n<p>Google predominantly uses the mobile version of your site for indexing and ranking. If your mobile experience is broken, hides content behind scripts that fail, or takes an age to load, that is the version Google judges you on.<\/p>\n<p>Practical checks:<\/p>\n<ul>\n<li>Load your site on a real phone on mobile data, not just a resized desktop browser.<\/li>\n<li>Confirm text is readable without zooming and tap targets are not crammed together.<\/li>\n<li>Make sure content is not hidden from crawlers by scripts that only run after user interaction.<\/li>\n<li>Run a page speed test and look at your field data, not just the lab score.<\/li>\n<\/ul>\n<p>Core Web Vitals measure loading, interactivity and visual stability. They are a real, if modest, part of how Google evaluates page experience, and they matter a great deal to whether a visitor sticks around. Our guide to <a href=\"https:\/\/www.webfort.co.uk\/blog\/core-web-vitals-explained-what-they-are-and-how-to-improve-them\/\">Core Web Vitals explained<\/a> covers what each metric measures and how to improve it, and there is more on the commercial side in <a href=\"https:\/\/www.webfort.co.uk\/blog\/why-your-website-speed-matters-more-than-you-think-in-2026\/\">why website speed matters more than you think<\/a>.<\/p>\n<p>A note on hosting, because it gets overstated in both directions. Google does not treat your server&#8217;s physical location as a direct ranking factor. What hosting genuinely affects is availability, response time and consistency. A server that times out during a crawl, returns 5xx errors under load, or takes two seconds to send the first byte will get crawled less, will frustrate visitors, and will make your Core Web Vitals worse. Those are real, practical SEO outcomes even though &#8220;hosting location&#8221; is not a line item in Google&#8217;s ranking systems.<\/p>\n<h2 id=\"content\">7. Improve the page itself<\/h2>\n<p>Once the technical gate is open, ranking is decided by whether your page is the best available answer. This is where a lot of small-business sites stall, and it is worth being blunt: fixing your robots.txt will not put you above an established competitor. Technical fixes make you eligible. They do not guarantee rankings.<\/p>\n<h3>Write something genuinely useful<\/h3>\n<p>Thin pages that restate what everyone else says give Google no reason to prefer you. For a UK small business, your advantage is specificity: the towns you cover, the exact services you offer, the questions your customers actually ask on the phone, the prices or ranges you can publish, the real photos of real jobs. That is original information a competitor cannot copy.<\/p>\n<h3>Get the basics right on the page<\/h3>\n<ul>\n<li><strong>Title tag.<\/strong> One per page, unique, descriptive, with the key term near the front. This is often what people click.<\/li>\n<li><strong>H1 and headings.<\/strong> One clear H1, then H2s and H3s that describe the sections honestly. Headings are for readers first.<\/li>\n<li><strong>Meta description.<\/strong> Not a ranking factor, but it influences click through rate. Write it like ad copy.<\/li>\n<li><strong>Internal links.<\/strong> Link to related pages using descriptive anchor text rather than &#8220;click here&#8221;.<\/li>\n<li><strong>Images.<\/strong> Compress them, use descriptive alt text, and set width and height to avoid layout shift.<\/li>\n<\/ul>\n<h2 id=\"how-long\">8. How long indexing takes and what to do after fixes<\/h2>\n<p>There is no fixed timetable, and anyone promising one is guessing. In practice, a well linked page on an established site can be indexed within days. A new page on a brand new domain with no inbound links can take considerably longer, sometimes several weeks. Google decides how often to crawl based on how important and how frequently updated it judges your site to be.<\/p>\n<p>After you make a fix, do this:<\/p>\n<ol>\n<li>Use <strong>Test live URL<\/strong> in URL Inspection to confirm Google can now access the page and sees no blocking rules.<\/li>\n<li>Click <strong>Request indexing<\/strong> for genuinely important pages. This nudges the queue. It does not force indexing, and there is a daily limit, so do not spam it.<\/li>\n<li>Resubmit your sitemap if its contents changed.<\/li>\n<li>Use <strong>Validate fix<\/strong> on the relevant issue group in the Page indexing report so Google recrawls the affected set.<\/li>\n<li>Wait. Check back in one to two weeks rather than refreshing daily.<\/li>\n<\/ol>\n<h2 id=\"checklist\">9. Troubleshooting checklist<\/h2>\n<ol>\n<li>Run <code>site:yourdomain.co.uk<\/code>. Any results at all?<\/li>\n<li>Is Search Console verified for the correct property, including the right www and HTTPS variant?<\/li>\n<li>What does URL Inspection say about your homepage and your top three service pages?<\/li>\n<li>What is the biggest group in the Page indexing report&#8217;s &#8220;not indexed&#8221; section?<\/li>\n<li>Does the site load in a private window on mobile data and return HTTP 200?<\/li>\n<li>Any redirect chains, loops, 403s, 404s or 5xx errors on key URLs?<\/li>\n<li>Is there a login wall, maintenance mode or &#8220;coming soon&#8221; page still active?<\/li>\n<li>Does robots.txt contain <code>Disallow: \/<\/code> or block important directories?<\/li>\n<li>Is there a <code>noindex<\/code> meta tag or <code>X-Robots-Tag<\/code> header on pages that should rank?<\/li>\n<li>Is a &#8220;discourage search engines&#8221; setting switched on in your platform?<\/li>\n<li>Is your sitemap present, valid, submitted and free of dead URLs?<\/li>\n<li>Are your important pages linked from the navigation or other pages, with no orphans?<\/li>\n<li>Are canonical tags pointing where you expect?<\/li>\n<li>Is the mobile version usable, and are your Core Web Vitals passing?<\/li>\n<li>Does each page have a unique title, one clear H1 and genuinely useful content?<\/li>\n<li>Does the page match the intent of the search you are targeting?<\/li>\n<li>Is your Google Business Profile complete and consistent with your site?<\/li>\n<\/ol>\n    <aside class=\"wf-blog-cta wf-blog-cta--hosting\">\n      <div class=\"wf-blog-cta__inner\">\n        <span class=\"wf-blog-cta__kicker\">Webfort Hosting<\/span>\n                <p class=\"wf-blog-cta__title\">Looking for fast, reliable UK hosting?<\/p>\n        <p class=\"wf-blog-cta__body\">Our plans start from <strong>\u00a34.99\/month<\/strong> with everything included: SSL, backups, email, and 24\/7 support.<\/p>\n        <a class=\"wf-blog-cta__btn\" href=\"https:\/\/www.webfort.co.uk\/web-hosting\/\">\n          View Hosting Plans          <svg class=\"wf-blog-cta__arrow\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2.5\" stroke-linecap=\"round\" stroke-linejoin=\"round\" aria-hidden=\"true\"><path d=\"M5 12h14M13 6l6 6-6 6\"\/><\/svg>\n        <\/a>\n      <\/div>\n    <\/aside>\n    \n<h2 id=\"final\">Final thoughts<\/h2>\n<p>When someone asks why is my website not showing on Google, the honest answer is that it depends on whether the problem is a closed gate or a lost race. A closed gate is a technical fault: a stray noindex, a robots.txt block left over from a build, a login wall, a server that keeps failing, a page nothing links to. These are usually quick to find with URL Inspection and the Page indexing report, and quick to fix once found.<\/p>\n<p>A lost race is harder. If you are indexed and still invisible, the work is content, relevance and reputation, and it takes months rather than days. Being clear about which situation you are in saves you from spending on the wrong thing.<\/p>\n<p>Start with Search Console, work down the checklist in order, change one thing at a time and give Google room to recrawl. Most UK small-business sites that seem to have disappeared are one setting away from coming back, and the rest need patience and better pages rather than a silver bullet.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Why is your website not showing on Google? Follow this practical UK SEO troubleshooting guide to check indexing, technical issues and Search Console.<\/p>\n","protected":false},"author":1,"featured_media":337,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[118,48,22,117,119],"class_list":["post-338","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-performance","tag-google-search-console","tag-seo","tag-small-business","tag-technical-seo","tag-website-indexing"],"_links":{"self":[{"href":"https:\/\/www.webfort.co.uk\/blog\/wp-json\/wp\/v2\/posts\/338","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.webfort.co.uk\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.webfort.co.uk\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.webfort.co.uk\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.webfort.co.uk\/blog\/wp-json\/wp\/v2\/comments?post=338"}],"version-history":[{"count":1,"href":"https:\/\/www.webfort.co.uk\/blog\/wp-json\/wp\/v2\/posts\/338\/revisions"}],"predecessor-version":[{"id":339,"href":"https:\/\/www.webfort.co.uk\/blog\/wp-json\/wp\/v2\/posts\/338\/revisions\/339"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.webfort.co.uk\/blog\/wp-json\/wp\/v2\/media\/337"}],"wp:attachment":[{"href":"https:\/\/www.webfort.co.uk\/blog\/wp-json\/wp\/v2\/media?parent=338"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.webfort.co.uk\/blog\/wp-json\/wp\/v2\/categories?post=338"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.webfort.co.uk\/blog\/wp-json\/wp\/v2\/tags?post=338"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}