Discovered means Google has not crawled the URL yet
To manage URLs discovered but not indexed in Google Search Console, first identify which pages you actually want in search. Google knows these URLs but has not crawled them yet. For priority pages, check crawling restrictions, noindex directives, internal links and sitemap inclusion; correct observed problems, then track whether the status changes. Do not treat the label alone as proof of poor content or a reason to rewrite every affected page.
Google’s Page indexing report documentation explains that this status typically means Google wanted to crawl the URL but expected doing so to overload the site, so it rescheduled the crawl. The last crawl date is empty because the page has not yet been crawled. That is an explanation of the status, not a confirmed diagnosis of your server’s condition.
By contrast, “Crawled – currently not indexed” means Google has already crawled the page but has not indexed it. Google says it may or may not be indexed later and that there is no need to resubmit that URL for crawling. The two labels therefore call for different questions: has Google fetched the page, or has it fetched the page without indexing it?
Keep the difference between crawling and indexing in view throughout the investigation. A discovered URL is not evidence that Google has evaluated and rejected the page’s content. You can still review whether that content deserves a place on your site, but that is an editorial assessment—not a conclusion supplied by this status.
Decide which URLs deserve indexing work
Start with the affected URLs, not just the total count. For each page, write down its intended purpose and whether you want people to find it through search. This separates an indexing objective from a desire to make every report entry disappear.
- Prioritize: a page intended for search that answers a distinct reader need. Put it into the access and discovery checks below.
- Resolve its purpose first: a page whose role overlaps heavily with another page. Decide which page should carry the answer before investing in indexing work for both.
- Keep outside the indexing work queue: a URL you deliberately do not want in search. Review its exclusion requirements separately rather than removing restrictions merely to change this status.
For example, a publisher might prioritize a completed reference guide over an unfinished draft or an alternate version of an existing article. These are illustrative editorial choices, not Google’s priority rules. The useful acceptance condition is concrete: you can explain the page’s distinct purpose and why it should be a search entry point.
Group the priority URLs by a shared characteristic, such as page template or section. If several pages share the same unintended access rule, investigate that rule together. If only one page lacks a relevant internal link, address that page. Grouping is a way to organize the work; it does not establish that every URL in the group has the same cause.
Check access rules before changing content
Inspect the exact URL you intend to have indexed. A practical review starts with robots.txt and noindex directives, both of which appear in IndexHub’s not-indexed checklist. Treat these as checks for conflicting instructions, not as causes already proven by the “Discovered” label.
- Confirm the page’s intended role: it belongs in search according to your priority review. If that decision is unresolved, settle it before changing access rules.
- Check crawling permission: review the applicable robots.txt rule and the “Crawl allowed” field in URL Inspection. If a rule blocks a page you intend Google to crawl, identify the rule and correct the unintended restriction.
- Check indexing instructions: examine the page’s noindex directives. For a page intended for indexing, resolve an unintended noindex instruction; do not remove a deliberate exclusion without revisiting the page’s purpose.
- Check the scope of any correction: identify whether the rule applies to one URL or a shared page pattern. Review other affected pages before changing a broad rule.
Read “Crawl allowed” and “Indexing allowed” together. Google’s URL Inspection documentation warns that when robots.txt blocks a page, “Indexing allowed” will always say “Yes”: Google cannot see any noindex directives behind the block. That “Yes” is therefore not confirmation that the page contains no exclusion instruction.
This distinction also matters for URLs you do not want in search. Google notes that a robots-blocked page might still appear in results. Do not assume that blocking crawling and supplying a noindex directive are interchangeable, or that Google can read the directive while access is blocked.
If access rules match your intentions, consider whether site load needs investigation. Because Google describes anticipated overload as a typical reason for deferring a crawl, ask whoever manages the site’s infrastructure to look for evidence of load or availability problems. Do not prescribe a hosting upgrade from the Search Console label alone; make infrastructure changes in response to an observed problem.
Review internal links and sitemap inclusion
Internal links and sitemap presence are also useful review items in the not-indexed checklist. However, Google has already discovered a URL carrying this label. The task is not to prove that Google has never encountered it; it is to check whether the page is represented consistently in your site’s links and sitemap.
- Find a relevant internal route: identify an existing page where a link to the priority URL would genuinely help the reader. If that useful connection is missing, add it rather than placing unrelated links across the site.
- Confirm the link destination: follow the link and check that it leads to the page you intended to prioritize. Correct an unintended destination.
- Review sitemap presence: if you use a sitemap for these pages, check whether the intended URL is included. Correct an accidental omission rather than treating sitemap inclusion as an indexing result.
- Document the finding: distinguish “link or sitemap correction made” from “no discrepancy found.” The latter is a reason to continue the investigation, not to invent a change.
For example, suppose a finished guide belongs under a topic overview but the overview never links to it. Adding that relevant link is a specific site-organization improvement. It is not evidence that the missing link caused the crawl delay, nor does it establish when Google will crawl the guide.
Keep content edits separate from discovery checks: address an incomplete explanation or overlapping page purposes on their editorial merits.
Use the next status to choose your next action
Keep a small record for each priority URL: intended purpose, observed status, access findings, internal-link and sitemap findings, changes made, and review date. This makes the next decision depend on what changed rather than on how often you have checked the report.
- Record the starting state. Save the exact URL and its reported status. For “Discovered – currently not indexed,” an empty last crawl date is consistent with Google’s definition, not a separate defect to repair.
- Correct a demonstrated mismatch. Record the specific rule, directive, link or sitemap entry you changed. Where several changes are necessary, list them separately so the work remains understandable.
- Review the URL’s subsequent status. If it is still discovered but uncrawled, revisit unresolved access or infrastructure findings. If those checks found no problem, leave it under observation rather than making arbitrary edits.
- Change the investigation when the stage changes. If the URL becomes “Crawled – currently not indexed,” Google has now crawled it. Treat that as a different indexing question; Google says there is no need to resubmit that URL for crawling.
- Close or redirect the task according to the outcome. If the intended page is indexed, close the not-indexed task. If you decide the page should not be a search entry point, move it out of the indexing-priority list and handle its intended exclusion separately.
Google’s description of this status does not provide a guaranteed waiting period. Choose a review cadence that fits the page’s publishing importance, but do not present that cadence as a Google deadline.
Also distinguish sequence from causation. If a URL is crawled after you add an internal link, record both events without claiming the link caused the crawl. Google’s documentation already describes rescheduled crawling as part of this status, so a later crawl alone cannot isolate the effect of your edit.
For ongoing reporting, choose SEO metrics worth tracking around the decision you need to make: which intended search pages remain unindexed, which have reached a different stage, and which still have an unresolved site issue. The practical goal is to address observed obstacles on useful pages—not to change every URL merely to reduce a report total.
