How do you track which city landing pages actually turn into booked jobs?

Decide what counts as a lead before you measure anything

Most businesses track pageviews because that is what the analytics tool shows by default, then get frustrated because pageviews do not pay for anything. Before setting up any tracking, write down the actions that actually matter: a phone call over a certain length, a submitted quote form, a booking through your scheduler, a text message. Each of those needs to be captured as an event tied to the page the visitor was on. If an action cannot be tied back to a page, it cannot tell you which city pages are working. Related: Why Thin City Pages Hurt You

You also need to decide how far to follow the lead. Some businesses stop at the call; others connect the call to a job in their invoicing system and record the ticket value. The second is far more useful, because a city page that produces many small calls may be worth less than one that produces a few large jobs. Even a rough manual link, such as asking the customer which town they are in and noting the source, gets you most of the way there.

Keep reading: Why Thin City Pages Hurt You, Building Genuinely Useful Local Pages, Ranking for a Service Area. See how Localander helps you service-area city landing page generator for local businesses.

Track phone calls per page without expensive tools

The simplest reliable method for calls is to fire an event when someone taps or clicks the phone number on a page. On mobile, that tap is a strong signal of intent even if you cannot confirm the call connected. Set up the click as a conversion event in your analytics tool, make sure the page URL is captured with it, and you will have a per-page count of call attempts. It undercounts people who read the number and dial manually, but the undercount is roughly consistent across pages, so comparisons still hold. Related: Keeping Local Pages Fast

If you want call confirmation and duration, call tracking services can swap the displayed number per page or per traffic source and record which number was dialed. That adds a monthly cost and some complexity around keeping your main number consistent for your Business Profile. Many small businesses do fine with click tracking plus a habit of asking every caller which page or town they were looking at. The answer goes into a field on the job record, and you have attribution that is good enough to make decisions. Related: What a Good Service Area Page Contains

Give forms and bookings a page field

Quote forms and booking widgets should carry a hidden field that records the page the visitor submitted from, along with the city the page targets. This is a small change that most form tools support, and it turns every submission into a data point you can sort by city. When the submission reaches your inbox or your job software, the city is right there. Over a few months, you build a picture of which pages produce real requests and which produce nothing beyond traffic.

Be careful with forms that live in a shared component, such as a footer or a popup that appears on every page. The hidden field should read the current page at submit time, not a fixed value baked into the component. It is also worth recording the referring source, so you can see whether a page's leads come from organic search, ads, or a directory. A city page that gets all its leads from a paid campaign is a different situation from one that earns them organically.

Review by city, not by page, and decide

Once the data is flowing, roll it up by city rather than staring at individual URLs. A city may have a hub page and two service pages, and the question that matters is whether that town is producing jobs, not which of the three pages got the click. Build a simple sheet with columns for impressions, clicks, calls, forms, booked jobs, and revenue by city, and update it monthly. Patterns become obvious within a quarter: a few towns carry the weight, some are steady, and some never convert. Related: How many city pages should a local service business actually build in its first year?

Then act on it. Towns that convert deserve more depth, more photos, and possibly ad spend. Towns with traffic but no calls need a look at the page itself, since something is losing visitors after they arrive. Towns with nothing at all go into the pruning review. The point of tracking is not the dashboard; it is the ability to say, with evidence, which pages earned their place and which are just taking up space.