A website usually does not show on Google for one of three reasons: it has not been indexed yet, indexing is technically blocked (robots.txt, a noindex tag or a wrong canonical), or the page is indexed but ranks too low for you to find it. The first step is always the same: check the exact URL in Google Search Console's URL Inspection tool and find out which of the three states you are in.
First: How to Check Whether Your Site Is Indexed at All
Before fixing anything, separate "Google cannot see me" from "Google sees me but ranks me too low". These are completely different problems with different solutions.
Two quick checks:
- Search Google for
site:yourdomain.com. No results at all means the site is not indexed. Some results but missing pages means the problem is local, not site-wide. - Google Search Console → URL Inspection. Paste the exact page address. The tool shows whether the URL is in Google's index, when it was last crawled, whether indexing is allowed, and which address Google treats as canonical.
Search Console is the only source that tells you the cause rather than the symptom. If you do not have it yet, that is job number one: verify the domain and submit sitemap.xml.
The 9 Most Common Reasons a Website Does Not Show on Google
| # | Cause | Where you see it | How to fix |
|---|---|---|---|
| 1 | Site is too new | No site: results | Verify in Search Console, submit sitemap, wait |
| 2 | robots.txt is blocking | "Blocked by robots.txt" | Remove the Disallow: / line |
| 3 | noindex meta tag | "Excluded by 'noindex' tag" | Remove the tag from the page <head> |
| 4 | Wrong canonical | "Alternate page with proper canonical tag" | Point rel="canonical" at the correct URL |
| 5 | Page has no internal links | No links from other pages | Add it to the menu or a related-pages block |
| 6 | Missing or broken sitemap | Search Console → Sitemaps | Generate and submit a valid sitemap.xml |
| 7 | Thin or duplicate content | "Discovered, currently not indexed" | Expand the content, merge duplicates |
| 8 | Content loads only via JavaScript | Not present in rendered HTML | Server-side rendering or static HTML |
| 9 | Server errors, 4xx, 5xx, soft 404 | Search Console → Pages | Fix redirects and server responses |
Here is what each one means in practice.
1. The Site Is Simply Too New
A new domain needs time. Realistically: a few days to a few weeks before the first pages appear in the index, and up to two or three months before the full structure settles.
What you can speed up:
- Verify the domain in Google Search Console
- Submit sitemap.xml
- Use "Request indexing" for your most important pages (the daily cap is roughly 10 to 12 URLs per property)
- Earn at least a few external links so Google has a path to your site
What not to do: hitting "Request indexing" on the same page every day does not speed anything up.
2. robots.txt Is Blocking Googlebot
This is the most common cause of "everything suddenly disappeared". The site is closed to search engines during development, and the block is forgotten at launch.
Check yourdomain.com/robots.txt. If you see:
User-agent: *
Disallow: /the whole site is closed. It should look more like:
User-agent: *
Allow: /
Sitemap: https://yourdomain.com/sitemap.xmlImportant: robots.txt prevents crawling, but it does not reliably remove a page from the index. To take a page out, use noindex, not Disallow.
3. A noindex Meta Tag
The second most common cause, and it is invisible to the naked eye. In the page source, inside <head>, sits:
<meta name="robots" content="noindex">On WordPress the usual culprit is the "Discourage search engines from indexing this site" setting (Settings → Reading). Turning it on adds noindex across the entire site.
How to check: right-click the page → "View page source" → search for noindex.
4. A Wrong Canonical URL
rel="canonical" tells Google which address is the master version. If every page points at the homepage, Google will index only the homepage and treat the rest as copies.
Search Console reports this as "Alternate page with proper canonical tag" or "Duplicate, Google chose different canonical than user". The rule is simple: every page should point at itself, unless it genuinely is a duplicate of another page.
5. A Page Nothing Links To
Google finds pages by following links. A page with no internal links pointing at it, an orphan page, can exist for a year and stay unnoticed even if it sits in your sitemap.
A practical rule: any important page should be reachable from the homepage in three clicks or fewer. Service pages belong in the menu, articles should link to each other, and every new page needs at least one link from an existing one.
6. Missing or Broken Sitemap
sitemap.xml is the list of pages you want indexed. Common mistakes:
- The sitemap was never submitted to Search Console
- It lists http:// addresses while the site runs on https://
- It contains pages that are noindex or return 404
- It is never regenerated, so new pages never appear in it
A sitemap does not guarantee indexing, but without one Google is working blind.
7. Thin or Duplicate Content
If Search Console shows "Discovered, currently not indexed" or "Crawled, currently not indexed", Google saw the page and decided not to store it. That is a quality problem, not a technical one.
Typical cases:
- A service page with 80 words
- Ten near-identical city pages with the name swapped
- Manufacturer descriptions copied into e-commerce product pages
- Auto-generated tag or filter pages
The fix: fewer pages, more substance in each. One thorough page ranks better than five empty ones.
8. Content Only Available Through JavaScript
Google does process JavaScript, but later and not always completely. If all your text loads after the page renders, part of it may never be seen.
How to check: Search Console → URL Inspection → "View crawled page" → HTML. If your text and links are not there, Google does not see them either.
The fix: your key text, headings and internal links belong in the initial HTML. This also makes the page faster, which we covered in a separate article.
9. Server Errors and Messy Redirects
5xx errors, redirect chains, soft 404s (a page that says "not found" but returns a 200 status) and a slow server response all reduce how many of your pages Google crawls at all.
The "Pages" report in Search Console gives you the exact list. Start there rather than guessing.
Is Indexing Really the Problem?
If a site: search does return your pages, you do not have an indexing problem. The question becomes a different one: why are they not ranking? For the mechanics of ranking itself, including page speed, see our site speed guide.
The usual causes:
| Symptom | The real cause |
|---|---|
| Page is indexed but invisible for the keyword | The content answers the query less precisely than competitors' |
| Only found by company name | No content about the service itself, only about the company |
| Used to rank, dropped | Algorithm update, competitor movement or a technical regression |
| Sitting on page 3 to 5 | Weak page authority and too few internal links |
| Slow on mobile | A technical problem, not an indexing one |
Speed and Core Web Vitals are a topic of their own: a slow page can be perfectly indexed and still lose both visitors and positions.
The Page Is Indexed but I Still Cannot Find It
How you search matters. Type your company name and you will see yourself. Type a competitive keyword and you may be on page three and conclude you are missing.
Also: Google results are personalised by location and browsing history. Check in an incognito window, or use the Search Console "Performance" report, which shows your true average position for each query.
For local services there is a separate layer: the map results, where the ranking asset is your Google Business Profile rather than your website. We have a dedicated guide for that.
Action Plan: From Diagnosis to Fix
- Search
site:yourdomain.comon Google - Open Google Search Console and verify the domain if you have not already
- Inspect the specific URL with the URL Inspection tool and note the exact status
- Review robots.txt and search the page source for noindex
- Check the canonical tag on every important page
- Submit sitemap.xml and make sure it contains only indexable https:// URLs
- Fix the errors listed in the "Pages" report
- Link forgotten pages into your internal structure
- Request indexing for the key pages, then wait
How Long Until You See a Change
| Fix | When it takes effect |
|---|---|
| Removing robots.txt block or noindex | 1 to 7 days |
| Correcting canonical tags | 1 to 3 weeks |
| Submitting a new sitemap | A few days |
| Adding internal links | 2 to 4 weeks |
| Expanding a thin page | 3 to 8 weeks |
| Full indexing of a new domain | 1 to 3 months |
Technical blockers clear quickly. Quality problems such as thin content take longer, because Google has to recrawl and reassess the page.
FAQ
If your page is indexed but still not visible for the queries that matter, the fix is often about how the answer is structured, not just whether the page exists. See our guide to winning Google's featured snippet for the format Google rewards.
A website does not show on Google for one of three reasons: it has not been indexed yet (most often a new site), indexing is technically blocked (robots.txt, a noindex tag or a wrong canonical URL), or the page is indexed but ranks too low to find. Google Search Console's URL Inspection tool shows you the exact status.
The first pages usually appear within days to a few weeks after the domain is verified in Google Search Console and sitemap.xml is submitted. Indexing the full site structure can take one to three months. Without Search Console the process is slower, because Google has no clear signal that the site exists.
Search Google for site: plus the page address, for example site:yourdomain.com/services. If a result appears, the page is in the index. The more precise method is the URL Inspection tool in Google Search Console, which also shows the last crawl date, the canonical URL and the reason if the page is not indexed.
No. robots.txt stops Googlebot from crawling a page, but an already indexed URL can stay in the results without a description. To remove a page from the index, keep it crawlable and add a noindex meta tag so Google can actually see it.
This status means Google knows about the page but decided not to crawl or store it for now. The usual reasons are thin or duplicate content, too few internal links pointing at that page, or a slow server that makes Google limit how much it crawls. The fix is stronger content and structure, not repeated indexing requests.
Google Cannot See Your Site? Let's Find Out Why
AMK Growth runs a technical site audit and tells you within days exactly what is blocking indexing: from robots.txt and noindex to canonical errors, link structure and server responses. We fix visibility not just in Google Search, but on maps and in AI answers too.
Book a Free Consultation