Why Is My Website Not Showing Up on Google? 11 Causes and Fixes

Your website is not showing up on Google because Google has either not indexed it or indexed it without ranking it for the words you searched. Indexing problems come from settings that block Google (noindex tags, robots.txt, staging switches), from pages Google cannot read or does not value, or from penalties and hacks. Ranking problems are a separate issue, covered in cause 11.

How to check whether Google has indexed your website

Check in three places, from fastest to most precise.

1. Run a site: search. Type site:yourdomain.com into Google. Google's SEO Starter Guide (Google Search Central, 2025) uses this as the first test: results pointing to your site mean you are in the index. Zero results means nothing is indexed.
2. Inspect one URL in Search Console. Paste a page address into the URL Inspection bar at the top of Search Console. It reports "URL is on Google" or "URL is not on Google" with the reason, and the live test shows the page as Googlebot sees it.
3. Open the Page indexing report. This report groups every non-indexed URL by reason. Google Search Console Help (2026) lists reasons such as "URL marked 'noindex'", "URL blocked by robots.txt", "Crawled - currently not indexed" and "Duplicate, Google chose different canonical than user".

Write down the exact reason Google gives. Each reason maps to one of the causes below.

11 reasons your website is not showing up on Google

1. The site is new and Google has not crawled it yet

A new site stays out of Google until Googlebot finds a link or a sitemap pointing to it. The SEO Starter Guide (Google Search Central, 2025) states that Google discovers pages mainly through links from pages it has already crawled, that changes take "a few hours" to "several months" to show, and that there is no guarantee any site is added to the index.

Confirm it: URL Inspection says the URL is unknown to Google, or the Page indexing report shows "Discovered - currently not indexed".

Fix it with four steps:

• Verify the domain in Search Console.
• Submit an XML sitemap under Sitemaps.
• Request indexing for the homepage and your 5-10 most important pages in URL Inspection.
• Earn 2-3 links from sites Google already indexes, for example your Google Business Profile, an industry directory or a partner's website.

2. A noindex tag tells Google to leave the page out

A noindex rule removes a page from Google even when everything else is correct. Open the page, view the source, and search for noindex inside a <meta name="robots"> tag. Also check the HTTP response headers for X-Robots-Tag: noindex, which is invisible in the page source. Search Console labels these URLs "URL marked 'noindex'".

Remove the tag. The usual sources are an SEO plugin toggle set to "no" on a page, a theme template copied from a staging site, or a header rule added in the server configuration.

3. robots.txt blocks Googlebot from crawling

A Disallow: / rule under User-agent: * in robots.txt stops Google from crawling the whole site. Open yourdomain.com/robots.txt and read every Disallow line. Search Console reports these URLs as "URL blocked by robots.txt".

Delete the blocking rule. Do not combine robots.txt blocks with noindex to hide pages: according to Google Search Central (2025), Google never sees a noindex rule on a page that robots.txt blocks, so the page can still appear. Google's robots.txt introduction (Google Search Central, 2025) also states that robots.txt is "not a mechanism for keeping a web page out of Google".

4. A staging or privacy setting is still switched on

Site-wide switches used during development often survive the launch and block the entire website. In WordPress, go to Settings > Reading and look at "Discourage search engines from indexing this site". WordPress.org documentation (2024) confirms that since version 5.3 this box adds a noindex,nofollow robots meta tag to every page.

Check these other launch leftovers:

• Password protection at the server or host level, which Search Console reports as "Blocked due to unauthorized request (401)".
• "Coming soon" or maintenance-mode plugins that serve a placeholder page to visitors who are not logged in.
• A firewall or bot-protection rule that challenges or blocks Googlebot.

Untick the WordPress box, remove the password or plugin, then request indexing again.

5. The canonical tag points to a different URL

A canonical tag pointing elsewhere tells Google to index the other URL instead of yours. In URL Inspection, compare "User-declared canonical" with "Google-selected canonical". The Page indexing report shows these pages as "Alternate page with proper canonical tag" or "Duplicate, Google chose different canonical than user".

Common mistakes include every page declaring the homepage as canonical, canonicals pointing to a staging domain, and canonicals using http:// on an https:// site. Google Search Central (2026) describes rel="canonical" as "a strong signal", not a command, so Google also weighs redirects, internal links and sitemaps. Give every indexable page a self-referencing canonical with the full live URL, and keep internal links and sitemaps pointing to that same URL.

6. The content depends on JavaScript Google does not render

Google indexes what it sees after rendering, so content that only appears after JavaScript runs is at risk. Google Search Central (2026) explains that Google processes JavaScript in three phases (crawling, rendering and indexing) and that pages wait in a render queue that "can take longer" than a few seconds.

This is where SEO and code meet. Run a live test in URL Inspection and open "View tested page". Check three things:

• Rendered HTML: the main text, headings and title are present.
• Links: navigation uses real <a href="..."> links, not click handlers on buttons or divs.
• Screenshot: the page looks complete, not blank or stuck on a loading spinner.

Missing content means Google sees an empty shell. Fix it with server-side rendering or static generation (Next.js, Nuxt or a prerender layer), which Google recommends because "not all bots can run JavaScript". I have written production code for over 10 years, including Next.js, and this fix belongs in the codebase, not in an SEO plugin.

7. The content is thin or duplicated

Google crawls thin or duplicate pages and then chooses not to index them. The Page indexing report shows "Crawled - currently not indexed" or "Duplicate without user-selected canonical". The full diagnosis for that status is in Crawled – currently not indexed: what it means and how to fix it.

Typical examples are city pages that swap only the town name, tag archives and product pages that reuse the manufacturer's description. Merge near-identical pages into one stronger page, add original information (prices, photos, process details, FAQs from real customers), and noindex low-value archives so Google spends its crawl on pages that matter.

8. A manual action has demoted or removed the site

A manual action is a penalty a human reviewer at Google applies for breaking Google's spam policies. Open Search Console > Security & Manual Actions > Manual actions. Google Search Console Help (2026) states that most issues listed there lead to pages or sites "being ranked lower or omitted from search results".

Fix every affected page, not a sample, then select Request Review and explain the issue, the steps you took and the result. Google does not partially restore a site that fixed only some pages.

9. The site is hacked or flagged for security issues

A hacked website loses visibility because Google warns users or drops the spam pages and the pages around them. Open the Security Issues report in Search Console. Google Search Console Help (2026) lists three types: hacked content, malware and unwanted software, and social engineering, and states that affected pages show a warning label in search results or a browser warning page.

Here is the insight a pure SEO checklist skips: many SEO spam injections show spam only to Googlebot and hide it from you. Your homepage looks normal in your browser while Google sees pharmacy, casino or Japanese-language pages. Search site:yourdomain.com casino or site:yourdomain.com viagra, and compare the crawled HTML in URL Inspection against what your browser shows. I have done security research since 2011, with acknowledgements from Google, BlackBerry and TeamViewer, and the cleanup only holds when the entry point (an outdated plugin, a weak admin password, a writable upload folder) is closed. My guide on what to do when your website is hacked covers the full cleanup order.

10. Pages are orphaned with no internal links

Google struggles to find pages that no other page on your site links to. Crawl the site from the homepage with Screaming Frog, then compare the crawled URLs against your XML sitemap. URLs that appear in the sitemap but not in the crawl are orphans.

Link each orphan from 2-3 relevant pages, such as a service hub, a related blog post or the main navigation, using anchor text that names the page's topic. A structured website audit checklist catches orphans together with broken links and redirect chains.

11. The page is indexed but does not rank for that search

A page can be in Google's index and still not appear for the term you typed, which is a ranking problem, not an indexing problem. URL Inspection reports "URL is on Google", yet your search shows competitors. Open the Performance report, filter by the page, and read its queries and average position. An average position of 38 means page 4 of the results.

Ranking depends on matching search intent, content depth, links from other sites and page experience. Slow pages also hold rankings back, as explained in my article on how site speed affects SEO. I have ranked a page #2 on Google for a search made 5 million times a month, and ranking work starts only once indexing is confirmed.

What to do after you fix the cause

Confirm the fix with Google before you wait for results.

1. Run a live test in URL Inspection and confirm the page is "available to Google".
2. Request indexing for the fixed URL.
3. Click "Validate fix" in the Page indexing report so Google rechecks every affected URL.
4. Track progress weekly in the Page indexing and Performance reports.

Get outside help if the report shows a cause you cannot trace in your CMS or code. My guide on how to hire an SEO consultant lists the questions to ask before you pay anyone.

Frequently asked questions

How long does it take Google to index a new website?

Google publishes no fixed timeline for indexing a new website. Its SEO Starter Guide states that changes take anywhere from a few hours to several months to appear, and submitting a sitemap plus requesting indexing in Search Console shortens the discovery step.

Does submitting a sitemap guarantee my site appears on Google?

A sitemap does not guarantee indexing. It tells Google which URLs exist, and Google still decides whether each page is worth indexing based on access rules, canonicals, content quality and security status.

Why does my website show up when I search its name but not my services?

Your website is indexed but does not rank for service keywords. Brand searches have little competition, while service searches require content that matches intent, links from other sites and a technically sound page.

Can a hacked website disappear from Google?

A hacked website loses traffic through browser and search warnings, and spam pages injected by the attacker get demoted or dropped. Check the Security Issues report in Search Console, clean the site, close the entry point, then request a review.

Why does Google say my page is not indexed when it looks fine in my browser?

Google and your browser often receive different content. A noindex header, JavaScript that Google does not render, or cloaked spam from a hack all leave the page looking normal to you; the URL Inspection live test shows exactly what Googlebot receives.