RecipeGoogle Ads
Read the Google Ads landing pages report
The landing page view: clicks, mobile speed, valid status per URL.
IntentWhich URLs take the clicks, and their mobile health, in one table.
- 2
- Steps
- 1
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Weekly hygiene.
- After site deploys.
Do not use it when
- As the full audit: landing-page-audit joins GA4 and classifies causes.
What it needs first
Required
Preconditions
- The account is ticked in the dashboard, confirmed via list_accounts.
Inputs
window- Analysis window.Default: last 30 days.
Procedure
In order. Every tool named is one the gateway ships, and links to its reference.
Pull the landing page view.
Rank by clicks and flag invalid or slow rows.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
Any URL with meaningful clicks reports invalid
Conclude
Emergency: bought clicks are landing on a broken page right now.
Evidence every conclusion must carry
- Every figure carries its account, metric and window.
- Anything below a readable sample size is reported as unjudged, not as zero.
Where the agent stops
- The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.
How it goes wrong quietly
The cases where the analysis is wrong and still looks right. Read them before trusting a number.
- Parameter variants split one page across rows: normalise before ranking.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.