Skip to content
Back to search

seo-aeo-geo

Audit and improve a website for search (SEO), answer engines (AEO: featured snippets, voice, "People also ask") and generative engines (GEO: Google AI Overviews and AI Mode, ChatGPT Search, Perplexity, Copilot, Claude). Use when the user asks to improve rankings, get cited by AI, fix technical SEO, add structured data, plan content for search, set up Search Console or Bing, or measure AI visibility. Works on any stack; has extra notes for Next.js App Router.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/bhagyashree-vaidya--seo-aeo-geo-skill/badge.svg)](/listings/bhagyashree-vaidya--seo-aeo-geo-skill)

HTML

<a href="/listings/bhagyashree-vaidya--seo-aeo-geo-skill"><img src="/api/listings/bhagyashree-vaidya--seo-aeo-geo-skill/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

git clone https://github.com/Bhagyashree-Vaidya/seo-aeo-geo-skill ~/.claude/skills/seo-aeo-geo

Then ask Claude Code to "audit my site for SEO, AEO and GEO".

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md · Manifest · 50 lines
  1. ---
  2. name: seo-aeo-geo
  3. description: Audit and improve a website for search (SEO), answer engines (AEO: featured snippets, voice, "People also ask") and generative engines (GEO: Google AI Overviews and AI Mode, ChatGPT Search, Perplexity, Copilot, Claude). Use when the user asks to improve rankings, get cited by AI, fix technical SEO, add structured data, plan content for search, set up Search Console or Bing, or measure AI visibility. Works on any stack; has extra notes for Next.js App Router.
  4. ---
  5. # SEO, AEO and GEO
  6. One system, three surfaces. Everything rests on the same base: a crawlable site, clear entities, and genuinely useful, original content. Google's own guide (May 2026) is explicit that no special AI files or markup are required for AI Overviews or AI Mode, so do the fundamentals first and treat GEO tactics as refinements, not shortcuts.
  7. ## How to run it
  8. 1. **Scope.** Ask (or infer) the site, the audience, the 3 to 5 queries that matter most, and which engines matter. Note the user's rules (tone, banned punctuation, what must not be deleted).
  9. 2. **Audit** with `references/checklist.md`. Fetch the live site, read robots.txt, sitemap, page source, and structured data. Record pass / fail / unknown per item with evidence (URL, line, header). Never claim a pass you did not check.
  10. 3. **Prioritize** by impact over effort: crawl and index blockers first, then entity and structured data, then content gaps, then off-site authority, then measurement.
  11. 4. **Fix** in small, verifiable commits. After each deploy, re-fetch the live URL and confirm the change (status code, rendered HTML, JSON-LD validates).
  12. 5. **Measure** with `references/measurement.md`: Search Console, Bing Webmaster Tools, AI-referral analytics, and a fixed prompt set run across engines on a schedule.
  13. 6. **Report** what changed, what was verified live, what was not, and what needs the owner (accounts, sign-ins, outreach).
  14. ## Principles
  15. - **People first.** Write for the reader; engines reward pages that fully answer a real question with first-hand detail. Commodity content that restates others gets neither rankings nor citations.
  16. - **Answer first.** Lead each page and section with a direct 1 to 3 sentence answer, then the evidence. Use question-shaped H2s where natural.
  17. - **Be quotable.** Specific numbers with their source, dates, named methods, short definitions, comparison tables. Engines lift self-contained passages.
  18. - **One entity, everywhere.** Same name, title, photo, and description across the site, LinkedIn, GitHub, author pages and directories, all linked with `sameAs`.
  19. - **Prove it.** Author bylines, credentials, first-hand experience, citations to primary sources, updated dates. This is what E-E-A-T means in practice.
  20. - **Be found elsewhere.** AI answers draw heavily on third-party pages (reviews, forums, press, podcasts, guest posts). Owned content alone is rarely enough.
  21. - **Fresh and honest.** Keep `dateModified` real; update pages when facts change; never fake freshness.
  22. - **Measure per engine.** Citation sources barely overlap across ChatGPT, Perplexity, Google AI features and Copilot; check each.
  23. ## Myths to skip (or deprioritize)
  24. - `llms.txt` as a ranking or citation lever: major AI crawlers rarely fetch it (Ahrefs, 2026: 97% of files got no requests). Fine to ship as a cheap convenience; never prioritize it over real fixes.
  25. - "AI-only" schema or hidden markdown copies of pages: Google says not needed.
  26. - Keyword stuffing, mass AI-written pages, doorway pages, fake reviews, invented stats: these get filtered or penalized.
  27. ## References
  28. - `references/checklist.md`: full audit checklist (technical, on-page, structured data, AEO, GEO, off-site, local, media).
  29. - `references/ai-crawlers.md`: robots.txt for search vs training bots, with a safe default.
  30. - `references/structured-data.md`: JSON-LD templates (Person, Organization, WebSite, Article, FAQ, BreadcrumbList, ProfilePage) and rules.
  31. - `references/measurement.md`: KPIs, Search Console and Bing setup, AI-visibility prompt testing, cadence.
  32. - `references/nextjs.md`: App Router specifics (Metadata API, sitemap.ts, robots.ts, OG images, rendering, redirects).
  33. - `references/vercel.md`: 307 vs 308 domain redirects, firewall bot checks, IndexNow cron with CRON_SECRET.
  34. ## Lessons from real audits
  35. - Verify before claiming a gap: grep the codebase and fetch the live page. Features often exist in the UI but not in the data (or the reverse).
  36. - Image-only content (decks, carousels) is invisible to search and AI; ship a text page per item and link both ways.
  37. - Hosting defaults are often temporary redirects; check the status code, not just that a redirect exists.
  38. - Dashboard-only settings (domains, env vars) need the owner signed in; connectors may be read-only. Confirm a saved setting by reloading the page, not by trusting the form.
README.md · README · 22 lines
  1. # SEO, AEO and GEO skill for Claude Code
  2. A Claude Code skill for auditing and improving a site for search engines (SEO), answer engines (AEO) and generative AI engines (GEO: Google AI Overviews and AI Mode, ChatGPT Search, Perplexity, Copilot, Claude).
  3. ## Install
  4. ```bash
  5. git clone https://github.com/Bhagyashree-Vaidya/seo-aeo-geo-skill ~/.claude/skills/seo-aeo-geo
  6. ```
  7. Then ask Claude Code to "audit my site for SEO, AEO and GEO".
  8. ## Contents
  9. - `SKILL.md`: workflow, principles, myths to skip
  10. - `references/checklist.md`: full audit checklist
  11. - `references/ai-crawlers.md`: robots.txt for AI search vs training bots
  12. - `references/structured-data.md`: JSON-LD templates
  13. - `references/measurement.md`: KPIs and a monthly AI-visibility test
  14. - `references/nextjs.md`: Next.js App Router notes
  15. MIT licensed.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.