First, decide whether this page belongs in search
A “not indexed” count is not a to-do list. An important public product page deserves attention. A tracking variant, a removed page, or an old address that redirects may be correctly excluded. Inspect the exact URL before changing your site.
In Search Console, enter the full URL in the inspection bar and expand Page indexing. Record the reason, last crawl, and Google-selected canonical. The canonical is the URL Google treats as the main version of that content. Then choose the closest message below.
The saved inspection and a live test answer different questions. The saved result describes Google’s existing information; a live test checks the page now. “URL is available to Google” in a live test does not mean the page is indexed. See Google’s URL Inspection explanation.
Get a checklist for your message
Use the message from Page indexing or URL Inspection. This helper does not connect to Google or scan your site.
Choose a message and an answer to see your checklist.
What the messages mean
These examples are illustrative. Each checklist starts with something you can verify, rather than treating a status label as a diagnosis of content quality.
Discovered – currently not indexed
Google knows the URL but has not crawled it yet.
- Link to this page from a relevant, already accessible page. Include the preferred URL in your sitemap.
- Use URL Inspection’s live test to check access. If many important pages are waiting, check server errors and whether the site generates large numbers of unnecessary URLs.
- Request indexing for a small number of important, ready pages. Record the date and watch for a crawl; repeatedly submitting the same URL is not a queue-jumping strategy.
Example: A new product is listed only in the sitemap. Add it to the relevant category and check that the category’s links lead to its final URL.
Crawled – currently not indexed
Google fetched the page but has not added it to the index. This status alone does not identify the cause.
- Check the last crawl date and the crawled HTML where available. A fix made after that crawl will not be reflected in the saved result.
- Compare the page with its closest alternatives on your site. Check for missing main content, near-duplicates, or a page that adds little beyond an existing one.
- Make a specific improvement if you find a problem. Test the current page and request a new crawl after a meaningful change; do not rewrite a useful page solely to make this label disappear.
Example: Twenty city pages contain the same service description with different city names. Review whether each page provides information that is actually specific to that location.
Excluded by ‘noindex’ tag
The page tells search engines not to index it.
- Check the page’s robots meta tag and its X-Robots-Tag response header. A CMS setting, template, or hosting configuration may supply the directive.
- Remove noindex only from pages you want in search. Check other pages using the same template before changing a site-wide setting.
- Keep the page crawlable so Google can see the change. Run a live test, then request indexing once the directive is gone.
Example: A shop left its staging-site noindex setting on after launch. Fix the production setting; keep the staging site protected.
Blocked by robots.txt
A robots.txt rule prevents Google from crawling the URL. Blocking crawling is not a reliable way to remove a URL from search.
- Find the matching rule in the robots.txt file for this exact host. Check both the path and the user-agent group it applies to.
- If the page should be searchable, adjust the unintended rule and verify that Google can fetch the page and its essential resources.
- Run a live inspection after the change. If the goal is exclusion instead, use an appropriate indexing directive on a crawlable public page; private content needs access controls.
Example: Disallowing /shop/ blocks every product under that path. Check whether the rule was meant for a narrower area such as a cart.
Alternate page with proper canonical / Duplicate
Google is treating another URL as the representative of this content.
- Inspect Google’s selected canonical and your declared canonical in the saved inspection. Open the selected URL and decide whether it is the right version.
- For intentional duplicates, keep internal links, sitemap entries, and canonical signals consistent with the preferred URL. The alternate does not need its own search result.
- If this URL should represent distinct content, check for an accidental canonical to another page and make the distinction in the content clear. A declared canonical is a signal, not a command.
Example: A product URL with a campaign parameter points to the clean product URL. That is usually the intended relationship. A different product pointing to it needs a closer look.
Page with redirect
This URL forwards visitors to another URL.
- Follow the redirect and inspect its final destination. Confirm that it is the page you want people to find.
- For a deliberate move, update internal links and the sitemap to the destination. The old redirecting URL does not need to be indexed separately.
- If the redirect is accidental, fix the redirect rule and check the intended page again.
Example: You moved /old-guide to /guides/coffee. Keep the useful redirect and investigate the new guide’s indexing status instead.
Not found (404) / Soft 404
The page is missing, or Google sees an error-like page even though the server may report success.
- For a page removed without a replacement, a real 404 or 410 is appropriate. Remove obsolete internal links and sitemap entries.
- If it moved, redirect to a genuinely equivalent replacement. If it should still exist, restore its content and successful response.
- For a soft 404, check whether the rendered page is empty or shows an error. Avoid redirecting unrelated deleted pages to the homepage.
Example: An empty product template that says ‘item unavailable’ is not a restored product page just because its HTTP status is 200.
Another message / I’m not sure
Start with the exact URL and its Page indexing details in URL Inspection.
- Inspect the full URL in the correct Search Console property. Expand Page indexing and note the reason, last crawl, fetch result, and Google-selected canonical.
- For server errors or access-denied responses, investigate the server, login requirements, CDN, or firewall before editing the page copy.
- Use a live test to compare the current page with Google’s saved result. A passing live test does not mean the page is indexed or guarantee that it will appear.
Example: A page works while you are logged into your CMS but redirects other visitors to a login screen. Test its public response before requesting indexing.
After a fix, check the new evidence
Write down what changed and when. Test a representative page, then inspect it again after Google’s next crawl. If a template caused the problem, check several pages using that template. A newer crawl date helps you distinguish an unresolved problem from an old saved result.
Request indexing in Search Console for important URLs after fixing the relevant issue. Submission is a request, not a promise of indexing or a ranking boost. Google’s inspection documentation explains the request and its limits.
Numic can show Google’s URL Inspection data and keep inspection history. Live tests and the request-indexing action are performed in Search Console. An API inspection refresh does not itself ask Google to crawl the page.
If the page is indexed but gets little traffic, investigate its queries and relevance next. The average-position guide can help you decide whether poor visibility is actually a ranking problem.