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.

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.

Sequel CLI

Install Sequel skills into your agent

One command connects your agent to Sequel and installs the Sequel skill, so it knows this playbook exists and reads it when a question matches. The CLI signs you in, provisions a scoped API key and writes the config for you.

Already have an MCP client?

https://api.sequel.sh/mcp

Point it at this URL and sign in when prompted, or send an API key from Settings as a Bearer token. Skills come with it; nothing else to install. Manual setup per client

  1. 1

    Install the Sequel CLI

    One line installs the latest CLI with whatever package manager you have.

    curl -fsSL https://sequel.sh/install | sh
  2. 2

    Sign in

    Authenticate in your browser and pick an organization.

    sequel login
  3. 3

    Install into your agent

    Writes the MCP config and installs the Sequel skill file for agents that support skills. Pick an agent from the list, or target one directly by its slug.

    sequel install
    • Claude Code
      sequel install claude-code
    • Claude
      sequel install claude
    • Cursor
      sequel install cursor
    • VS Code
      sequel install vscode
    • Windsurf
      sequel install windsurf
    • Zed
      sequel install zed
    • Codex
      sequel install codex
    • OpenClaw
      sequel install openclaw
    • Hermes
      sequel install hermes

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.

Put this playbook to work

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