You have connected the Search Console MCP and Analytics MCP. What should you ask next? This walkthrough turns their separate reports into an evidence-backed shortlist of pages to improve. It does not promise that an assistant can reveal which Google query generated a lead.
Outcome: a spreadsheet with a baseline, an observed problem, a proposed change and a way to verify its effect. You need: read access to the correct GSC and GA4 properties, an MCP-capable client, and roughly 50 minutes. The worked numbers here are fictional, not this site's analytics.
1. Make the periods comparable
Choose two complete 28-day windows, excluding the most recent days if GSC data is not final. Record the date ranges, property, timezone, search type, device/country filters and whether branded searches are included. GA4's property timezone and GSC's reporting timezone can differ; compare trends, not row-by-row identities.
Ask your agent:
Using my read-only Search Console tools, show clicks, impressions, CTR and average position by page for the two specified periods. Include the exact periods, property and filters. Never invent missing rows. Separate complete data from fresh/incomplete data.
GSC may return top rows rather than every query or page; a missing row is not automatically zero. Query-level privacy and aggregation limits also matter.
2. Find candidate pages
Start with pages having meaningful impressions and declining clicks or CTR; also inspect pages with rising impressions but no corresponding clicks. Don't apply an arbitrary universal CTR threshold: position, device and search intent change the expected CTR. For each candidate, request query mix and device split.
Fictional example only:
| Page | Earlier impressions | Recent impressions | Earlier clicks | Recent clicks | First question |
|---|---|---|---|---|---|
/guides/mcp/ | 2,000 | 2,600 | 70 | 52 | Did the position or query mix change? |
/services/ | 1,200 | 1,100 | 44 | 38 | Is this a seasonal or technical shift? |
/faq/payments/ | 500 | 900 | 8 | 13 | Are new queries less relevant? |
In the first row, clicks fell by 18 (about 26%) despite 30% more impressions. That is a reason to investigate, not proof the title is poor.
3. Check what visitors do in GA4
Ask for Google organic sessions and engagement for the relevant landing pages, plus configured key events. Define the metrics explicitly. eventCount counts event occurrences; it is not automatically the number of sessions with that event or the number of qualified leads. A contact-page view is not a form submission; an unconfigured event is unknown, not zero.
From my GA4 property, compare Google organic traffic on these landing pages over the same named periods. Show sessions, engaged sessions, and the configured contact-submit/key event. Clearly label absent instrumentation or unavailable data. Don't join individual search queries to individual GA4 conversions.
Normalize paths, redirects, UTM variants and language prefixes before comparing GSC page URLs with GA4 landing page dimensions. Expect discrepancies: the platforms use different collection and attribution mechanisms.
4. Recommend only testable changes
For each shortlisted page, write Observation → Hypothesis → Change → Verification. Examples: align the title and introduction to queries actually received; add a troubleshooting section answering a real repeated question; improve a relevant call-to-action; fix discoverability on mobile. Do not claim a change will raise rankings.
Use the priority worksheet to record effort, confidence and expected business relevance. A low-traffic service page may matter more commercially than a highly viewed general AI comparison.
5. Run a controlled review
Capture the baseline and publication date. After changes are live, monitor comparable periods, noting seasonal events and site changes. A small sample cannot establish causality. Keep the original report/CSV so someone can reproduce the decision.
Troubleshooting
- Properties disagree: check property identity, landing-page path, country/device filters, timezone and GA4 tracking coverage.
- No key events: verify instrumentation instead of reporting zero leads.
- MCP tools missing: re-open the relevant setup guide and verify the client connection and permissions.
- Sudden drop: check whether the latest GSC reporting days are incomplete.
Related guides and sources
Search Console MCP setup · GA4 MCP setup
Official references: Google on using both data sources, GSC Search Analytics API, GA4 API metric definitions.
Downloads and next steps
Download the fictional period-comparison CSV and priority worksheet. The CSV uses the same example numbers above; its paths do not refer to measured pages on this site.
Need help turning the findings into website changes? See website development.
Source references and fictional calculations checked on 12 November 2026. The sample is not a client report and does not identify individual leads.
Turning search visits into useful next steps?
Useful content needs a clear website behind it. I can help improve page structure, performance and the path from an article to your services, products or enquiry form.