SEO & Technology
Website or page not indexed? All the causes explained
A page that is not indexed is not in Google’s index and therefore cannot appear in the search results. The cause is almost always one of three things: Google is not allowed to include the page, Google cannot fetch it properly, or Google does not consider it valuable enough to keep. In Search Console, you can see which of the three applies to each page.
By Dries Nijs, Organic Web Specialist
Last updated: 19 November 2026
At a glance
Why is my page not in Google? The short answer
Google goes through three steps for every page: discovery, crawling and indexing. If something goes wrong in one of those steps, the page gets the status ‘not indexed’ in Search Console, along with a reason. That reason is your starting point: it tells you whether you need to unblock something, fix something or improve the page itself.
Not every status is a problem. A shopping basket, a thank-you page or an old URL that redirects does not belong in the index. It only becomes a problem when pages that should bring in visitors, such as your services, products or articles, appear on that list.
If you have a new website, patience is sometimes the whole answer. If a page is still not in Google after a few weeks, there is usually an identifiable cause.

Measure first
How do you check whether a page is indexed?
Do not rely on a hunch or a single search. Together, these three checks give a reliable picture, from quick to thorough.
01
Search with site:
In Google, type site:jouwdomein.be, or the full address of a single page. You will see roughly which pages are in the index. It is an indication, not an exact count.
02
Use URL Inspection
Paste the address into the search bar at the top of Search Console. You will see whether the URL is on Google, when it was last crawled and which canonical URL Google has selected.
03
Open the Page indexing report
Under ‘Indexing’, you can see how many pages are and are not indexed, grouped by reason. Click a reason to see the affected URLs.
04
Look at the pattern
Is it one page, one type of page or the entire website? One page points to the content or a setting, a whole group to a template, the entire website to a block.
Diagnosis
The three causes behind every status
However many statuses Search Console shows, they fall into three groups. Once you know the group, you know in which direction the solution lies.
Setting
Google is not allowed
A noindex tag, a rule in robots.txt, a password or a canonical pointing to another page. Often a setting left on after the build, such as ‘Discourage search engines from indexing this site’ in WordPress.
Technology
Google is not able
The server returns an error, the page no longer exists, a redirect gets stuck or the content only appears after JavaScript that is not executed properly.
Quality
Google is not willing
The page is reachable and allowed, but Google does not include it: too little original content, almost identical to another page, or barely linked internally.
You solve the first two groups with a change to the website. The third requires more: the page itself has to get better, or you have to decide that it does not need to be in the index.
Search Console
All statuses in Search Console, with the solution
These are the reasons you will come across most often in the Page indexing report. The names follow the English-language Search Console; the wording may vary slightly between versions. Google describes each status in the Page indexing report help page.
| Status | What it means | What to do |
|---|---|---|
| Crawled – currently not indexed | Google has fetched and read the page, but not included it. | Improve the content, add internal links or merge the page with a stronger one. |
| Discovered – currently not indexed | Google knows the address, but has not crawled the page yet. | For a new website: wait. If it takes a long time: check internal links, the sitemap and server speed. |
| URL marked ‘noindex’ | The page itself asks not to be included. Also shown as “Excluded by ‘noindex’ tag”. | Intentional? Do nothing. Unintentional? Remove the noindex in your SEO plugin, your template or the HTTP header. |
| Blocked by robots.txt | Google is not allowed to crawl the page. | Adjust the rule in robots.txt if the page does need to be found. |
| Page with redirect | The address redirects to another address. | Normal for old URLs. Do check that internal links and the sitemap point to the final address. |
| Alternate page with proper canonical tag | The page names another URL as the preferred version, and Google follows that. | Usually fine. Only step in if the canonical points to the wrong page. |
| Duplicate without user-selected canonical | Google sees duplicate content and chose a preferred version itself. | Set a canonical, or avoid or redirect the duplicate URLs. |
| Duplicate, Google chose different canonical than user | Your canonical is not being followed because other signals contradict it. | Align internal links, the sitemap and redirects with the canonical. |
| Redirect error | The redirect loops, is too long or contains an invalid address. | Shorten the chain: every old address goes to the final address in one step. |
| Not found (404) | The page does not exist (any more). | Removed and replaced? Redirect. Removed without a replacement? Leave it, and remove internal links to it. |
| Soft 404 | The page returns code 200, but appears empty or looks like an error page. | Show real content, or return a genuine 404 or a redirect. |
| Server error (5xx) | The server returned an error when Google requested the page. | Look for the cause in the hosting or the code: overload, timeouts or an error in a plugin. |
Once you have fixed a cause, you can click ‘Validate fix’ in the report. Google then rechecks the affected URLs. That can take a few weeks.
The two trickiest
Crawled or discovered, but not indexed: what is the difference?
Discovered – currently not indexed
Google knows the URL exists, through a link or your sitemap, but has not visited it yet. In Search Console, this status is called ‘Discovered – currently not indexed’; translated versions of Search Console sometimes word it differently. For a new website, this is simply the queue. If a large group of pages stays stuck here, Google is postponing the crawl. That happens when the server responds slowly, when there are many near-identical URLs, such as filters and search results, or when nothing on the website links to those pages.
Crawled – currently not indexed
Here, Google has visited and has decided not to include the page for now. That is a judgement about the page, not a technical error. A new indexing request rarely changes that. What does help:
- Original content: does the page answer a question that no other page on your website already answers?
- Internal links: is it linked to from relevant pages, or does it only exist in the sitemap?
- Merging: five thin pages on the same topic are weaker than one complete page.
- Leaving out: tag pages, empty categories and internal search results do not need to be in the index. In that case, a noindex is more honest than hoping.
If your most important pages have this status, that is a signal about the website as a whole: too many pages with too little value of their own.
Often overlooked
Causes you will not spot at a glance
Some blocks are not on the page itself, or are only visible to someone who looks at the code or the server response.
- A noindex in the HTTP header The header
X-Robots-Tagdoes the same as the meta tag, but is not in the HTML. You only see it in the server response. - A forgotten setting from the test environment A website that was hidden from search engines during the build sometimes goes live with that block still in place.
- Content that only appears after JavaScript If the text is not in the HTML the server sends, everything depends on how well Google can render the page.
- A canonical pointing to another page One mistake in a template, and hundreds of pages point to the homepage as their preferred version. See Canonical tag: explanation and common mistakes.
- Orphan pages Pages that no internal link points to. Google has difficulty finding them and rates them low.
- Blocked and noindexed If robots.txt blocks the page, Google cannot read the noindex. The URL can then still turn up in the results, without a description. More about robots.txt in robots.txt and AI crawlers.
Action
How do you get a page (re)indexed?
You can ask Google to look at a page. You cannot force it to include the page. This order has the most effect.
Requesting the same URL repeatedly does not speed anything up. There is also a daily limit on requests.
01
Fix the cause first
A request for a page with a noindex or a server error results in the same status.
02
Test the live URL
In URL Inspection, ‘Test live URL’ checks whether Google can fetch the page now and whether indexing is allowed.
03
Request indexing
In URL Inspection, click ‘Request indexing’. That puts the page in a priority queue, without a guarantee.
04
Submit a sitemap
For many pages at once, an XML sitemap with only indexable, canonical URLs works better than individual requests.
05
Link to it
A link from a page that Google visits often, such as your homepage or a main page, is the strongest signal that a page matters.
New website
My new website is not in Google yet
A new website does not appear in the search results on the day it goes live. Google first has to discover, crawl and process the domain. Google itself mentions a period of a few days to a few weeks, without a firm promise. A domain with no history and no links from other websites is at the back of that queue.
You can speed it up by setting up Search Console, submitting a sitemap and making sure at least one existing website links to you: a business profile, a partner or a professional association. Also check that the test environment’s block has been switched off. That is the most common reason why a newly launched website remains completely invisible.
Is your website in the index, but you cannot find it for your most important keywords? Then it is not an indexing problem but a matter of ranking: the page is in the running, but too far down. That calls for a different approach, and usually starts with an SEO audit.
FAQ
Frequently asked questions about indexing
What does indexed mean?
Indexed means that Google has fetched a page, processed it and stored it in its index, the database from which the search results are compiled. Only indexed pages can appear in Google. Being indexed says nothing yet about ranking.
How long does it take for Google to index a website?
There is no fixed timeframe. Google itself speaks of a few days to a few weeks. An existing website with regular new content is visited more quickly than a new domain without links.
Why is Google not finding my website?
Either it is not in the index, because of a block, a technical error or content that is too thin, or it is in the index but ranks too low for the keywords you are testing. URL Inspection in Search Console shows you immediately which of the two it is.
How can I get Google to re-index my website?
For a single page: URL Inspection in Search Console and ‘Request indexing’. For an entire website: submit an up-to-date XML sitemap. Google decides for itself when it visits and what it includes.
Does every page on my website need to be indexed?
No. Pages without search value, such as the shopping basket, internal search results, thank-you pages or thin archives, do not belong in the index. A website with only strong pages in the index is in a better position than one with hundreds of weak ones.
Is ‘not indexed’ a penalty from Google?
Almost never. A manual action is rare and is listed separately in Search Console, under ‘Security & Manual Actions’. The statuses in the Page indexing report are technical findings, not sanctions.
Further reading
The related service
Technical SEO as a service
Are important pages staying out of the index, or do you not know where the cause lies? On the service page, you can read how I investigate and fix crawlability, rendering and indexing.

About the author
Dries Nijs, Organic Web Specialist
I am Dries Nijs, a developer and SEO consultant from Maasmechelen. I investigate indexing problems in a website’s code and server responses, not just in a report. MadeByDries is the personal brand under which I work.
Are your pages staying out of Google?
Send me your website address and what you see in Search Console. Then we will look at where it gets stuck.