SEO

Check sitemap health

Check that the site's XML sitemaps are submitted, fresh, error-free and complete: compare submitted vs indexed counts in Search Console, find sitemap URLs that redirect or return errors, and find pages with search traffic that the sitemap does not list.

  • Is our sitemap healthy?
  • How many sitemap URLs are actually indexed?
  • Are there redirects or 404s in our sitemap?

The playbook

A sitemap is a promise to Google about which URLs matter. Broken promises (URLs that redirect or 404, lastmod dates that never change, whole sections missing) make Google trust the file less, and the file is often the only way large or new sections get discovered at all.

Sequel supplies Search Console's view of each sitemap. Reading the XML itself and checking its URLs uses your own browsing.

Steps

  1. List what Search Console knows. google_search_console.list_sitemaps. For each: type, whether it is an index, pending state, last submitted, last downloaded, warning and error counts, submitted and indexed totals. If any row is a sitemap index, call again with sitemapIndex set to its path to see the children. Use google_search_console.get_sitemap on any sitemap with errors for the detail.

  2. Read the XML. Fetch each sitemap (or the index and its children) with your browsing. Count the URLs, note the lastmod values, and compare the URL count to the submitted total Search Console reports.

  3. Check a sample of listed URLs. Thirty to fifty URLs spread across the file. For each: does it return 200, is its canonical itself, is it free of noindex. Any redirect, error or noindex in a sitemap is a finding. Use sequel_workbench for the loop if you can execute code.

  4. Check completeness against traffic. google_search_console.query with dimensions: ["page"], 90 days ending 3 days ago, rowLimit: 2000. Pages with clicks that are absent from every sitemap are the pages the sitemap forgot.

  5. Check freshness. A last downloaded date weeks old on a sitemap that changes often, a lastmod that is the same on every URL, or a lastmod in the future all tell Google the dates are meaningless. Note which applies.

  6. Report. Per sitemap: submitted, indexed, gap, errors, warnings, last downloaded, URL count from the XML. Then the findings: listed URLs that redirect or error (with the final URL), listed URLs carrying noindex, pages with traffic missing from the sitemap, and freshness problems. Fixes are specific: remove or replace listed URLs, add the missing pages, generate real lastmod values. Continue with index-coverage-review if the indexed gap is large.

Gotchas

  • Indexed counts in the sitemap report lag and are per sitemap. A URL listed in two sitemaps is counted twice.
  • Sitemaps should list only canonical, indexable, 200 URLs. That is the whole rule; every finding above is a violation of it.
  • lastmod only helps when it is honest. Google has said it ignores the field on sites that set it to the current time on every URL.
  • Limits are 50,000 URLs and 50 MB uncompressed per file. A file near either should be split.
  • 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 should a sitemap contain?
Only canonical, indexable, 200-returning URLs. A sitemap entry that redirects, 404s, carries noindex, or points at a non-canonical URL is a finding. The sitemap is a priority signal to Google, so every URL it contains should be one you want crawled and indexed.
How do I check if Google has processed my sitemap?
Search Console shows each submitted sitemap with the last download time, the number of URLs submitted, and the number discovered as valid. A large gap between submitted and discovered indicates URLs in the sitemap that Google cannot or will not index.
Why are there URLs in my sitemap that Google has not indexed?
Common causes: the URLs redirect, return noindex, are near-duplicate, are thin, or are excluded by robots.txt. Pull a sample and inspect each with the URL Inspection API to find the coverage state.
How often should I update my sitemap?
Automatically on new content publication and on a scheduled weekly basis for large sites. The sitemap is not a substitute for internal links: Google does not crawl sitemap URLs it cannot also reach via links.
Can an AI agent audit my sitemap?
Yes. With Search Console connected, the agent pulls sitemap data, cross-references with coverage states, and returns URLs in the sitemap that are not indexed and pages with traffic that are not in the sitemap. Sequel provides the connection and the sitemap-health playbook.

Put this playbook to work

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