Why is my website not showing up on Google? 9 causes, in the order to check them
When a website does not appear on Google, Search Console nearly always says why. These are the nine usual causes, from a site that is simply new to a noindex tag left on at launch, each with the status that confirms it and the fix.
If your website does not appear when you search for it, Google is almost always telling you why. The answer is in Google Search Console, and the cause is usually one of nine things. Here they are in the order we check them, from the quickest to rule out to the slowest to fix.
Before you start, add your site to Google Search Console if it is not there yet. It is free, and it is the only place Google reports what it found. Most of the checks below use its URL Inspection tool: paste a page's address into the search bar at the top.
1. It is new, and Google has not got to it yet
A brand-new domain can take days to weeks to be crawled, and a new site with no links pointing to it waits longest. Search for site: followed by your domain (for example site:yourshop.com). If nothing comes back and URL Inspection says "URL is not on Google", Google simply has not indexed the page yet.
Fix: submit your sitemap in Search Console (Sitemaps, then the address of your sitemap, usually /sitemap.xml), use "Request indexing" on your most important pages, and get a few links from places that already rank: your Google Business Profile, local directories, suppliers and partners.
2. The page asks not to be indexed
A noindex tag tells Google to leave the page out, and Google does. In WordPress, one checkbox under Settings, Reading, "Discourage search engines from indexing this site", adds it to every page. It is often ticked while a site is built and forgotten at launch. 5 of the 315 homepages in our check of small-business sites still had it.
Check: URL Inspection reports "Excluded by 'noindex' tag". Or view the page source and search for noindex. How to switch it off in WordPress.
3. robots.txt blocks Google
A Disallow: / under User-agent: * or User-agent: Googlebot tells Google not to crawl anything. In our check, 4 sites blocked Googlebot from their own homepage, and 17 had a robots.txt that would not load at all, which can make crawlers back off from a whole site.
Check: open yourdomain/robots.txt in a browser, look for "Blocked by robots.txt" in Search Console's Pages report, and open Settings, robots.txt report, to see the copy Google last fetched. Safe robots.txt templates and what each robots.txt status in Search Console means.
4. A firewall or security plugin turns Googlebot away
Bot protection at your host, your CDN or a WordPress security plugin can block crawlers before robots.txt is even read. Usually it targets AI crawlers and scrapers, but a strict rule can catch search engines too. Real Googlebot comes from Google's own IP addresses, so a good firewall lets it through and blocks only impostors.
One setting deserves a special look. Since September 15, 2026, setting Cloudflare's AI Training control to "Block" stops Googlebot, Bingbot and Applebot entirely, because Cloudflare counts them as crawlers that also feed AI. The option that keeps search working is "Disallow AI Training".
Check: URL Inspection, "Test live URL". If Google cannot fetch the page you will see a crawl error such as "Blocked due to access forbidden (403)". Then look in your firewall's event log for blocked requests from Googlebot. The Cloudflare settings to look at.
5. The canonical tag points somewhere else
The canonical tag tells Google which address is the real one. When it names a different URL, Google indexes that one instead. 15 of the homepages we checked pointed somewhere else, and 4 of them named a staging or preview address left over from the build, on hosts like netlify.app and github.io.
Check: URL Inspection shows "User-declared canonical" and "Google-selected canonical". Both should be the page itself. In the source, search for rel="canonical".
6. The page is empty until JavaScript runs
Google renders JavaScript, but later and not always completely. If your words only appear after scripts run, the page can be indexed with little or no text, and it will be invisible to the AI crawlers that do not run JavaScript at all. 49 of the homepages we checked were nearly blank without it.
Check: press Ctrl+U on the page and search for a sentence you can see. If it is missing, see JavaScript SEO and how we fixed our own React homepage.
7. Google found the page but chose not to index it
Two statuses in Search Console's Pages report cause the most confusion:
- "Discovered – currently not indexed": Google knows the URL but has not crawled it yet. On a young site this is a sign that Google does not yet think the site is worth crawling often. Our own new pages sat in this state for weeks in October 2026.
- "Crawled – currently not indexed": Google read the page and decided not to keep it for now. Thin pages, near-duplicates of other pages and pages nothing links to end up here.
Fix: there is no switch. Make the page clearly useful and different from your other pages, link to it from pages that are indexed, and earn a few links from other sites. Then request indexing once, not daily.
8. It is indexed, just not for what you searched
A page can be on Google and still not show for a broad search like "bakery near me", where hundreds of pages compete. Search for your exact business name first. If you appear for that, you are indexed and the problem is ranking, not visibility. For local searches, your Google Business Profile usually matters more than the website.
9. A manual action or security issue
Rarely, Google removes a site for spam or because it was hacked. Search Console lists both under Security & Manual actions. If there is something there, fix it and request a review from the same screen.
The quick version
| What you see | Likely cause | Where to look |
|---|---|---|
Nothing for site: your domain | New site, noindex or robots.txt | URL Inspection |
| "Excluded by 'noindex' tag" | WordPress setting or SEO plugin | Settings, Reading |
| "Blocked by robots.txt" | A Disallow rule | yourdomain/robots.txt |
| Crawl error 403 or 5xx | Firewall, CDN or server | Firewall event log |
| "Alternate page with proper canonical tag" | Canonical points elsewhere | Page source |
| "Discovered" or "Crawled – currently not indexed" | Too little reason to index yet | Content and links |
Most of these also decide whether AI assistants can find you, because ChatGPT, Claude and Perplexity send their own crawlers through the same doors. The free AI visibility checker checks robots.txt, firewall behavior, noindex, the canonical tag and the text in your HTML in one go, for Google and the AI crawlers at once. More in what we found checking 400 small-business websites.