Location pages are the most misused tactic in local SEO. The theory is sound: build a page for every city you serve, rank for “tree service [city]” in each one, expand your footprint across the whole metro area. Tree companies do it. They just usually do it wrong.
The wrong version: copy your homepage, change the city name in three places, publish it. Google identifies this pattern immediately. A page that shares 90% of its content with your homepage is not a separate page in Google’s view — it’s a duplicate. It will not rank. It may actually reduce the authority of your stronger pages.
The right version requires more work. But done correctly, a well-built location page can rank for “tree removal [city]” in a market you don’t physically operate in — closing the proximity gap against competitors who are physically closer to the searcher.
Every neighborhood like this one has homeowners searching for tree service right now. A well-built city page is how your company shows up in that search instead of a competitor.
Why the Swap-the-City-Name Approach Fails
Google’s algorithm has been specifically trained to detect templated location pages. The signals it looks for:
- High percentage of shared content with other pages on the domain
- City name appearing in title, H1, and meta description but almost nowhere in the body text
- No content specific to that location — same services, same descriptions, same CTAs
- No external signals (citations, reviews, GBP service area) confirming you operate in that city
When Google detects these patterns, it either suppresses the page from ranking entirely or assigns it very low relevance for local queries. You end up with a page that exists but does nothing.
“Looking for tree service in Murray, UT? Elite Tree Service serves Murray with professional tree removal, trimming, and stump grinding. Call us today for a free estimate in Murray.”
“Murray has a mix of older cottonwoods and box elders that can develop significant crown weight over time. We’ve completed over 80 removals in Murray in the past two years, including several near the older homes on the east bench where power line clearance is a regular concern.”
The difference is specificity. The second version could not have been written without knowledge of Murray. Google recognizes that. So do homeowners reading it.
What Makes a Location Page Actually Rank
Location-Specific Content
Every location page needs content that could only be written about that specific city. This does not mean you need to write a history essay — it means weaving in details that confirm you know and operate in this market. Options that work well for tree companies:
- Tree species common in that area (cottonwoods near water, mature oaks in older neighborhoods)
- Specific neighborhoods, subdivisions, or landmarks you’ve worked near
- Local conditions — soil type, wind exposure, storm patterns
- HOA or utility considerations specific to that city
- Approximate number of jobs completed there (“over 60 removals in Sandy in the past 18 months”)
- Any permits or city ordinances that affect tree work in that municipality
Even two or three specific sentences of this type will differentiate your page from a template. Combined with the rest of the page, it signals genuine local presence to Google.
Page Structure That Covers the Full Query
A location page that ranks needs to answer every question a homeowner in that city might have before calling. That means covering:
- What services you offer there — not just tree removal, but the full list with brief descriptions
- Your service area within or around that city — are you covering all of it? Just certain zip codes?
- Response time and availability — especially for emergency queries
- Credentials specific to tree work — ISA certification, local business license, insurance levels
- Reviews from that city — even a single embedded review mentioning the city name adds local relevance
- Call to action — phone number, estimate request form, or both
Minimum length for a location page that ranks: 500 words. The sweet spot for most competitive markets is 600–900 words. Below 400 words, the page is too thin. Above 1,200 words without genuine new content, you’re padding.
Technical Signals That Confirm Local Presence
On-page content alone is not enough for highly competitive city pages. Google cross-references what your page claims against external signals. The most important ones for tree companies:
- GBP service area listing — the city must be listed in your Google Business Profile service areas. If it’s not there, the page has no GBP signal to lean on.
- Citations — directory listings (Yelp, Angi, BBB) that include that city in your service area description
- Schema markup — LocalBusiness or Service schema on the page with the city name in the areaServed field
- Internal linking — your homepage and service pages should link to the city page. Orphan pages (no inbound links) rarely rank.
- Reviews mentioning the city — on Google, Yelp, or embedded on the page itself
How Many City Pages Do You Need?
Build one page for every city where you regularly complete jobs — not every city in the metro area. The distinction matters. A page you can write specifically about a city (because your crews work there) will outrank a page you had to write generically (because you’re just hoping to rank there).
| Situation | Pages to Build | Content Approach |
|---|---|---|
| Primary city where you’re based | 1 strong page per service | Most specific content |
| Cities where you work regularly (10+ jobs/year) | 1 page per city | Job history + local detail |
| Cities you serve but work less frequently | 1 page per city, thinner | Service focus + area context |
| Cities you want to expand into | Build after establishing GBP service area | Start with GBP, then build page |
Title Tags and H1s That Actually Get Clicked
The title tag is the headline in search results. It has to include the city name and the primary service, and it has to give the searcher a reason to click yours over the two competitors listed next to it.
Formats that perform well:
- “Tree Removal in Murray, UT — Licensed Arborists, Free Estimates”
- “Murray Tree Service — Removal, Trimming & Stump Grinding Since 2008”
- “Tree Service Murray UT — Same-Week Estimates, Fully Insured”
Formats to avoid:
- “Tree Services — Murray” (generic, no differentiator)
- “Murray, UT Tree Removal, Tree Trimming, Stump Grinding, Land Clearing, Emergency Tree Service” (keyword stuffing — truncates in results and looks spammy)
Our Search Gap Engine™ shows you exactly which cities in your market you’re missing coverage for — and which competitors are ranking there instead of you. It’s the fastest way to prioritize which city pages to build first based on actual search data from your market.
When to Add More Pages vs. Improve Existing Ones
If you already have city pages but they’re not ranking, the answer is almost always to improve what exists before adding more. A site with 15 thin location pages ranks worse than a site with 6 solid ones. Google distributes authority across your entire domain — more weak pages dilute that authority further.
The improvement checklist for an underperforming city page:
- Is the word count below 500? Add specific content about that city until it is over 500.
- Does the page have fewer than 3 location-specific references? Add them.
- Is the city in the GBP service area? Add it if not.
- Does any other page on your site link to this one? Add an internal link from the homepage or a related service page.
- Is there schema markup on the page? Add LocalBusiness schema with the city in the areaServed field.
Work through that checklist on your lowest-performing pages before building new ones. You will almost always see faster results improving existing pages than creating new thin ones.
Using Reviews to Strengthen Location Pages
One of the most effective things you can add to a city page is a real review from a customer in that city. Even a single embedded review that mentions the city name — “Elite Tree removed two huge cottonwoods from our yard in Murray” — does two things: it adds local keyword relevance naturally, and it provides social proof specific to that market.
You can embed Google reviews directly using the Google Places API, or simply screenshot and display a handful of relevant reviews. If you use a review management tool, most of them have embeddable widgets. The goal is to have at least two to three reviews visible on every city page that mention the city or a nearby landmark.
When requesting reviews from customers, consider asking them to mention the city or neighborhood in their review. “We’d love it if you mentioned where you’re located in your review — it helps other homeowners in [city] find us.” Most customers are happy to do this, and it generates the most useful reviews for both your GBP and your location pages.
Adding a FAQ Block to Each City Page
A FAQ section at the bottom of a city page accomplishes two things: it adds relevant content that addresses specific homeowner questions, and it qualifies for FAQ schema markup that can expand your search result footprint.
Questions that work well for city-specific FAQ blocks:
- “How much does tree removal cost in [City]?” — Answer with a range and the factors that affect pricing in that specific market.
- “Do you need a permit to remove a tree in [City]?” — Answer with the actual local ordinance if you know it. This is highly location-specific content Google values.
- “How quickly can you respond to emergency tree service in [City]?”
- “What tree species are most common in [City] that need regular attention?”
Four to five questions per page is enough. Write the answers at 50 to 100 words each — enough to be genuinely useful, not so long they read like padding. Add FAQPage schema to make them eligible for rich result display in Google Search.
Mapping your service area is the easy part. Building a page for each city that actually ranks is what converts that coverage into calls.