ToolSura
    HomeTools
    Blog

    Understanding your results: INDEXED, NOT INDEXED, and coverage states

    Posted on July 19, 2026 by Abhay khant

    Key Takeaways

    Read gsc-indexer output: indexed vs not, coverage state, fetch state, robots state, and last crawl time, and what each one tells you.

    You ran the tool. Now what do the verdicts actually mean?

    The two outcomes

    • [INDEXED]. Google's verdict is PASS and the coverage state is not "excluded". Google has this URL in its index.
    • [NOT INDEXED]. anything else: a non-PASS verdict, or an "excluded" coverage state. Google does not currently serve this URL in search.

    A NOT INDEXED result is not an error. the inspection succeeded; Google just doesn't have the page indexed.

    "URL is unknown to Google"

    You'll often see this coverage text on a NOT INDEXED result. It means Google has never indexed the page. To move it toward indexed:

    1. Make sure the page is live (returns HTTP 200, not a 404).
    2. Check it isn't blocked by noindex or robots.txt.
    3. Submit your sitemap in GSC so Google discovers it.
    4. Re-run gsc-indexer to request a fresh crawl, then wait (hours–days).

    Coverage states, in plain English

    Coverage state Meaning
    Submitted and indexed Google has it and serves it.
    URL is unknown to Google Not indexed yet.
    Excluded by meta tag A noindex tag tells Google not to index it.
    Excluded by robots.txt robots.txt blocks crawling.
    Crawled - currently not indexed Google fetched it but chose not to index (often thin/duplicate content).
    Discovered - currently not indexed Google knows of it but hasn't crawled yet.

    The other fields

    • fetch. whether Google could download the page (SUCCESSFUL / errors).
    • robots. whether robots.txt allowed crawling.
    • last crawl. when Google last fetched it (empty if never).

    "inspection submitted; Google will re-crawl"

    This line prints after every run. It means the tool asked Google to re-fetch the URL. It does not mean the page is indexed now. indexing is Google's decision and usually takes hours to days to reflect.

    Verdict: PASS vs NEUTRAL

    Only a PASS verdict with a non-excluded coverage state counts as indexed. A NEUTRAL verdict ("URL is unknown to Google") is not indexed, even though the request was submitted successfully.

    Next

    • Process lots of URLs: batch, stdin, sitemaps.
    • Something broke? Troubleshooting.

    Sources

    • Google Search Console
    • URL Inspection API documentation
    • Google Search APIs overview
    • Service account OAuth (Google Identity)
    • About service accounts (Google Cloud IAM)
    • Verify site ownership
    • Property types: URL-prefix vs Domain
    • URL Inspection tool help
    • Indexing API (JobPosting/BroadcastEvent only)
    • Request indexing / inspect a URL

    Frequently Asked Questions

    What does INDEXED versus NOT INDEXED mean?

    INDEXED means Google has the URL in its index. NOT INDEXED means it does not, even though the inspection itself succeeded. A NOT INDEXED result is normal for a brand new or just-submitted page and is not an error; it just reflects current state.

    What is the coverage state?

    Coverage tells you how Google sees the page: valid, excluded, error, or warning. An excluded or error state explains why a URL is not indexed, such as a noindex rule or a crawl blocker, and points you at the fix far better than the indexed flag alone.

    What do fetch state and robots state show?

    Fetch state reports whether Google could retrieve the page, and robots state reports whether your robots rules allowed it. If either is blocked, indexing will not happen regardless of your inspection. These two fields are where most 'why isn't this indexed' answers live.

    What is the last crawl time for?

    It is the most recent time Google fetched that URL. A stale date means Google rarely visits, which is why a manual re-crawl request helps. After you inspect a URL, expect that timestamp to move forward on the next natural crawl.

    Why does the tool print the submission confirmation only once?

    Because inspecting already submits the URL for re-crawl, the confirmation is a single end-of-run statement, not a per-URL line. Per-URL lines show the indexed/coverage/fetch/robots state; the 'submitted for re-crawl' note appears after the whole run so the output stays readable.

    Community Feedback

    Reviews & Discussions

    0
    Based on 0 Reviews

    Leave a Review

    Rate this tool
    Overall Rating
    Spam Protection Active
    ToolSuraPrivacy-First Tools

    Building the next generation of privacy-first developer utilities. No trackers, no bloat, just performance.

    All Systems Operational

    Product

    • Free Online Tools
    • Contact
    • FAQs
    • About

    Legal

    • Privacy Policy
    • Cookie Policy
    • Terms & Conditions

    Resources

    • Blog
    • Brand
    • Help

    © 2026 ToolSura. Engineering Excellence in Browser-Native Software.

    Remote-First / Based in India

    Technical Manifesto

    Private • Client-Side • No Tracking

    ToolSura on Nick Launches
    Browser-Native
    Privacy-First