If your website isn't showing on Google, you usually have one of two problems: Google hasn't indexed your pages yet, or your pages are indexed but aren't ranking for the searches you care about. These require different fixes. First, figure out which one you're dealing with.
First, do this
Search site:yourdomain.com.
Open Google Search Console.
Inspect the specific URL you're worried about.
Check the Page Indexing report for the exact status.
That takes about a minute and tells you which half of this article applies to you. Everything below explains what each result means and how to fix it.
Key takeaways
Not showing on Google usually means one of two problems: not indexed, or indexed but not ranking.
A site:yourdomain.com search gives a rough read in seconds. Search Console's URL Inspection tool provides a reliable check for any page.
Robots.txt and noindex are different mechanisms: one stops crawling, the other stops indexing an accessible page. A robots.txt block can even hide a noindex tag from Google entirely.
A firewall, bot-protection tool, or strict Content Security Policy can silently block Google without you noticing, since your browser still sees the page normally.
Canonical tags are a signal, not a command. Consistent internal linking reinforces them more reliably than the tag alone.
A lack of backlinks doesn't prevent indexing. It mainly affects how competitive you are in rankings once you're indexed.
Start here: is it an indexing or ranking problem?
Search site:yourdomain.com, replacing "yourdomain.com" with your actual domain. This asks Google to show only pages it has indexed from your site.
Treat this as a rough first check, not a definitive test. For a specific page, Search Console's URL Inspection tool provides a more reliable read, including whether Google can access and render the live version.
Nothing comes back: Google may not have indexed your site, though a site search alone isn't conclusive. Confirm with URL Inspection, then go to the indexing section below.
Pages come back, but not for the searches you actually want to rank for: Google knows your site exists; it just isn't ranking for those terms yet. Go to the ranking section below.
Someone with a ranking problem doesn't need to touch robots.txt, and someone with an indexing problem doesn't need to rewrite their content yet. Diagnose first, fix second.
Your site isn't indexed at all
Is your site too new?
If your website launched recently, this is the most common and least worrying cause. Google needs to discover your site, crawl it, and decide to index it. There is no fixed timeframe for these steps. In practice, a healthy new site is often crawled and indexed within days or a few weeks, but repeatedly hitting "request indexing" does not speed it up.
Have Google's crawlers actually found your pages?
Google mostly discovers new URLs through links and sitemaps. A page with no internal links is called an orphan page and can sit undiscovered for a long time even if it's live. A new service page that isn't linked from your homepage, navigation, or elsewhere is a common example. Give every important page a clear path from your homepage, such as homepage → category → page.
Is robots.txt blocking Google from crawling your site?
Robots.txt is a small text file at yourdomain.com/robots.txt that controls your site's crawlability and which parts of your site crawlers can access. Visit it directly and check for a rule like this under the wrong user agent:
User-agent: *
Disallow: /That line blocks all crawlers from accessing your entire site. It's often left behind when a site moves from staging to production, particularly after a redesign or platform migration.
Also check which specific crawlers your robots.txt file allows or blocks. The rules can apply to Googlebot as well as other crawlers, including AI crawlers such as GPTBot and PerplexityBot. If these crawlers are blocked, your content may not be accessible to the systems that generate AI-powered search answers. Cralite's free AI crawl checker can show which AI crawlers your robots.txt currently allows or blocks.
Think your robots.txt file might be blocking Google? Check it with Cralite's free robots.txt validator, or use the robots.txt generator to produce a corrected file.
Do you have a noindex directive somewhere?
A noindex tells Google not to include an accessible page in search results. It usually appears as a meta tag in the page's HTML:
<meta name="robots" content="noindex">But it can also arrive as an HTTP response header instead, which is easy to miss because it never appears in the page source:
X-Robots-Tag: noindexThat header is usually added at the server level rather than in a page's code. If Search Console reports a page as noindexed but you can't find a meta tag, check your CDN settings, security plugin, or .htaccess or Nginx/Apache configuration.
Some CMS platforms add their own shortcut for the same effect. WordPress also has a "discourage search engines from indexing this site" setting under Settings> Reading that can accidentally remain enabled after launch, particularly on sites built in a staging environment or on a host that switches it on automatically during setup. Search Console's Indexing report will show pages "excluded by noindex tag" if this is what's happening.
Worth noting: robots.txt and noindex solve different problems, and confusing the two can cause unexpected results. If robots.txt blocks a page, Google may never be able to crawl it and see its noindex tag. In that case, the robots.txt block prevents Google from accessing the page, rather than the noindex tag controlling its indexing.
Is your sitemap missing, broken, or just not helping?
An XML sitemap lists your pages and helps Google discover them more efficiently. It's especially useful while you're still building up internal links and external mentions. Submit it through Search Console's Sitemaps report. A sitemap can hold up to 50,000 URLs and 50 MB uncompressed before it needs to be split into an index file.
If it returns an error or shows "no URLs found" even though the file clearly contains them, run it through Cralite's free sitemap checker to see exactly what's wrong. The usual culprits are:
The wrong file format or encoding
Broken or malformed XML
URLs that don't match your live domain
Cralite's free sitemap generator will automatically create a well-structured sitemap. Keep in mind that a sitemap helps Google discover your pages, but it doesn't guarantee that those pages will be indexed.
"Discovered" vs "crawled, not indexed": what's the difference?
If Search Console's Page Indexing report shows either status, Google knows your URL exists but hasn't indexed it, for two different reasons.
Discovered, currently not indexed means Google found the URL but hasn't crawled it yet. On very large sites, this can be a crawl budget issue, since Google limits how much it crawls a site over a given period. For most smaller sites, it's often a queueing delay while Google works through the URLs it has discovered, rather than a sign that something is wrong.
Crawled, currently not indexed means Google visited the page but hasn't included it in the index. Google doesn't publish the exact reason why a specific page remains unindexed, but if an important page stays in this state, review its content quality, duplication, canonicalisation, internal linking, and other site signals rather than repeatedly requesting indexing. It generally warrants more attention than a newly discovered URL because Google has already crawled the page.
A related status worth knowing: a soft 404 is a page that returns a normal 200 OK response but has so little content that Google treats it as an error page anyway; an empty category, a "coming soon" placeholder, or a thin auto-generated tag page is a typical cause.
Is there a manual action against your site?
Rare, but worth ruling out if nothing else fits, particularly if a previously healthy site suddenly disappears. Check the Manual Actions report under Security & Manual Actions in Search Console. Most missing pages have far more ordinary explanations than a penalty, so don't assume this is the cause without checking.
Could a security tool or firewall be blocking Google itself?
This is less common than the causes above, so check it after you've ruled those out. It's also worth separating three different things that often get lumped together as "security issues":
Manual actions, covered above, mean Google's own team found something on your site that violates its guidelines.
The Security Issues report, a separate tab next to Manual Actions in Search Console, flags a different problem entirely: Google's crawler detected malware, hacked content, or deceptive pages on your site.
A firewall, CDN, or bot-protection tool blocking Googlebot itself, which is a problem you created rather than one Google flagged.
That third one is the easiest to miss because your site looks completely normal to you. Some bot-protection systems treat crawler traffic as suspicious and serve a verification or "prove you're human" screen instead of the real page. Google then indexes whatever it receives, which may be the challenge screen rather than your content. This can result in an unexpected canonical URL or cause the page to drop out of the index with no obvious explanation.
Check this with URL Inspection's live test rather than just viewing the page yourself, since your browser and Googlebot can be served two different things by the same security rule.
A narrower version of the same problem is a Content Security Policy, a security header that restricts which scripts and resources a page can load. If a JavaScript-heavy page's policy is too strict, it can block the scripts needed to render the content. Googlebot may then see a mostly empty page even though the page looks fine in your browser.
This mainly affects sites that build content client-side rather than serving it in the initial HTML. It's also much rarer than a robots.txt or noindex mistake, so check it if your site is JavaScript-heavy and everything else looks clean.
Your site is indexed but not showing for your searches
If site:yourdomain.com returned pages, Google already has your site. The problem now is relevance, not access.
Are you searching for the wrong thing?
This sounds obvious, but it's a genuinely common mix-up. Searching your own business name yields different results than searching for the services you offer. If you show up fine for "[your business name]" but not for "plumber in Nairobi," that's not a visibility bug; it's a sign your content doesn't yet match how people actually search for what you do. See Cralite's local SEO guide for small businesses for how to close that gap.
Does your content actually answer the question behind the search?
Google ranks pages based on how well they match search intent, or what the searcher is actually trying to accomplish. It's not simply about whether the right words appear on the page. A services page that lists what you offer without answering the questions a prospective customer actually has will struggle against a competitor's page that answers those things directly, questions like:
How much does this cost?
What's the process, step by step?
How long does it take?
Do you cover my area?
Do you have duplicate or thin content competing with itself?
If several pages cover near-identical ground, Google has to pick one to show and often doesn't pick any of them particularly well. A canonical tag tells Google which version you prefer:
<link rel="canonical" href="https://example.com/preferred-page">Treat this as a signal rather than a command. Google can still choose a different canonical if its own systems decide another version fits better. Consistent internal linking and a consistent URL structure pointing to the same version reinforce that signal more reliably than the tag alone. The real fix is consolidating genuinely duplicate pages and linking consistently, not just adding the tag and assuming it's settled.
Not sure your canonical tags are set up correctly? Cralite's canonical tag generator produces the correct tag for your preferred URL.
Are you aiming at more competition than your site can currently win?
A brand new site chasing a broad, high-competition term like "insurance" is a different fight from chasing a long-tail keyword like "travel insurance for Kenyan students going abroad." The second is more specific, easier to satisfy fully, and a realistic place for a newer site to build some topical footing before taking on the bigger terms.
Does anything else on the web point to your site?
New sites with few backlinks and thin internal linking can take longer to build the authority needed for competitive terms, even once fully indexed. A lack of backlinks doesn't stop a page from being indexed, though. That's a separate mechanism. Backlinks matter more for how competitive your site can be in the rankings. Building authority doesn't mean buying links; it means getting genuinely listed somewhere relevant, for example:
A relevant local or industry directory
A partner or supplier's website
A mention in a news article or roundup
and making sure your own pages link to each other in a way that shows Google which ones matter most.
Why "showing up" looks different in 2026
Google increasingly surfaces AI-generated summaries above traditional search results. Being indexed and ranking well doesn't guarantee that your content will appear in one of these summaries. However, crawling, indexing, and relevance are still the starting points.
For a growing number of searches, ranking and being seen are no longer quite the same thing. For more on what this shift involves, see Cralite's guide to Generative Engine Optimisation.
Check your status, using free tools
You don't need paid software for any of this. Search Console and Analytics, both free, cover almost everything above.
Search site:yourdomain.com for a rough read, then open Search Console's URL Inspection tool for any specific page you're worried about. Its live test shows what Googlebot receives right now. It can also reveal when a security tool or CSP is serving Google something different from what you see in your browser.
Go to Indexing, then Pages, the Page Indexing report, for the exact reason any URL isn't indexed: noindex, blocked by robots.txt, discovered or crawled but not indexed, duplicate without a user-selected canonical, and so on. Click through to the actual URL list rather than reading just the summary count.
Visit yourdomain.com/robots.txt directly, or run it through the robots.txt validator.
Check the page source and response headers for a noindex directive.
Confirm your sitemap is submitted and error-free under Sitemaps, or run it through the sitemap checker if it looks malformed.
Check the canonical URL Google has actually selected for the page, to make sure it isn't treating a different URL as the preferred version.
Check Manual Actions and Security Issues, two separate reports under the same menu, to rule out a Google-side penalty or a malware flag.
If indexing looks clean but you're still not showing up for the searches you want, check Performance for impressions and average position by query. Zero impressions means Google isn't showing your page for that search at all. Reasonable impressions with very few clicks usually point to your title or snippet rather than the ranking itself.
Cross-check in Analytics: under Acquisition, then Traffic acquisition, look for the Organic Search channel. If Search Console shows clicks from Google but Analytics shows none, you may have a broken tracking tag rather than a visibility problem. Rule this out before assuming traffic genuinely isn't arriving.
Once you've actually fixed something, request indexing rather than before.
Frequently asked questions
How long should I wait before assuming something's wrong?
There's no fixed number of days Google promises. A new page can be indexed within days of being crawled, or it can take longer. There's no set rule either way. Rather than counting days, check Search Console. If it shows a specific exclusion reason, that's more useful than the calendar.
Does resubmitting my sitemap help if a page is stuck?
Only if the sitemap was the actual problem. If robots.txt or a noindex tag is the real cause, resubmitting a sitemap won't touch it.
Is "crawled, not indexed" worse than "discovered, not indexed"?
Generally yes. Discovered is often just a queueing delay. Crawled, not indexed means Google has crawled the page but hasn't included it in the index. If it remains in this state, review content quality, duplication, canonicalisation, and other indexing signals rather than requesting indexing again.
Can a robots.txt block hide a noindex tag from Google?
Yes. If robots.txt prevents Google from reaching a page at all, it never gets far enough to see a noindex tag on that page, so the block is what's actually driving the outcome.
Can a security plugin or firewall stop my site from being indexed?
Yes, if it treats Googlebot as suspicious traffic and serves it a challenge screen instead of your real page. Your own browser won't show you this, since it only affects crawler requests. Check with URL Inspection's live test rather than judging by what you see when you visit the site yourself.
Will a redesign or new theme cause this?
It can, particularly if a staging robots.txt file or a "discourage search engines" setting gets carried over to the live site by mistake. Worth checking specifically after any migration or relaunch.
Does being indexed guarantee traffic?
No. Indexing makes a page eligible to appear in Google's search results; it doesn't determine whether that page shows up for any given search. A page can be fully indexed and still sit on page ten if it's not relevant or authoritative enough for the terms you want.
