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.
Start with your project’s latest successful website crawl and matching Google Search Console property. Screpy checks the eligible URLs against Google’s indexed view, so the result describes inspected pages rather than every URL on your website.
example.com850
/old-pricing404Narrow the results to important pages that should appear in Google Search. Combine index status, coverage and URL search to review a product category, article folder or individual landing page without treating every excluded URL as a defect.
example.com850
/guides/seoNot indexedThe overview separates indexed and not-indexed inspections, breaks down available coverage states and highlights reasons among not-indexed pages. Repeated reasons help you choose which templates or URL groups to investigate first.
Indexed
824Keep the crawl evidence beside the index result while you investigate. Words, H1/H2 counts, incoming internal links, linking-page counts and depth come from the crawl used by that audit, which can differ from the page Google last processed.
/guides/seo200
Large audits can pause at the daily inspection limit or need a Google reconnection. Continue Audit is available for eligible interrupted runs and preserves completed inspections instead of starting the whole review again.
/guides/shopexample.comDownload a focused CSV or Excel file after applying the filters you need. Export uses the currently loaded table page, with up to 50 rows, so it suits a review handoff rather than a complete bulk-audit download.
After fixing a page that should be indexed, complete another website crawl and start a new audit when eligible. Continuing an old audit keeps its existing inspections, and starting a new one does not promise an immediate change in Google’s information.
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.
Connect the Search Console property that matches the project. A new Index Status audit automatically uses the latest successful website crawl, so complete a fresh crawl first if the website has changed.
Start the audit and review inspected rows as they become available. Use the indexed/not-indexed overview and coverage charts; if an inspection limit or reconnection message appears, follow it and continue when the audit is eligible.
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.
Compare crawl context with the coverage reason and the page’s purpose. Fix only pages that should be indexed, complete another crawl and start a new audit when eligible. Allow for reused inspection information and Google’s processing time before judging the change.
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 articleChoose SEO alerts for indexing, rankings and organic traffic. Set useful GA4 rules, verify site changes, and triage warnings with clear owners and evidence.
Read articleCompare server-side rendering vs client-side rendering for SEO, including crawlability, Core Web Vitals, caching, hybrid options and page-type release checks.
Read articleRun 30 Lovable SEO checks before launch: verify rendering, domains, metadata, sitemaps and published fixes, with examples and a release worksheet.
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. A new audit starts from the latest successful crawl’s 2xx pages with no canonical or a canonical matching the final URL. Only URLs inside the connected property are inspected. This excludes some crawled URLs and is not Google’s full URL inventory. A URL missing from the results is not automatically not indexed: it may be outside the scope, pending, skipped or have a failed inspection.
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, accessible Google Search Console property and a successful website crawl. A new audit automatically uses the latest successful crawl. Only one audit can be active, and new audits can be started once every 5 hours.
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.
