AIKO: The dry-cleaning chain built a page for each of thirty locations, which is the right instinct, but every page is the same template with the city name swapped in. That’s the problem hiding inside a good idea. Thirty near-identical pages aren’t thirty local pages, they’re one page printed thirty times, and search engines treat that as thin, duplicative content rather than genuine local presence.
ELENA: So structurally they have the right architecture filled with the wrong content, real URLs, real intent, but interchangeable text.
AIKO: Exactly. The skeleton is correct, a page per location is how local works. What’s missing is anything that makes each page actually about its location rather than a find-and-replace of the last one.
MARCUS: Hold on, before they scramble to make thirty pages “unique,” I want to push on what unique actually means here, because the wrong fix is spinning the same paragraph thirty ways.
AIKO: Meaning rewording the boilerplate doesn’t solve it.
MARCUS: Right. If they take the identical template and just reshuffle sentences to dodge the duplicate-content flag, they get thirty pages that are technically different and still say nothing local. That’s gaming the check, not fixing the problem. Real uniqueness isn’t reworded boilerplate, it’s actual location-specific substance, and if a location genuinely has nothing distinct to say, maybe it shouldn’t have a standalone page at all. Don’t manufacture difference, find or create the real thing.
AIKO: That’s the line, the goal isn’t passing a duplicate check, it’s each page genuinely being about its place.
HANNAH: And there’s real material for that, the locations aren’t actually identical, the team just didn’t capture it. Each has its own address, hours, staff, the neighborhoods it serves, parking, local landmarks, services that location specializes in, reviews from that area’s customers. That’s all genuinely distinct and genuinely useful, and most of it isn’t writing, it’s information the business already has and didn’t put on the page. The uniqueness is sitting in the operational details nobody surfaced.
SOFIA: And that local detail is exactly what the searcher wants, which is the conversion angle. Someone searching for dry cleaning in their neighborhood wants to know this location is near them, when it’s open, whether it does the specific thing they need, what the parking is like. The generic templated page answers none of that, it just proves a location exists. The page with real local detail answers the searcher’s actual question and earns the visit, which for local intent is often a same-day one.
NOAH: The pattern is satisfying a structure without satisfying its purpose, building the local-page architecture and skipping the local substance that was the whole point. It’s form without the content the form exists to hold. And there’s a name for the failure mode at the far end of this, doorway pages, near-identical pages made to capture many local searches that all funnel to the same generic experience, which search engines treat as a violation, not just thin content. The tell is pages identical except for a swapped city name, the template visible because nothing filled it.
THEO: So the rule is to make each location page genuinely about its location with real specifics, not reworded sameness. For each one, capture the distinct material, the address and service area, the actual hours, the staff, the neighborhoods served, location-specific services, real local reviews, directions and parking. If a location has genuine specifics, the page writes itself from them. If a location truly has nothing distinct, per Marcus, reconsider whether it needs its own page rather than manufacturing filler. Substance per location, not a template thirty times.
HANNAH: And the structured local information, the consistent name, address, and phone, matters alongside the unique content, because local results lean on that consistency, but consistency of the factual details doesn’t mean sameness of the page. There’s local-specific machinery these pages should connect to as well, LocalBusiness schema marking up each location’s address, hours, and service area so search engines read it cleanly, and each page tied to its Google Business Profile, since for local intent the profile and the page reinforce each other.
THEO: The contact facts stay consistent everywhere, the page content gets locally distinct, those are two separate requirements people collapse into one.
AIKO: Operationally this means feeding location pages from real location data, not a single template, so each page is generated with its own hours, staff, service area, and reviews populated from that location’s actual information. The template provides the consistent structure, the local data fills it with genuine specifics, and a page only goes live when it has real distinct content, not when the city name’s been swapped. The system enforces substance per page rather than letting the template publish thirty copies.
DANA: So where we land is real local substance per page, not a template thirty times. The near-identical pages are a problem because thirty copies of one page read as thin duplication, not local presence, even though the page-per-location architecture is correct. Per Marcus, the fix isn’t rewording boilerplate to pass a duplicate check, that’s gaming it, it’s genuine location-specific substance, and a location with nothing distinct to say maybe shouldn’t have its own page. And per Hannah, the material exists, the addresses, hours, staff, neighborhoods, parking, local reviews the business already has and didn’t surface, with the consistent contact facts kept uniform even as the content gets locally distinct. We feed each page from real location data and publish only when it has genuine specifics. The instinct to build a page per location was right. Filling them all with the same swapped-name template is what made them thin.
SOFIA: A local page earns its place by being genuinely about that place. The searcher wants their neighborhood, their hours, their location, not a template with the city pasted in.
DANA: A page per location is correct, a template per location isn’t. Fill each one with what’s actually true about that place, and publish only the ones that have something real to say.