Why Your Website Is Not Showing Up on Google

When a website is not showing up on Google at all, the cause is nearly always a setting, a block or a discovery problem that can be found in an afternoon. Most of the checks take minutes and need nothing more than a browser and access to Google Search Console. Working through them in the order below separates the quick fixes from the problems that need more time. The same checks are the starting point for any programme of SEO for growing B2B businesses.

The first job is to be precise about the symptom, because not ranking for a competitive phrase is a different problem from not appearing at all. A website that appears when someone types its exact name but not for the services it offers is indexed, so the work lies in content and competition rather than technical access. A website that does not appear even for its own brand name usually has an indexing problem. The sections below cover those causes first.

Check Whether Google Has Indexed the Website

The quickest way to check whether Google has indexed a website is to search for site:yourdomain.co.uk in Google. If pages appear, the website is in the index and the problem is visibility rather than access. Google’s own guidance on getting a website on Google recommends the same search, while noting that the site: operator does not necessarily return every indexed URL.

The result points to where the rest of the investigation should go. Read it alongside the age of the website and any recent changes, since a brand new domain and an established website that vanished overnight have very different causes.

A brand name search is a useful second test. If the website does not appear when someone searches for the organisation’s exact name, Google is either unaware of the website or has been told to keep it out of results. Brand names that are common words can muddy this test, so add the town or the sector to the search before drawing conclusions.

Look for a Block Left Over From the Build

A common cause on new websites is an instruction, left over from development, that tells search engines to stay away. Developers often block crawling or indexing on a staging copy so unfinished pages never appear in results. That block can travel with the website when it goes live.

Two different mechanisms do this job and they behave differently. Google’s introduction to robots.txt explains that a robots.txt file controls which URLs a crawler can access and is not a way of keeping a page out of Google. A noindex rule is the instruction that removes pages from results. Google’s guidance on blocking indexing with noindex confirms it can be set as a meta tag or as an X-Robots-Tag HTTP response header. The two can also conflict, because Google never sees a noindex rule on a page that robots.txt stops it from crawling.

WordPress websites have one extra place to check. The WordPress reading settings include a box labelled Discourage search engines from indexing this site. When it is ticked, WordPress adds a noindex, nofollow robots meta tag to the head of the website’s pages. The box is often ticked during development and missed at launch.

A noindex rule can also arrive later in a website’s life. A plugin update, a theme change or a page left as private after editing can keep content out of results without anyone noticing, so repeat the check whenever pages drop out of the index.

Read the Page Indexing Report in Search Console

Google Search Console is the tool that shows exactly which pages are indexed and why the rest are not. Google’s guide to getting started with Search Console describes an index report covering every page Google indexed or tried to index, along with a URL Inspection tool that shows the current index status of a single page.

Setting up Search Console means verifying ownership of the domain, usually through a DNS record or a file uploaded to the server. Once that is done, the Page indexing report lists the pages that are not indexed and groups them under a named reason.

Each reason points to a different fix, so read the label before changing anything. The reasons that appear most often on a website missing from Google are listed below.

• Excluded by noindex tag, which means a noindex rule is still in place on those pages
• Blocked by robots.txt, which means Google has been told not to crawl those URLs
• Discovered, currently not indexed, which means Google knows the URLs exist but has not fetched them yet
• Crawled, currently not indexed, which means Google fetched the page and decided not to include it for now
• Duplicate without user-selected canonical, which means Google treats the page as a copy of another URL
• Server error (5xx), which means the server failed when Googlebot tried to load the page
• Page with redirect, which means the URL forwards to another address that Google indexes instead

The URL Inspection tool confirms the picture for any single page. It shows when Google last crawled the URL, whether it found a noindex rule and which version of the page it chose as canonical. The Test live URL button then checks the page as it stands now rather than as Google last saw it.

Fix the cause first and only then use the same tool to request indexing. Requesting indexing on a page that still carries a noindex rule or returns an error achieves nothing, because Google will find the same problem again.

Help Google Discover a New Website

A brand new website with no links pointing at it can go unnoticed for some time, because Google finds pages by following links and reading sitemaps. Google’s explanation of how Search works describes this process as URL discovery and states that Google does not guarantee it will crawl, index or serve any page.

An XML sitemap removes the guesswork from discovery by listing every URL that should be indexed. Google’s guidance on building and submitting a sitemap covers the format and the submission process. On WordPress, an SEO plugin usually generates the sitemap automatically at a predictable address.

Submission is not the same as indexing, a distinction covered in our guide to what a sitemap is. The sitemap tells Google what exists, then Google decides which pages deserve a place in the index, so keep it to the pages that matter.

Google’s page on how to ask Google to recrawl URLs says crawling can take anywhere from a few days to a few weeks and that individual requests are subject to a quota. Requesting the same URL again and again does not speed anything up, so once the steps above are done the remaining ingredient is patience.

Links from other websites matter for discovery as much as they do for ranking. A handful of mentions from established organisations you already work with gives Google more routes to a new website than any number of requests in Search Console.

Rule Out Thin and Duplicate Pages

Google can crawl a page and still decide not to index it when the content is thin or repeated elsewhere. The same explanation of how Search works lists low quality content among the common reasons a processed page does not make it into the index.

Duplicates cause a related problem. When several URLs show the same or very similar content, Google treats them as one set and shows a single preferred version, which is why its guidance on specifying a canonical URL explains how to tell Google which page you want people to see in results. Common causes on business websites include pages that load with and without a trailing slash, tracking parameters, print versions and location pages that only change the name of the town.

Quality is the harder issue to fix because no setting can solve it. Google’s guidance on creating helpful, reliable content says its ranking systems are designed to prioritise information created to benefit people rather than content made to manipulate rankings. A service page that repeats the wording of a competitor, or a blog post written only to target a phrase, gives Google little reason to index it.

Thin pages are worth merging, expanding or removing rather than leaving in the sitemap. A smaller set of strong pages is easier for Google to crawl and gives each page a better chance of being indexed.

Check the Server and How Pages Render

Server errors and rendering problems can stop Google reading pages that look fine in a browser. Google’s documentation on HTTP status codes and network errors explains that Search Console reports errors for responses in the 4xx and 5xx ranges and that even a successful response does not guarantee indexing.

Hosting problems often show up as intermittent server errors in the Page indexing report. A server that times out under load, a firewall that blocks Googlebot or a security plugin that challenges unknown visitors can all keep pages out of the index while the website looks normal to staff. The Crawl stats report in the Search Console settings shows how Google’s requests to the server are faring over time.

Websites that rely on JavaScript to load their main content add another step. Google’s JavaScript SEO basics describes how pages pass through crawling, rendering and indexing in turn. Content that only appears after scripts run can be missed if rendering fails or is delayed.

Our guide to JavaScript SEO best practices covers the fixes in more detail. Websites that output their main content as plain HTML avoid most of these problems in the first place.

Find Out Why an Established Website Disappeared

An established website that disappears from Google has usually been moved without redirects, hit by a manual action or compromised by a hack. Each of these leaves evidence in Search Console, so start there rather than guessing.

Domain changes and redesigns are a common trigger. Google’s guidance on moving a website with URL changes recommends mapping every old URL to its new equivalent and redirecting with permanent redirects, which it says do not cause a loss in PageRank. Our guide to planning an SEO migration during a redesign covers what to check before and after launch.

Manual actions need a different response from technical faults, because Google has to review the fix before the action is lifted. Google’s spam policies state that websites which break them may rank lower or not appear in results at all. Its guide to debugging drops in Search traffic recommends checking the Manual Actions report and the Security Issues report whenever visibility falls sharply.

Once the cause is fixed, the route back is the same as for a new website. Submit the sitemap again, request indexing on the most important pages and, where a manual action applied, file a reconsideration request from the same report.

When the Website Is Indexed but Not Ranking

If the site: search shows your pages but customers still cannot find the website, the problem is relevance and competition rather than indexing. Being in the index only makes a page eligible to appear. Where it appears depends on how well it answers the search compared with the other pages competing for it.

Results also vary from person to person. Location, language settings and SafeSearch all change what Google shows, so a quick search on a colleague’s phone is not a reliable test of visibility. The Performance report in Search Console shows the queries a website appears for and its average position, which gives a far more accurate picture than individual searches.

The fix at this stage is a proper look at what ranks instead and why, starting with content, links and the technical foundations. Our guide to why an SEO audit matters explains what that review should cover and how to prioritise what it finds.

Priority Pixels runs technical SEO as its own discipline, with indexation control, JavaScript rendering and canonicalisation all part of its technical SEO services. Whoever does the work, run the checks above first, because many causes of a website missing from Google take minutes to fix once they are found.