SEO

Find where paid search overlaps organic

Compare the pages the site already ranks for organically against the landing pages receiving paid search clicks in GA4, to find where ads are buying visits organic would deliver anyway, and where paid traffic reveals demand organic has not captured.

The playbook

Paid and organic search are usually run by different people looking at different dashboards. Put the two side by side and the same pages show up in both, which raises two useful questions: is the ad spend on those pages incremental, and which paid-only pages point at demand the organic team has not gone after?

Steps

  1. Pull the organic side. google_search_console.query with dimensions: ["page"] over 28 days ending 3 days ago, rowLimit: 500, and again with dimensions: ["query", "page"], rowLimit: 5000.

  2. Pull paid landing pages from GA4. google_analytics.run_report with dimensions: ["landingPage", "sessionMedium"], metrics: ["sessions", "conversions", "totalRevenue"], the same dates, dimensionFilter on sessionMedium EXACT cpc. Run it a second time with organic so paid and organic conversion rates can be compared on the same pages.

  3. Join on the path after stripping origin, query string and trailing slash from every URL.

  4. Sort the pages into three groups.

    • Overlap: paid sessions on a page whose main organic queries sit at position 1 to 3 with solid clicks. These are the candidates for an incrementality test.
    • Paid only: paid sessions, no organic clicks. Paid has found demand organic has not. Pass the page's paid intent to query-clusters-to-content-plan.
    • Organic only: no action here.
  5. Look at brand specifically. Filter the query rows to brand terms. If the site holds position 1 for its own brand and a brand ad is running, quantify the paid brand sessions separately. This is the most common overlap and the most contested.

  6. Compare conversion on the overlap pages. Paid conversion rate versus organic conversion rate on the same pages. If they are similar, the page converts regardless of channel and the test is about volume; if paid is much higher, the ad copy or the query mix is different and pausing would lose something.

  7. Report. The overlap table (page, organic position on main queries, organic clicks, paid sessions, paid conversions, organic conversions), the paid-only list as opportunities, the brand overlap figure, and a recommendation to test pausing on the two or three strongest overlap pages rather than a blanket cut. Say explicitly that cost is unknown.

Gotchas

  • There is no cost data here. GA4 shows paid sessions and conversions, not spend. Without a Google Ads connection, the overlap can be described but not priced; say so plainly.
  • Position 1 organic does not make the ad wasted. Ads plus organic take more of the results page than either alone, and brand ads block competitors bidding on the brand. The honest recommendation is a test, not a conclusion.
  • cpc is every paid search engine and sometimes more. Anything tagged with medium cpc lands here, including Bing Ads and mis-tagged social. Check sessionSource before treating it as Google Ads.
  • Search Console is Google only. The overlap is Google organic against all paid search, which slightly overstates paid-only pages.
  • Search Console lags 2 to 3 days. End every 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.