location-page-seo
Skill0 starsChanged 36 days agoMITView on GitHub
Audit or draft local service and branch landing pages, fix evidence-backed on-page SEO gaps, and prepare accurate LocalBusiness JSON-LD. Respect service-area privacy and avoid fabricated locations, testimonials or doorway pages.
In this repository8 other files it gives its agents.
- citation-auditSkill
- gbp-auditSkill
- local-competitor-analysisSkill
- local-keyword-researchSkill
- local-seo-reportSkill
- maps-rank-trackingSkill
- review-insightsSkill
- vibelocalSkill
The file
Files
Authentic location-page SEO
Read WORKFLOW.md and ACTORS.md. Reuse public branch/service-area facts and the keyword/page map. Start with the supplied page or local source files. A website plan can crawl a public HTTPS branch page with a small bound, normally 10 pages, while respecting robots.txt. Do not crawl private/authenticated pages or customer portals.
Check observed status, title, description, headings, canonical, visible contact/service details, internal links, accessibility of useful content and JSON-LD types. Distinguish raw response HTML from rendered content. Missing JSON-LD in a direct fetch needs rendered inspection before concluding it is absent. Crawl flags are leads for review; response time is not Core Web Vitals and crawl directives are not proof of Google's index status.
Draft the page around real services and a real branch or public service area: clear title/H1, useful service information, accurate hours/contact/booking route, verified access details, approved FAQs and a clear next action. Use distinct owner-provided local evidence. No invented office, landmarks, testimonials, awards, qualifications, prices or boilerplate pages with city swaps. A service-area page can describe service areas without publishing a hidden address.
Use schema --context CONTEXT.json --out DRAFT_SCHEMA.json for a restrained LocalBusiness draft. Storefront/hybrid schema requires a verified public address; service-area schema omits private addresses and explains that it lacks Google's required rich-result address. No self-serving aggregate review stars or fabricated ratings. Choose a more specific schema type only after checking it against the actual business and current requirements.
Validate draft markup against visible page facts and Google LocalBusiness structured-data guidance. Valid markup does not guarantee a rich result or ranking uplift. Deliver the reviewed issue table, concrete page/schema drafts and a verification plan. Local implementation may be authorized by the user's request; public publishing requires approval of the resulting change.
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.

