Do duplicate service-area pages help or hurt local rankings?

Properties1
tagsduplicate-content, service-area-pages, local-seo, contested

3 min read

Do duplicate service-area pages help or hurt local rankings?

Asked: 2026-07-01 | Confidence: medium (genuine open dispute)

Answer

This is the wiki’s sharpest contested question, and the two sides are both credible.

Position A — duplication works (pro): James Dooley states, from repeated testing, that copied service-area pages outrank spun/“unique-ified” content, and that duplicate content “isn’t the problem — crawl budget and brand trust are.” Crucially, host Joy Hawkins (a respected, independent local SEO) says on-air she tested the same and saw the same result. Two independent practitioners agreeing from testing is stronger evidence than any single creator.

Position B — unique/local wins (con): Caleb Ulku’s system (Core 30, Programmatic SEO) insists every page be genuinely local and unique — real neighborhoods, weather, permits — and warns that “thin, spammy” or “AI slop” pages won’t (and increasingly can’t) get indexed. This aligns with mainstream Google guidance against doorway/duplicate pages.

They may be less opposed than they look. Three variables reconcile most of the conflict:

  1. What “duplicate” is measured against. Dooley compared clean duplication vs. spun content (low-quality auto-rewrites) — and clean duplication won. Caleb advocates genuinely-unique-local, also rejecting spun content. So the likely quality order is unique-local ≥ clean-duplicate > spun — and both sources agree spun is worst. They’re partly arguing past each other.
  2. Domain trust / crawl budget is the hidden variable. Dooley explicitly says a trusted domain can run thousands of near-identical pages and rank, while a new, no-trust domain gets them de-indexed. Caleb’s audience is often new local-business sites — exactly where thin duplication fails and unique-local helps build the trust Dooley presupposes. Same mechanism, different starting points (this connects to Brand & User Signals as Ranking Drivers — trust/traffic as the gate).
  3. Effort vs. payoff. If clean duplication ranks nearly as well on a trusted domain at a fraction of the cost, it’s an efficiency argument, not a correctness one.

Bottom line: On a low-trust/new site, invest in genuinely unique, locally-specific pages (Caleb is right for that context). On a high-trust domain scaling many locations, clean duplication may rank efficiently and “unique-ifying” via spinning can hurt (Dooley is right for that context). Avoid spun content in all cases. The blanket claim “duplicate content is always bad” is not supported by the evidence here.

Caveats

  • No controlled experiment isolates the variables (domain trust × content type). Both sides argue “from testing” without published methodology.
  • No official Google statement in the corpus on service-area/duplicate pages; historical guidance warns against doorway pages, but that predates the 2026 AI-search context.
  • Dooley has commercial incentives (lead-gen at scale favors cheap duplication); Caleb sells unique-content tooling (Core30 AI Tool, 8-Pass AI Writing Pipeline). Both framings serve their offers.

Next Steps

  • Run/seek a controlled test: same market, three page variants (unique-local vs. clean-duplicate vs. spun) on domains of differing trust; measure map-pack + organic over 60–90 days.
  • Backfill an official Google source (Search Central docs / statements) on duplicate & doorway pages in a local context.
  • SERP-audit currently-ranking multi-location local sites to see whether their location pages are unique or duplicated.