Guide library · Software Help HQ
Discovered vs. Crawled — Currently Not Indexed: What to Check First
Software Help HQ | Documentation-backed conceptual troubleshooting guide | Editorial source, not a tested PageBuilder fix
Short answer: In Google Search Console, Discovered — currently not indexed means Google knows a URL exists but has not crawled it yet. Crawled — currently not indexed means Google fetched the page but has not put it in the index. Neither label by itself proves a penalty, a broken website, or a permanently rejected article. The distinction tells you which question to investigate first.
Imagine publishing two original tutorials on Monday. Search Console lists Tutorial A as Discovered and Tutorial B as Crawled. You could spend an afternoon rewriting both titles, but that would answer neither diagnostic question. A needs a discovery-and-fetch investigation; B needs a look at what Google could actually fetch and whether that document is a useful, distinct index candidate.
First, record the exact URL
Write down the address shown in the report, including trailing slash, .html suffix, and hostname.
A page at /guide is not automatically the same URL as /guide.html. Open
URL Inspection for the exact address; record the inspection date, last crawl date, index
status, indexing permission, page-fetch result, and both user-declared and Google-selected canonical where
available. Do not treat an old report screenshot as today's crawler state.
Use this evidence sheet:
| Evidence | Tutorial A | Tutorial B |
|---|---|---|
| Intended indexable page? | Yes / No | Yes / No |
| Exact inspected URL | ||
| Google status | Discovered | Crawled |
| Last crawl timestamp | Empty or not shown | Record the value |
| Canonical inspected | ||
| Crawl and indexing allowed? | Verify | Verify |
| Linked from an existing live page? | Verify | Verify |
| Content meaningfully distinct? | Verify | Verify |
When the status is Discovered
Start with whether the address deserves to be indexed. Draft previews, duplicate utility routes, expired redirects, and intentionally private pages often do not. For a public page you want indexed, check three things in order.
A readable route. Open the URL as a signed-out visitor. Confirm it returns the intended article, not the PageBuilder editor, a sign-in screen, a soft error, or a redirect to an unrelated page. A web response with 200 is only part of the proof: check the rendered article text and links.
A discoverable path. Find at least one relevant, already live page that links to it using a normal hyperlink. A sitemap is useful, but a visitor should also be able to navigate to the material from an appropriate topic hub. Avoid adding dozens of near-duplicate links to every page footer.
Consistent URL signals. Record the exact URL in the sitemap, canonical link, navigation and internal links. If these disagree, correct the conflict only after backing up the site's approved state. Google may choose its own canonical even when a preferred one is supplied.
Then wait for Google to reassess. Google's help explicitly says newly known URLs can take time to crawl; repeatedly pressing Request Indexing cannot promise a faster or positive result.
When the status is Crawled
Now the key question is: Which version of the page did Google fetch? Compare the cached inspection
details with the current Test Live URL result. Check whether essential article content is
present in rendered HTML, whether a noindex setting accidentally survived publication, and whether
the selected canonical points somewhere else.
If the page is technically readable, evaluate its role. Is it genuinely different from an existing guide? Does it answer a clear question? Does it include a concrete example, useful comparison, or a test the reader can perform? A nearly identical definition page adds little for the reader. That is an editorial choice, not proof that Google penalized the site.
For an educational article, make the answer unmistakable in the opening paragraph. Then support it with an example, warnings about where advice stops applying, and a concise next action. If the better choice is to improve an existing page rather than publish a redundant one, preserve the stronger URL and internal-link route.
A real-world decision tree
- Intentionally private or duplicate? Record an intentional exclusion; don't request public indexing.
- Public URL fails for an anonymous reader? Resolve the fetch, redirect, or access problem before editing copy.
- Discovered and not crawled? Verify crawlable links, consistent canonical/sitemap, and time since publication.
- Crawled but not indexed? Verify rendered content and canonical signals, then inspect duplication and actual reader value.
- Indexed but not receiving impressions? That's a separate visibility and demand investigation, not this indexing issue.
Mini-case: the invisible draft
A training site publishes an article but leaves its preview template's noindex directive in place.
An operator sees it in a sitemap and assumes it should rank. The correct response is not to add more keywords.
Confirm that the production page is deliberately indexable, remove the preview restriction through the site's
supported publishing settings, and inspect the live page again. Never remove privacy safeguards from an actual
private draft to chase traffic.
Before you finish
Save one row per affected URL with its current observation, responsible fix, and date for a later recheck. Avoid mixing old and new Search Console screenshots. That simple history shows whether the underlying condition changed, even when a ranking hasn't appeared.
Related next step: Once a page is indexed, use Search Console's Performance report to understand actual query and page visibility. Indexing is eligibility to appear, not proof of a first-page ranking.
Sources and scope: Google Page indexing report; Google URL Inspection; Google canonical guidance. These explain platform behavior; no live Software Help HQ account was operated for this guide.