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.

  • Which pages bring in the most organic traffic?
  • What does our pricing page rank for?
  • Show me our top landing pages and their queries

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.

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

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.

FAQ

Frequently asked questions

How do I find my best-performing landing pages in Search Console?
Pull the pages report sorted by clicks over the last 90 days. Those are your top landing pages by organic traffic. Adding average position and CTR shows which pages are efficient earners and which rank only because they are very high, making them vulnerable.
Why should I analyze high-ranking landing pages?
Understanding what makes your best pages work tells you what to replicate. Content format, internal link depth, keyword targeting, and schema markup patterns from high performers are the most reliable signal of what Google rewards on your specific site.
Should I update high-ranking pages that are already performing well?
Carefully. Content updates on high-performing pages can lose rankings if the changes reduce topical depth or shift the page away from the queries it ranks for. Do targeted updates that add missing subtopics rather than rewrites that change overall structure.
Can an AI agent analyze my top-performing landing pages?
Yes. With Search Console and GA4 connected, the agent pulls performance data, identifies top pages by clicks and engagement, and returns a profile of what they have in common. Sequel provides both connections over MCP and the analyze-high-ranking-landing-pages playbook.

Put this playbook to work

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