agentleFS
LukeJMaddenLukeJMadden/Veltrix-skills/skills/content/seo-geo/SKILL.md

seo-geo

Skill1 starsChanged 8 months agoMITView on GitHub

SEO, AEO, and GEO optimisation skill. Use when creating or auditing content for search visibility, answer engine discovery, and generative AI citation.

55 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-agentic, seo-competitor-pages and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AgriciDanielSkill

    seo-agentic

    Audit and fix agent readiness: the Lighthouse Agentic Browsing fraction, accessibility tree for agents, robots.txt and Content-Signal for AI agents, WAF treatment of agent traffic, llms.txt, Markdown delivery, ai-catalog.json, /.well-known discovery files, and WebMCP tools. Use when the user asks whether AI agents can use or browse the site, or about llms.txt or WebMCP. Exclude AI citability and brand signals (seo-geo) and commerce protocol depth (seo-ecommerce).

    Also in 5 projects that use this

  • megastepSkill

    seo-competitor-pages

    Generate SEO-optimized competitor comparison and alternatives pages. Covers "X vs Y" layouts, "alternatives to X" pages, feature matrices, schema markup, and conversion optimization. Use when user says "comparison page", "vs page", "alternatives page", "competitor comparison", or "X vs Y".

    Also in 21 projects that use this

  • megastepSkill

    seo-images

    Image optimization analysis for SEO and performance. Checks alt text, file sizes, formats, responsive images, lazy loading, and CLS prevention. Use when user says "image optimization", "alt text", "image SEO", "image size", or "image audit".

    Also in 20 projects that use this

  • timruebenachSkill

    seo-google

    Google SEO APIs: Search Console (Search Analytics, URL Inspection, Sitemaps), PageSpeed Insights v5, CrUX field data with 25-week history, Indexing API v3, and GA4 organic traffic. Provides real Google field data for Core Web Vitals, indexation status, search performance, and organic traffic trends. Use when user says "search console", "GSC", "PageSpeed", "CrUX", "field data", "indexing API", "GA4 organic", "URL inspection", "google api setup", "real CWV data", "impressions", "clicks", "CTR", "position data", "LCP", "INP", "CLS", "FCP", "TTFB", or "Lighthouse scores".

    Also in 13 projects that use this

  • timruebenachSkill

    seo-image-gen

    AI image generation for SEO assets: OG/social preview images, blog hero images, schema images, product photography, infographics. Powered by Gemini via nanobanana-mcp. Requires banana extension installed. Use when user says \"generate image\", \"OG image\", \"social preview\", \"hero image\", \"blog image\", \"product photo\", \"infographic\", \"seo image\", \"create visual\", \"image-gen\", \"favicon\", \"schema image\", \"pinterest pin\", \"generate visual\", \"banner\", or \"thumbnail\".

    Also in 12 projects that use this

  • +3 more from megastep
  • +4 more from timruebenach

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 50 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use FAQ schema for question-based content

    line 23
  2. Distinctive:

    Write content that AI would want to quote verbatim

    line 32
  3. Distinctive:

    Use authoritative language: "According to X" / "Data from Y shows"

    line 34
  4. Distinctive:

    When auditing existing content:

    line 39

“Common” is measured: kept by at least 6 in 10 of the 50 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Optimise content for three discovery channels: traditional search, AI answer engines, and generative AI citation.

SEO (Search Engine Optimisation)

For every piece of content:

  • Primary keyword in: title, H1, first paragraph, meta description
  • Meta description: max 155 characters, compelling, includes keyword
  • Heading hierarchy: one H1, logical H2/H3 nesting
  • Internal links: 2-3 relevant links to other content
  • Schema markup: Article, FAQ, or HowTo as appropriate
  • URL slug: short, keyword-rich, no stop words

AEO (Answer Engine Optimisation)

Make content discoverable by AI assistants (ChatGPT, Perplexity, Google AI Overviews):

  • Structure content as questions and direct answers
  • First sentence of each section should be a standalone answer
  • Use FAQ schema for question-based content
  • Include specific numbers, dates, and named entities
  • "What is X?" format performs better than "About X"

GEO (Generative Engine Optimisation)

Make content citable by generative AI:

  • Include structured claims with supporting evidence
  • Cover named entities comprehensively (people, companies, products)
  • Write content that AI would want to quote verbatim
  • Include source attribution — cite your sources
  • Use authoritative language: "According to X" / "Data from Y shows"
  • Present unique data or analysis that can't be found elsewhere

Audit Checklist

When auditing existing content:

  1. Does the meta description exist and contain the primary keyword?
  2. Is there only one H1?
  3. Does the first paragraph answer the page's core question?
  4. Are there internal links?
  5. Is there FAQ or structured data schema?
  6. Score: SEO (1-10), AEO (1-10), GEO (1-10)
  7. List specific improvements, not generic advice

Content Type Patterns

TypeSEO focusAEO focusGEO focus
Blog postLong-tail keywords, headersQ&A sectionsUnique analysis, data
Tool pageProduct keywords, comparisonFeature summariesStructured specs
Landing pageBrand + category keywordsValue propositionTrust signals
GuideHow-to keywordsStep-by-step answersComprehensive coverage

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.