Recommendations
Answer to the stakeholder question
Yes — tell developers and content to fix this. Different H1/banner with identical body and FAQ is not “harmless duplication.” Fix before production indexation. Synonym-level paraphrases of the same FAQ are not a strategy.
Option A — Hub + locations (preferred)
- One authoritative page per service (e.g.
/teeth-in-a-day/or keep the production-style services path). - Location pages own NAP, providers, neighborhoods, offers, and trust — and link to the hub for deep education.
- Build
/{location}/{service}/only for proven money intents with real local demand and unique assets (implants, emergency, Invisalign, Teeth-in-a-Day if uniquely staffed). - Lowest content cost; closest to what production already does well.
Option B — Keep full location×service matrix (higher cost)
- Only if each URL gets a true local brief before indexable launch.
- Minimum unique blocks per page: local intro; why this office; provider(s); neighborhoods served; process/aftercare specifics; 2–3 unique FAQs; local proof (photos/reviews).
- Shared boilerplate capped (short procedure explainer), not the whole page body + FAQ dump.
- Priority queue: Teeth-in-a-Day → Dental Implants → Invisalign → Porcelain Veneers → Emergency → remainder.
Content rules (either option)
| Do | Don’t |
|---|---|
| Unique title + meta per indexable URL | Identical “Service - Dental Team” titles |
| One location-qualified H1 | Two H1s (generic + location) |
| One office phone + booking CTA | Stacks of every office phone |
| Self-canonical to final host/path | Missing canonicals / -2 duplicate publishes |
| FAQ schema only for unique answers | Clone FAQ JSON across offices |
Tech checklist (blocking)
- To resolve
[location_phone],[location_booking_link],[location_content]in rendered HTML — URL evidence sheet (205). - To stop injecting full shared
service_acf_content+service_faqinto every location URL — shared CPT sheet. - To collapse duplicate roots (
/services/…,/florida/…,*-2) to one canonical per intent — duplicate roots sheet. - To keep staging noindex until P0 passes; then index only the approved URL map — robots checklist sheet.
Suggested reply (UA)
Так, треба фіксити до запуску. Інший H1/банер недостатньо — основний текст і FAQ скопійовані між локаціями. Плюс на стейджі не підставляються [location_phone] / booking tokens і в CTA висять телефони кількох офісів. Або унікалізуємо money pages, або прибираємо матрицю location×service на користь hub + location pages.
Track execution on the action plan.