Sequel
SEO

Review index coverage of important pages

Estimate how well the pages that matter are indexed when the Coverage report is not available through the API: combine Search Console page data with the sitemap and URL inspection of a prioritised sample to find pages Google has dropped, pages with the wrong canonical, and sitemap URLs that never earn an impression.

Install into your agent
  • Are our important pages actually indexed?
  • Which sitemap URLs never get impressions?
  • Is Google indexing the wrong canonical anywhere?

The playbook

Search Console's own coverage report is not available through the API, but two things are: the pages that earn impressions (which are therefore indexed) and the URL Inspection API for anything specific. Put together with the sitemap, that is enough to find the pages that should be indexed and are not.

Steps

  1. Pull the pages Google is showing. google_search_console.query with dimensions: ["page"], 90 days ending 3 days ago, rowLimit: 1000. Every page here has been indexed at some point in the window.

  2. Pull the sitemap picture. google_search_console.list_sitemaps for submitted and indexed counts per sitemap; the gap is the first coverage number. Then fetch the sitemap XML with your own browsing to get the full URL list (call list_sitemaps again with sitemapIndex set if there is an index).

  3. Find the two mismatches.

    • Sitemap URLs with zero impressions in 90 days: possibly not indexed, or indexed with no demand. Rank them by how much they matter: product, pricing, docs and top-level guides first, tag pages and archives last. Ask if the ranking is not obvious.
    • Pages with impressions that are not in the sitemap: indexed, but the sitemap is incomplete. A list to add.

  4. Inspect a prioritised sample. google_search_console.inspect_url with up to ten URLs per call: the five highest-priority zero-impression URLs, plus five of the top-traffic pages to catch canonical drift on the pages that matter most. Run a second call if the user wants more, and say the API is quota-limited so this is a sample.

  5. Classify the inspected rows. Indexed (verdict PASS, coverage submitted and indexed), not indexed by choice (noindex, canonical elsewhere), not indexed by problem (crawled or discovered but not indexed, blocked, fetch error), and canonical mismatch (Google canonical differs from user canonical). Count each.

  6. Report. The sitemap submitted-vs-indexed table; the count and top twenty of zero-impression sitemap URLs; the count and top twenty of indexed pages missing from the sitemap; the inspected sample with its classification; and a short list of URLs to hand to page-not-indexed-debug one at a time.

Gotchas

  • Zero impressions is not proof of not indexed. A page can be indexed and never shown. Inspection is the only confirmation, which is why the sample exists.
  • The sitemap report's indexed count is Google's own and lags. Treat it as directional.
  • Search Console page rows are capped and filtered. A large site will not return every indexed page in 1000 rows. Raise the limit or scope with a page filter per section.
  • Inspect the winners too. Canonical drift on a top page (Google picking a different URL) costs more than a hundred unindexed tag pages.
  • Search Console lags 2 to 3 days. End the window 3 days back.

Install

Install Sequel skills into your agent

Pick your app and Sequel installs itself: a one-click link where the client supports it, that client’s own few steps where it doesn’t. The playbooks come with the server: your agent sees that this playbook exists and reads it when a question matches.

Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex, Grok, Muse, dots and any other MCP app

Already have an MCP client?

https://api.sequel.sh/mcp

Add it as a remote (streamable HTTP) server and sign in when prompted. Skills come with it; nothing else to install. Manual setup per client

Choose your app

  • Claude

    One click, opens in the app

  • Cursor

    One click, opens in the app

  • VS Code

    One click, opens in the app

  • ChatGPT

    Turn on developer mode, then add Sequel. About two minutes.

  • Claude Code

    Run one command, then sign in with /mcp.

  • Codex

    Run one command, then sign in.

  • Gemini CLI

    Run one command, then sign in with /mcp auth.

  • Grok

    Add Sequel as a connector and sign in.

  • Grok Bot

    Paste this to the bot. It registers Sequel and asks you to sign in.

  • Muse

    Muse writes its own connector. One message is the whole setup.

  • dots

    Add Sequel in ChatGPT; your dot picks it up with no extra step.

  • OpenCode

    Add Sequel as a remote server from the OpenCode CLI.

  • Other MCP app

    Any client that speaks remote MCP can connect with this URL.

More like this

Other SEO skills

Analyze high-ranking landing pages

See which pages perform best in organic search: the landing pages that earn the most clicks and impressions, the queries behind each one, and how they compare with competitor estimates from Ahrefs.

Audit internal links to important pages

Audit the site's own internal linking: crawl navigation and body links between the site's pages to find valuable pages with too few inbound internal links, orphan pages, and the handful of cross-links that would lift striking-distance rankings.

Audit or draft an llms.txt

Check whether the site has an llms.txt, whether it follows the spec and points at the pages that matter, and if it is missing draft one from the pages Search Console shows people actually find, so AI assistants get a curated map of the site instead of guessing.

Audit redirect chains and loops

Follow every redirect on the URLs Search Console still sends traffic to, on the sitemap, and on backlinked pages, to find chains, loops, redirects to the homepage, and temporary redirects that should be permanent, so link equity and crawl budget stop leaking.

Audit referring domain quality

Grade the domains linking to a site by authority, traffic and link count, spot concentration risk and link-farm patterns, and separate the referring domains that carry weight from the ones that are noise.

Audit titles and meta descriptions

Compare the title and meta description of each top page against the queries it actually ranks for in Search Console, and find missing, duplicate, truncated or misaligned metadata on the pages where a rewrite would earn the most clicks.

FAQ

Frequently asked questions

What is an index coverage review?
A review of which pages on your site Google has indexed versus which it has not, grouped by the coverage state Search Console reports. It answers how much of your content is actually visible in Google and whether the non-indexed pages are excluded deliberately or by accident.
How do I find how many pages Google has indexed on my site?
The site: operator in Google search gives a rough estimate. Search Console coverage reports give a more accurate count grouped by state. The difference between submitted URLs in your sitemap and indexed URLs is the coverage gap.
Should every page on my site be indexed?
No. Tag pages, filtered listings, thin variants, paginated archives, and internal search results are usually better excluded. The goal is that every page Google indexes serves a search purpose and every page that serves a search purpose is indexed.
What is index bloat and why does it matter?
Index bloat is a large number of low-quality indexed pages that dilute crawl budget and may reduce the authority distribution to the pages that matter. Common causes are parameter URLs, duplicate locale variants, and paginated archives with thin content.
Can an AI agent run an index coverage review?
Yes. With Search Console connected, the agent pulls coverage data grouped by state, samples the non-indexed pages, and returns findings with recommended actions per state. Sequel provides the Search Console connection and the index-coverage-review playbook.

Put this playbook to work

Connect a source, ask the question, and the agent follows these steps. Free to start.

Get started freeAll skills