We all know by now that search is an effective channel for local marketing. Marketing through search at the local level is best practice for businesses with physical locations (and even for some without), but doing that at scale can be tricky. If you have a business with multiple locations, you’ll want to ensure that people searching in a particular area get served an ad that calls out the city they’re in. Ideally, you would show offers for that city and drive to the landing page specifically for that city. The most straightforward way to accomplish this is to create one campaign for each city and set the geo-target to that city alone.
So what if you have 1,500 cities? And then what if you want to split your budget by brand vs. non-brand? This means you have to create 3,000 campaigns. If you have 50 ad groups per campaign, you’re now dealing with 150,000 ad groups and potentially millions of keywords. This can start to get pretty messy for day-to-day management.
The level of geo-granularity when it comes to structuring paid search campaigns is an on-going struggle. As the space becomes increasingly competitive, appearing as the most relevant ad on the SERP is critical. To accomplish this, should you geo-target strictly at the city level and create one campaign per city? Should you create one campaign at the state level and geo-target only the list of cities where you have locations? Or should you target the entire state and separate your locations using ad groups?
I tested two of these scenarios.
For a company with 40 locations in the state of Texas, for a 14 day period, I created one campaign for each city and set the geo-targeting for each campaign to that city only. For the next 14 days, I created one campaign, and geo targeted the same list of 40 cities, but all within one campaign. Keywords, ad copy and max CPC bids stayed the same.
|Metric||40 Campaigns – 40 Cities||1 Campaign – 40 Cities||% Change|
|Search Impr. share||62.41%||61.71%||-1.12%|
|Search Lost IS (rank)||37.12%||31.51%||-15.11%|
The results in this test show that having one campaign with multiple geo-targets yielded better results in this case. Gains were recognized in impressions, clicks, CTR, average position, lead volume, cost per lead, conversion rate and lost impression share due to rank. The down side is a slightly higher CPC and higher impression share loss due to budget. However, the results for the last 14 days were much more desirable overall than those from the first 14 days.
For a company with 64 locations in the state of California, for a seven day period, I had one campaign geo-targeted to all of California. For the next seven day period, within the same campaign, I changed the geo-targeting from all of California to the list of 64 cities. As with the first test, other variables remained the same.
|Metric||1 Campaigns – 1 state||1 Campaign – 64 Cities||% Change|
|Search Impr. share||50.73%||59.94%||18.15%|
|Search Lost IS (rank)||49.27%||40.06%||-18.69%|
In this test, the differences in results are not as dramatic, but they’re still there. With far fewer impressions, we were able to maintain the same number of clicks, which means a higher click-through-rate and higher conversion rate. Cost-per-click also came down, average position went up and most notable are the gains in impression share and the drop in lost impression share due to rank.
In summary, from these two tests, we see that creating one campaign for each city may be too much of a granular choice for geo-targeting. At the other extreme, broadening the geo-targeting to cover the entire state may be too broad. The reasons why this is happening are completely open to speculation. The former may be severely restricting the number of auctions you enter, while the latter may be opening you up to too many auctions, reducing your relevance/QS, and increasing costs.
The middle-ground seems to be the sweet spot here. In both tests, one campaign with a list of city level geo-targets had the best results. What kind of results are you seeing from your geo-targeting testing? Please share in the comments below.