Why Is My Website Not Showing Up on Google? Here's How to Find the Problem
The Social Stellor Studio
Creative Team
You launched the website. It works. You can send someone the link and they can open it, click around, see exactly what you built. Then you open Google, search for your business name or the service you offer, and nothing. Or worse, something shows up, but it's a directory listing or a competitor, not you.
Before you start rewriting titles, buying an SEO tool subscription, or assuming the whole site is broken, it helps to know which problem you actually have. A page Google has never seen needs a completely different fix from a page that's sitting in Google's index just fine but doesn't rank for the search you happened to try. Treating those two situations the same way wastes time and, occasionally, makes things worse.
Find Out Where the Problem Starts
Every page that eventually ranks on Google passes through the same rough sequence of states. Knowing which one your page is stuck in tells you what to check next.
- Not discovered: Google doesn't know the URL exists yet. Nothing has linked to it and it hasn't been submitted anywhere.
- Discovered but not crawled: Google has seen a reference to the URL, through a sitemap or a link, but hasn't visited it yet.
- Crawled but not indexed: Googlebot has fetched the page, but decided (for now) not to add it to the index.
- Indexed but not ranking: the page is in Google's index and eligible to appear in results, it just isn't showing up for the particular search you tried.
The fastest way to place yourself on this list is Google Search Console's URL Inspection tool. Paste in the exact URL and it will tell you, directly, whether the page is indexed, and if not, roughly why.
First, Check Whether Your Website Is Actually Missing From Google
"Not showing up on Google" can mean three different things, and they're not the same problem. It might mean the site isn't indexed at all. It might mean the site is indexed and shows up if someone searches your exact business name, but not for a service keyword like "plumber in Leeds" or "project management software for agencies." Or it might mean the specific page you're checking, a new blog post or a service page you just added, hasn't caught up with the rest of the site yet.
A quick way to get a rough read is a site: search. Type site:yourdomain.com into Google and see what comes back. If pages appear, at least some of your site is indexed. If a specific page doesn't show up under site:yourdomain.com/that-page, it's a reasonable sign that page specifically isn't indexed.
Treat site: searches as a rough signal, not a precise count. Google has said plainly that the number of results shown for a site: search is an estimate and can be inaccurate, sometimes by a wide margin. Use it to spot-check whether a page exists in the index, not to audit your whole site's indexing status.
For anything more reliable than a site: search, Search Console's URL Inspection tool is the actual source of truth. It queries Google's index directly for that specific URL and tells you what Google currently has stored, including the last crawl date and whether the page is eligible to appear in search results.
Your Website Is Still New
If the site went live recently, this is very often the whole explanation. New domains generally don't have an established crawl pattern yet. Google doesn't have a reason to visit a brand new site frequently until it builds up some signal that the site is worth checking regularly, whether that's other sites linking to it, people searching for it directly, or a sitemap consistently pointing to fresh content.
There's no fixed countdown here. Some new pages get crawled and indexed within a day or two. Others take a few weeks. A site with no existing authority, no backlinks, and a sitemap nobody's told Google about can sit in limbo for longer than that. If your site is under a month old, patience combined with the checks below is a more useful strategy than assuming something is broken.
Google Has Not Discovered the Page Yet
Google can only crawl a URL it knows about. Discovery generally happens one of three ways: Google follows a link from a page it already knows, it reads the URL from your sitemap, or someone submits it manually through Search Console. If none of those have happened, the page is effectively invisible, no matter how good the content is.
A few things worth checking here. Does the page actually appear in your sitemap.xml file, and does that sitemap exist where Search Console expects it? Is the page linked from somewhere else on your own site, ideally your navigation, a hub page, or another article, using a real crawlable link rather than a button that only works after a click or a JavaScript-only interaction? A page that exists purely as an orphan, with zero internal links pointing to it and no sitemap entry, is asking Google to find it by luck.
Search Console Says "Discovered, Currently Not Indexed"
Discovered, currently not indexed means exactly what it says: Google knows the URL exists but hasn't crawled it yet. It's one of the more common statuses on newer or smaller sites, and it doesn't automatically mean anything is wrong.
Crawl priority comes down to a mix of factors, including how much trust and authority a site has built up so far. A brand new site with a handful of pages and no inbound links is, quite reasonably, lower on Google's list of places to check often. A valid sitemap does not guarantee an immediate crawl; it just tells Google the URL exists and roughly how important you consider it. If a page has sat in this status for weeks rather than days, it's worth checking the other issues covered further down, particularly internal linking and overall site quality, but on a new site, a few days here is nothing to worry about.
Google Crawled the Page but Did Not Index It
A crawl is more specific than a discovery. Google visited the page and, for now, chose not to add it to the index. A few common reasons this happens:
- Duplicate or near-duplicate content: the page says almost the same thing as another page on your site, or closely mirrors content that already exists elsewhere on the web
- Thin content: the page doesn't offer enough substance for Google to consider it worth serving on its own
- Canonical conflicts: your canonical tag points somewhere else, so Google is treating this URL as a variant of a different page rather than indexing it independently
- Rendering problems: if your page relies heavily on client-side JavaScript to display its actual content, and that content doesn't render properly when Google processes it, Google may see a mostly empty page
- Soft 404s: the page technically returns a 200 OK status, but its content looks so thin or broken that Google treats it as if it were a "not found" page
The Search Console URL Inspection tool will usually tell you which of these applies, under a heading like "Why is this page not indexed?" Read that reason literally rather than guessing. It's the most direct clue you'll get.
A Noindex Directive Is Blocking the Page
Sometimes the explanation is simpler than any content quality issue: the page is explicitly telling Google not to index it. This can happen through a meta robots tag in the page's HTML head, or through an X-Robots-Tag HTTP header. It's surprisingly common on sites built with a CMS or page builder, where a "noindex" toggle gets left on from a staging environment, or a plugin applies it by default to certain page types.
You can check this in a few ways. View the page's source code and search for "noindex" in the head section. Or, faster, run the URL through Search Console's URL Inspection tool, which will explicitly flag "Indexing allowed? No" if a noindex directive is present, along with where it's coming from.
robots.txt Is Blocking Google
Your site's robots.txt file, usually found at yourdomain.com/robots.txt, tells search engine crawlers which parts of the site they're allowed to visit. If a Disallow rule accidentally covers the page in question, or an entire section of your site, Googlebot won't crawl it.
Crawling and indexing are not the same thing, and robots.txt only controls crawling. A URL blocked by robots.txt can, in some cases, still appear in Google's index without a proper title or description, if enough other pages link to it. If you actually want a page kept out of search results entirely, a noindex directive is the correct tool. robots.txt alone is not a reliable way to keep a page out of Google.
Google Is Using a Different Canonical URL
A canonical tag tells Google which version of a page is the "real" one, useful when the same content is reachable through more than one URL (with or without a trailing slash, with tracking parameters, across http and https, and so on). You declare your preferred canonical in the page's HTML. Google then decides whether to respect that choice or select a different URL as canonical instead, based on its own signals.
When Google picks a different canonical than the one you declared, the URL you actually care about might not get indexed on its own; instead, Google treats a different URL as the authoritative version and folds this one into it. Search Console's URL Inspection tool shows both your declared canonical and Google's selected canonical side by side, so you can see immediately if they disagree.
The Page Is Hard to Discover Inside Your Own Website
A page can clear the discovery bar once, through a sitemap entry, and still stay low priority if nothing else on the site treats it as important. Internal links are one of the clearest signals of that kind of importance: a service page linked from your homepage and a couple of related articles reads as more central than one sitting four clicks deep with nothing pointing to it.
A common technical mistake hides here too. If your navigation menu, a "view more" list, or an FAQ accordion is built so that the links only exist in the page's HTML after a click or hover interaction, and not in the actual server-rendered markup, search engines may never encounter those links at all. A real anchor element with a real href attribute, rendered directly into the page (the output of a standard HTML link or a framework's own Link component), is what a crawler needs to see. A link that only appears after JavaScript runs a click handler is a much less reliable signal, and in some setups isn't seen at all.
Contextual links from related articles, service hub pages, and your main navigation all help here. If a page can only be reached by typing its exact URL, it's effectively isolated, no matter how well it's written.
The Page Does Not Clearly Answer a Search Need
Even once a page is indexed, Google is constantly evaluating whether it genuinely satisfies what someone was searching for. This isn't about hitting a minimum word count; a short page that directly answers a specific question can outperform a long page that circles the topic without saying much. What matters is whether the content matches the intent behind the search: is someone looking to learn something, compare options, or take an action, and does your page actually deliver that.
A useful gut check: read the page as if you were the person searching, not the person who wrote it. If it takes several paragraphs to get to the actual answer, or the page talks more about your company than about the reader's problem, that's worth revisiting.
Your Website Is Indexed but It Does Not Rank Yet
People get this case wrong more than any other, so it's worth being blunt about it: being indexed and being ranked are not the same thing. Indexing means a page is eligible to appear in search results. Ranking means Google has decided it deserves a specific position for a specific search, compared against every other page competing for that same query. A page can be perfectly, cleanly indexed and still rank nowhere close to page one for a competitive term.
Ranking depends on how well a page matches search intent, how much relevant depth it offers compared to competing pages, how much authority the domain has built up (largely through other reputable sites linking to it), how the page connects internally to the rest of the site, and simply how mature the site is overall. None of these move overnight. A six-month-old site with three backlinks is not going to outrank an established competitor with years of content and a much larger link profile for a broad, competitive keyword, even with perfect technical SEO.
Your Search Terms May Be Too Competitive
If you're testing your ranking by searching a broad, high-competition term, like "marketing agency" or "web design," with no location or specificity attached, a newer site is very unlikely to appear on the first page regardless of how well it's built. Those terms are dominated by sites with years of accumulated authority.
New and growing sites tend to rank for long-tail terms first: more specific, lower-competition phrases closely related to what the page actually covers. If your service page targets "email marketing agency," you might see movement first on something like "email marketing agency for ecommerce brands" before you see it for the shorter, more contested phrase. That's just the normal progression, nothing has gone wrong. Search Console's Performance report will show you which specific queries you're already getting impressions for, which is often a more useful signal than whichever single term you happen to type into Google yourself.
Technical Problems May Be Getting in the Way
Beyond indexing status specifically, a handful of technical issues can quietly limit crawling and ranking without producing an obvious error message. Worth ruling out:
- Server errors (5xx responses) that intermittently prevent Googlebot from reaching the page at all
- Slow-loading pages, particularly on mobile, which can affect both crawl efficiency and user experience signals
- Content that only appears after heavy client-side JavaScript execution, which can delay or complicate how Google renders and indexes it
- Broken internal links leading to dead ends, which waste crawl budget and disrupt the link paths described earlier
- Accidental noindex tags or robots.txt rules left over from a staging or development environment
- Unexpected HTTP status codes, such as a page returning a redirect or an error where a normal 200 OK is expected
None of these are reasons to panic. They're simply worth checking systematically rather than guessing, which is exactly what the checklist below is for.
A Practical Google Indexing and Ranking Checklist
A working order to check things in, from most direct to most general:
| Check | What to Look For | What to Do |
|---|---|---|
| URL Inspection | Indexed status, last crawl date, declared vs. selected canonical | Start here for any single page; it's the most direct source of truth |
| Live Test | Whether the current live version of the page can actually be indexed right now | Run it from within URL Inspection if the indexed version looks outdated |
| Sitemap | Whether the URL is included, and whether the sitemap itself loads without errors | Add missing URLs; resubmit the sitemap in Search Console if it's changed |
| robots.txt | Any Disallow rule that could be covering the page or a whole folder | Remove or narrow the rule if it's blocking something it shouldn't |
| Meta robots | A noindex tag in the page's head section | Remove it if the page is meant to be indexed |
| Canonical | Whether Google's selected canonical matches your declared one | Fix conflicting signals (duplicate content, inconsistent internal links) if they disagree |
| Internal links | Whether the page is reachable through a real, crawlable link somewhere else on the site | Add contextual links from relevant pages, navigation, or related content |
| Page content | Whether the page clearly answers a specific search need, without excess thin or duplicate content | Rewrite or consolidate pages that don't stand on their own |
| Performance | Server errors, slow load times, or broken links | Fix errors first; they can block crawling entirely |
| Search queries | Which terms you already get impressions for, in Search Console's Performance report | Use this to understand where you realistically stand before testing broad keywords manually |
Should You Request Indexing?
Search Console's "Request Indexing" option, available from the URL Inspection tool, asks Google to prioritize crawling a specific URL sooner than it otherwise might. It's genuinely useful right after publishing or meaningfully updating a page, or after fixing one of the issues covered above.
Requesting indexing does not guarantee faster indexing, and it doesn't override whatever underlying issue is preventing the page from being indexed. If the page has a noindex tag, a canonical conflict, or a quality problem, requesting indexing repeatedly won't fix that; it just asks Google to look again. Submitting the same URL over and over in a short window doesn't speed things up either, and Search Console has a daily limit on manual submissions.
Should You Click "Validate Fix"?
In Search Console's Coverage or Page Indexing report, once you've addressed an issue affecting multiple URLs, there's a "Validate Fix" option that asks Google to recheck the affected pages. It's worth using once you're confident the underlying problem is actually resolved, not as an exploratory click.
Validating before the fix is genuinely in place tends to produce a failed validation, which doesn't cause lasting harm, but does waste a validation cycle, and the process can take a week or two, sometimes longer, before you can try again. Confirm the fix is live (check the actual page source, not just your CMS settings) before starting validation.
How Long Should You Wait?
There's no single honest number here, and anyone giving you an exact day count is guessing. As a rough shape: a healthy, established site can sometimes see a new page indexed within a day or two. A brand new site with little existing authority can reasonably take several weeks for initial indexing, and considerably longer than that to see meaningful ranking movement for anything beyond long-tail terms.
The more useful question usually isn't "how long," it's "is anything actively blocking this." If you've worked through the checklist above and found nothing wrong, technically, an indexing delay on a new or low-authority site is often just the ordinary pace of things. If the checklist surfaced a real blocker (a noindex tag, a robots.txt rule, a canonical conflict), fix that first; the timeline conversation matters a lot less until the actual blocker is gone. For a fuller breakdown of what typically happens month by month, and how to spot progress before rankings show up, see our guide on how long SEO actually takes to work.
What to Do If Your Website Is Indexed but Still Gets No Traffic
Indexed, ranking somewhere, and getting clicks are three different milestones, and it's entirely possible to clear the first two without seeing the third. Search Console's Performance report separates this out clearly: impressions tell you how often your pages appeared in search results, queries tell you what people actually searched to see them, average position tells you roughly where you're ranking for those queries, and click-through rate tells you what share of those impressions actually turned into a visit.
A page with plenty of impressions but very few clicks usually points to a title or meta description that isn't compelling enough to earn the click, even at a reasonable position. A page with almost no impressions at all points back to the ranking and relevance issues covered earlier in this article. Reading these numbers together tells you which stage of the funnel actually needs attention, rather than treating "no traffic" as one undifferentiated problem.
What to Do Next
- Check URL Inspection first. It will tell you, directly, whether the page is indexed and roughly why if it isn't.
- Rule out simple blockers before anything else: noindex tags, robots.txt rules, and canonical conflicts.
- Make sure the page is actually reachable through real, crawlable internal links, not just a sitemap entry.
- If the page is indexed but not ranking, judge it against realistic long-tail terms first, not the broadest possible keyword.
- Use Search Console's Performance report to see which stage (impressions, ranking, or clicks) actually needs attention.
- Give a new or low-authority site real time before assuming something is broken; weeks, not hours, is the normal pace.
Still not sure whether you're dealing with an indexing problem or a ranking problem? Social Stellor can help review technical SEO, crawlability and organic visibility, and tell you plainly what's actually going on.
Talk to Our SEO TeamFrequently Asked Questions
Why is my website indexed but not ranking?
Indexing only means a page is eligible to appear in search results. Ranking depends on how well it matches search intent compared to every other page competing for the same query, along with authority, relevance and site maturity. A page can be indexed correctly and still rank poorly for competitive terms.
Why does Search Console say "discovered but not indexed"?
It means Google knows the URL exists but hasn't crawled it yet, usually because the site hasn't built up enough crawl priority. This is common on newer or smaller sites and isn't automatically a sign of a quality problem.
Does submitting a sitemap guarantee indexing?
No. A sitemap tells Google which URLs exist and that you consider them important; it doesn't force Google to crawl or index them. It's a strong signal, not a guarantee.
Should I request indexing for every page?
No. Save it for pages you've just published or meaningfully changed, or right after fixing an indexing issue. Requesting it repeatedly for the same URL doesn't speed anything up, and Search Console limits how many manual requests you can make in a day.
Can Google find pages that are not in the sitemap?
Yes, if they're linked from somewhere Google already crawls, whether that's your own site's navigation or an external link. A sitemap makes discovery more reliable, but it isn't the only way Google finds a URL.
Why can I find my website by URL but not by keyword?
Searching your exact URL or domain name tests whether the page is indexed at all. Searching a keyword tests whether Google considers your page the best match for that specific query, against every competing page. It's entirely possible to pass the first test and not the second, particularly for competitive terms on a newer site.