SEO

Turn search demand into a content plan

Find content gaps and plan what to write next from Search Console data: group the queries the site already gets impressions for into topic clusters, map each cluster to the page that serves it, and surface clusters with real demand but no dedicated page.

  • What should we write next?
  • Find content gaps from our search queries
  • Group our impressions into topics we don't cover

The playbook

The best content plan comes from queries Google is already testing the site against. Every impression is Google saying "this site might be relevant here". Clusters of those impressions that no page is built for are the gaps worth writing to, and they come with proof of demand attached.

Steps

  1. Pull the query inventory. google_search_console.query with dimensions: ["query", "page"], a 90-day window ending 3 days ago, rowLimit: 5000. Strip branded queries. Keep rows with at least 30 impressions and state the floor.

  2. Cluster the queries. Group by shared head term and intent. Do this in sequel_workbench or by inspection; either way, state the method. Label each cluster with a representative query and an intent: informational, commercial investigation, transactional, or navigational.

  3. Score each cluster. Total impressions, total clicks, impression-weighted average position, the distinct pages that received impressions for it, and which single page received the most.

  4. Classify the clusters.

    • Gap: meaningful impressions, average position above 20, impressions spread thinly across pages that were not written for the topic. No page serves this; a dedicated one probably would.
    • Cannibalised: several pages each receiving a solid share. Continue with keyword-cannibalization-check rather than adding another page.
    • Under-clicked: one page, good position, low CTR. Continue with ctr-underperformers.
    • Served: one page, position under 10. Leave it alone.
  5. Size the top gaps (if Ahrefs is connected). Pass the representative queries of the top gap clusters to ahrefs.keywords_overview for volume, difficulty and CPC. Drop gaps whose difficulty is far above what the site already ranks for. High CPC marks commercial intent.

  6. Report. A cluster table (cluster, intent, impressions, clicks, position, serving page, classification), then briefs for the top five gaps: working title, the queries to target, the intent to satisfy, and which existing page should link to the new one. Explicitly list the clusters you are recommending nothing for.

Gotchas

  • Plan clusters, not keywords. One page per cluster. A page per query is how cannibalization starts.
  • Do not build a page for a cluster an existing page already serves at position under 10. Improve that page instead; a new one splits the signal.
  • Search Console omits the anonymised long tail. The inventory is a sample of demand, not all of it. Clusters are more robust to this than individual queries, which is another reason to cluster.
  • Ahrefs numbers are estimates. Use them to rank gaps against each other, not as a forecast of traffic.
  • Intent decides the format. An informational cluster wants a guide; a commercial one wants a comparison; a transactional one wants a product or landing page. Say which in each brief.

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 is a query cluster in SEO?
A query cluster is a group of search queries sharing the same underlying intent best served by a single page. Clustering is the step between keyword research and content planning: instead of writing one article per keyword, you write one article that ranks for ten related queries.
How do I cluster keywords from Search Console?
Export the query report, group queries by semantic similarity, and assign each cluster a primary topic and supporting queries. Question forms, how-to variants, and comparison terms often cluster naturally around the same intent. An agent can do the grouping at scale.
How does query clustering help me prioritize what to write?
Each cluster represents an opportunity. Rank clusters by total impression volume across member queries, weighted by estimated click uplift from page-one ranking. That gives you a content backlog ordered by potential impact.
Can an AI agent create a content plan from my Search Console data?
Yes. With Search Console connected, the agent pulls query data, clusters by intent, scores each cluster by opportunity, and returns a prioritized content plan with suggested titles and target queries. Sequel provides the connection and the query-clusters-to-content-plan playbook.

Put this playbook to work

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