SEO & Rankings
Why Isn't My Website Showing Up on Google?
You search for your own business on Google and it's nowhere to be found. Here are the most common technical causes — and how to check which one is yours.
Miguel Prot
If you search for your site on Google and it's not there, there's almost always an identifiable technical cause — an active noindex tag, a robots.txt block, a misconfigured canonical, or the site simply being too new. It's not a mystery, and in most cases it can be diagnosed in minutes with Google's free tools.
Before going through each cause, there are three concepts that get mixed up constantly and are worth separating first.
Discovery, Crawling, Indexing, and Ranking Are Not the Same Thing
For your page to show up in a search result, it has to pass through four stages, in order — described in Google's own documentation on how Search works:
- Discovery — Google learns your URL exists (through a link, a sitemap, or someone submitting it manually).
- Crawling — Google's bot (Googlebot) visits that URL and downloads its content.
- Indexing — Google decides to store that page in its database as a candidate to appear in results.
- Ranking — Google decides where to place that page for a specific search, competing against everything else already indexed.
Your page can fail at any of the first three stages and never reach the fourth. And even if it clears all four, being indexed doesn't guarantee a top position — it only guarantees the possibility of showing up.
The Most Common Causes, and How to Check Each One
| Cause | How to check it |
|---|---|
| New site | Normal if it's days or weeks old; initial crawling can take days to weeks |
| Active noindex tag | URL Inspection in Search Console — explicitly flags a noindex |
| robots.txt block | Visit yourdomain.com/robots.txt and check which paths it blocks |
| Misconfigured canonical | URL Inspection — shows which URL the detected canonical points to |
| Poorly configured redirects | Redirect-checking tool or manual inspection of each hop |
| 404 or 5xx errors | Page indexing/coverage report in Search Console |
| Duplicate content | Compare "www" vs. non-"www" and trailing-slash versions |
| Missing or outdated sitemap | Sitemaps report in Search Console |
| Lack of relevance or authority | Site indexed but not ranking — needs a content review, not a technical one |
A couple of these deserve extra context:
Noindex is an explicit instruction in the page's code telling Google "don't store me in your index." It's commonly left active by mistake after moving a site from staging to production — the site looks perfect, but it's literally asking Google to ignore it. Google documents this tag in its guide on blocking indexing.
Robots.txt tells search engines which parts of the site they can or can't crawl — the official robots.txt documentation covers its syntax. If it mistakenly blocks important pages (or the entire site), Google can't even visit them to evaluate them.
How to Check if Your Page Is Indexed
Two quick ways, no technical knowledge required:
- A direct Google search: type
site:yourdomain.cominto the search bar. If results show up, those pages are indexed. If nothing shows up, it isn't (or is only indexed in a very limited way). - Google Search Console: the URL Inspection tool lets you paste any page from your site and see its exact status — indexed, not indexed, and the specific reason if it isn't.
Search Console doesn't just diagnose — it also has a button to request indexing for a specific URL once you've confirmed the underlying issue is fixed. It's worth using after fixing any of the causes in the table, rather than waiting for Google to revisit on its own.
What to Do With This
- Check
site:yourdomain.comto see if anything is indexed. - If nothing is, open Google Search Console and check the status of your main pages.
- Identify which cause from the table applies to your case.
- Fix the root cause, not just the symptom.
- Request indexing from Search Console for the corrected URLs.
This solves the visibility problem — making sure Google can see and store your page. The ranking problem — showing up near the top for competitive searches — is a separate, ongoing effort that depends on how well your content matches the search compared to everything else already out there.
Frequently Asked Questions
How long does it take Google to index a new page?
It varies widely — from a couple of days to several weeks, depending on how many external signals (links, sitemap, site activity) help Google discover it faster. Manually submitting the URL through Search Console usually speeds things up compared to waiting for spontaneous crawling.
Does being indexed mean I'll rank near the top?
No. Indexing only means your page exists in Google's database as a candidate to appear. Ranking — where it actually appears — depends on how well your content matches the search compared to everything else competing for the same query.
Can I force Google to index my page faster?
Not with a guarantee, but you can help: requesting manual indexing in Search Console, keeping an up-to-date sitemap, and getting other already-indexed pages to link to yours are the legitimate ways to speed up discovery.
Does a site built heavily on JavaScript affect indexing?
It can complicate things if the main content depends entirely on client-side JavaScript to render. Sites that deliver content already in the initial HTML — like this one, built on Next.js and server-rendered — avoid that risk by design.
If you go through this and still can't identify the cause, or the site has a deeper technical issue, it's worth a review with whoever built or maintains the site.
Have a project in mind?
Tell me what you need and we'll figure out the best approach for your business.
Tell me about your project Free quote · Reply within 24 hours