Audit crawlable URLs from a completed website crawl against Google’s indexed view, group indexed and not-indexed pages by coverage reason, and investigate each result with words, headings, internal links, and crawl depth.
Too Long; Didn't Read
Screpy Index Status checks the crawlable URLs in a completed project crawl against index information from the connected Google Search Console property. It groups indexed and not-indexed URLs by available coverage reason, keeps crawl context beside every result, and lets an incomplete audit resume without discarding completed inspections.
Review indexed and not-indexed URLs from the connected property without separating coverage information from the project pages you actually crawled.
Learn more about google index coverageUse the crawl data next to each URL to investigate whether page content, headings, internal links, or crawl depth need closer attention.
Learn more about page investigationChoose the connected Google Search Console property, wait for the project crawl to complete, then continue an unfinished audit when the review needs more time.
Learn more about connected workflowIndex Status connects Google’s page-level index information with the audit progress, filters, coverage groups, and crawl metrics needed to investigate important URLs responsibly.
See the indexed and not-indexed crawlable URLs included in the selected audit without treating a coverage result as a ranking promise.
Review the available coverage reason for not-indexed pages and filter repeated states before beginning a page-by-page investigation.
See indexed versus not-indexed totals, the coverage breakdown, and the most common not-indexed reasons before opening individual URLs.
Review words, headings, internal links, and crawl depth beside the URL to understand the page context behind an index status.
Filter the audit to indexed, not-indexed, or failed rows, choose one coverage state, and search for a full URL or shared path pattern.
Use the connected Google Search Console property and the latest completed crawl as the scope for each authenticated audit.
Check the crawlable URLs collected by a known completed crawl instead of mixing the audit with unknown or uncrawled website inventory.
Follow processed, indexed, not-indexed, skipped, and failed URL totals, then continue an eligible incomplete audit without replacing existing results.
Use SEO MCP to inspect existing Index Status audits and their URL records. Ask about affected pages and available Search Console URL inspection evidence; MCP does not start a new Index Status audit.
Define the URLs that should be indexed, run the audit against a known crawl, group repeated coverage states, and use page context before deciding what to change.
Start with the page purpose. Identify the canonical product, service, category, article, or campaign URLs that should be eligible for search, and separate duplicates, redirects, filters, and intentionally excluded pages.
Use the Search Console property that represents the project scope and a completed website crawl that contains the pages you want to review. A property or crawl mismatch weakens the audit.
Check the crawlable URL set and follow processed, indexed, not-indexed, skipped, and failed totals. If the run pauses or reaches an inspection limit, continue the eligible audit later.
Start with indexed versus not-indexed totals, then use the coverage and not-indexed reason charts. Filter by status, coverage state, full URL, or shared path pattern to find repeated behavior.
Read words, headings, incoming internal links, source-page counts, and crawl depth beside the coverage reason. Change only pages that should be indexed, then recrawl and allow Google time to process the result.
The audit is most useful when it narrows a large crawl to business-critical URLs, shared coverage reasons, weak discovery paths, or comparable page groups.
Search for important product, service, category, location, or article URLs and confirm that their index state matches the role each page should play in organic discovery.
Group not-indexed URLs by the available Google coverage reason, then inspect shared templates or path patterns before treating every affected page as a separate problem.
Use incoming internal links, source-page counts, and crawl depth to see whether an important URL is difficult to discover within the crawled website structure.
Compare words and heading counts across similar URLs to identify thin, inconsistent, or unexpectedly empty pages that deserve a closer page and template review.
Indexing is necessary for search eligibility, but a status alone does not explain page value, live indexability, ranking potential, or the right technical action.
Duplicates, alternate URLs, redirects, and intentionally excluded pages may correctly remain outside Google’s index. First decide whether the URL should be indexed.
An indexed page is eligible to appear, but the result does not promise rankings, impressions, clicks, or appearance for a particular query.
The audit does not run a live URL test. A recent content, directive, canonical, or server change may not yet be reflected in the index information returned for the page.
Screpy checks crawlable URLs from the selected completed crawl, not every historical or externally discovered URL Google may know. Inspection quotas can also pause a large audit.
Use Index Status for Google’s indexed view across crawled URLs, Website Audit for current crawl and page signals, and Search Console for observed search performance.
Check indexed and not-indexed crawlable URLs, group coverage reasons, filter the audit, and inspect crawl context beside each result.
Inspect current status codes, directives, canonicals, content, links, and crawl paths across the completed website crawl.
Review clicks, impressions, CTR, average position, queries, and pages when the question is search visibility rather than index state.
Screpy documentation
Use the Screpy guide to review indexed and not-indexed URLs, investigate coverage reasons, and validate changes.
Learn the concepts behind this workflow and apply them with practical SEO guidance.
URL parameters can waste crawl budget and create duplicates; set canonicals, noindex/robots rules, and GSC checks so Google indexes the right URLs for key pages.
Read articleConnect Google Search Console through MCP, run verifiable SEO analysis, and fix date, filter, pagination, and total mismatches using a real example.
Read articleFind out why your vibe-coded website is missing from Google. Check live URLs, Search Console indexing reasons, redirects, canonicals, rendering, and fixes.
Read articleTrailing slashes SEO: avoid duplicate URLs by choosing one format and aligning 301 redirects, canonicals, sitemaps, and internal links for clean indexing.
Read articleUnderstand what an Index Status audit reports, what it needs, and where its result should fit in your SEO workflow.
Screpy Index Status checks the crawlable URLs in a completed project crawl against index information from the connected Google Search Console property. It reports indexed and not-indexed states, available coverage reasons, and related crawl context for the audited URLs.
No. The audit checks the version represented in Google’s index through the connected Search Console property. It does not test the current live page or prove that a recent website change has already been processed by Google.
No. Duplicate, alternate, redirected, intentionally noindexed, or otherwise unnecessary URLs may correctly remain outside Google’s index. Decide whether the URL should be indexed before treating its coverage reason as a problem to fix.
No. Index Status reports Google index information for the audited URLs. It does not submit indexing requests, force Google to crawl a page, or guarantee that a URL will appear in Google Search results.
No. Screpy starts from the crawlable URLs in the selected completed project crawl. This creates a known website scope, but it is not a complete inventory of every historical, external, parameterized, or otherwise discovered URL Google may know.
The dashboard currently labels Index Status as experimental. Audit states and available Google coverage information can evolve, so validate important findings against the current page, Search Console, and a fresh crawl before making a broad website change.
The project needs a connected Google Search Console property and a completed crawl. Index Status uses that scope to review the crawlable URLs in the project.
Yes. When an audit is eligible to continue, use Continue Audit to resume the same review instead of discarding its existing progress. A daily inspection limit or interrupted run can require you to return later.
Being indexed means Google has an indexed version of the page; it does not guarantee ranking, impressions, clicks, or a specific position. Review the page, its intent, technical conditions, and search performance before deciding on the next action.
