geo-tracking
Measure AI visibility without paid tools or API keys. Input: your site (GA4 and server logs) and a buyer prompt panel. Output: GA4 AI-traffic reporting (custom…
Write blog articles that rank on Google and get cited by AI engines (ChatGPT, Perplexity, AI Overviews). Input: a keyword, topic, or existing draft. Output: a publish-ready article, outline, or brief built on a 12-element answer-first skeleton (question H2s, expert quotes,
$ npx -y skills add Thibaultbm/claude-seo-geo --skill seo-content-blog --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/seo-content-blogContext preview
The summary Claude sees to decide when to auto-load this skill.
Write blog articles that rank on Google and get cited by AI engines (ChatGPT, Perplexity, AI Overviews). Input: a keyword, topic, or existing draft. Output: a publish-ready article, outline, or brief built on a 12-element answer-first skeleton (question H2s, expert quotes,
name: seo-content-blog description: "Write blog articles that rank on Google and get cited by AI engines (ChatGPT, Perplexity, AI Overviews). Input: a keyword, topic, or existing draft. Output: a publish-ready article, outline, or brief built on a 12-element answer-first skeleton (question H2s, expert quotes, stats, FAQ, internal links, SERP-benchmarked length). Use when writing, rewriting, refreshing, or auditing a blog post, or when one will not rank or get cited by AI engines." license: MIT metadata: author: "Sorank (https://sorank.com)" version: "1.0.0"
Write or rewrite blog articles on a 12-element skeleton (field methodology from 115+ agency audits, layered with 2024-2026 citation research) so the same article ranks in Google and gets extracted as an answer by ChatGPT, Perplexity, and Google AI Overviews.
If the working environment contains an Obsidian vault or any local knowledge base (a folder of .md notes, often with a .obsidian directory), read the relevant notes before acting: brand and product facts, target keywords, competitors, and the SEO action log of what was already tried. Ground every recommendation in that context instead of asking the user for facts the vault already holds. At the end of the session, append the actions taken to the vault's SEO action log so the next session starts informed. Vault structure, read-first and write-back protocols: the obsidian-brain skill.
Route adjacent jobs to their own skills:
Confirm before writing:
Enforce one angle = one article: two articles on the same intent cannibalize each other and split clicks, links, and signals (merge test in seo-keyword-research).
Fetch the top 3-5 Google results for the keyword and record:
| Per competitor | Why it matters | |---|---| | Word count | Sets the length floor; never come in under the median | | H2 structure and questions answered | The subtopics Google already rewards; this is the coverage checklist | | Tables, images, videos used | The formats the query expects | | Publication and update dates | The freshness bar; an aging SERP is an opening | | People Also Ask questions | Raw material for the FAQ and the question H2s |
For on-page fact collection, run the bundled audit script from the seo-geo-audit skill (scripts/seo_audit.py). Why this step exists: the SERP is the specification. Google is showing what it already considers a satisfying answer for this query; writing blind produces a worse copy of it.
Target the median of the ranking pages or above (thresholds table below). Never plan a rewrite shorter than the page it replaces: replacing long ranking content with shorter content is one of the most common self-inflicted ranking losses observed in audits.
Name at least one element the current top 5 do not have:
Why: Google holds a patent on scoring pages by information gain (US 11,354,342, "Contextual estimation of link information gain"; a patent signals research direction, not confirmed production use); a page that restates the SERP gives the index no reason to rank it and gives AI engines no reason to cite it. This step is also what makes AI-assisted drafting safe (rules below).
Next section. Write the body first; write the title and meta description last, they are sharper once the article exists.
These are the interventions with measured visibility gains in generative engines (see GEO layer).
Anchor rules and site-level architecture: seo-internal-linking.
Run the pre-publish checklist (Output format section), then sweep the Common mistakes list.
Apply every element. Each one exists because its absence showed up as a recurring loss across 115+ agency a
SEO & GEO skills for Claude Code, built with Claude Mythos 5. Rank in Google AND in LLMs like ChatGPT, Perplexity, and Gemini.
Repo: Thibaultbm/claude-seo-geo
Measure AI visibility without paid tools or API keys. Input: your site (GA4 and server logs) and a buyer prompt panel. Output: GA4 AI-traffic reporting (custom…
Get cited and recommended by AI engines (ChatGPT, AI Overviews and AI Mode, Perplexity, Claude, Gemini). Input: a page or piece of content. Output:…
Build a local Obsidian vault that acts as the company and founder second brain, the knowledge layer every other skill reads before acting and writes back to.…
Turn a JavaScript-only site built by an AI website generator into indexable HTML. Input: a site made with Lovable, Base44, Bolt, v0, Replit, Firebase Studio,…
Plan and run off-page SEO to earn links and brand mentions, including for AI visibility. Input: a site, niche, and competitors. Output: a link strategy and…
Optimize e-commerce collection, category, and product listing pages (PLPs) for Google and AI assistants. Input: a collection or category page (Shopify,…