The Two Approaches and Their Trade-Offs

Location-specific pages give each location its own URL with local content, surgeon bios, location-specific reviews, photos, and structured data. A glaucoma practice with five locations would publish five pages, each with its own MIGS volume reporting, OCT and HFA technology lists, surgeon credentials, and contact details. Hub pages put all locations on one page with a location selector, dropdown, or interactive map. The user lands and chooses their location, then sees relevant content below.

Hybrid approaches create a location directory that lists all locations briefly and links to per-location pages for the substantive content. Each approach has trade-offs across PPC Quality Score, organic SEO local visibility, and ongoing maintenance cost. The three-axis trade-off is what makes this debate persistent: practices that optimize for maintenance cost reach for hub pages, practices that optimize for performance reach for per-location pages, and the right answer depends on group size and service heterogeneity. Single-doctor solo practices do not face this question; multi-location groups face it constantly.

The 2026 Performance Data

Location-specific pages outperform hub pages on PPC Quality Score and SEO local visibility for groups with 5 or more locations. The CVR differential on paid traffic typically runs 15 to 30 percent higher for location-specific pages, driven by tighter relevance between query, ad copy, and landing page. A “glaucoma specialist in [city]” search that lands on a per-city page with local provider photos, local reviews, and the city name in the headline converts substantially better than the same search landing on a hub page asking the user to pick their location before seeing relevant content.

Quality Score impact compounds the CVR advantage. Landing page experience is a Quality Score factor, and Google rewards tight query-to-page relevance with lower CPCs. A hub page serving 20 locations cannot match the relevance signal of a dedicated city page, and the resulting Quality Score penalty (typically 1 to 2 points lower on average) translates to 10 to 30 percent CPC inflation across the cannibalized keywords. SEO local visibility favors per-location pages because Google’s local algorithm rewards location-specific entity signals, schema, and content depth.

The maintenance cost is real. Per-location pages require 3 to 8 hours per location per year to maintain (review refreshes, provider bio updates, technology list edits, holiday hours). For a 10-location glaucoma group that is 30 to 80 hours annually. The ROI math usually clears the threshold by a wide margin once the CPC and CVR effects are quantified. The companion multi-location account structure piece covers the campaign-side architecture that pairs with this landing page decision.

Where Hub Pages Still Fail

Five red flags indicate a hub-page strategy is breaking. First, 10 or more locations on one hub page. The selector becomes unusable, the page weight balloons, and Google’s crawl treats the page as an aggregated directory rather than a service page. Second, the location selector requires multiple clicks to reach relevant content. Every click between the ad and the conversion form depresses CVR roughly 10 percent, and a hub page with a multi-step selector compounds that penalty across every visit.

Third, no unique structured data per location. LocalBusiness schema needs to surface address, phone, hours, geo coordinates, and aggregate review data per physical location. A hub page that does not implement separate schema blocks per location loses the local-pack signal entirely. Fourth, reviews and photos are not location-specific. A patient searching for the [city] location wants to see reviews from that location’s patients and photos of that specific facility, not a generic gallery from corporate marketing. Fifth, the phone number is identical across all locations on the hub page. Beyond confusing patients, this collapses the local entity signal and produces the same generic conversion behavior across every market the practice serves.

The Structural Recommendation by Group Size

Use location-specific pages for groups with 5 or more locations or mixed service offerings. Hub pages remain acceptable only for 2 to 4 locations with truly identical services and shared providers across sites. URL structure should be predictable and consistent: /locations/[city]-[state] or /locations/[neighborhood] for major-metro groups. Each page needs unique content blocks at minimum, including location-specific photos, provider bios with surgeon names and fellowship credentials, recent reviews tagged to that location, the local phone number, and LocalBusiness schema with the correct address and geo coordinates.

For glaucoma-specific multi-location groups, additional per-location signals matter. MIGS procedure volume per location (when reportable) communicates surgical experience to the second-opinion searcher. Per-location technology lists (OCT model, HFA visual field perimeter, gonioscopy capability) signal diagnostic depth to the referring optometrist as well as to the patient. Per-location surgeon biographies including fellowship training and society memberships build the trust signal that converts the higher-intent diagnosed patient. Build the page architecture so a per-location update never requires touching shared template code; each page should be edit-isolated to keep the maintenance hours predictable. The companion geo-targeting mistakes piece covers the campaign settings that pair with this landing page setup.

Avoid the common over-correction where each per-location page is a thin template clone with only the city name swapped. Google treats high-similarity pages as duplicates. Aim for 40 to 60 percent unique content per page with location-specific reviews, photos, and provider content as the differentiation drivers.

Implementation Sequence

Start with the location data audit. Pull patient ZIP distributions per location, dominant queries per local market, and the current Quality Score and CVR on whatever the practice currently serves traffic into. Most multi-location glaucoma groups discover that 1 to 2 locations carry 60 to 70 percent of paid traffic, which means the per-location page build can be sequenced. Build the highest-volume locations first, measure CVR lift over 60 days, then justify the rollout to remaining locations on demonstrated ROI.

Templated page generation with database-driven dynamic content is appropriate as long as the per-location uniqueness threshold is met. Templated pages can pull location name, address, phone, hours, surgeon list, and recent reviews from a CMS, which keeps maintenance hours bounded. The risk is that templated pages tend to drift toward 90 percent identical content with only the city name varying, which Google may treat as thin or duplicate. Build the template with mandatory unique-content fields per location (a per-location intro paragraph written by the practice, location-specific photos, the location’s specific provider biographies) so the template never collapses to an SEO duplicate.

Match each per-location page to a location-specific ad group with city-specific ad copy and tight geo targeting. The end-to-end relevance chain (keyword to ad copy to landing page) is what produces the Quality Score and CVR lift the data shows. Per-location landing pages without per-location ad groups capture half the available improvement. The companion high-converting landing page piece covers the on-page elements that drive the CVR lift.

Specialty Vision’s Take on Per-Location Pages

Our view, the hub-page approach was a 2018 to 2021 convention that made sense when each location page was a thin template and the local entity signals in Google’s algorithm were less mature. Current landing-page best practice produces pages with enough substance (credentialing depth, technology specifics, provider bios, condition-specific positioning) that separate per-location pages win on every measurable axis except the maintenance hour line. The maintenance trade-off is real but almost always worth it once the CPC and CVR effects are quantified for the practice. We have rarely seen a multi-location glaucoma group with 5 or more sites where the hub-page approach beat per-location pages on the full audit math. For the broader audit context that surfaces this and adjacent multi-location issues, see our 2026 PPC audit playbook.

Operationally, we sequence per-location page rollouts by traffic volume and pair them with city-specific ad groups so the relevance chain stays tight from query to conversion.