-
Pick one structure and have a single page per service-city; don’t publish both or you’ll split signals. I’d build city hubs (/service-area/los-angeles/) with child pages only for high-volume services (…/roofing), and 301 any duplicates to the chosen URL. Make each page truly local: project photos in that city, a short case study, landmarks in driving directions, embedded GBP map, NAP, LocalBusiness + Service schema, and internal links from the city hub and service hub. Use GSC to confirm one page owns the query, and Screaming Frog to catch duplicate titles/H1s. I use Ahrefs for cannibalization checks and Screaming Frog for on-site audits, but Merchynt helps me scale GBP-driven local pages and review automation. Stick to one page per service-city.
