geo-implementlisted

# geo-implement Implement GEO (AI-search visibility) artifacts on a static site: generate every artifact below, adapted to the user's framework, then verify with `findable-audit`. For purely technical-SEO findings (canonical, `noindex`, redirect hygiene, broken internal links, duplicate titles, hreflang), use the `fix-technical-seo` skill instead. ## 0. Shortcut: generate starters from a live audit ```bash npx findable-audit <url> --emit ./out ``` writes generic starter versions of `robots.txt`, `llms.txt`, `llms-full.txt`, `.well-known/ai.json`, `sitemap.xml` and `jsonld-stubs.json` (plus a `GENERATED-README.md` explaining each file) based on what the audit saw. Use them as a starting point, then adapt per framework with the sections below — **review everything before deploying, especially `robots.txt`**, and replace placeholder/stub values with real business data. ## 1. Gather inputs Ask (or infer from the repo) before generating anything: - **Site URL** — canonical production origin, e.g. `https://example.com` - **Language** — primary content language (`en`, `fr`, …) - **Business type** — one of: **local business**, **organization**, **blog/personal** - **Framework** — Astro, Next.js, Hugo, or plain static For a local business, also collect NAP (name, address, phone), geo coordinates, and opening hours — from the user, never invented. ## 2. `robots.txt` Place in the static/public root (`public/` for Astro & Next, `static/` for Hugo). Explicitly allow the AI crawl