Google Ads for tree service companies: the build order

For tree service companies the conversion that matters is a sold estimate that becomes a completed, invoiced job, and it lives in your tree care software (SingleOps, Arborgold, ArboStar or Jobber) — not in the ad platform. Google can only optimize toward what you send it, so whatever you pick here decides what the algorithm spends the next ninety days chasing. Pick the wrong one and every later step in this playbook is executed perfectly in the wrong direction.

This is the step we get called about most. If you do not have a developer for it, that is the normal situation rather than the exception — it is most of what we do, and it is worth fixing before the spend rather than after.

Google enables these on every new Search campaign, and none of them are keyword decisions — they are switches on the settings screen that decide where the money goes before a single keyword applies. Everything else in this playbook operates on whatever is left after they have taken their cut, so a reader who skips this step spends the rest of it optimizing a remainder.

For Tree service · Target ZIP codes from where sold estimates cluster, Presence only, and keep storm response in its own paused campaign so it goes live on the forecast and stops on a date.

Tree jobs run from a quick stump grind to a crane removal over a house, and the equipment decides the economics: moving a bucket truck, a chipper and a crew costs about the same whether the job is small or large. A stump job at the edge of a wide radius can lose money; a crane removal at the same distance pays for the trip. Draw the area from where you have sold work, give large removals a wider area than trimming and stumps, and decide before storm season how far the storm campaign goes.

Tree leads arrive both ways: a tree on a house is a phone call, often at night, while a removal or pruning job is often a form with photos or a call that books an estimate visit. Google counts a call once it passes the duration you set, and cannot tell a homeowner with a split oak from someone asking whether you drop free wood chips. Count calls that describe a job at an address you serve, and let the sold estimate, not the call, be what bidding learns from.

One flat keyword list is why most accounts in this vertical cannot tell which half of the budget works. Sorting terms by the intent behind them means you can bid, write and judge each group on its own terms — a problem-aware search and a competitor search convert at rates that have nothing to do with each other, and averaging them hides both.

Exact match includes close variants — misspellings, plurals, reordered words, dropped function words. Phrase match now behaves roughly like the old broad-match-modified. Broad match reaches as far as Google judges useful, which with a good conversion signal is genuinely valuable and without one is an open tap. Start narrow, prove the signal, then widen — in that order, because widening is reversible and a mistrained bidding algorithm is not.

For Tree service · Broad match on 'tree' drifts into firewood, nurseries, chainsaws and Christmas trees. Keep removal and storm terms on exact and phrase until sold estimates are importing.

Every vertical has a set of searches that look commercial and are not. In tree service companies those are job seekers, students, people looking for free help, and DIY researchers. Broad and phrase match will find all of them for you. Add this list at the account level on day zero — the first week of an unfiltered account is the most expensive week it will ever have.

Ad groups exist so the ad can match the search. The moment a group holds two intents, the ad has to be vague enough to cover both, and vague ads lose the auction on relevance before budget ever enters the picture. Build these groups, each with its own ads and its own landing page.

Google rewards assets that match the search and the page behind it. It penalizes — and increasingly disapproves — copy that promises something the page does not deliver. Every line below is written to be provable on arrival. Character counts are shown because assets over the limit are rejected at upload, which is where most copied-from-a-blog ad copy dies.

Local Services Ads in the Tree services category carry the Google Verified badge and sit above the text ads on many 'tree removal near me' searches, so in storm weeks they take many of the first calls. LSA leads have no click ID, so match them to estimates by phone number and date. Search wins the homeowner planning a removal who wants photos, credentials and a page before calling, and the large removals that need an on-site estimate. Google no longer credits leads for job types or areas you do not service, so set LSA job types and the service area to match what you sell instead of relying on disputes.

Tree demand has a base and spikes. The base is planned work: dormant-season pruning and removals in late fall and winter, when the leaves are off, and dead or dying trees that owners notice when everything else leafs out in spring. The spikes are storms: wind, ice and hurricane weather produce a burst of emergency calls over a few days, then a long tail of cleanup and hazard-tree removals.

Position is not bought, it is earned and then paid for. Google ranks you on your bid multiplied by how good it expects your ad and landing page to be, plus your assets — so a relevant advertiser at half the bid outranks a vague one, and then pays less per click at the same position. This is the mechanism underneath everything above: tight ad groups and honest ad copy are not tidiness, they are the discount.

For Tree service · Local Services Ads and storm crews from out of town crowd the page after bad weather, and prices jump in the hit ZIP codes. In quiet months you compete with established local companies and lead sellers on removal and trimming terms.

Start on Maximize Conversions with qualified calls and estimate requests as the primary goals, because sold estimates are too few in the first weeks to steer bidding. Import sold estimates from the tree care software with their value inside the 90-day import window, then move removal and trimming campaigns to value-based bidding once enough have imported. Give the storm campaign its own budget and its own goal, and pause it on a date, so a week of storm calls never sets the bids for planned work. Smart bidding is a data problem before it is a strategy problem: with thin or wrong conversion data it will confidently optimize toward noise, and it does that faster than a manual account can lose money.

For Tree service · Bid on qualified calls and estimate requests until sold estimates import from SingleOps, Arborgold, ArboStar or Jobber, then move removal campaigns to value-based bidding. Never let the storm campaign share a budget with planned work.

Most accounts are killed or rescued on evidence that could not have meant anything yet. The bidding algorithm is fitting a model, and a model fitted on two weeks of data is fitted on noise. This is the shortest honest schedule: what to look at each stretch, and — more usefully — what to ignore.

For Tree service · Expect the first month to go on cleaning up calls and negatives. Judge month one on qualified calls, month two on estimates written, and month three on estimates sold, by campaign.

An account left alone drifts toward the cheapest clicks it can find, because that is what the system is built to do when nobody corrects it. This is the shortest routine that keeps it honest. It takes about an hour and it is the difference between an account that compounds and one that plateaus at month three.

For Tree service · Compare calls Google counted with estimates written in the software, by campaign. A campaign with many calls and few estimates has a call-rule or negative-keyword problem before it has a bid problem.