Research / DSO & Multi-Location SEO
§ 01

Per location duplicate content dental.

How Google's algorithm reads DSO per-location pages

Per-location pages on a multi-location DSO get evaluated against each other and against the brand's centralized pages. Templates that swap only the city name across otherwise identical content read as near-duplicates and get demoted together. The algorithm is structural: paragraph-level token overlap, heading sequence, schema content overlap. The risk applies to ProSites, PBHS, Sesame Communications, and any other templated dental-website platform that ships near-identical per-location pages by default. Substantive uniqueness per location is the only durable signal. The risk compounds at DSO scale: a hundred near-duplicate location pages demoted together carries more impact than ten templated pages on a small group. The siteAuthority inheritance hub covers the broader architecture surface.

What actual per-location uniqueness looks like

Per-location practitioner bylines with the actual dentist's name, state license number from the location's state dental regulatory body, and CODA-accredited program references. The location's specific availableService enumeration (the actual procedures the location performs, not the brand's full catalog rendered identically across every location). Per-state advertising disclosures rendered programmatically based on the location's jurisdiction (the Texas-location pages carry the TSBDE-required scope-of-service disclosure language; the California-location pages carry the Dental Board of California's disclosure overlay). Insurance networks populated per-location through healthPlanNetworkId with the actual local contracts. Neighborhood-anchored content that is substantive (not stuffed-city-name templates that swap "Downtown Dallas" for "Downtown Houston" and call it unique). Patient testimonials specific to the location's clientele. The work routes through DSO SEO as the engagement surface and the one-listing-per-location rule spoke covers the paired GBP-side work.

siteAuthority inheritance flow

Google's siteAuthority signal lives at the domain level. The multi-tier DSO hierarchy (National Brand → Regional Brand → Local Office) lets local-office pages inherit domain-level authority, provided the internal linking and entity nesting are mathematically precise. Organization at the root domain. subOrganization array of per-location Dentist nodes. A clean internal-link graph routing brand-level authority to each location's commercial-query landing page. Sloppy nesting or weak internal-link plumbing leaves the per-location pages stranded. The domain-level authority doesn't flow to where the commercial-query traffic needs to land. The website-architecture work hub covers the broader pattern. The foundation sits under SEO for dental practices.

Common questions

What DSOs ask about per-location duplicate content.

01.

How does Google's duplicate-content algorithm read DSO per-location pages?

Per-location pages on a multi-location DSO get evaluated against each other and against the brand's centralized pages. Templates that swap only the city name across otherwise identical content read as near-duplicates and get demoted together. The detection is structural: paragraph-level token overlap, heading sequence, schema content overlap. Substantive uniqueness per location is the only durable signal. Location-specific staff biographies, localized service mixes (which CDT codes the location actually performs), unique facility photography, and neighborhood-specific content.
02.

What does actual per-location uniqueness look like?

Per-location practitioner bylines with the dentist's name, state license, and CODA-accredited program. The location's specific availableService enumeration (the actual procedures the location performs, not the brand's full catalog). Per-state advertising disclosures rendered programmatically based on the location's jurisdiction. Insurance networks populated per-location through healthPlanNetworkId with the actual local contracts. Neighborhood-anchored content that's substantive (not stuffed-city-name templates). Patient testimonials specific to the location's clientele.
03.

How does <code>siteAuthority</code> flow from brand to location pages?

Google's siteAuthority signal lives at the domain level. The multi-tier DSO hierarchy (National Brand → Regional Brand → Local Office) lets local-office pages inherit domain-level authority, provided the internal linking and entity nesting are mathematically precise. Organization at the root, subOrganization array of per-location Dentist nodes, clean internal-link graph routing brand-level authority to each location's commercial-query landing page. Sloppy nesting or weak internal-link plumbing leaves the per-location pages stranded.
04.

What does Section 5.B actually say about testimonials?

ADA Section 5.B governs testimonials and prohibits materially deceptive testimonials. The interpretive guidance enforces an "average patient" rule: a testimonial that quotes a statistically anomalous outcome creates an unjustified expectation under Section 5.F.2's false-or-misleading definition. Quotes have to reflect the typical patient experience for the procedure or service described. The CEBJA Advisory Opinions interpret Section 5.B for specific testimonial patterns the main text does not explicitly cover.
Booking diagnostics for Q3 2026

Build actual per-location uniqueness. Skip the templated-page demote. Let siteAuthority flow through clean entity nesting. Book a diagnostic.

We audit your existing per-location pages against the duplicate-content algorithm surface, surface the templated patterns that risk demotion, and ship the per-location uniqueness scope plus the entity-nesting plan. The diagnostic comes back inside two weeks.

Book a diagnostic

Four fields. We respond inside one business day with a few questions to make sure we can help, before either of us spends time on a call.

We use what you submit to qualify, then respond by email. We don't subscribe you to anything.