Sign in Start free

Local landing pages that are not doorway pages

A location page earns its place only if it contains something that could not be written about any other town. Swapping a place name into a template produces pages that are technically indexable and practically worthless. This skill defines the minimum unique substance a page needs to survive.

CATEGORY
Local SEO
FORMAT
local-landing-pages.md
STEPS
6
PRICE
Free - no account
WHEN TO REACH FOR THIS

Use when a business serves multiple towns and needs a page per location, without producing the templated near-duplicates that get filtered or manually actioned.

The skill file

local-landing-pages.md 
---
name: local-landing-pages
description: Use when a business serves multiple towns and needs a page per location, without producing the templated near-duplicates that get filtered or manually actioned.
---

# Local landing pages that are not doorway pages

A location page earns its place only if it contains something that could not be written about any other town. Swapping a place name into a template produces pages that are technically indexable and practically worthless. This skill defines the minimum unique substance a page needs to survive.

## What you need first

- The list of towns or areas to target and the search volume for each
- Evidence available per location: jobs completed, staff, stock, delivery times, reviews
- The current template, if one exists

## Method

1. Cut the list first. A town with no served customers, no evidence and negligible volume should not get a page - the strongest local pages are fewer than the sales team wants.
2. For each surviving town, gather location-specific evidence: named projects, local pricing or travel charges, response times, staff based there, reviews from that area.
3. Require a hard threshold before publishing - roughly 60 percent of the page body unique to that location, with the boilerplate confined to trust and conversion blocks.
4. Write the intro and the proof sections from the evidence, not from the template, and link to genuinely local resources or case studies rather than generic service copy.
5. Give each page a distinct internal linking context, so it is reachable from relevant regional hubs rather than only from a footer list of towns.
6. Publish in batches and measure indexation per batch. Pages landing in crawled-not-indexed are telling you the uniqueness threshold was not met.

## What this produces

A reduced set of location pages, each with documented location-specific evidence and a measured share of unique body content.

## Where this goes wrong

- Generating hundreds of towns from a script because the template supports it, which is the definition of a doorway page
- Treating a footer list of every town as internal linking, when it passes almost nothing and signals templating
- Reusing the same embedded map and the same testimonials across every page as the only differentiator

---

From the QuQi skill library - https://www.quqi.io/skills/local-landing-pages
Free to download · no account, no email

What you need first

  • The list of towns or areas to target and the search volume for each
  • Evidence available per location: jobs completed, staff, stock, delivery times, reviews
  • The current template, if one exists

Method

  1. 01 Cut the list first. A town with no served customers, no evidence and negligible volume should not get a page - the strongest local pages are fewer than the sales team wants.
  2. 02 For each surviving town, gather location-specific evidence: named projects, local pricing or travel charges, response times, staff based there, reviews from that area.
  3. 03 Require a hard threshold before publishing - roughly 60 percent of the page body unique to that location, with the boilerplate confined to trust and conversion blocks.
  4. 04 Write the intro and the proof sections from the evidence, not from the template, and link to genuinely local resources or case studies rather than generic service copy.
  5. 05 Give each page a distinct internal linking context, so it is reachable from relevant regional hubs rather than only from a footer list of towns.
  6. 06 Publish in batches and measure indexation per batch. Pages landing in crawled-not-indexed are telling you the uniqueness threshold was not met.

What this produces

A reduced set of location pages, each with documented location-specific evidence and a measured share of unique body content.

Where this goes wrong

  • Generating hundreds of towns from a script because the template supports it, which is the definition of a doorway page
  • Treating a footer list of every town as internal linking, when it passes almost nothing and signals templating
  • Reusing the same embedded map and the same testimonials across every page as the only differentiator

Use this skill in your own AI

The download is a plain markdown file with the name and trigger in its frontmatter. Where an assistant supports skills it can load itself, that frontmatter is what it reads to decide this one applies.

Claude Code Save it as ~/.claude/skills/local-landing-pages/SKILL.md and Claude loads it on its own when what you are doing matches the trigger line. Put it in .claude/skills inside a project instead if the whole team should have it.
Claude Upload the file in the skills section of your settings. Once it is there it applies itself in any conversation where the trigger fits, so you do not have to remember it exists.
ChatGPT There is no skills format to install into, so paste the file contents into a Project instruction or a Custom GPT instead. It then applies to every chat in that project rather than only the one you paste it into.
Anything else Paste the markdown into the chat before your question. It works in any assistant, it just has to be pasted again each time.

Questions about this skill

When is a page per town the right method rather than one strong service page?

Only when you have location-specific evidence to put on each page. A single service page covering the region beats twenty templated town pages that differ by a place name. If the business has completed jobs, staff, delivery times or reviews particular to a town, the page can stand. If all it has is the town name, it cannot.

What do I need in hand before writing?

The town list with volume, and per town the evidence: named projects, staff based there, response or travel charges, reviews from that area. Start without it and you write a template with a variable in it, which is the doorway pattern by definition. Cutting the list comes first, and the surviving set is normally smaller than the sales team asked for.

What do I end up with, and which part of it gets used?

A reduced set of pages, each with documented local evidence and a measured share of unique body content, around 60 percent as a working threshold rather than a published rule. The indexation result per batch is what you act on. Pages landing in crawled but not indexed are telling you the uniqueness bar was missed, before you build another thirty.

What ruins this most often?

Generating every town the script can produce because the template supports it. Cheap to make and expensive to unwind: the whole set can be filtered at once, and a manual action reaches the pages that were fine. The subtler failure is treating a footer list of towns as internal linking, which passes almost nothing and advertises the templating.

More in Local SEO

Google Business Profile optimization

Use when a business is visible on its own site but absent or weak in the map pack, and the profi...

NAP consistency audit

Use when a business has moved, rebranded, changed phone numbers, or has been listed by third par...

Review acquisition and response

Use when review volume is stagnant, ratings are dropping, or reviews arrive in bursts that look...

Multi-location cannibalisation

Use when a business with several branches finds the wrong branch page ranking for a town, or bra...