--- title: "claude-code-seo-skill by factive1 · skilld" canonical_url: "https://skilld.dev/gh/factive1/claude-code-seo-skill" meta: description: "Write or edit a piece of content that ranks in Google, gets cited by ChatGPT, Perplexity, and AI Overviews, and reads like a person wrote it. Use when the user… From factive1/claude-code-seo-skill." "og:description": "Write or edit a piece of content that ranks in Google, gets cited by ChatGPT, Perplexity, and AI Overviews, and reads like a person wrote it. Use when the user… From factive1/claude-code-seo-skill." "og:title": "claude-code-seo-skill by factive1" "twitter:description": "Write or edit a piece of content that ranks in Google, gets cited by ChatGPT, Perplexity, and AI Overviews, and reads like a person wrote it. Use when the user… From factive1/claude-code-seo-skill." "twitter:title": "claude-code-seo-skill by factive1" --- ` [All skills](https://skilld.dev/skills) [![factive1 avatar](https://skilld.dev/_img/avatar?url=https%3A%2F%2Fgithub.com%2Ffactive1.png%3Fsize%3D96)](https://skilld.dev/gh/factive1) # **/claude-code-seo-skill** [@043cd04](https://github.com/factive1/claude-code-seo-skill/commit/043cd04dc29b3490497f021ffeb88e44e2bae036 "Your agent reads SKILL.md at commit 043cd04") by [Cameron Olthuis](https://skilld.dev/gh/factive1)· [factive1](https://skilld.dev/gh/factive1)/ [claude-code-seo-skill](https://skilld.dev/gh/factive1/claude-code-seo-skill)·10 stars 1 Write or edit a piece of content that ranks in Google, gets cited by ChatGPT, Perplexity, and AI Overviews, and reads like a person wrote it. Use when the user asks for a blog post, article, guide, comparison, listicle, landing page, or FAQ meant to rank in search or get cited by AI, or asks to humanize, de-slop, review, or refresh a specific draft or page. For auditing many pieces at once — a library, resource section, blog, or docs set — use content-library-audit instead. - 1 file - 3.2 KB - MIT - Updated 3 weeks ago - [GitHub](https://github.com/factive1/claude-code-seo-skill/blob/043cd04dc29b3490497f021ffeb88e44e2bae036/SKILL.md "View SKILL.md on GitHub") ## SKILL.md 3.2 KB **≈126** tokens always: the name and description. **≈670** when used: this file. ## SEO + GEO content Read `seo-geo-content-guide.md` in this directory in full before writing or editing anything. It is the source of truth. This file only says how to apply it. ### Before drafting 1. Ask for or find the author's voice samples. A sample overrides every pattern rule in the guide, including the dash rule. 2. Know the job: who the piece is for, where it will be published, and what the reader should do after reading it. Ask if the brief doesn't say. 3. Run the research in the guide's SEO and GEO sections. Collect every statistic, quote, and source you plan to use, with its URL, before you write a sentence. ### While drafting Follow the four rules at the top of the guide. Never invent a fact. Match the voice samples. Every sentence adds something. Every sentence passes the portability test. Put the keyword in the title, the H1, and one or two H2s. Open with what the reader doesn't already know from the query. Lead sections with a quotable statement. Use only sourced numbers, names, dates, and quotes, and leave `[SOURCE NEEDED: ...]` where you don't have one. ### After drafting Run the guide's rewrite pass before the checklist: mark every tell strongest first, rewrite around the point, search for the five survivors (not-X-but-Y, one-line closer, dash, triad, bold label), check the ending, verify no fact was added, dropped, or smoothed into a generic claim, then read it aloud. Then run the final gate in the implementation checklist. If any item fails, fix it and run the checks again. ### Editing or auditing existing content When the user asks whether a draft sounds like AI, name each pattern from the guide that appears, quote the line, and give the fix in a few words. Do not score the draft or guess whether AI wrote it. When the user asks for an edit, make the minimum effective edit: fix the tells, keep strong human sentences as they are, and list what changed. The writer should recognize the result as their own. ### When it's a whole library, not a piece This skill works on one piece at a time, and the standard holds when a person is applying it to one piece. Across a corpus it fails in ways a single-piece review can't see: writers certify their own work as clean, repetition is invisible from inside one file, and fabrication recurs during the rounds meant to fix it. If the user points at a directory, a resource section, a blog, or more than a handful of pieces, use `content-library-audit`. It runs this guide as its standard and adds the verification the scale requires. ### What to return The full draft, every `[SOURCE NEEDED]` marker listed at the end, and a short note on what voice samples or sources were used. Source: [SKILL.md on GitHub](https://github.com/factive1/claude-code-seo-skill/blob/043cd04dc29b3490497f021ffeb88e44e2bae036/SKILL.md) ## Third-party checks No third-party reports yet. ## Provenance [Signed by skilld at 043cd04.](https://github.com/factive1/claude-code-seo-skill/commit/043cd04dc29b3490497f021ffeb88e44e2bae036 "043cd04dc29b3490497f021ffeb88e44e2bae036") This ties the file your Agent reads to that commit on GitHub. It does not review the instructions. Last checked against GitHub 3 weeks ago. Activeupdated 3 weeks ago ## Capability
metadata
``` { "version": "2.1.0" } ```
## README badge ![README badge for factive1/claude-code-seo-skill](https://skilld.dev/b/factive1/claude-code-seo-skill?theme=light&label=0) ## Related skills - - - - - -