When reviewing the Page Indexing report in Search Console, it is common to find some URLs under the “Crawled – currently not indexed” status. Sometimes, this may even include important pages that we expected to find in the search results.
This status does not reveal the exact problem on its own, nor does it necessarily mean that there is a technical issue. To determine whether we need to take action, we first need to understand what types of URLs appear in the report and why they may have been left out of the index.
Contents
What does “Crawled – currently not indexed” mean?
The “Crawled – currently not indexed” status means that Googlebot has visited the URL, but the page has not been added to Google’s index. As a result, the page cannot appear in the search results while it remains in this situation.
Crawling and indexing are two different processes. During crawling, Googlebot accesses a URL and downloads its content. Later, during indexing, the information on the page is analyzed to determine whether it should be stored in the index and which version of the content should be treated as the main one. Not every page that is processed ultimately becomes part of the index.
The word “currently” is also important. A URL with this status may be indexed later without us making any changes, although it may also remain excluded if Google continues to find no compelling reason to include it.
Therefore, this message should not be interpreted as an error with a single solution. Search Console shows us the result of the process, but not the exact reason why the page was not indexed.
Is this an error we need to fix?
Before changing the content or technical configuration of the website, we need to ask ourselves whether the affected URLs should actually appear in the search results. Not every page that Google crawls needs to be indexed.
The report may include RSS feeds, parameterized URLs, files, filtered pages, internal search results, or alternative versions of the same content. Googlebot may discover and crawl these URLs even when they do not provide enough value as standalone search results.
Paginated pages, out-of-stock products, empty pages, or URLs automatically created by the CMS may also appear. In many of these cases, the URL not being indexed may be the expected behavior, and there would be no need to try to fix it.
The situation is different when the report includes articles, categories, product pages, or service pages that we want to rank. If an important URL has remained in the report for some time, we should analyze it to determine whether the problem lies in the content, its relationship with the rest of the website, or the way Google accesses it.
We should not assess the issue based solely on the number of affected URLs either. Having hundreds of excluded URLs is not necessarily concerning if they are parameters or pages with no value for search users. However, even a small number of URLs may be important if they correspond to the website’s main commercial pages.
How to analyze the affected URLs in Search Console
The first step is to open the Page Indexing report, select the “Crawled – currently not indexed” status, and review the examples provided by Search Console. If there are many URLs, we can also export them to make the analysis easier.
It is not advisable to study every URL individually from the beginning. It is usually more useful to group them by page type, directory, or template to check whether they share any common characteristics.
For example, we may discover that most of them are out-of-stock product pages, articles published during a particular period, or pages created using the same template. Identifying this pattern allows us to focus the analysis on the possible source of the problem instead of applying different changes to every URL.
Once the main groups have been identified, we can select several representative URLs and analyze them using the URL Inspection tool. This allows us to check the last crawl, the user-declared canonical, the Google-selected canonical, and other indexing-related information.
It is also advisable to use the Test Live URL feature. This test shows whether Googlebot can currently access the page and allows us to review the rendered HTML, a screenshot, and any resources that could not be loaded.
The version seen by Googlebot does not always match the version we see in the browser. A page may appear to work correctly for users while showing only an empty structure or part of its content when it is processed without certain resources.
URL Inspection may also reveal that a URL listed in the report is already indexed. Search Console’s general reports do not always reflect changes immediately, so important pages should be checked individually before we make any modifications.
On larger websites, server logs can provide additional information. They allow us to see how often Googlebot visits the pages, which response codes it encounters, and whether there are intermittent errors that may not appear during a one-time test.
Why does Google crawl a page but not index it?
There is no single reason that explains every URL included under this status. Two apparently similar pages may remain outside the index for different reasons.
For this reason, we should not apply broad changes across the entire website without first identifying a pattern. Adding more text, requesting indexing again, or creating internal links may be useful in some cases, but none of these actions will solve every possible problem.
The following are some of the most common situations we may encounter.
Google has not reassessed the page yet
A new URL may be crawled shortly after it is published without being added to the index immediately. The process is not always completed during the first visit, and the page may be reassessed during subsequent crawls.
This is more common on new websites, sites that publish large numbers of URLs, or pages that receive few internal and external signals. The amount of time that has passed since publication should also be considered before assuming that there is a problem.
In these cases, repeatedly requesting indexing will not necessarily speed up the process. Crawl requests are subject to limits, do not guarantee that the page will be indexed, and submitting the same URL several times will not make Googlebot return sooner.
If the page is recent, properly linked, and has no obvious errors, waiting may be enough. However, if it has remained under the same status for several weeks or months, we will need to investigate the other possible causes.
The content does not provide enough standalone value
A page may be technically crawlable and indexable but still fail to provide enough value as a search result. This can happen when the content is too basic, incomplete, or adds very little information compared with other available pages.
This is not simply a matter of length. A short answer can fully address a specific need, while a long article may repeat the same ideas without providing anything useful.
To evaluate the page, we need to check whether it genuinely satisfies the search intent and whether users would find all the information they need. It is also useful to compare it with other results to understand what type of content is being shown for those searches.
The goal should not be to copy the structure of other results or increase the word count until we reach a particular number. The page should provide a clearer explanation, original data, examples, first-hand experience, useful images, or another element that justifies its existence as a standalone search result.
This issue often appears on pages created at scale using the same template. Even if certain words, products, or locations change, the main content may be practically identical across all of them and provide very little specific information.
The content is duplicate or too similar
During indexing, pages are compared with other similar content. When several URLs display practically the same information, they are grouped together and one main or canonical version is selected.
The remaining URLs do not necessarily appear as errors. They may simply be left out of the index because another page represents that group of content more effectively.
This can happen with product pages that have minor variations, filtered categories, articles targeting the same search intent, or local pages where only the city name changes. It may also occur when the same content is available through multiple URLs because of parameters, protocols, or CMS configurations.
The canonical tag allows us to indicate our preferred version, but it is not an absolute directive. Redirects, canonical tags, the sitemap, and internal links all act as signals, and it is important that they consistently point to the same URL.
If two important pages are competing with each other, it may be more appropriate to clearly differentiate them or combine them into a single, more complete piece of content. Maintaining numerous URLs with minor variations does not guarantee that all of them will eventually be indexed.
The page has limited internal linking
A page that is isolated within the website architecture may appear unimportant, even if it is included in the sitemap. This is particularly common when it receives no internal links or can only be reached after navigating through many other pages.
Internal links help Googlebot discover URLs, but they also provide context about their content and their relationship with other parts of the website. An important page should be linked from relevant content using anchor text that helps users and search engines understand what they will find there.
There is no need to add links from every page or create artificial link blocks solely to try to get a URL indexed. The links should make sense for users and appear within related content.
We should also make sure that the links are crawlable. Googlebot needs to be able to find them in supported HTML elements, and the important URL should be reachable from another known page on the website.
Internal linking will not solve a duplicate page or a page with no useful content, but it can help when the problem involves an isolated URL or one whose importance within the website is unclear.
Google cannot properly see the content
A URL returning a 200 status code does not mean that all of its content is being processed correctly. Some pages depend on JavaScript, API calls, or other resources that may fail during crawling or rendering.
In these cases, Googlebot may encounter an almost empty page, a loading screen, or only the elements shared by the template. From Googlebot’s perspective, the URL would contain far less content than users can see.
The Test Live URL feature in Search Console allows us to check the rendered HTML and screenshot. If the main content does not appear there, we need to review the JavaScript implementation, blocked resources, response times, and any errors generated during loading. Content that is unavailable in the rendered HTML cannot be used during indexing.
The robots.txt file can also cause indirect problems. Even if the page itself can be crawled, CSS files, JavaScript files, or other requests required to display the main content may be blocked.
We should also review the server’s behavior. An incomplete response, a temporary error, or a page that loads differently for Googlebot may cause the processed content to differ from what we expected.
The URL is not a useful search result
Some URLs exist for technical or navigational purposes but are not intended to attract users from Google. Feeds, certain parameters, internal search results, or pages generated by filters may belong to this group.
Googlebot may discover these URLs through links, old sitemaps, or external references. The fact that Google crawls them does not mean that all of them need to be indexed.
Before trying to index them, we need to consider whether they provide a useful and independent answer. A URL that displays practically the same content as the main category page, but in a different order, probably does not need to appear in the search results.
When these pages should not be indexed, we need to manage their creation and signals consistently. Depending on the situation, it may be enough to remove them from the sitemap, avoid unnecessary internal links, use a canonical tag, or prevent indexing.
How to fix “Crawled – currently not indexed”
The solution will depend on why each group of URLs has been left out of the index. This is why we should not begin by requesting indexing for every page or adding text without understanding what we are trying to fix.
First, we need to separate the URLs we want to rank from those that provide no value in search. We can then determine whether the important pages have a technical, content-related, or internal-signals problem.
Changes should address the pattern we have identified. If all the affected URLs use the same template, it will make more sense to fix that template than to manually edit hundreds of individual pages.
Determine whether the page should be indexed
The first question is simple: do we expect users to find this URL directly through a search? To answer it, we need to consider the purpose of the page rather than simply the fact that it exists on the website.
An available product page, a useful article, or a service page may have a clear purpose in the search results. A feed, temporary filter, or empty page, on the other hand, is unlikely to provide a useful answer on its own.
If the URL should not appear on Google, we do not need to fix the status. Instead, we should review why the URL is being generated, linked, or included in the sitemap and decide how we want to manage it.
If the page is important, however, we need to identify what is limiting its indexing. Making this distinction at the beginning prevents us from spending time on URLs that should not be part of the index.
Make sure the page is technically indexable
The page must respond correctly and allow Googlebot to access it. We also need to check that it does not contain a noindex tag, that it has not been blocked accidentally, and that its canonical points to the appropriate URL.
A noindex tag or a canonical pointing to another page will normally appear under a more specific Search Console status. Even so, these elements are worth reviewing because the configuration may have changed since the last crawl or there may be conflicting signals.
We should also check the response code, the mobile version, and the rendered content. The Test Live URL feature is particularly useful for identifying differences between the content we expect to show and the content Googlebot can process.
If the website uses JavaScript, checking the initial source code is not enough. The main text, links, and other relevant elements must be available after rendering.
After fixing a technical issue, we can request indexing again for the most important URLs. When the changes affect many pages, it will usually be more practical to update the sitemap and wait for Googlebot to crawl them again.
Improve, consolidate, or remove the content
When a page does not provide enough value, the solution is not necessarily to write more. We need to understand what users need and what the content is missing in order to satisfy that need.
We can improve a page by adding relevant information, answering questions that were previously left unaddressed, or including examples and first-hand experience. It may also be necessary to change the approach if the chosen format does not match the search intent.
If several pages are too similar, consolidating them may be a better option. This prevents them from competing with each other and brings all the information and signals together on a single, more complete URL.
The less useful page can be redirected to the main version when both serve the same purpose. If there is no equivalent alternative and the URL no longer serves any purpose, we can also remove it and return the appropriate status code.
In other cases, similar pages need to remain because they address different needs. In that situation, we need to genuinely differentiate them rather than simply changing the title or replacing a few words within a template.
Improve internal linking
An important page should be naturally integrated into the website architecture. We can link to it from categories, related articles, service pages, or other content covering the same topic.
The anchor text should also be descriptive. This makes navigation easier for users and helps explain the relationship between the source page and the linked page.
There is no need to repeat the same link across dozens of pages or place it in areas unrelated to the content. One or several contextual links from relevant pages may be more useful than a generic block displayed throughout the website.
We can also check whether the URL is too far away from the homepage or relies entirely on deep pagination. A clear architecture allows important pages to be reached through normal internal links.
Review the sitemap
The sitemap should include the URLs we consider canonical, indexable, and important. Including parameters, redirects, errors, or pages we do not want to rank sends unclear signals about the website structure.
Being included in the sitemap does not guarantee indexing. Its main purpose is to facilitate discovery and communicate which URLs we consider relevant, but the final decision will still depend on the content and the other available signals.
We also need to maintain consistency between the sitemap, canonical tags, and internal links. If a URL appears in the sitemap but every page links to another version, we will be sending conflicting signals.
After improving a large number of pages, we can update the last-modified date only when the content has changed significantly. Changing the date without making any real modifications will not cause the URLs to be indexed.
Request indexing after making changes
The URL Inspection tool allows us to request indexing for an individual URL. This option is useful after fixing an important page or publishing content that we want Google to reassess.
The request does not force Google to add the page to the index. It only asks Google to crawl and process it again, so the result will still depend on the content and the available signals.
There is no need to repeat the request every day either. Doing so will not speed up crawling and may cause us to reach the submission limit without gaining any additional benefit.
For a large number of URLs, it is better to maintain an updated sitemap and a strong internal linking structure. Manual indexing requests should be reserved for specific, high-priority pages.
How long does it take for a page to leave this status?
There is no fixed timeframe for a page to move from “Crawled – currently not indexed” to being indexed. The amount of time required will depend on the website’s crawl frequency, the changes we have made, and how the page is evaluated during subsequent visits.
After requesting another crawl, it may take anywhere from a few days to several weeks. In addition, Googlebot revisiting the URL does not mean that the page will be indexed immediately—or that it will eventually be indexed at all.
A specific technical change may produce relatively quick results when it was the only issue preventing the content from being processed. Improvements involving the website’s overall quality, duplicate content, or architecture may take longer to be evaluated.
We should also avoid making constant changes while we wait. If we modify the content, canonical, and internal linking every few days, it will be more difficult to determine which improvement worked, and we will not allow enough time for the previous versions to be processed.
The best approach is to record the changes, wait for the pages to be crawled again, and monitor their development in Search Console. If they remain outside the index, we can return to the analysis and check whether we correctly identified the cause.
How can indexing issues be prevented?
The best way to reduce these types of problems is to avoid creating URLs without a clear purpose. Every indexable page should address a specific need and provide enough value to work as a standalone result.
It is also important to monitor templates that generate large numbers of pages. A small issue in a product, category, or location template can eventually affect thousands of URLs.
The website architecture and internal linking should make important content easy to reach. The sitemap can support this process, but it should not be the only place where Googlebot can discover the pages.
Technical signals also need to remain aligned. Canonical tags, internal links, redirects, and the sitemap should all use the same version of each URL to avoid uncertainty about which one is the main version.
Finally, it is advisable to review the Page Indexing report regularly and monitor how it develops over time. The goal is not to have every known URL indexed, but to make sure that the pages we actually care about can be crawled, understood, and added to the index.
Ultimately, “Crawled – currently not indexed” is neither a penalty nor a specific technical error. It means that Googlebot has visited the page, but the page has not been added to the index at this time. Before making changes, we need to determine whether the URL should actually appear in the search results.
When the page is important, the analysis should focus on its content, its similarity to other URLs, its internal linking, and the version Googlebot is able to process. Requesting indexing may be useful after fixing the problem, but it does not replace the need to provide a useful page that is properly integrated into the website.
