Find pages with high organic traffic but low GA4 conversion rate
Surface the 'leaky bucket' — pages that rank, get clicks, and then fail to convert. Combine SC clicks with GA4 conversion-rate per landing page.
The prompt
Copy this and paste it into Claude, Cursor, or any AI client connected to your GenieSeo MCP URL.
For my main Search Console property AND its matching GA4 property:
1. Compute the site-wide GA4 conversion rate over the last 28 days (organic search channel only): conversions ÷ sessions.
2. From Search Console, list every page with at least 500 clicks over the last 28 days, and the top query each page ranks for.
3. For each of those pages, run a GA4 report over the same 28-day window with dimension pagePath and metrics sessions, engagedSessions, conversions. Filter to organic search.
4. Compute conversion rate per page. Flag every page whose conversion rate is below the site-wide median from step 1.
5. For each flagged page, write a 1-line hypothesis about why conversion is weak — intent mismatch with the top query, weak CTA, slow page, content gap, etc.
Output as a Markdown table sorted by SC clicks descending. Include the site-wide median in the table caption for context.When to use it
When traffic is up but pipeline isn't. The conversation moves from 'we need more traffic' to 'we need to fix these specific pages' — much more actionable for the content team.
What you get back
- Up to 25 pages with at least 500 SC clicks in the last 28 days where GA4 conversion rate is below the site-wide median.
- For each page: SC clicks, SC top query, GA4 sessions, engaged sessions, conversion rate, the site-wide median for context.
- A 1-line hypothesis per page about why conversion is weak (intent mismatch, slow load, weak CTA, etc.).
How this runs
GenieSeo doesn't execute prompts — your AI client does. Make sure your MCP URL is connected to Claude, Cursor, Codex, or Antigravity. New here? Read the 60-second setup guide.
Tags
- search-console
- ga4
- conversion-rate
- rewrite