SEO

Find queries that fell off page one

List the search queries that recently dropped out of Google's top ten results between two periods, with the pages that lost them, so ranking losses are caught while they are still cheap to recover.

The playbook

Position 10 to position 11 is the most expensive single-place move in search: page two receives almost nothing. A query that just slipped over that line is usually recoverable with a modest update, while one that collapsed to position 40 usually is not. This playbook finds both and tells them apart.

Steps

  1. Pull both windows. Two calls to google_search_console.query with dimensions: ["query", "page"] and rowLimit: 5000: the last 28 days ending 3 days ago, and the 28 days before that.

  2. Join and filter. Join on query and page. Keep rows where the prior position was 10 or better and the recent position is worse than 10, and where the prior window had at least 50 impressions (state the floor). Sort by prior clicks descending so the list leads with what was actually earning traffic.

  3. Separate the slips from the collapses. Recent position 10.5 to 14: a slip, the cheap-to-recover group. Recent position above 20: a collapse, usually a different problem (the page changed, was overtaken, or the query's results page was restructured). Report them as two groups.

  4. Check whether the page is still the page. For each row, look in the recent window for the same query served by a different URL on the site. If one is, the site's own second page has taken over and this is cannibalization; continue with keyword-cannibalization-check. If the page received no impressions at all in the recent window, check with your browsing that it still returns 200 and is not noindexed; continue with technical-crawl-audit if it is not.

  5. Report. Two tables (slips, collapses): query, page, prior position, recent position, prior clicks, prior impressions, and a one-word diagnosis (slipped, overtaken, cannibalised, technical). Recommend work only for the slips and the cannibalised rows; say what to verify for the collapses.

Gotchas

  • Position is an average. A row moving from 9.6 to 10.4 may be the same rankings with a slightly different mix of impressions. Treat moves under one position as noise unless clicks fell too.
  • The floor decides the list. Fifty impressions is a starting point; on a large site raise it or the list will be hundreds of rows of long tail.
  • A month is short. Rankings fluctuate. If the user wants confidence rather than an early warning, compare 90-day windows instead.
  • Brand queries do not belong here. Strip them; a brand query falling off page one is a different kind of emergency.
  • Search Console lags 2 to 3 days. End the recent 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.