agentleFS
Sign inStart free
whyashthakkerwhyashthakker/estack/skills/seo-geo/SKILL.md

seo-geo

Skill0 starsChanged 13 days agoMITView on GitHub

Make a page rank in Google and get cited by AI answer engines (ChatGPT, Perplexity, Gemini, Claude, Google AI Overviews). Audits or writes the page with an answer-first structure, specific numbers with sources, FAQ and article schema, clean meta tags, internal links, and crawl access for AI bots. Use when the user mentions SEO, GEO, AI search visibility, "rank for", "get cited by ChatGPT", schema, JSON-LD, meta tags, or indexing.

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

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

  • 0

    Common

    Most of the 50 edited versions we read keep these.

  • 2

    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:

    Check demand if you have a keyword tool or Search Console.

    line 13
  2. Distinctive:

    Check what ranks now. Your page must be better than the top result on at least one thing: newer, more specific, tested by hand, or simpler.

    line 14

“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

SEO + GEO

Two readers decide if a page wins: a search engine that ranks it, and an AI engine that quotes it. Both reward the same thing: a page that answers a real question clearly, with facts it can prove.

1. Pick the question

  • One page, one main question. Write it the way a person types or asks it ("how much does Claude Code cost", not "Claude Code pricing considerations").
  • Check demand if you have a keyword tool or Search Console. If not, use the search engine's own suggestions and "People also ask".
  • Check what ranks now. Your page must be better than the top result on at least one thing: newer, more specific, tested by hand, or simpler.

2. Structure for quoting

  • Answer first. The first 40 to 60 words under the H1 answer the question directly, with a number if there is one. An AI engine often quotes this block.
  • Headings as questions people ask. Each section starts with its direct answer, then the detail.
  • Specific facts with sources. Numbers, dates, names, each linked to a primary source. Pages with clear stats and citations get quoted more.
  • Tables for comparisons and prices. Lists for steps.
  • Date it. Show "Updated <date>" and keep it true.
  • Show who wrote it and why they know (author bio, hands-on testing).

3. Technical checks

  • Title under about 60 characters with the main term near the start. Meta description under about 155 characters that answers, not teases.
  • One H1. Descriptive URL slug.
  • JSON-LD: Article or BlogPosting (headline, author, datePublished, dateModified, image), FAQPage for a real FAQ section, BreadcrumbList. Validate it. Never mark up content that is not on the page.
  • Canonical URL set. No duplicate pages competing for one question.
  • robots.txt does not block AI crawlers you want (GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended) unless the owner chose to block them. Ask before you change this.
  • Images: modern format (WebP or AVIF), compressed, descriptive alt text, width and height set.
  • An llms.txt file is optional and cheap. Add it only if the site wants one.

4. Links

  • Link out to primary sources.
  • Link in: add the new page to 2 to 5 related pages on the same site, with anchor text that says what the target is. Add links back from those pages too.

5. Report

For an audit: a list of fixes, worst first, each with the exact change. For a new page: the page, the schema, and the list of internal links you added. Do not promise rankings. Say what to measure (impressions, clicks, AI citations) and when to check again (2 to 4 weeks).

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.

Check your setup, free