How to build city pages that actually rank (without doorway penalties)

The doorway page trap

Most local businesses build city pages the wrong way. They take one template, swap "Austin" for "Round Rock" for "Cedar Park", and publish 50 near-duplicate pages. Google's algorithms catch this in days and either ignore the pages or actively suppress them. This is the doorway page penalty, and it's the single biggest reason programmatic local SEO fails.

The fix isn't to abandon templates — it's to give every page enough genuine local context that it earns its place in the index.

What a city page Google actually rewards looks like

After auditing hundreds of ranking city pages across home services, legal, medical and home improvement, the pattern is consistent. The pages that win share these elements:

• A unique opening tied to that neighborhood — a sentence about the local climate, a building stock detail, a road, a landmark, a regulation.
• Two or three real testimonials from customers in that area — names, neighborhoods, photos when possible.
• Service-specific FAQs that answer the questions people in that city actually ask (not generic ones).
• LocalBusiness + Service schema correctly nested, with the right service area defined.
• Internal links to 3–5 nearby city pages — this is the lever almost everyone forgets.
• A unique hero image or map — even a styled map of the service area beats a stock photo.
• Clear NAP (Name, Address, Phone) consistent with your Google Business Profile.

Notice what's not on the list: 3,000-word essays, exact-match anchor text, or stuffing the city name 40 times. Google is smarter than that, and so are your customers.

A page Google likes — the structure

Here's the structure we use for every city page Bloggie generates:

1. Hero with intent-matched H1

The H1 should match what people actually search: "AC Repair in Round Rock, TX" — not "Welcome to our Round Rock service area".

2. Local proof bar

Years serving the city, number of jobs completed, response time, average rating. Real numbers, not made up.

3. Unique local intro (150–250 words)

This is the make-or-break section. Write something only a business that actually serves this city could write. Mention the local climate's impact on the service, a common housing-stock issue, a permit consideration, a neighborhood callout.

4. Services offered in that city

Not a generic list — specifically the services you provide there, with realistic pricing or response time when possible.

5. Testimonials from that city

If you have them, use them. If you don't yet, leave the section out rather than fake it.

6. Service-specific FAQs

5–8 questions a customer in that city would actually ask. AI can generate good first drafts; a human should review.

7. Internal links to nearby cities

"We also serve [Pflugerville], [Cedar Park], and [Hutto]." Three to five links, naturally placed.

8. Schema

LocalBusiness with the parent business, Service describing what you do, and the right areaServed. Skip this and you're leaving 20–30% of your potential ranking on the table.

Scale without sacrificing quality

Templates are fine. Boilerplate is not. The trick is to template the structure and let AI expand each section with real local signals — neighborhood names, climate, common local issues, building types — that you provide as inputs.

This is exactly how Bloggie's city page generator works: you connect your site once, define your services and cities, and the system produces unique, schema-marked, internally-linked city pages that publish straight to WordPress.

Common mistakes to avoid

• Identical H1s with only the city swapped — vary the wording.
• The same testimonials on every page — leave the section out if you don't have local ones yet.
• Forgetting internal linking — orphan city pages don't rank.
• No schema, or wrong schema — LocalBusiness with wrong areaServed is worse than none.
• Publishing all 50 pages on the same day — drip them out over weeks.

Done right, city pages are still one of the highest-ROI SEO plays available to local businesses in 2026. Done wrong, they're a fast track to a manual action.