Website Not Showing on Google? 8 Checks to Run
Most sites missing from Google are blocked, not broken: a robots.txt, noindex, redirect or sitemap. Eight checks in order, with a free tool for each.

The short answer
A website that does not show on Google is almost always in one of two states: Google has not found it yet, or something on the site is telling Google not to index it. The fastest way to tell which is to run a site: search for your domain and then paste your home page into the URL Inspection tool in Google Search Console.
This page walks through the eight checks we would run, in the order that finds the cause quickest, and names the free tool for each. Start with the robots.txt checker, because a leftover Disallow: / from a staging site is the most expensive mistake on the list and takes thirty seconds to rule out. If the checks find a problem you do not want to fix yourself, our SEO and digital marketing service starts with exactly this audit.
First decide which problem you have
"Not showing on Google" covers three situations that have different fixes. Work out which one is yours before you touch anything.
| What you see | What it means, and where to look |
|---|---|
site:yourdomain.com returns nothing | Not indexed: Google has not found it, or it is blocked. Checks 2 to 7. |
| Your pages are indexed, but not for the words you expected | Indexed, not ranking for that query. Check 8. |
| You used to appear and now do not | Something changed: a deploy, a migration, a setting. Checks 2 to 5, then the migration note in check 4. |
Check 1: Is it really missing?
Search for site:yourdomain.com in Google. Google's own guide to getting a site into search describes the same test, with one caveat that matters: the site: operator does not necessarily return all the URLs that are indexed, so a short list is not proof of a problem. Treat it as a quick signal and confirm with the real source.
The real source is the URL Inspection tool in Google Search Console. Enter a full page address and it tells you whether the URL is on Google, when it was last crawled, whether crawling is allowed by robots.txt, whether indexing is allowed, and which canonical Google chose. Two of those lines (crawl allowed, indexing allowed) answer checks 2 and 3 directly, so look there first.
If you have not added the site to Search Console yet, do it now. It is free, and every later step depends on it.
A new site is a different case. Google says it can take a few weeks for Google to notice a new site, so if yours is days old, the answer may be patience plus checks 5 and 7.
Check 2: Is robots.txt blocking Google?
The file at yourdomain.com/robots.txt tells crawlers which parts of the site they may fetch. The classic accident is a development or staging site that launches with Disallow: / still in place, which asks every crawler to stay away from everything.
Run your domain through the robots.txt checker. It fetches the live file, lists the rules for each user-agent and flags a site-wide block. You are looking for a User-agent: * group containing Disallow: / with nothing after the slash.
Two things worth knowing. First, Google says robots.txt is not a mechanism for keeping a page out of Google; it manages crawling. Second, the same rule works against you in one specific way, covered next.
Check 3: Is something telling Google not to index?
A noindex directive keeps a page out of the index, and it can be placed in two spots. As Google's block-indexing documentation explains, it is either a <meta name="robots" content="noindex"> tag in the page's head or an X-Robots-Tag: noindex response header.
- The meta tag. Open the page, view source and search for
noindex. - The header. Enter the page in the HTTP header checker, which lists every response header. A header is invisible in the page source, which is why it catches people out, and it is common on PDFs and on sites behind certain proxies.
- The CMS switch. WordPress has a Settings, Reading option called "Discourage search engines from indexing this site". Since version 5.3, ticking it adds a
noindex,nofollowrobots meta tag to every page. Developers tick it during a build and forget to untick it at launch.
The interaction with check 2 is the trap. For noindex to work, Google says the page must not be blocked by robots.txt, because a blocked crawler never reads the tag. If you want a page out of Google, use noindex and let it be crawled. If your problem is the opposite, remove the noindex and confirm the URL Inspection tool says indexing is allowed.
Check 4: Does the address you gave Google actually load?
A site can answer on four addresses: http:// and https://, with and without www. If the wrong one is the one Google knows about, or the chain between them is broken, pages are discovered and then dropped.
Trace the address with the redirect checker. It follows up to ten hops and shows each URL, status code and timing. You want one permanent redirect to a single preferred address and then a 200. Watch for a loop, a long chain, a redirect to a login page, or a temporary redirect that was meant to be permanent.
Also look at the canonical. A rel="canonical" link that points at a different page, or at a staging domain, asks Google to treat that other URL as the real one. In Search Console this shows up as Duplicate, Google chose different canonical than user, and the fix is to point the canonical at the page itself. Our note on moving a site without losing search traffic covers the redirect mapping in detail.
Check 5: Does the sitemap work?
A sitemap is a list of the URLs you want crawled. Google says it is useful when a site is new and has few external links, and also says plainly that a sitemap does not guarantee that the items in it will be crawled and indexed. It helps discovery; it is not a command.
Check that yours exists and parses with the sitemap checker. It confirms the file is a valid sitemap, counts the entries and samples the first URLs, so you can see at a glance whether the list contains the pages you care about or a thousand tag archives. Then submit it in Search Console under Sitemaps. If you do not have one, the sitemap generator will build one for a small site.
Make sure the sitemap lists the same address form your redirects settle on. A sitemap full of http:// URLs on a site that redirects to https:// hands Google a thousand redirects instead of a thousand pages.
Check 6: Found, but not indexed
If the URL Inspection tool says the URL is not on Google, the reason is often named in the Page indexing report. Two statuses cause most of the confusion, and Google defines them in its page indexing report help:
- Discovered, currently not indexed: "The page was found by Google, but not crawled yet."
- Crawled, currently not indexed: "The page was crawled by Google but not indexed."
The first is about priority and access: Google knows the URL exists and has not fetched it. Make the page easier to reach by linking to it from pages that are already indexed, and check the server is not slow or returning errors. The second is about the page itself: Google looked and chose not to keep it. Thin pages, near-duplicates and pages that add nothing the site does not already say are typical. The fix is to make the page worth keeping, not to resubmit it.
The same report lists the technical reasons by name: server errors, redirect errors, soft 404s, 403 and 404 responses, noindex and robots.txt blocks. If your URL is in one of those, you have found the cause.
Check 7: Does anything link to it?
Google's own list of reasons a site is missed starts with the site not being linked to by other sites on the web. A brand-new domain with no inbound links, and pages that are not linked from your own navigation, are hard for a crawler to find. Three practical steps:
- Link every important page from at least one other page that is already indexed, using a descriptive anchor.
- Make sure the pages you care about are reachable by ordinary links in the HTML, not only through a script or a search box.
- Get your business listed where a real link is natural: a supplier, a chamber or association, a profile you control. Google warns against buying links, and we agree.
Check 8: Indexed, but not for the words you expected
If site: shows your pages, the problem is no longer indexing. It is relevance and competition, and the question changes from "is Google blocked?" to "what did people actually type?"
Open the Performance report in Search Console and look at the queries your pages already appear for. Three patterns are common:
- No impressions at all for the phrase you wanted. The page does not say that phrase or answer that question. A page titled "Welcome" cannot match a search for a service, a city or a product.
- Impressions, but a position far down the list. You are indexed and being outranked. The fix is a better, more specific page, not a technical one. We cover the shape of such pages in local business website design.
- Good position, few clicks. The title and description are the problem. Rewrite them so a stranger can tell what they will get.
Nobody can promise you a position, and anyone who does is guessing. What can be promised is a measured audit, fixes you can verify and reports from Search Console.
After you fix it
Once the cause is fixed, use the URL Inspection tool's Test live URL to confirm Google can now fetch and index the page, then Request indexing. Be realistic about timing. Google says crawling can take anywhere from a few days to a few weeks, that requesting a recrawl more than once for the same URL does not make it faster, and that there is a quota for individual submissions. Submit once, then watch the Page indexing report rather than resubmitting.
When to hire someone
Fix it yourself when the cause is a single switch: a robots.txt line, a WordPress setting, one sitemap. Bring in help when:
- the checks above find several problems at once;
- the site was recently rebuilt or moved and rankings fell;
- you cannot get at the DNS, hosting or CMS because they belong to a previous developer (start with getting your website back from a previous developer);
- the site is indexed but the real work is content that matches what your customers type.
The SEO and digital marketing service covers technical fixes, structured data, content for real queries and Search Console reporting. If the cause turns out to be a broken page, a certificate or a server problem, website fixes and maintenance handles that side. You can also run our website health checker first, and bring the report with you.
Frequently asked questions
Why is my website not showing up on Google?
Usually because Google has not found it yet, or because something tells it not to index the site: a robots.txt block, a noindex tag or header, or a canonical pointing elsewhere. Use site: plus the URL Inspection tool to see which, then work through the checks above.
How long does it take for a new website to show on Google?
Google says it can take a few weeks for it to notice a new site, and crawling after a request can take anywhere from a few days to a few weeks. Submitting a sitemap and linking to the site from elsewhere helps discovery, but does not set a deadline.
How do I check if my website is indexed?
Search site:yourdomain.com for a quick view, then use the URL Inspection tool in Google Search Console for an exact answer on any page. The site: search does not necessarily list every indexed URL, so rely on Search Console for a verdict.
Why is my site indexed but not ranking?
Being indexed only means Google stored the page. Ranking depends on how well the page answers the query compared with other pages. Check the Performance report for the queries you appear for, then improve the page that should match.
Does a sitemap guarantee indexing?
No. Google says a sitemap does not guarantee that the items in it will be crawled and indexed. It helps Google discover pages, which is most useful for new sites with few links.
How do I know if I blocked Google by mistake?
Run your domain through a robots.txt checker for a site-wide Disallow: /, check the page source and response headers for noindex, and look at the Crawl allowed and Indexing allowed lines in the URL Inspection tool.
Why did my website disappear from Google?
After a rebuild or a move, the usual causes are a staging robots.txt or noindex that went live, a redirect map that was not carried over, or a changed address form. Check those first, in that order.
Tools mentioned in this post
- Robots.txt CheckerFetch and lint any site’s robots.txt: catch the Disallow that deindexes you.
- HTTP Header CheckerInspect any URL’s response headers and get a security-header report card.
- Redirect CheckerFollow a URL’s full redirect chain hop by hop: statuses, targets and timing.
- Sitemap CheckerValidate any sitemap.xml live: type, URL count and the errors crawlers would hit.


