← ClaudeAtlas

geolisted

Audit and improve visibility in generative engines (AI answers, LLM-powered search): GEO, complementary to classic SEO. Use when the user asks about GEO, AI search visibility, llms.txt, or being cited by AI assistants.
sbnet/flux · ★ 0 · AI & Automation · score 70
Install: claude install-skill sbnet/flux
# Skill: GEO (Generative Engine Optimization) ## Purpose Classic SEO optimizes for ranking in result lists; GEO optimizes for being **retrieved, quoted and cited** by generative engines that compose answers. This skill audits a site and applies the fixes. It complements a classic SEO pass and never replaces it (meta, sitemap and Core Web Vitals stay SEO territory; if a dedicated seo skill is available, use it for those). ## Audit 1. **Renderability.** Fetch key public pages with `curl` (no JS). What does a crawler actually see? SPA/Inertia pages render an empty shell, and generative crawlers mostly do not execute JS. If the content that should be cited is invisible without JS, that is finding #1 and nothing else matters until it is fixed (SSR, prerendering, or dedicated server-rendered pages for public content). 2. **Machine surface.** Check for `/llms.txt` (curated map of the site's content for LLM crawlers), `robots.txt` rules for AI crawlers (GPTBot, ClaudeBot, PerplexityBot…: blocked intentionally or by accident?), and schema.org structured data (JSON-LD: Organization, Product, FAQPage, Article, BreadcrumbList as relevant). 3. **Citability of the content itself.** Generative engines quote passages, not pages. Look for: self-contained paragraphs that answer one question (quotable without surrounding context); headings phrased as the questions users actually ask; concrete facts with units, dates and sources rather than marketing pr