Quick start
- ping a third-party geo-location API
- wait for the response
- update the page content dynamically
Follow the detailed steps below to complete the setup.
One of the easiest ways to boost conversions on a landing page is simple. Make the page feel like it was built specifically for the person viewing it.
That is exactly what Corey wanted to do.
He asked how to automatically display a visitor’s city on his landing page, hoping to create that “Hey, this is for me” effect.
And yes, the idea is smart. But the implementation can get a little tricky.
Let’s break down what actually works and what to avoid, so you can personalize your pages without tanking your load time or relying on tech that breaks half the time.
The Dream: “Welcome, {{city}}!”
A dynamic city tag on your landing page is powerful for relevance and trust.
Imagine seeing:
“Roofing Services in Charlotte”
or
“Your Personal AI Setup Concierge in Chicago”
Your brain instantly says, “Oh wow, this applies to me.”
Corey tried using the classic {{city}} merge field and it worked when the city was added manually in the URL.
So the next question was: “Can we detect the visitor’s location automatically?”
Short answer: Yes, but you probably should not.
Why IP-Based Detection Slows Everything Down
Here is the problem with auto-detecting the visitor’s city.
To get the city from an IP address, the page has to:
- ping a third-party geo-location API
- wait for the response
- update the page content dynamically
That “waiting” part is the deal-breaker.
Even a tiny half-second delay impacts conversions, and sometimes the script stalls or misfires entirely.
The last thing you want is a blank spot on your headline because location detection hiccuped.
And speed is everything. A slow landing page is a dead landing page.
The Winning Solution: Use Google Ads to Pass the City Automatically
Instead of detecting the user’s city on-page, HighLevel recommended a much cleaner approach.
Here is how it works:
- Create different ad groups for different cities.
- Append the city to the landing page URL as a parameter.
- Use that parameter to populate {{city}} dynamically on the page.
For example:
yourlandingpage.com?city=Charlotte
yourlandingpage.com?city=Raleigh
yourlandingpage.com?city=Greensboro
The page loads instantly, no API calls, no delays. And the visitor sees their city, perfectly inserted.
Corey’s only pushback? “Man, that is a lot of manual setup.”
And, yes. The tradeoff for speed and reliability is legwork up front. But once it is done, it runs flawlessly.
Why This Approach Works Better Long-Term
- zero load-time penalty
- no dependence on unreliable IP data
- complete control over ad-to-page messaging
- higher Quality Scores from Google
- improved personalization without “technical fragility”
Plus, if you are running paid traffic, you already know that specificity is what wins.
“Best HVAC service” is good.
“Best HVAC service in Nashville” is better.
“Best HVAC service in East Nashville near you” is unbeatable.
Personalization is worth the extra setup.
Want smarter tools to speed up your HighLevel builds?
It is the easiest way to level up your workflow without reinventing your entire process.
Cool Free Thing
If you want clients to trust you faster, start collecting strong testimonials automatically.
I am giving you a free workflow that handles the entire testimonial collection process for you, from request to storage.
.
Frequently Asked Questions
What should I know about the Dream: “Welcome, {{city}}!”?
A dynamic city tag on your landing page is powerful for relevance and trust. Imagine seeing: “Roofing Services in Charlotte” or“Your Personal AI Setup Concierge in Chicago” Your brain instantly says, “Oh wow, this applies to me.” Corey tried using the classic {{city}} merge field and it worked when the city was added manually in the URL. So the next question was: “Can we detect the visitor’s location automatically?” Short answer: Yes, but you probably should not.
Why IP-Based Detection Slows Everything Down?
Here is the problem with auto-detecting the visitor’s city. To get the city from an IP address, the page has to: ping a third-party geo-location API wait for the response update the page content dynamically That “waiting” part is the deal-breaker. Even a tiny half-second delay impacts conversions, and sometimes the script stalls or misfires entirely. The last thing you want is a blank spot on your headline because location detection hiccuped. And speed is everything. A slow landing page is a dead landing page.
What should I know about the Winning Solution: Use Google Ads to Pass the City Automatically?
Instead of detecting the user’s city on-page, HighLevel recommended a much cleaner approach.
Start Your HighLevel Free Trial
Browse all GoHighLevel guides · HighLevel Funnel.