Indexing in Google: why the site is not visible and how to fix it
You have a website ready, but you can't find it in the search? Pages must be in the index at all before you start addressing positions. We will show you how to check indexing, why pages are not indexed and how to fix it step by step.
What is indexing and why everything depends on it
Before a page can be placed in the search results, it must go through two steps: the search engine must first find and download it (crawl) and then include it in its index (index). Only what is in the index can be displayed to users at all. Addressing positions or keywords for a page that is not in the index makes no sense — it is invisible to the search engine.
A common misunderstanding: "I have a website online, so it's in Google". It's not automatic. Google has to discover a website, crawl it, and decide to index it — and at each of those steps, something can go wrong.
How to find out if a page is in the index
Quick orientation check: enter `site:vasedomena.cz` in Google. You will see the approximate number of indexed pages. Be careful — this operator is imprecise and sampled, so take it only as a rough signal, not the truth.
A reliable source is Google Search Console, "Page Indexing" section. It will show exactly which pages are indexed, which are not and most importantly why (exclusion reasons). You can check a specific URL via the "URL Checker", which will tell you the current status and allow you to request indexing.
The most common reasons why a page is not indexed
- Blocking in robots.txt — the file prohibits search engines from crawling the page. Then Google won't download it at all.
- The noindex tag — in the header of the page (meta robots) or in the HTTP header X-Robots-Tag is the instruction "do not index". A common pitfall after moving from a test site to production.
- Canonicalization elsewhere — canonical refers to another URL, so Google indexes it instead of this page (typically everything merges on the homepage).
- The page is not linked anywhere — the search engine has no way to discover it (the link and the record in the sitemap are missing).
- Thin or duplicate content — Google crawls the page, but rates it as insufficiently valuable ("Passed - not indexed").
- Server errors or slow response — when the page returns 5xx or takes a long time to load, the crawl will not complete.
- New or weak domain — young sites with little authority take weeks to index the entire site; Google crawls slowly.
How to fix indexing step by step
Work your way from the hardest blocks to the subtle causes — there's no point in addressing content while the page is blocked by robots.txt.
- Check robots.txt that it does not prohibit important sections (Disallow lines). Unblock what should be public.
- Check that the page does not have noindex in the meta robots or in the HTTP header. If it's left over from development, delete it.
- Verify canonical — it should point to itself (self-referencing), not to another page, unless that's the intention.
- Return HTTP status 200 for pages to be indexed; handle non-existent via 404/410, redirect via 301.
- Complete the page in an XML sitemap and crosslink it from relevant pages so that the search engine discovers it.
- For thin content, add value — original text, answers to user questions, structure with headings.
- In Search Console, request indexing of key URLs and resubmit the sitemap. Then wait — the recrawl takes days to weeks.
How to help Google faster
You direct the search engine with three things: an up-to-date XML sitemap sent in the Search Console, high-quality internal linking (link new pages from strong, already indexed pages) and backlinks from trusted websites that will bring the crawler first.
Be patient with a brand new website — even a technically perfect website is indexed gradually on a young domain. Do not trust the `site:` operator, follow the report in Search Console.
Indexing and Search Engine AI (GEO)
The same logic applies to generative search engines like ChatGPT, Perplexity or Google AI Overviews — if they can't read and process your content, they can't cite you. The access of AI bots is again controlled by robots.txt (and additionally the file llms.txt), so only block them consciously. A readable, structured and interlinked website is easier to get into both the classic index and the AI answers.
How to verify indexing and its obstacles
After each major modification of the website, it is worthwhile to repeat the check. Our indexability tool goes through the page and points out noindex, blocking in robots.txt, incorrect canonical and missing sitemap — that is, all technical obstacles that prevent indexing. In particular, check the robots.txt and XML sitemap itself so that Google gets the right instructions.
Frequently asked questions
How long does it take for Google to index a new website?
For a new domain with little authority, it can take days to weeks, for large sites even longer. You can speed up the process by submitting a sitemap in Search Console, requesting indexing of key URLs and high-quality internal linking.
Why is Search Console reporting "Passed - Not Indexed"?
Google has pulled the page but decided not to rank it (yet) — most often due to thin, duplicate or low-value content. Add the original value and link the page.
Does the page get indexed when it is in the sitemap?
A sitemap helps a page to be discovered, but is not a guarantee of indexation. The page must not be blocked (robots.txt/noindex), must return 200, be self-canonical and carry sufficiently valuable content.
Is site: operator reliable?
No. `site:vasedomena.cz` is only a rough orientation — it is sampled and delayed. You can find the exact numbers and reasons for exclusion in Google Search Console in the "Page Indexing" report.