Location pages are one of the easiest SEO deliverables to get flagged as doorway pages: same template, city name swapped, nothing else different. This prompt is built to refuse fabricating local color it wasn’t given, and will recommend consolidating thin cities into a shared page rather than force six near-identical ones to exist.
SEO
Write localized SEO content for city/location pages
A prompt for drafting genuinely differentiated location page copy at scale, built to avoid the template-swap pattern Google treats as doorway pages.
Works with Claude / GPT2,000 uses★ 4.6
The prompt
seo-localized-city-location-pages
A plumbing franchise needs location pages for the 6 cities it services: [Austin, Round Rock, Cedar Park, Georgetown, Pflugerville, Leander, all in Texas]. The previous freelancer delivered pages that are identical except for the city name swapped in, which the client's SEO consultant flagged as a doorway-page risk before publishing. SERVICE: [emergency plumbing repair] CITIES: [Austin, Round Rock, Cedar Park, Georgetown, Pflugerville, Leander] CITY-SPECIFIC DETAILS (paste anything real: local landmarks, service area boundaries, average response times, city-specific plumbing issues like hard water or older housing stock): [paste here] Write these the way someone avoiding a doorway-page problem would, not a mail-merge: 1. For each city, identify at least one genuinely differentiating detail from the notes provided (e.g. Georgetown's older homes have more galvanized pipe issues, Cedar Park's newer developments see more slab leak calls from foundation settling) and build a real paragraph around it, not just swap the city name into an identical template. 2. If the provided city-specific details run out before covering all 6 cities meaningfully, say so explicitly rather than inventing plausible-sounding local details, since fabricated local specificity is worse than admitting the input didn't support it and asking for more detail on the remaining cities. 3. Write unique title tags and meta descriptions per city that reflect the differentiating detail, not just "[City] Emergency Plumber | Company Name" six times over. 4. Recommend which cities can share a single page with a service-area section instead of a full standalone page, if two cities are close enough and lack distinct local detail to justify separate pages, since forcing thin pages to exist just for keyword coverage is itself part of the doorway-page risk. 5. Note any schema (LocalBusiness with a serviceArea, or separate LocalBusiness entities) each page should carry, based on whether it's a shared physical location or a service-area-only business.