Local seo

Skill avelikiy/great_cto/skills/local-seo

Local-business SEO and structured-data framework for content-platform Product-Builder products that need to be found (storefronts, restaurant online-ordering, real-estate listings, service-business sites). Codifies schema.org structured data (LocalBusiness/Product/Menu/RealEstateListing), Core Web Vitals as a ranking input, local on-page signals (NAP consistency, Google Business Profile alignment), sitemap/robots/canonical hygiene, and listing syndication. Applied by senior-dev when building public pages and checked by cms-reviewer. cms-reviewer reviews SEO; this skill is how you BUILD it right the first time.From its SKILL.md

Install

npx -y skills add avelikiy/great_cto --skill local-seo

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

4.5 KB, 852 tokens by cl100k_base, as published. Nobody here has run it

Local SEO — built to be found, not just reviewed

For a storefront, a restaurant, or a listing site, being discoverable IS the product. SEO designed in is cheap; SEO retrofitted is a rebuild. Build these signals from the first page.

1. Structured data (schema.org) — the biggest local lever

Emit JSON-LD matching the entity, validated against Google's Rich Results requirements:

LocalBusiness (+ the specific subtype: Restaurant, HomeAndConstructionBusiness, RealEstateAgent) — name, address (PostalAddress), geo, telephone, openingHours, priceRange, url, sameAs (social). This is the single highest-impact local SEO signal.
Product + Offer (storefront) — name, image, price, availability, aggregateRating.
Menu / MenuItem (restaurant online-ordering).
RealEstateListing / Residence (listings) — price, address, floorSize, numberOfRooms.
BreadcrumbList on every deep page; FAQPage where there's Q&A.

Validate every type with the Rich Results test before shipping; invalid JSON-LD earns nothing.

2. NAP consistency + Google Business Profile alignment

Name / Address / Phone must be byte-identical across the site, the LocalBusiness JSON-LD, and the Google Business Profile. Inconsistent NAP fractures local ranking. State the canonical NAP once and reuse it.

3. Core Web Vitals are a ranking input (not just perf)

LCP / INP / CLS feed search ranking for these pages. Coordinate with performance-engineer, but the SEO-driven minimums: optimized responsive images (AVIF/WebP + srcset — see media-pipeline-engineer), no layout shift on load (sized media), fast TTFB. A slow local page loses to a fast competitor regardless of content.

4. Crawl + index hygiene

sitemap.xml auto-generated from the catalog/listings, with lastmod; submitted.
robots.txt allows indexable pages, blocks app/admin/checkout-internal.
Canonical on every page (self or the preferred variant) — kills duplicate-content loss from filters/pagination/UTM.
noindex authenticated + thin/internal pages explicitly.
Clean, stable, keyword-relevant URLs (/menu/margherita, not /p?id=8842).

5. On-page + content signals

One <h1> per page; descriptive <title> + meta description per page (templated from the entity, not duplicated site-wide).
Descriptive alt text on every image (a11y AND image search).
Internal linking between related entities (product↔category, listing↔neighborhood).
Location pages for multi-location businesses (one indexable page per location, unique content).

6. Syndication (where the product distributes)

For listings/storefronts that syndicate (MLS/IDX, Google Shopping, marketplaces), the canonical lives on our page; syndicated copies point back. Define the feed format + update cadence (coordinate the source-of-truth with integrations-engineer).

Output

When applied, contribute an SEO section to the architecture/design doc and a checklist the senior-dev build satisfies:

## SEO
- schema.org types: <LocalBusiness subtype + Product/Menu/Listing> · JSON-LD validated
- canonical NAP: <name/address/phone> (identical in JSON-LD + GBP)
- CWV minimums: LCP/INP/CLS targets (with performance-engineer)
- crawl: sitemap.xml (lastmod) · robots.txt · canonical on all · noindex app/admin
- on-page: 1×h1, per-page title/meta, alt text, clean URLs
- syndication (if any): canonical = our page; feed = <format/cadence>

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 1 of the 12 instructions most marketing audience skills give in 852 tokens

Counted across 690 of the 894 authors here whose files we hold, read 2026-08-07

Apply Poppins font to headingsin 41 of 690, across 6 files
Apply Lora font to body textin 41 of 690, across 6 files
Use Arial fallback for headingsin 39 of 690, across 4 files
Use Georgia fallback for body textin 39 of 690, across 4 files
Maintain text hierarchy and formattingin 39 of 690, across 4 files
Use accent colors for non-text shapesin 38 of 690, across 3 files
Use RGB values for precise color matchingin 38 of 690, across 3 files
Use brand colors for primary text and backgroundsin 36 of 690, across 1 file
Read product marketing context file before asking questions, starting, or auditingin 35 of 690, across 23 files
Use active voice instead of passive voicein 26 of 690, across 10 files
Implement or generate appropriate JSON-LD structured datahere, and in 24 of 690, across 17 files
Prioritize clarity over clevernessin 22 of 690, across 8 files

Said here and by no other author read

keep nap identical across site and profiles
enforce core web vitals targets
use stable keyword-relevant urls
keep canonical content on our page

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.