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.

  • Are we paying for clicks we already rank for?
  • Where do ads and organic overlap?
  • Which paid landing pages have no organic coverage?

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.

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 paid and organic keyword overlap?
Queries where you run paid search ads and also have a strong organic ranking. If you rank organically in position 1 for a query and also run ads, you are paying for traffic you are already capturing for free. The overlap analysis tells you which ad spend to cut and which to keep.
Should I stop running ads for queries where I rank organically?
Not automatically. Ads and organic listings appear together, and some data suggests they increase total clicks. But for branded queries where you hold position 1, and for high-volume queries where your organic ranking is strong and stable, reducing ad spend rarely hurts volume meaningfully.
How do I find queries where I pay for ads and also rank organically?
Join Search Console query data with your paid search data on the query string. Rows where both an impression count and a paid click exist are the overlap. Filter to queries where your organic position is 1 to 3, because that is where organic already captures most of the available clicks.
How much money could I save by eliminating paid-organic overlap?
Estimate the CPC of each overlapping query multiplied by the paid clicks on that query. That is the upper bound. In practice, some portion of those clicks would not switch to organic if the ad were removed. Use a 50 to 70% capture rate as a conservative estimate.
Can an AI agent find paid-organic overlap?
Yes. With Search Console and GA4 or Google Ads connected, the agent joins organic and paid query data and returns the overlap ranked by paid spend with an estimated saving. Sequel provides the Search Console connection over MCP and the paid-and-organic-overlap playbook.

Put this playbook to work

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