Purpose
Advisory playbook for the Dental Team FL website redesign. Staging introduces a large /{location}/{service}/ matrix. Stakeholders asked whether near-duplicate service pages (different H1/banner, same body/FAQ) are acceptable. They are not safe to launch as-is. Track remediation on the action plan.
Verdict
- Fix before cutover. Location-swapped H1 and hero copy are not enough when the main educational body and FAQ are cloned across offices.
- Choose IA now: hub service page + strong location pages or fully unique money location×service pages — not a thin template matrix “to uniquify later.”
- Blockers on staging today: unresolved
[location_*] tokens, multi-office phone CTAs, dual H1s, identical titles, missing meta/canonical on sampled location-service pages.
Scope checked (2026-08-12)
Headline evidence
- All checked Teeth-in-a-Day location pages share the same ~4.4k-character All-on-4 body and identical 5 FAQs.
- Staging page sitemap contains on the order of ~216 location×path URLs; high-volume services (Invisalign, implants, veneers, whitening, root canal, etc.) follow the same CPT-reuse pattern.
- Production location pages (Bayview, Atlantic Blvd East) are meaningfully unique — staging should not regress into doorway clones.
- Staging robots:
noindex, nofollow (good for QA). Risk becomes ranking-critical at launch.
Work order
- Fix location merge tags + single-office CTAs
- Lock IA (hub model vs unique matrix)
- Remove shared full-page CPT dumps from location URLs
- Unique titles / metas / one H1 / canonicals
- Dedupe overlapping service roots and
-2 URLs
- Pre-launch robots and sample URL inspection
Key pages in this playbook