If you are asking “why is my website not showing on google?”, run this five-minute check
A missing website usually falls into one of four states: Google cannot access it, Google is still processing it, the site is indexed but ranks too low or only its Google Business Profile is visible. Each state needs a different response.
Start with a site search, then inspect the exact homepage URL in Google Search Console. These checks tell you whether to wait, repair the launch or work on rankings. Buying an SEO campaign before making that distinction risks paying someone to investigate a release fault.
Search Google for:
site:yourdomain.co.uk
This is a quick signal because Google recommends the site: search when checking whether a website is indexed. It is still a clue rather than a final verdict, so follow it with URL Inspection in Search Console.
Use this decision tree:
- “URL is on Google” means the page is indexed and eligible to appear. It does not guarantee visibility for a particular search.
- “URL is not on Google” means you need to read the indexing reason shown underneath the status.
- No site results, with a visible Business Profile means the local listing and website need to be diagnosed separately.
- No blocker, with a recent submission usually means waiting is reasonable.
If you submitted the site less than a week ago and Search Console reports no blocking issue, leave it alone for now. Google recommends waiting at least one week after an indexing request or sitemap submission before treating continued absence as a fault.
Check the launch settings that commonly hide a website
Google sets a fairly low technical threshold. Googlebot must be allowed to access the page, the page must return HTTP 200 and it must contain indexable content. Meeting those requirements still does not guarantee indexing, but failing any of them gives Google a clear reason to stop.
Common launch mistakes include:
- A
noindexinstruction copied from the staging site - An
X-Robots-TagHTTP header that blocks indexing - Password protection left enabled
- A firewall or security tool blocking crawlers
- A private-store or maintenance setting
- A homepage returning an error or redirect loop instead of HTTP 200
- An empty client-rendered page that exposes little usable content to a crawler
A noindex instruction tells Google to leave a page out of its index. A robots.txt rule prevents crawling. They solve different problems: a robots.txt block makes appearance unlikely but does not reliably guarantee removal.
CMS launch settings to check
- WordPress: Go to Settings → Reading and untick “Discourage search engines from indexing this site”. WordPress generates a noindex directive when this option is enabled. This is one of the first places we look when a WordPress website is not showing on Google after launch.
- Wix: Enable “Let search engines index your site”. Wix requires this site-wide toggle to be enabled before the site is eligible to appear.
- Squarespace: Disable “Block Search engine crawlers” and check individual page visibility. The crawler block adds a site-wide Disallow rule, while “Hide page from search results” adds noindex.
- Shopify: Make the online store public. Shopify creates and updates
sitemap.xmlautomatically, although Google cannot access that sitemap while the store is private.
Fix the underlying setting before requesting indexing. A request cannot override a password, a server error or an instruction telling Google to exclude the page.
Use Google Search Console to find the actual reason
Verify the website in Search Console, then open URL Inspection. Inspect the precise public homepage address, including https:// and the correct www or non-www hostname.
If several versions redirect to one address, inspect the final destination. That is the canonical version Google should be evaluating.
Translate the report into an action:
| Search Console report | What to do |
|---|---|
| URL is on Google | Stop requesting indexing. Test the searches you expect to rank for. |
| Indexing allowed? No | Remove the noindex meta tag or HTTP header. This status means the page is returning a noindex directive. |
| Blocked from crawling | Review robots.txt, security rules, passwords and crawler restrictions. |
| Page with redirect | Confirm the redirect reaches the intended live page without loops or unnecessary hops. |
| Duplicate or canonical issue | Inspect the canonical target and check that internal links, redirects and sitemap entries agree with it. |
| No explicit blocker | Test the live URL, submit once and allow time for processing. |
Next, open the Page indexing report. If only one page is affected, investigate that URL. If most of the site is excluded for the same reason, treat it as a site-wide release problem.
Submit the XML sitemap rather than manually requesting every page. A sitemap gives Google a consistent list of the URLs you intend it to discover.
After fixing a blocker, use “Test live URL” and request indexing once. Crawling can take from a few days to a few weeks, and repeated requests do not make Google crawl the URL faster.
If the website was redesigned, check redirects first
When a site disappears after a redesign, we treat it as a migration problem until the evidence says otherwise. Looking only at the new homepage misses old service pages, articles and location URLs that Google previously knew.
Export or reconstruct the old URL list and compare it with the new site. Valuable old URLs should have one-to-one permanent redirects to their closest replacements. Sending every removed page to the homepage erases the relationship between the old content and its replacement.
Google recommends permanent 301 or 308 redirects retained for at least one year. Temporary search fluctuations during a move are normal. Missing redirects, staging noindex rules and production passwords are preventable release failures.
A proper migration checklist should cover:
- Old-to-new URL mapping
- Redirect status and destination checks
- Removal of staging restrictions
- Canonical tags on the new pages
- Updated internal links
- A new XML sitemap
- Search Console checks for both site-wide and page-specific errors
Careful redirect planning belongs in the web design and redesign process, before URLs change. When the fault sits in headers, routing or deployment configuration, it needs technical web development diagnosis rather than another round of copy changes.
What to do when the site is indexed but still does not appear
If URL Inspection says “URL is on Google”, you have moved from an indexing issue to a ranking issue. Another indexing request will not improve the page’s relevance for the search you are testing.
Search for the exact business name first. Then test broader phrases such as the service and town. A new site may appear for its distinctive name before it earns visibility for competitive commercial searches.
Review the homepage and important service pages for:
- A descriptive page title that names the service or business clearly
- One clear primary heading
- Useful information about the business, services and locations covered
- Crawlable internal links to important pages
- Specific copy instead of generic claims that could describe any competitor
- Consistent business names, addresses and contact details
- Relevant external mentions and links that help establish the business online
Thin, duplicated or near-identical location pages give Google little information to use when choosing a result. Strengthen the page that best answers the search instead of producing many weak variations.
You do not have to pay Google to be included in organic search results. Google Ads is a separate paid product. Technical eligibility, advertising spend and agency work cannot guarantee a particular organic position.
Why Google Maps can show your business while the website is absent
A Google Business Profile and a website are separate properties. They can appear together, but one does not prove that the other has been indexed or selected for a result.
| Google Business Profile | Website |
|---|---|
| A local listing shown in Search and Maps | A collection of URLs Google must crawl and index |
| Managed through the Business Profile | Diagnosed through Search Console |
| Can link to the business website | Can be indexed without appearing in the local map pack |
Google describes a Business Profile as a local listing displayed on Maps and Search that can include a website link. Its visibility does not establish that the linked site is indexed.
Check that the profile links to the correct live HTTPS address, especially after a domain change or redesign. Diagnose website indexing through URL Inspection rather than relying on the Business Profile dashboard.
Local results are mainly influenced by relevance, distance and popularity. Businesses cannot request or pay Google for a better local ranking. Normal organic results use a separate selection process, so strong map visibility does not guarantee a matching organic position.
When to wait, when to fix it and when to get help
Use the evidence from Search Console to choose the next action:
| What you find | Next action |
|---|---|
| Submitted within the past week, with no reported blocker | Wait and monitor Search Console. |
| Noindex, blocked access, password protection or a non-200 response | Fix the release configuration, then test the live URL. |
| Redirect, duplicate or canonical problem | Repair the implementation and make every signal point to the intended URL. |
| Site-wide exclusions in the Page indexing report | Check templates, headers, robots.txt and deployment settings. |
| URL is indexed but absent for broad searches | Work on page relevance, useful content, internal links and external business signals. |
| Visibility fell immediately after a redesign | Compare the old and new URL lists before changing content. |
If you need a developer to investigate, retain the inspected URL, its Search Console status, examples of affected pages, the sitemap address and the redesign or launch date. A useful diagnosis should reproduce the fault on a specific URL and name the setting, response or redirect that needs changing.
Run the free audit on your own site, or on a site you are authorised to test. It can identify likely crawl, indexing and implementation blockers. It cannot promise indexing, search positions or rankings.