Why Is My Website Not Showing on Google? 10 Fixes

A website not showing on Google is almost always caused by one of a small number of problems: Google has not found the site yet, something is telling Google to stay away, Google has chosen not to index certain pages, or the pages are indexed but rank too low for the searches you are trying. This guide gives you a decision tree to find which one applies, then walks through ten causes with the symptom, the diagnosis and the fix for each.

Quick answer: Search “site:yourdomain.com” on Google. If nothing appears, check for a noindex tag, a robots.txt block, a password wall or server errors, then submit a sitemap in Google Search Console. If pages appear but not for your keywords, the issue is ranking, not indexing, and requires better content, links and local signals.

Website not showing on Google: is it not indexed or not ranking?

The first step is separating two different problems that look identical from the outside. Indexing means Google has stored your page and can show it in results. Ranking means where your page appears for a particular search. A page can be indexed and still sit on page five for the phrase you care about.

Think of Google’s index as a library catalog. If your book is not in the catalog, nobody can find it no matter what they search. If it is in the catalog but filed under a vague title on a crowded shelf, people can find it only if they search for its exact name. Causes 1 to 9 below are catalog problems. Cause 10 is a shelf problem.

Start here: a five-minute diagnostic decision tree

This decision tree tells you which of the ten causes to investigate first. Work through it in order and stop at the first branch that matches your situation.

START: Search Google for  site:yourdomain.com
|
+-- No results at all
|     |
|     +-- Site launched in the last few weeks?
|     |     YES -> Cause 1 (not discovered yet)
|     |     NO  -> Check page source for "noindex" ........ Cause 2
|     |            Check yourdomain.com/robots.txt ......... Cause 3
|     |            Open site in a private window ........... Cause 4
|     |            Search Console > Manual actions ......... Cause 9
|
+-- Some pages appear, but important ones are missing
|     |
|     +-- Inspect the missing URL in Search Console
|           "URL is not on Google" + reason shown:
|             URL marked 'noindex' ................... Cause 2
|             Blocked by robots.txt .................. Cause 3
|             Server error / 401 / 403 / 404 ......... Cause 4 or 8
|             Duplicate / canonical issue ............ Cause 5
|             Crawled or Discovered, not indexed ..... Cause 6
|             Indexed, but content looks empty ....... Cause 7
|
+-- Pages appear for site: and your brand name,
      but not for your target keywords ............... Cause 10

Two notes before you begin. First, the site: search is a rough check, not a complete list, so use it for direction rather than precise counts. Second, if you have not set up Google Search Console yet, do it now: verify ownership of your domain, then open the URL Inspection tool and the Page indexing report. Almost every diagnosis below depends on them.

1. Has Google simply not discovered your website yet?

A brand-new website often does not show on Google because Google has not found it yet. Google discovers pages mainly by following links from pages it already knows and by reading sitemaps you submit. A new domain with no inbound links and no sitemap can sit unnoticed.

Symptom: the site launched recently, site: returns nothing, and Search Console shows few or no pages in the Page indexing report.

How to diagnose:

• Check your launch date. If it was within the last few weeks, this is the likeliest cause.
• Inspect your homepage URL in Search Console. A status saying the URL is unknown to Google confirms it has not been discovered.
• Check whether any other website links to you, including your social profiles and business directories.

Fix:

1. Verify the site in Google Search Console.
2. Submit your XML sitemap in the Sitemaps report. Most platforms generate one automatically, often at /sitemap.xml.
3. Inspect your homepage and key service pages, then click request indexing once for each.
4. Earn a few genuine links: your social profiles, partner websites, local chambers of commerce or industry directories.

Patience matters here. Our guide to how long SEO takes to work explains why early weeks are mostly about discovery rather than traffic.

2. Is a noindex tag telling Google to stay away?

A noindex directive is an instruction that tells search engines not to include a page in their results, and it overrides almost everything else. It often gets left behind when a site moves from a staging environment to the live domain.

Symptom: the whole site, or specific templates, are missing even though the site has been live for weeks. Search Console may report “URL marked ‘noindex'”.

How to diagnose:

• View the page source and search for noindex. Look for a robots meta tag in the head.
• Check the HTTP response headers for an X-Robots-Tag: noindex header, which some servers and plugins add.
• On WordPress, open Settings, then Reading, and look at the “Search engine visibility” option. If “Discourage search engines from indexing this site” is ticked, WordPress adds noindex to every page.
• Check your SEO plugin’s settings for page types set to noindex, such as categories or entire post types.

Fix: remove the noindex directive from every page you want indexed, clear any caching layer, then inspect the live URL in Search Console to confirm the tag is gone before requesting indexing.

3. Is robots.txt blocking Google from crawling your pages?

A robots.txt file is a plain text file at the root of your domain that tells crawlers which paths they may and may not access. A single misplaced line can block an entire site.

Symptom: pages are missing, or appear in results with no description. Search Console may show “URL blocked by robots.txt” or the warning “Indexed, though blocked by robots.txt”.

How to diagnose:

• Visit yourdomain.com/robots.txt in a browser.
• Look for Disallow: / under User-agent: * or User-agent: Googlebot. That line blocks everything.
• Look for disallow rules covering important folders, such as /blog/ or /products/.

Fix: edit the file so it only blocks genuinely private areas, such as admin or cart paths. Remember a subtle trap: if a page is blocked in robots.txt, Google cannot crawl it to see a noindex tag. If you want a page removed from results, allow crawling and use noindex instead of blocking it.

4. Is your site behind a password, a login or failing with server errors?

Google can only index what it can load. Password-protected staging sites, maintenance-mode plugins, firewall rules and unreliable hosting can all return errors to Googlebot even when the site looks fine to you.

Symptom: Search Console reports “Server error (5xx)”, “Blocked due to unauthorized request (401)”, “Blocked due to access forbidden (403)” or “Redirect error”.

How to diagnose:

• Open the site in a private browser window while logged out. Do you hit a login screen or a “coming soon” page?
• Use the test live URL option in URL Inspection to see the exact response Google receives.
• Check with your host or security plugin for rules that block unfamiliar bots or entire countries.
• Review uptime monitoring for frequent outages.

Fix: remove password protection and maintenance mode from the live site, allowlist legitimate search engine crawlers in your firewall, and move to more reliable hosting if errors are frequent. Slow, unstable servers also hurt visitors, which is one reason a full technical SEO audit checks server response alongside indexing.

5. Is Google treating your pages as duplicates?

Google picks one version of duplicate or near-duplicate pages as the canonical (the main version) and usually indexes only that one. If your site exists at several addresses, or you have many similar pages, the version you care about may be the one left out.

Symptom: Search Console shows “Duplicate without user-selected canonical”, “Duplicate, Google chose different canonical than user” or “Alternate page with proper canonical tag” for pages you expected to rank.

How to diagnose:

• Check whether your site loads at http://, https://, www and non-www versions without redirecting to one.
• Look at the canonical tag in the page source. Does it point to itself, or somewhere unexpected?
• Compare similar pages, such as location pages with only the city name changed, or products with near-identical descriptions.

Fix: redirect all versions of your domain to one preferred version, make each canonical tag point to the correct URL, and either merge near-duplicate pages or rewrite them so each offers something distinct.

6. Has Google crawled your pages but decided not to index them?

Google does not index every page it finds. The statuses “Crawled – currently not indexed” and “Discovered – currently not indexed” mean Google knows the page exists but has not added it to the index, at least for now. This is common with thin, repetitive or low-value pages, and on new sites with little authority.

Symptom: a large share of your pages sit in these two statuses, often blog tag pages, short service pages or auto-generated content.

How to diagnose:

• Read the affected pages honestly. Would a searcher learn anything here that they could not find on a hundred similar pages?
• Check how many internal links point to them. Pages buried deep with no links look unimportant.
• Look for patterns: are they all one template, such as tag archives or filtered product lists?

Fix: improve or consolidate rather than resubmit. Expand thin pages with original detail, merge overlapping posts, noindex low-value archives, and link to important pages from your main navigation and related content. Show who wrote the content and why they are qualified, as our guide to E-E-A-T describes. Organizing content into topic clusters and pillar pages also gives Google clearer signals about which pages matter most.

7. Is your content hidden behind JavaScript that Google cannot render?

Some websites load their main content with JavaScript after the initial page loads. Google can render JavaScript, but errors, blocked resources or content that only appears after a click can leave Google seeing an almost empty page.

Symptom: pages are indexed but do not appear for phrases clearly on the page, or Search Console warns “Page indexed without content”.

How to diagnose:

• In URL Inspection, run a live test and view the tested page’s rendered HTML and screenshot. Is your main text there?
• Check whether scripts, stylesheets or API endpoints are blocked by robots.txt.
• Disable JavaScript in your browser and reload. If the page is blank, you depend entirely on rendering.

Fix: have your developer render key content on the server or at build time, unblock required resources, and make sure navigation uses real links rather than click handlers. This is especially important for single-page applications built with modern frameworks.

8. Did a redesign or migration break your URLs?

A redesign or platform change can make a website disappear from Google if old URLs stop working without redirects. Every ranking page that now returns a 404 loses the position it had earned.

Symptom: traffic dropped right after a relaunch, and Search Console shows a spike in “Not found (404)” or “Page with redirect” statuses.

How to diagnose:

• Compare a list of old URLs (from an old sitemap, analytics or Search Console’s performance report) against the new site.
• Test a sample of old URLs. Do they redirect to the most relevant new page, or land on a 404 or the homepage?
• Check for redirect chains and loops.

Fix: map every old URL to its closest new equivalent with a permanent 301 redirect, update internal links, and submit the new sitemap. If you are planning a relaunch, follow our website redesign checklist to avoid this problem entirely.

9. Has Google applied a manual action or flagged a security issue?

A manual action is a penalty applied by a Google reviewer when a site breaks Google’s spam policies. Security issues, such as a hacked site serving spam, can also remove or warn against your pages. Both are rare for ordinary businesses, but they are serious.

Symptom: a sudden, site-wide disappearance, or search results showing a warning that the site may be hacked.

How to diagnose: open the Manual actions report and the Security issues report in Search Console. Each tells you whether an issue exists and gives examples of affected pages.

Fix: follow the instructions in the report. For manual actions, remove the violating content or links, document what you changed, and submit a reconsideration request. For hacking, clean the site, close the vulnerability, change all passwords, update software and request a review.

10. Is your site indexed but not ranking for the keywords you search?

If your site appears for a site: search and for your exact business name, it is indexed. The problem is visibility for competitive keywords, which depends on relevance, content quality, authority and, for local searches, proximity and your Google Business Profile.

Symptom: you can find your site only by typing your brand name, or it appears on page three or beyond for your main service.

How to diagnose:

• Open the Performance report in Search Console and look at the queries you already appear for and their average position.
• Check whether you have a dedicated page for each core service and location, or one general page trying to rank for everything.
• Search your target phrase and study the top results. What do they cover that you do not?
• Note your search location. Local results change block by block.

Fix: build a dedicated, genuinely helpful page per service, write titles that match how customers search, earn relevant links and mentions, and improve page experience. For searches with local intent, a complete profile matters as much as your website, so work through our Google Business Profile optimization tips and the local SEO checklist.

Quick reference: causes, checks and fixes

This table summarizes the ten causes so you can share it with whoever manages your website.

How long after fixing will my site appear on Google?

Your site can reappear within days of a fix for simple problems like a removed noindex tag, but it may take several weeks for Google to recrawl every affected page. Google Search Central states that crawling can take anywhere from a few days to a few weeks, and that requesting a recrawl multiple times for the same URL will not make it faster.

A sensible routine after fixing an issue:

1. Confirm the fix with a live test in URL Inspection.
2. Request indexing once for your most important pages.
3. Resubmit your sitemap if many URLs were affected.
4. For issues listed in the Page indexing report, use the validate fix option.
5. Check progress weekly rather than daily.

How can you stop this from happening again?

You can prevent most indexing problems by adding a few checks to your routine. Small sites need only a monthly review; sites that publish or change often benefit from weekly checks.

• Search Console email alerts are going to an inbox someone reads.
• Launch checklists include “remove noindex and staging passwords”.
• Robots.txt is reviewed whenever developers deploy major changes.
• The Page indexing report is reviewed monthly for new spikes.
• Every new page gets at least one internal link from a relevant page.
• Redirects are planned before any URL changes go live.
• CMS, plugins and themes are kept updated to reduce hacking risk.

Keep reading

Technical SEOCore Web Vitals 2026: How to Pass LCP, INP and CLSRead articleTechnical SEOTechnical SEO Audit Checklist: 25 Points to Check YourselfRead articleTechnical SEOSchema Markup for Beginners: Get Rich Results in GoogleRead article