Read landing page reports
Hero AI reports how your Google Ads landing pages perform. Ask for a landing page report to learn which pages get clicks, which pages convert, and whether a weak result comes from the page or from the traffic mix. Landing page reports are for Google Ads only.
A landing page report is read only. It does not draft a wireframe unless you ask for a redesign. See Landing page redesign.
When to ask for a landing page report
Landing page reports answer questions, for example:
Show landing page performance for the Search | Non Brand campaign over the last 30 days.
Which landing pages have the highest CPA?
Why am I seeing so many versions of the same URL?
Break landing page performance down by device.
Is the homepage converting differently for different keyword themes?
Name the campaign and the date range. If you only ask about "landing pages," Hero AI uses the last 30 days and your active Google Ads account.
Why URLs get grouped into destination pages
Google Ads often reports several rows for one page. One click can land on:
https://example.com/?hsa_kw=seo%20tool&gbraid=...
Another might land on:
https://example.com/?hsa_kw=ai%20seo&gclid=...
These are not two pages. They are one destination with different tracking values. Hero AI groups them into one destination page first, and keeps the tracking variants as secondary detail:
| What you see | What it means |
|---|---|
| Destination page | The real page after Hero AI removes common tracking parameters |
| Tracking variants | The URL versions that UTM, ValueTrack, click IDs, and similar parameters create |
| Variant count | How many tracked URL rows combine into that page |
| CVR | Conversions divided by clicks |
| CPA | Cost divided by conversions |
Start with destination pages. Do not judge a page by one tracking variant unless the variant has enough clicks to matter.
How to read the breakdowns
Hero AI adds three breakdowns to a landing page report when they help explain the result.
Keyword breakdown
Keyword rows come from URL tracking parameters, for example hsa_kw, utm_term, or keyword, when your final URLs have those values. This breakdown is useful when one landing page gets traffic from different keyword themes.
Read keyword rows as tracking evidence, not as a full Google Ads keyword report. If your URLs do not include keyword tracking parameters, this breakdown is empty.
For true keyword performance, ask:
Show keyword performance for this ad group over the last 30 days.
Device breakdown
Device rows come from Google Ads landing page segments. They show whether one page performs differently on mobile, desktop, or tablet. Use them when a page performs well overall but has a weak mobile conversion rate.
Landing page source breakdown
Source rows come from Google Ads landing page segments. They separate main final URLs from other traffic sources, for example sitelinks, when Google exposes that detail. Use them when a campaign has sitelinks and you need to know whether the main page or a linked page does the work.
What a good landing page answer includes
A useful landing page answer shows:
- Destination pages first, sorted by spend or cost impact.
- Clicks, cost, conversions, CVR, and CPA for each destination.
- Campaign or ad group context when it is available.
- Keyword, device, or source breakdowns only when they explain the result.
- A plain note when a breakdown is unavailable.
If the answer leads with a table of long UTM URLs instead, ask:
Group these by real destination page and explain the tracking variants separately.
When to ask for a redesign instead
A report tells you what happened. A redesign drafts a wireframe that you can give to a designer. Ask for a redesign after a report shows a real page issue, for example:
- Strong CTR but weak conversion rate.
- One page with a much higher CPA than similar pages.
- A mobile conversion rate much worse than desktop.
- An ad promise and page message that do not match.
For example:
The homepage has weak conversion rate on mobile. Redesign the landing page for this campaign using that finding.
See Landing page redesign for what the wireframe includes.
Limits of landing page reports
- Landing page reports use Google Ads data. They do not show lead quality from a CRM, or Google Analytics data, unless that data is in Google Ads.
- By default, Hero AI groups away click IDs, for example
gclid,gbraid, andwbraid. They help with debugging but add noise to normal reporting. - Keyword breakdowns depend on tracking parameters in the URL. If those parameters are missing, Hero AI says so. It does not invent keyword rows.
- Small samples mislead. A page with 2 clicks and 1 conversion shows a 50 percent CVR. That is not enough data to trust.