Website not showing on Google: the five causes behind almost every case
When a website is not showing on Google, the cause nearly always falls into one of five groups. Knowing the group tells you where to look, and saves you from changing things that were never the problem.
Google's documentation describes search in three stages: crawling, indexing and serving. A missing site has failed at one of those stages, and it states that Google does not guarantee it will crawl, index or serve any page. Your job is to find which stage failed and remove the obstacle.
1. Not discovered yet
A new domain with no links and no Search Console setup may simply not have been crawled. Common in the first days or weeks after launch.
2. Blocked by the site
A noindex tag, a robots.txt rule, password protection, a firewall or a platform setting tells Google to stay away or keeps it out.
3. Crawled but not indexed
Google visited and decided the page was thin, duplicate or not worth storing, or it chose a different URL as the canonical version.
4. Penalised or unsafe
A manual action for spam, or a hacked site flagged in the Security issues report, can remove pages or whole sites from results.
5. Indexed but not ranking
The pages are in Google, but not for the searches you tried. This is a ranking problem, not an indexing one, and needs different work.
The rest of this guide walks through how to tell which one you have. If you would rather not do it yourself, send us the domain and we will check.
How to check if Google has indexed your website: the site: test
Type site:yourdomain.com into Google, with your real domain and no space after the colon. Google's SEO Starter Guide suggests exactly this to see whether a site is in the index. The number and type of results tell you which branch of the diagnosis to follow.
The site: search is a rough tool. The result count is an estimate and not every indexed page is always shown. For a definitive answer about a specific page, use the URL Inspection tool in Google Search Console. But as a first five-minute check, site: is enough to separate the main cases.
- Zero results: nothing is indexed. Check for blocks, a new domain, or a removal request
- Only the home page: Google found the domain but not the inner pages; check internal links and sitemap
- Old pages or an old design: Google has not recrawled recently, or the new pages are blocked
- Strange pages in other languages or selling things you never sold: the site may be hacked
- Plenty of results but none for your service searches: indexing is fine; ranking is the issue
Try the test with and without “www”, since some sites have one version indexed and the other blocked.
Website not showing on Google even when searching its own name
If your site does not appear even for your exact business name, the problem is almost always indexing, not competition. A site that is indexed and has its name on the home page usually appears for that name unless the name is a common word or shared with a much larger brand.
Check the site: test first. If it returns nothing, jump to the sections on noindex, robots.txt and new domains. If it returns pages, look at the name itself. A business called “Sunrise” or “Classic” competes with thousands of pages using the same word, so try the name plus your city or trade. If that finds you, the site is fine; the name is simply ambiguous.
A few other signals help Google connect a name to your site. Put the full business name clearly on the home page, in the title tag and in WebSite structured data. Google's documentation on site names says adding WebSite structured data with a name property on the home page is the most effective way to indicate your preferred site name. Link your Google Business Profile to the site and keep the name identical everywhere.
- Business name in the home page title and main heading
- WebSite and Organization structured data with the exact name
- Business Profile linked to the website with the same name
- Social profiles and directory listings linking to the domain
Is a noindex tag the reason your website is not showing on Google?
Very often, yes. When we investigate a website not showing on Google, a noindex instruction is the first thing we look for. A noindex, in a meta tag in the page head or in an X-Robots-Tag HTTP header, tells Google not to keep the page in its index. It is a frequent culprit when a finished site is missing, usually left behind from the staging version.
To check, open a page, view the source and search for “noindex”. Also check the HTTP headers, since some servers and security plugins send X-Robots-Tag: noindex without anything visible in the page. The URL Inspection tool in Search Console reports whether indexing is allowed and, if not, why.
On WordPress, look under Settings, then Reading, for the box labelled “Discourage search engines from indexing this site”. When it is ticked, the whole site asks not to be indexed. SEO plugins such as Yoast or Rank Math also let individual post types, categories or pages be set to noindex, and a wrong default there can hide every product or every service page at once.
After removing the block, request indexing for the key pages in Search Console and resubmit the sitemap. Google has to recrawl each page to see the change, so it is not instant.
WordPress sites have several places a stray noindex can hide; our WordPress SEO services page lists them.
Can robots.txt leave a website not showing on Google?
Yes, though not always in the way people expect. A robots.txt file controls crawling, not indexing. A line such as “Disallow: /” stops Googlebot from fetching any page, so Google cannot read your content, but Google's own robots.txt documentation says a blocked URL can still appear in results without a description.
That same documentation is explicit that robots.txt is not a mechanism for keeping a page out of Google; to keep a page out, Google says to use noindex or password protection. So robots.txt produces two confusing symptoms: pages missing from results because Google cannot crawl them, or pages listed with a note that no information is available.
Check yourdomain.com/robots.txt in a browser. A disallow-all rule left from development is common, and so is a rule that blocks the folder holding your CSS or JavaScript, which can stop Google rendering pages properly. Search Console's robots.txt report shows which version Google fetched and when.
One trap to avoid: if a page is blocked in robots.txt and also carries a noindex tag, Google cannot see the noindex because it cannot crawl the page. To remove pages from the index, allow crawling and use noindex; to get pages indexed, remove the disallow rule.
Reading Search Console when your website is not showing on Google
Google Search Console is free and it is the only place Google tells you directly why pages are excluded. If your site is not verified there yet, that is the first fix. Verify the domain property so all versions, with and without www and on http or https, are covered.
The Page indexing report groups every known URL as indexed or not indexed, and gives a reason for each excluded group. Reading those reasons correctly is most of the diagnosis. Some are harmless, such as redirected URLs or alternate pages with a proper canonical. Others point straight at the cause.
Excluded by ‘noindex’ tag
Pages carry a noindex instruction. Fine for thank-you pages; a problem for service pages.
Blocked by robots.txt
Crawling is disallowed. Check whether the rule is intended.
Crawled – currently not indexed
Google read the page and chose not to store it for now, often a quality or duplication signal.
Discovered – currently not indexed
Google knows the URL but has not crawled it yet, often because of weak internal links or server limits.
Duplicate, Google chose different canonical than user
Google treats the page as a copy of another URL and indexes that one instead.
Not found (404) and Server error (5xx)
Broken or unavailable pages, often after a redesign or during hosting problems.
The two “currently not indexed” statuses are common enough to have their own page: crawled, currently not indexed.
New site or penalised site: how to tell which one you have
Look at the history of your website not showing on Google. A site that has never appeared on Google is almost never penalised; it is new, blocked or not yet trusted. A site that used to appear and then vanished suddenly is the one to check for a manual action, a security problem or a technical change.
In Search Console, open Security and Manual Actions. The Manual actions report lists any action a Google reviewer has applied for spam policy violations, such as unnatural links or thin, auto-generated content, and says whether it affects the whole site or some pages. The Security issues report shows hacked content, malware or deceptive pages. If both say no issues detected, a penalty is very unlikely.
A manual action needs the problem fixed and a reconsideration request explaining what you did. A security issue needs the site cleaned, the entry point closed and a review request. Neither is solved by waiting. For a new site, by contrast, waiting a short while after fixing blocks is reasonable, because Google has to discover and assess the domain.
- Never appeared, new domain: check blocks, links and Search Console setup
- Never appeared, older domain: check noindex, robots.txt and canonicals
- Appeared, then vanished overnight: check manual actions, security, recent changes
- Appeared, then faded over weeks: likely ranking changes, not removal
If a manual action is listed, our Google penalty recovery page explains the clean-up and reconsideration process.
Could someone have removed your website from Google?
It is an easy cause to overlook, and it produces a website not showing on Google for no obvious reason. Search Console's Removals tool lets anyone with owner access hide URLs from Google results, and a previous developer or an overzealous staff member may have used it on a whole folder or even the whole site while testing.
Google's Search Console help says a successful temporary removal lasts only about six months, and that the tool alone does not remove a URL permanently. That means a removal can hide pages for months and then they reappear, which confuses everyone. Open Index, then Removals, in Search Console and check for any active requests. If one covers pages you want in search, cancel it.
While you are there, check who has access. Settings, then Users and permissions, lists every account. Remove anyone who no longer works with you, and make sure the business, not a former freelancer, is the owner of the property.
Related situations: an expired domain or lapsed hosting plan makes the site unreachable, and Google drops pages it cannot fetch over time. If your domain registration or hosting renewal was missed, even briefly, that can explain a sudden disappearance.
Server, hosting and JavaScript causes of a website not showing on Google
Sometimes the site looks perfect in your browser but Google sees something else. Firewalls, bot-protection services and security plugins can block or challenge Googlebot, some hosting plans block traffic from outside India, and a slow or overloaded server returns errors when Google visits.
Use URL Inspection's live test to see what Google actually fetches. If the test fails or the screenshot is blank, the problem is between your server and Google. Check firewall and CDN settings for bot rules, look at the Crawl stats report under Settings for server errors, and ask your host whether any country or bot blocking is active.
JavaScript sites are a separate case. A React, Angular or Vue app that builds everything in the browser may send an almost empty HTML page, and Google has to render the JavaScript to see content. That adds delay and sometimes fails. Compare the page source with the rendered HTML in URL Inspection; if key text and links are missing from the source, moving to server-side rendering or static generation usually solves it.
- Bot protection or firewall rules challenging Googlebot
- Geo-blocking that stops visits from outside India
- Frequent 5xx errors in the Crawl stats report
- Content and links that exist only after JavaScript runs
- Very slow responses that make Google crawl less
Moving a React app to server rendering is covered on our React to Next.js migration page.
Wrong canonical tags and duplicate versions of your site
A canonical tag tells Google which URL is the main version of a page. If every page on your site points its canonical at the home page, or at the staging domain, or at an old URL, Google may index only that one address and ignore the rest.
This happens with copied templates and badly configured plugins. A developer copies a page, the canonical tag comes along unchanged, and suddenly twenty service pages all claim to be the same URL. Or a site moves from a test domain and every canonical still names the test domain.
Duplicate domain versions cause a milder version of the same problem. If your site works at http and https, with and without www, and none of them redirect to one preferred version, Google has to pick one and may split signals between them. Choose one version, redirect the others to it with permanent redirects, and make sure canonicals, sitemap and internal links all use it.
URL Inspection shows both the canonical you declared and the one Google selected. If they differ on important pages, that is a sign Google sees those pages as duplicates, and the content or tags need work.
Indexed but not ranking: when the site is on Google but nobody finds it
If site: shows your pages but you still cannot find yourself for “dentist in Andheri” or “steel almirah manufacturer”, the site is indexed. The problem is ranking, and that needs a different kind of work: better pages, a clearer match to the search, stronger signals from other sites and, for local businesses, a Business Profile.
Check Search Console's Performance report. It shows the searches your pages already appear for, how often, and at what average position. Often a site is on page two or three for its main searches, which feels like invisible but is actually close. Tightening the page title, answering the search more directly and adding internal links can move those pages up.
Also be honest about what you are searching. Your own browser personalises results, and searching from your office may show different map results from a customer across town. Use Search Console data rather than your own searches to judge visibility.
For ranking work on existing pages, see on-page SEO services; for a small local business, SEO services for small business sets out where to start with a limited budget.
Business not showing on Google Maps even though the website is indexed
Google Maps and the local pack run on your Google Business Profile, not on the website. A site can be fully indexed while the business is missing from the map, and a business can appear on the map with no website at all.
Check that the profile exists, is verified and is not suspended. Search your exact business name on Google Maps; if you see nothing, the profile may be unverified, marked as closed, or suspended. If you see it but not for service searches, the issue is local ranking. Google's Business Profile help says local results are mainly based on relevance, distance and prominence, and that there is no way to pay for a better local ranking.
Common fixes include choosing a more precise primary category, completing services and hours, adding real photos, building reviews steadily and making sure name, address and phone match the website exactly. Profiles suspended for guideline issues need a reinstatement request with evidence.
See a suspended Business Profile for reinstatement, or Google Map par dukan kaise dale for adding a shop from scratch.
Each platform has its own switch that can hide a whole site, and a site-wide disappearance often traces back to one of these being in the wrong position. Check yours before anything else.
WordPress
Settings → Reading → “Discourage search engines from indexing this site” must be unticked. Then check SEO plugin defaults for noindex on posts, pages, products or categories, and any maintenance or coming-soon plugin that may still be active.
Shopify
A store with password protection switched on is hidden from visitors and search engines. Remove the storefront password once you are ready to sell, and check that themes or apps have not added noindex tags.
Wix and Squarespace
Both have a site-level setting that decides whether search engines may index the site; on Wix it is a toggle in the SEO settings, on Squarespace an option to hide the site from search engines. The site also has to be published and free of a site-wide password.
Blogger
Settings include a visibility option for search engines, and custom robots header tags can add noindex. Blogs switched to private are not indexed.
Custom React, Angular or PHP sites
Look for noindex in the base template, disallow rules in robots.txt, environment variables that switch on staging mode, and content that only appears after JavaScript runs.
How long until a website shows on Google after the fix?
Once the obstacle is removed, key pages often reappear within days to a couple of weeks, but it depends on how often Google crawls the site and how many pages need reprocessing. Google's Search Console help says requesting indexing does not guarantee inclusion and that indexing can take a week or two.
Speed it up sensibly. Request indexing for the handful of most important URLs in URL Inspection; Google notes there is a daily limit on these requests, so do not try to submit every page by hand. Resubmit the sitemap so Google sees the full list, and make sure the key pages are linked from the home page and navigation.
A manual action or security issue takes longer, because a reviewer has to process the reconsideration or review request after you have fixed the problem. A brand-new domain may take longer too, because Google has to decide how much to crawl it.
Keep checking the Page indexing report weekly. You should see the “not indexed” count for the fixed reason fall and the indexed count rise. If nothing changes after a few weeks, something else is still blocking the pages and the diagnosis needs another look.
Worked example: a clothing site missing from Google after launch
This is a hypothetical scenario to show how a diagnosis of a website not showing on Google runs, not a client story. Say a chikankari kurta seller in Lucknow launched a new React storefront two months ago. Orders come only from Instagram, and searching the brand name on Google shows nothing but the Instagram profile.
Step one, the site: test, returns only the home page. Step two, URL Inspection on a product page, shows the page is allowed to be indexed but the rendered HTML contains almost no product text: the catalogue loads from an API after the page opens. Step three, the Page indexing report lists most product URLs as “Discovered – currently not indexed”, which fits a site whose links Google cannot easily follow.
Checking the source also shows every page's canonical tag pointing to the home page, a leftover from the template. So there are two problems stacked: thin initial HTML and a canonical telling Google that every page is really the home page.
The fix is to render product and category pages on the server with real links in the HTML, correct the canonicals so each page names itself, add Product structured data and resubmit the sitemap. Over the following weeks the product pages would be expected to move into the indexed group, after which the work shifts to ranking: category content, product descriptions and links from fashion blogs and marketplaces the brand already sells on.
Our done-for-you fix when your website is not showing on Google
If you would rather hand it over, send us the domain on WhatsApp. We ask for user access to Search Console, never the password to your Google account, and read-only or limited access to the CMS or code if the fix needs it. Another of us leads the technical diagnosis; one of us makes any template or code changes; the third of us keeps you updated on what was found and when.
You receive a short written diagnosis: which of the five causes applies, the evidence from Search Console and the live test, and the fix. We quote the fix as a one-off job in about two working days and start only after you approve it in writing. Payments in India are by UPI or bank transfer; international clients pay in USD by Wise, wire or PayPal.
After the fix, we watch the Page indexing report until the key pages are indexed, and tell you plainly if something else turns up. If you then want to work on rankings and enquiries, monthly SEO starts at ₹10,000/mo, but it is not a condition of the fix.
- Written diagnosis with evidence, not a generic tool report
- Fixes made in your templates, settings or server configuration
- Key URLs inspected and indexing requested after the fix
- Follow-up checks until the indexed count recovers
- Everything stays in your accounts and your code
Want the full picture of your site's health too? An SEO audit covers content, speed and links as well as indexing.