location-pages
Skill0 starsChanged 49 days agoMITView on GitHub
Plan and write location pages and city or service-area landing pages that rank without being doorway pages. Use when the user wants pages for each city, town, neighborhood or service area ("plumber in Springfield", "near me" pages), pages for each branch or location of a multi-location business, or asks whether city pages are spam, how many to make, or how to make them unique. Applies Google's spam policies on doorways, scaled content and keyword stuffing.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- google-business-profileSkill
- local-business-schemaSkill
- local-seo-auditSkill
- local-site-migrationSkill
- review-managementSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
1. Physical location pages (a branch, office or store): Always create one per real location.
- Distinctive: line 45
If a town's page would only swap the city name into the same text, don't create it.
- Distinctive: line 49
Start with physical locations, then the handful of towns where the business does the most work and has real material.
- Distinctive: line 64
Don't create orphan pages reachable only from the sitemap.
- Distinctive: line 80
Remove footer or sidebar blocks listing dozens of towns.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Location Pages and Service-Area Pages
Pages for places are legitimate, and often necessary. They are also the most common way local businesses break Google's spam policies. The difference is whether each page is genuinely useful to someone in that place.
The rules that apply
From Google's spam policies (https://developers.google.com/search/docs/essentials/spam-policies):
- Doorway abuse: "Doorway abuse is when sites or pages are created to rank for specific, similar search queries." Among Google's examples:
- "Having multiple domain names or pages targeted at specific regions or cities that funnel users to one page"
- "Creating substantially similar pages that are closer to search results than a clearly defined, browseable hierarchy"
- Scaled content abuse: "Scaled content abuse is when many pages are generated for the primary purpose of manipulating search rankings and not helping users." It applies no matter how the pages are made, including with AI or templates.
- Keyword stuffing includes "Blocks of text that list cities and regions that a web page is trying to rank for."
- Consequence: sites that violate these policies "may rank lower in results or not appear in results at all."
Google publishes no uniqueness percentage or word count that makes a page safe. The helpful content guidance says Google does not target a word count. The test is usefulness: https://developers.google.com/search/docs/fundamentals/creating-helpful-content
Two kinds of page
1. Physical location pages (a branch, office or store). Always create one per real location. Each needs:
- The location's own name, address and phone, matching its Google Business Profile.
- Its own
LocalBusinessJSON-LD withurlset to this page (local-business-schema skill). - Hours, including holiday hours; an embedded map or directions; and parking or entrance notes.
- What is specific to this location: its staff, services or menu differences, photos of this building, and reviews or testimonials about this location (shown, not marked up as the business's own ratings).
- A link from a "Locations" hub page, so the pages form a clear, browseable hierarchy.
2. Service-area pages (towns you serve but have no office in). Create them only where you have something true and specific to say about that place:
- Jobs actually done there, e.g. a project gallery with the town named. Get the client's permission, and show no private addresses.
- Local specifics that change the service: housing stock, water hardness, permits and inspections, climate, HOA rules, travel time and fees.
- Testimonials from customers in that town.
- Staff or crews based near there.
- Anything that differs by area: pricing, availability, response times.
If a town's page would only swap the city name into the same text, don't create it. Mention the town in a service-area list on one strong page instead: a short, readable list, not a keyword block.
How many pages?
Start with physical locations, then the handful of towns where the business does the most work and has real material. Add more only when new material exists. Ten useful pages beat two hundred templated ones, and the templated ones put the whole site at risk.
Page structure
H1: {Service} in {City}, {State}. Only as specific as the page really is.
Intro: who you help in {City}, in one or two sentences written for people, not keywords.
Local proof: projects, photos, testimonials from {City}.
What's different in {City}: permits, conditions, pricing, travel.
Services offered here, each linking to its full service page.
Contact: phone, hours, how to book. For a physical location, add the address and a map.
FAQ drawn from real questions customers there ask.- Link each page from the Locations hub or service-area list, and back to the core service pages.
- Don't create orphan pages reachable only from the sitemap.
Checklist before publishing
- Would a person in this town find something here that is not on the other location pages?
- Is every claim true: projects, staff, response times, prices?
- For a physical location, do the name, address and phone match the Business Profile and the schema exactly?
- Is the page reachable through normal site navigation?
- Are there no city lists stuffed into paragraphs or footers?
- If AI helped draft it, has a person added the local facts and checked every sentence?
Auditing existing city pages
- List every city or area page. Compare their main content side by side.
- Merge or remove pages that are near-duplicates. 301-redirect each removed URL to the most relevant remaining page, such as the service page or the nearest location. Don't send them all to the home page (local-site-migration skill).
- Rewrite the pages worth keeping with real local material.
- Remove footer or sidebar blocks listing dozens of towns.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

