Localize one landing page for every city you bid on.
Overview
Bidding on city keywords means a hundred near-identical pages to maintain, or one generic page that ignores where the click came from. This is the third option: one page that reads the city from your ad's URL parameter and localizes the headline, intro, and any section you choose. Give the agent your city list up front, since values are validated against it, and anyone arriving without a recognized parameter just sees your normal page.
Before you start
- Google Ads campaigns bidding on city keywords
- Your city list as a CSV
- A landing page to localize
- Your branding where the agent can see it: a brand kit in Brand Studio, or any reference that shows your look and voice
The prompt
Paste this into the agent. The bold values are yours to change:
Build a landing page at [/local] that reads the [city] URL parameter from my Google Ads campaigns and localizes the headline, intro copy, and [the testimonial section] for that city — so [?city=austin] renders "Now delivering in Austin."
Validate against my city list: [CSV of 100 cities]. Anything missing or unrecognized falls back to my generic copy.
Give me the exact URL pattern to paste into my campaigns, and confirm UTM parameters pass through untouched.
If you want real per-city pages instead (for SEO rather than ad traffic), say so: the agent generates a page per CSV row the same way.
What the agent does
- Builds the dynamic page with city-aware slots for headline, intro, and the sections you name.
- Validates every value against your city list, so a typo in an ad never renders on the page.
- Falls back to your generic copy for missing or unknown parameters.
- Hands you the URL pattern for your campaigns and confirms tracking parameters carry through.
Try it on your store
The prompt opens in the agent ready to edit, with your store and tools connected.