Google Search Console says not indexed: now what?
Understand Crawled - currently not indexed, Discovered - currently not indexed and common Google indexing issues with a practical diagnosis checklist.
Not indexed does not always mean broken. First confirm that the URL should be indexed, then inspect its canonical, crawlability, HTTP response and content usefulness. ‘Discovered - currently not indexed’ and ‘Crawled - currently not indexed’ describe different states and require different checks.
What does ‘not indexed’ mean?
An unindexed URL is not currently represented as an indexed page in Google Search in the way you might expect. That can be intentional: duplicate URLs, redirects, filter parameters, private pages and pages marked noindex should often be excluded.
The first question is not ‘How do I force this page into Google?’ It is ‘Is this a unique, valuable URL that should be indexed?’
Search Console’s Page indexing report and the URL Inspection interface help narrow down the answer.
Common statuses and what to investigate
| Status | What it generally indicates | First checks |
|---|---|---|
| Discovered - currently not indexed | Google knows the URL but has not crawled it recently enough to index it | Internal links, sitemap, server capacity and whether the page is worth crawling. |
| Crawled - currently not indexed | Google crawled the URL but did not index it | Content uniqueness, quality, canonical signals and whether the page duplicates another. |
| Excluded by ‘noindex’ tag | An indexing directive excludes the page | Confirm whether noindex is intentional. |
| Duplicate, Google chose different canonical | Google selected another URL as representative | Compare duplicate content, redirects, internal links and canonical tags. |
| Not found (404) | Google encountered a missing page | Restore important pages or return a proper 404/410 if permanently gone. |
| Server error (5xx) | Google could not reliably fetch the page | Investigate uptime, hosting and error logs. |
The exact labels and reasons may change in the UI. A status is a diagnostic clue, not a guaranteed single root cause.
A practical URL inspection process
- Paste the complete URL into Search Console → URL Inspection for the correct property.
- Check whether Google reports the URL as indexed and note the canonical Google selected.
- Review the last crawl indicators and whether crawling and indexing are allowed.
- Where supported in the interface, perform a live URL test to compare the current page with the indexed state.
- Check HTTP status, robots.txt, meta robots, redirects and canonical markup yourself.
- Check whether the page is linked internally from an accessible relevant page.
- Decide whether the content answers a distinct search intent and offers value beyond existing pages.
Fix the underlying issue before requesting any available re-evaluation in Search Console’s interface.
Discovered versus crawled: which matters?
For Discovered - currently not indexed, look at discovery, crawl demand and site-level reliability. More sitemap submissions are not necessarily the answer.
For Crawled - currently not indexed, Google has encountered the page. Review relevance, duplication, canonicalization and site signals instead of treating it as a simple discovery failure.
A handful of unindexed pages can be normal. Prioritize high-value pages and patterns affecting whole sections, not every parameterized URL.
Can I request indexing with an API?
Google provides a URL Inspection API to query indexed-version status. It is not a live test or a button to force Google to index the page.
Google’s Indexing API is restricted to specified JobPosting or livestream BroadcastEvent use cases. It is not a general solution for normal blog articles or product pages.
You can learn more about the supported API operations in our Search Console API guide.
A prompt for auditing a shortlist
Using Search Console URL Inspection data where available, review these ten important URLs. Return each reported status, Google-selected canonical, evidence, and the next manual check. Do not claim a live URL test was run through the API.
Group issues by shared pattern and prioritize pages with business value. Do not treat all unindexed URLs as errors.
This requires a Search Console connector with URL Inspection permissions. An assistant without tool access can suggest a checklist, but it cannot know the current indexed status of your private URLs.
A decision tree for an important URL
Use this sequence when a page that should appear in Google Search is reported as not indexed.
Question 1: Does the page exist and return a successful response?
If it returns 404 or 5xx, fix the server or publishing problem first. A URL that intentionally no longer exists usually should not be forced into the index.
Question 2: Is indexing intentionally blocked?
Check meta robots, X-Robots-Tag where applicable, password/access restrictions and robots.txt. Remember that robots.txt blocking and noindex do different things: a crawler blocked from fetching a page may not see a noindex directive placed inside it.
Question 3: Does the page point to another canonical?
Review the declared canonical and Google’s selected canonical in URL Inspection where available. If Google prefers a different near-duplicate URL, investigate duplicate content and inconsistent internal linking before attempting to change it.
Question 4: Has Google crawled the URL?
A discovered-but-not-crawled page calls for a different investigation than a crawled-but-not-indexed page. Review internal linking, sitemaps and technical availability for the former; relevance and duplication for the latter.
Question 5: Is the content distinct and genuinely useful?
If the page repeats another article with only minor keyword substitutions, publishing yet more similar pages will not necessarily help. Strengthen the unique explanation, examples and intended audience.
Question 6: Has enough time passed for re-evaluation?
Changes can take time to crawl and process. Record the fix date, then monitor status. Do not interpret a lack of immediate indexing as proof that the fix failed.
Example: which unindexed pages should you fix?
Consider this hypothetical list:
| URL | Reported issue | Priority |
|---|---|---|
| /product | Unexpected noindex | High: commercial page intended to be public |
| /blog/unique-guide | Crawled - currently not indexed | Investigate content, canonical and duplication |
| /search?q=keyword | Crawled or discovered, not indexed | May be intentional for internal search results |
| /old-product | Redirect | Usually normal if replaced by a new URL |
Prioritize business value and whether indexing is intended. A thousand excluded filter URLs might be less important than one noindexed signup page.
Sitemap inclusion, request indexing and actual indexation
A sitemap is a structured way to tell search engines which canonical URLs you consider important. It is not a command to index everything it contains. Internal links and crawlable HTML also matter.
Where Search Console offers a Request indexing action in the UI, use it for an appropriate important page after resolving underlying issues. The separate URL Inspection API reports indexed-version status and is not the same as that UI action.
Don’t try to use Google’s restricted Indexing API for a normal product page or blog post. It is intended for the documented eligible content types.
Frequently asked indexing questions
Why is my page crawled but not indexed?
Google may have crawled it without selecting it for indexing. Possible areas to investigate include content duplication, canonical signals and usefulness; no single status proves a specific cause.
Why does the live URL test pass but the page remain unindexed?
Live testing confirms certain current fetchability signals, not that the page will be selected for the index. Google still processes indexing decisions separately.
Does ‘not indexed’ mean the page is penalized?
No. Exclusion is common and often intentional. Verify the exact status and whether the URL should be indexed before assuming a penalty.
Should I create a new URL for a page that is not indexed?
Usually not as a first response. Investigate content, technical signals and canonicalization before creating duplicate URLs that could make the problem harder to diagnose.
What to do after a fix
Keep a list of changed URLs, implementation dates and expected outcomes. Allow time for crawling and indexing, then recheck statuses. Monitor impressions and clicks separately: an indexed page is not guaranteed search visibility.
For unexpected visibility losses, see our traffic-drop checklist. To make search diagnostics easier to use with AI tools, explore GSC Magic.
Join the waitlist
Coming soon. Get 30% off Pro for 6 months when you join.