SEO

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.

The playbook

Answer "which pages are winning in search, and why" by layering three views of the same URLs. Search Console is the source of truth for your own performance; Ahrefs adds competitive context; GA4 tells you whether the traffic is worth anything.

Steps

  1. Get your top pages by real search traffic. Call google_search_console.query with dimensions: ["page"], a 28-day window, and rowLimit: 100. Sort the result by clicks descending. This is ground truth. Use it, not Ahrefs estimates, whenever the site is verified in Search Console.

  2. Get the queries behind the top pages. Re-query with dimensions: ["page", "query"] over the same window. Group by page and keep the top ~10 queries per page. This tells you what each page actually ranks for, which is usually broader than what it was written for.

  3. Add competitive context (if Ahrefs is connected). Call ahrefs.top_pages with the site as target to get estimated traffic value and ranking keyword counts per page. Traffic value is the number worth surfacing, because it separates a page pulling 10k low-intent visits from one pulling 500 visits that are worth real money.

  4. Check whether the traffic converts. Call google_analytics.run_report with dimensions: ["landingPage"], metrics: ["sessions", "engagementRate", "conversions"] (add "totalRevenue" for ecommerce), same date range. Join to the Search Console pages on the URL path.

  5. Report. One table, one row per page: clicks, impressions, average position, top query, engagement rate, conversions, and Ahrefs traffic value where available. Sort by clicks. Then call out the two or three pages with high clicks but weak engagement or conversions. Those are the real findings, not the leaderboard itself.

Gotchas

  • Join on the URL path, not the full URL. Search Console returns absolute URLs (https://example.com/pricing); GA4's landingPage is a path (/pricing). Normalize both to the path, strip trailing slashes and query strings, before joining.
  • Search Console data lags 2 to 3 days. Never end the window at today or you'll report a fake cliff. End it 3 days back.
  • Search Console truncates. Rows are capped and low-volume queries are omitted for privacy, so per-page query clicks won't sum to the page total. Don't present the gap as missing traffic.
  • Ahrefs traffic is modelled, not measured. When both are available, quote Search Console for your own numbers and use Ahrefs only for value estimates and competitor comparison. If they disagree, say so rather than averaging them.
  • Average position is an average. A page at "position 8.4" may rank 3rd for its main term and 40th for a long tail. Don't optimize off it without looking at the per-query rows.

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

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.

Backlink profile health check

See who links to the site and whether the backlink profile is healthy: referring domains, authority distribution, anchor text mix, dofollow share and concentration risk from Ahrefs, optionally compared against a competitor.

Put this playbook to work

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