Why is a page not indexed by Google?
A page is usually not indexed because Google has not discovered the URL yet, cannot crawl the page properly, hits an indexing block, chooses a different URL as the main version, or decides the content is not valuable enough. A page that is technically reachable does not automatically end up in the Google index.
This guide helps you find the real cause. Start in Google Search Console. Then check access, status code, noindex, canonical, content, and internal links. Always fix the reported cause first. Asking for reindexing without improving anything usually does not help.
- Why is a page not indexed by Google?
- How do you check indexing with URL inspection?
- How do you check this on your own website?
- How do you improve indexing step by step?
- When is the content itself the indexing problem?
- What do you do with crawled but currently not indexed?
- Frequently asked questions about a not indexed page
Why is a page not indexed by Google?
Google Search works in three broad steps. First, Google discovers and crawls a URL. Then Google analyzes the content and decides whether the page should enter the index. Only after that can an indexed page appear for a suitable search query.
Not every URL goes through all these steps. Google does not guarantee crawling, indexing, or rankings. A page can be technically fine and still not be included. This happens, for example, with new pages, duplicate pages, very weak content, or pages that seem unimportant within the website.
The minimum technical requirements are clear. Googlebot must not be blocked. The page must return a successful status code and must contain indexable content. Meeting these requirements makes a page eligible for indexing, but it still does not guarantee anything.
So do not make general assumptions. Inspect the exact URL in Search Console. Check the reported indexing status, the last crawl, crawl permission, any noindex, and the chosen canonical.
A page that is indexed but does not rank has a different problem. In that case, read why a website does not rank in Google.
Why does indexing affect visibility in Google?
Only pages in the Google index can normally be selected as search results. Without indexing, even an excellent text cannot get organic clicks from Google. So check indexing first before trying to improve titles, keywords, or positions.
Indexing is not proof of high quality and also not a guarantee of a strong position. Google still has to find the page relevant and useful for a specific query. Language, location, device, competition, and other signals all play a role.
A major indexing problem can distort your measurements. You may think there is no demand for a topic, while the right page was never added to the index. Always check important URLs individually.
Not all URLs need to be indexed. Shopping carts, internal search results, duplicate filters, and private pages often should not appear in search results. The goal is not the highest possible indexing rate. The goal is to make important and unique pages available in Google.
Make a deliberate choice for every excluded group. A valid exclusion can be healthy for your website. An important product page that accidentally has a noindex needs immediate action.
How do you check indexing with URL inspection?
Open Google Search Console and paste the full URL into URL Inspection. First check whether you are using the correct property. Differences between http, https, www, and a subdomain may mean that you need a different property.
First read the status from the Google index. Check whether the URL is indexed and which reason Google mentions for an exclusion. Then check the last known crawl, whether crawling is allowed, whether indexing is allowed, and which canonical Google selected.
Then use the live test to check the current version of the page. Index data can show information from an older crawl. A live test shows whether Googlebot can reach and render the page right now.
Compare the two results carefully. Was the old page blocked, but does the live version now work? Then a new crawl may be enough. Does the live test also show an error? Fix that error first.
Request indexing only after you have made a real improvement. An indexing request is not a guarantee. It does not automatically make a weak, blocked, or duplicate page suitable for the index.
Can Googlebot crawl the page?
First check the robots.txt file. A rule in this file can deny Googlebot access to an entire path. Keep in mind that robots.txt controls crawling and does not reliably remove a page from the index. A blocked URL can sometimes still appear without content when other websites or pages link to it.
Also check access at server level. A login, firewall, security plugin, country block, or bot protection can stop Googlebot. Do not test only in your own browser. You may have a valid cookie, an active login, or an allowed location.
Check the server logs if the problem continues. Look for requests from Googlebot and verify the received status codes and timings. Confirm real Google crawlers with the official method before you change any block.
Also watch for temporary outages. Many 500 status codes and long timeouts can cause Google to crawl less often. A stable and fast server is therefore more important than constantly sending new indexing requests by hand.
Does the content only appear after scripts run? Then check the rendered HTML in URL Inspection. Google can render JavaScript, but an error or blocked resource can make the main content invisible.
Does the page return the correct HTTP status code?
An indexable page should normally return HTTP status code 200. Pages with status code 404, 410, or a server error are not indexed as normal working content.
A soft 404 technically returns status code 200, but looks like an error page in terms of content. This happens, for example, with empty categories, removed products with only a short message, or pages without unique content. Make such a page useful or return the proper error status.
A redirect sends Google to another URL. Always check where the redirect ends. A long chain, a loop, or a redirect to an unrelated homepage makes the intent unclear.
Test the exact URL variant. A slash, uppercase letter, parameter, or language path can lead to a different response. Choose one preferred version and use it consistently everywhere.
Check the status code with URL Inspection, server logs, or a reliable HTTP tool. Do not rely only on what the browser shows visually. A page can look normal and still return the wrong status code technically.
Does noindex block the page?
A meta robots noindex or an X Robots Tag in the HTTP headers asks search engines not to index the page. This is often the right setting for unwanted results. It only becomes harmful when it is applied by accident to important content.
Check the final HTML and the HTTP headers. A CMS, SEO plugin, or template can add the setting automatically. Also check different devices, page types, and languages when templates differ.
Do not block the page in robots.txt at the same time if you want Google to be able to read the noindex instruction. Google must be able to crawl the page to find and process that instruction.
Remove noindex only when the page is truly allowed to appear in Google. Then run a live test and request indexing if needed.
Removing noindex does not guarantee a ranking. The page must be crawled again, processed, and selected as a suitable main version again.
Does Google choose a different canonical URL?
Google groups duplicate or highly similar pages and chooses a canonical from them. This is the URL Google sees as the main version. The other URLs may be excluded, while the chosen main version is indexed. That is often normal and does not have to be a problem.
In URL Inspection, check both the canonical you specified and the canonical Google selected. A difference can point to conflicting signals or signals that are not strong enough.
Make sure internal links, the sitemap, redirects, and canonicals all point to the same preferred version. Do not use a canonical to a page about a different topic.
Make language versions truly translated and locally relevant. Use hreflang where appropriate. Still let each language page point to itself as canonical when they are standalone variants.
Remove unnecessary parameter combinations and duplicate paths as much as possible at the source. A canonical can help, but a simple and consistent URL structure is easier to crawl and maintain.
How do you check this on your own website?
Start with the Page indexing report in Search Console. Group the different exclusion reasons. First choose groups that contain important pages. A large number of unwanted filter URLs may be less urgent than one excluded sales page.
Inspect a few examples per group. Check the live test, status code, robots.txt, noindex, canonical, sitemap, and internal links. Then look for a shared cause in the technical setup or template.
Crawl the website and compare the found URLs with your sitemap and main navigation. Mark orphan pages that are not linked internally anywhere. Google discovers most URLs through links.
Then assess the content. Is the page unique, complete, and clearly made for people? A technically perfect page with almost no unique value can still stay out of the index.
| Check point | How to check it | Solution | Priority |
|---|---|---|---|
| Important URL has noindex | URL Inspection, HTML, and HTTP headers | Remove noindex from the correct template | Very high |
| Googlebot is blocked | Live test, robots.txt, and server logs | Allow access to important public pages | Very high |
| Server does not return status code 200 | URL Inspection and HTTP check | Fix the error, server issue, or redirect | Very high |
| Google chooses a different canonical | Compare the declared and chosen canonical | Make canonical, internal links, and sitemap consistent | High |
| Page is not linked internally anywhere | Crawler and internal link report | Link from relevant and accessible pages | High |
| Content is thin or duplicate | Compare pages and search intent | Add unique value or merge pages | High |
Which mistakes most often block indexing?
Keep requesting indexing without fixing the cause
An indexing request does not change noindex, server errors, duplicates, or weak content. Always fix the problem first that Search Console or the live test reports.
Using robots.txt as noindex
Robots.txt blocks crawling. Use a noindex instruction for a public page that should not appear in the index. Make sure Google can crawl the page and read the instruction.
Treating every exclusion as a mistake
Redirects, duplicates, and intentionally excluded pages can be normal and desirable. Give priority to important and unique URLs that should be indexed.
Looking only at the sitemap
A sitemap helps Google discover URLs, but it does not guarantee crawling, indexing, or rankings. Internal links, good technical setup, and page quality still matter.
Using the wrong canonical
A canonical to the homepage, a different search intent, or an unrelated language page can cause the desired URL to be excluded.
Confusing indexed with visible rankings
An indexed URL can still sit outside the first search results. So check search intent, relevance, content quality, and competition separately.
How do you improve indexing step by step?
- Choose one important excluded URL.
- Inspect the full URL in Search Console.
- Run a live test.
- Check access, status code, and rendered content.
- Check noindex and the HTTP headers.
- Compare the declared canonical with the chosen canonical.
- Add the correct preferred version to the sitemap.
- Place relevant internal links to the page.
- Improve duplicate, thin, or insufficiently useful content.
- After the fix, request indexing and keep monitoring the group.
Prefer working by pattern. If one hundred URLs all receive a noindex through the same template, you do not need to adjust every page separately. Fix the template once and then test different examples. A backlink is not a solution for a block you set yourself.
How do you use a sitemap and internal links properly?
Put only the preferred versions of important and indexable URLs in the sitemap. Remove redirects, error pages, noindex pages, and unnecessary duplicates from the file.
Use the lastmod date honestly. Update this date only when the page has changed in substance. Automatically showing a new date all the time without a real change does not improve quality.
Submit the sitemap in Search Console and check whether there are reading errors. Successful processing only means Google can use the file. It does not guarantee that every URL will be crawled or indexed.
Link important pages from relevant and accessible pages. Use normal anchor elements with an href and descriptive anchor text. Do not hide the only route to a page in a script that Google may not reliably process.
Also build a logical website structure. A user and search engine should understand from the navigation and content where a page belongs and why it matters.
When is the content itself the indexing problem?
Google names low content quality as a possible cause of an indexing problem. A page with only a few general sentences, copied text, or nearly the same content as dozens of other URLs gives Google little reason to include a separate version.
Answer a specific question fully. Add your own experience, clear examples, primary sources, or useful data. Also make it clear who the page is for and which problem the content solves.
Do not add words only to reach a certain length. Google does not use a fixed preferred word count. Complete means the visitor gets enough information to achieve their goal.
Merge pages when they serve the same task and the same search intent. Choose one strong main version and keep internal signals consistent. Keep separate URLs only when they truly offer visitors something different.
Also check the title and main heading. They should describe the real content of the page. They must not promise an answer the page does not actually give.
How do you check JavaScript and rendered content?
Google renders pages with a recent version of Chrome. Still, content can be missing when a script throws an error, an important resource is blocked, or data loads only after manual interaction.
Use the live test in Search Console and view the rendered HTML or screenshot. Check whether the main text, internal links, and important images are present.
Place essential information as much as possible in the first HTML response or use reliable server-side rendering. Do not build important navigation only with elements that do not contain an href.
Check error messages in the browser and server logs. Test with empty cookies and a normal mobile connection. A page that works only for logged-in users is not publicly indexable.
After a technical change, test multiple templates. A product page can be built and rendered differently from a blog, landing page, or category.
Which measurement shows whether the improvement works?
Use the Page indexing report and follow the specific reason you fixed. Check whether the number of important affected URLs decreases after new crawls.
Also inspect a few examples again. Look at the new crawl date, chosen canonical, and indexing status. A chart for a full group can also contain other URL types.
Then filter the Performance report on the fixed pages. Impressions show that the pages can appear for search queries. No impressions do not automatically mean indexing is broken again. The page may still be insufficiently relevant or ranking too low.
Keep a change log. Note the template, date, URL group, found cause, and chosen solution. That makes it easier to explain a later rise, drop, or new error.
Do not expect a fixed timeframe. Crawling and indexing depend on many factors. A new and small website sometimes needs more patience than a large news site that Google crawls often.
What does a practical repair example look like?
An online store discovers that new categories are not indexed. URL Inspection shows a noindex. The live test confirms that the instruction is still present. The cause turns out to be a wrong setting in the category template.
The developer removes the noindex only for public categories with products and their own explanation. Empty filters stay intentionally excluded. After that, the team checks the status code, canonical, and internal links.
The correct category URLs are added to the sitemap. The team then tests several examples with the live test. Only after everything works properly does the team request indexing.
In the following weeks, the team checks whether the relevant reason decreases in the indexing report. After that, it reviews impressions and search queries. This way, the technical problem is solved first and performance is assessed separately afterwards.
How do you prioritize thousands of excluded URLs?
Do not start automatically with the biggest number. First determine which groups contain important and unique pages. One million excluded filter URLs may be fine, while ten excluded core products can directly cost revenue.
Make a sample per exclusion reason. Check at least several URLs from different templates. Look for a shared cause before you start adjusting individual pages.
Give very high priority to blocks, noindex instructions, and server errors on important URLs. Give normal priority to intentional duplicates and old redirects that work correctly.
Measure the same group again after the fix. That way you can see whether the template change really worked. You also avoid a falling total hiding a different problem.
What do you do with discovered but currently not indexed?
This message means Google knows the URL, but has not crawled the page yet. First check whether the page is new and whether the server is stable. For a new website, it can take time before Google visits all pages.
Check internal links and the sitemap. Important pages must be logically reachable. Avoid large numbers of nearly identical URLs that spread attention over unnecessary variants.
Check server capacity and crawl statistics when many important pages stay in this status for a long time. Do not keep requesting indexing again and again for thousands of URLs. That will not solve a website structure or server problem.
Improve the website structure and remove unnecessary crawl waste. Then give Google enough time to rediscover and process the changes.
What do you do with crawled but currently not indexed?
This message means Google visited the page but did not include it in the index. First check the canonical, noindex, and content. Compare the page with other URLs that give almost the same answer.
Add only value that visitors truly need. Do not make a small cosmetic change only to request indexing again. Clarify the page’s task, add your own information, or merge overlapping pages.
Also check whether the page is treated as important internally. An isolated URL without relevant internal links gives users and search engines little context.
After a real improvement, you can live test the page and request indexing. If the page remains excluded, honestly assess whether a separate URL is really necessary.
Keep the date, status, and chosen solution for every check. That way you can later see whether the same pattern returns after an update, migration, or CMS change.
Also share this information with developers, editors, and other team members involved. That helps prevent a fixed problem from coming back after a later change.
What questions are often asked about a not indexed page?
Why is indexing important for SEO?
A page normally has to be in the Google index before Google can show it as a search result. Indexing alone still does not guarantee a high position or organic traffic.
How do I check myself whether a page is indexed?
Use URL Inspection in Google Search Console. Check the indexing status, live test, permission to crawl, noindex, canonical, and the date of the last crawl.
What tool do I need for this?
Google Search Console is the main free source. A website crawler, HTTP check, and server logs help with larger or more complex technical problems.
How fast is a page indexed?
There is no fixed timeframe and Google gives no guarantee. Discovery, crawling, technical setup, content quality, and the importance of the page all matter.
What is the most common mistake?
The most common mistake is requesting indexing again without fixing the reported cause. So always check the current page first with the live test.
When is help from a specialist useful?
For large template errors, migrations, rendering issues, or thousands of wrong canonicals, a technical SEO specialist can often find patterns and shared causes faster.
Which SEO action has the highest priority now?
Inspect your most important excluded URL today. Write down the exact reason from Search Console and use a live test to check whether that cause still exists. Then fix one concrete issue and test the page again.
Only start content promotion or other SEO actions when Google can reach and index the right page. Then compare organic visibility with other channels using the difference between SEO and Google Ads.
