agentleFS
Sign inStart free
yeer0syeer0s/ultimate-seo-collection/skills/seo-strategy/SKILL.md

seo-strategy

Skill1 starsChanged 30 days agoMITView on GitHub

Builds SEO strategy and new angles: playbooks by site stage and type (new domain, comparison site, local, publisher, SaaS, YMYL, multi-locale), a register of out-of-the-box ideas each with mechanism, evidence label, per-engine policy check and test recipe, and a catalogue of official docs, tools and datasets. Use for "SEO roadmap", "where do we start", "creative SEO ideas", "best SEO tools". Not for auditing a page (seo-optimizer).

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-content-brief, seo-programmatic and 3 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.
  • 01claudingSkill

    seo-content-brief

    Generate comprehensive, SERP-driven content briefs for writers. Analyzes top-ranking competitors, identifies content gaps, specifies structure, word count, keywords, E-E-A-T requirements, AI citation readiness, and schema recommendations. Use when user says "content brief", "writing brief", "content outline", "article brief", or "create brief for".

    Also in 4 projects that use this

  • megastepSkill

    seo-programmatic

    Programmatic SEO planning and analysis for pages generated at scale from data sources. Covers template engines, URL patterns, internal linking automation, thin content safeguards, and index bloat prevention. Use when user says "programmatic SEO", "pages at scale", "dynamic pages", "template pages", "generated pages", or "data-driven SEO".

    Also in 3 projects that use this

  • megastepSkill

    seo-schema

    Detect, validate, and generate Schema.org structured data. JSON-LD format preferred. Use when user says "schema", "structured data", "rich results", "JSON-LD", or "markup".

    Also in 3 projects that use this

  • indranilbanerjeeSkill

    keyword-research

    Research keywords via the connected data source: intent, gaps. Grouping → keyword-cluster. \"what keywords should we target\"

    Also in 3 projects that use this

  • AnthropicSkill

    seo-audit

    Run a comprehensive SEO audit — keyword research, on-page analysis, content gaps, technical checks, and competitor comparison. Use when assessing a site's SEO health, when finding keyword opportunities and content gaps competitors own, or when you need a prioritized action plan split into quick wins and strategic investments.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never forecast a published number onto a client site.

    line 14
  2. Very specific:

    No rollout without a pre-declared revert rule (applicability, holdout, what stays fixed, metric + window, trigger).

    line 15
  3. Distinctive:

    Every playbook step carries an evidence label and passes the policy gate before it is planned.

    line 43
  4. Distinctive:

    No traffic forecast from published numbers.

    line 46

“Common” is measured: kept by at least 6 in 10 of the 10 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-strategy

Where to start, in what order, which engines matter per market, and which new ideas are worth a test.

<!-- grammar-excerpt -->

Label every tactic with one of the 9 marks: [documented: <URL>, <date>] · [documented-secondary: …] · [unverified: …] · [measured: MARK, n=S, c=C] · [practitioner: anonymised sources · …] · [hypothesis] · [vendor] · [memory] · [unvalidated house heuristic]. Numbers keep their denominator; marks are counts, not verdicts; bundles support direction, not size. Never forecast a published number onto a client site; only the client's own GSC demand and funnel forecast. No rollout without a pre-declared revert rule (applicability, holdout, what stays fixed, metric + window, trigger). Repetition never proves; full grammar: skill seo-optimizer § Evidence marks.

<!-- /grammar-excerpt -->

Load rule

Open one reference per load-when row the question touches (a "by H2" row: only the part holding that H2); never a file "to be thorough". A pointer into another seo- skill's file is a citation: quote it, or first load that skill's SKILL.md and open the file through its own load-when row. Engine pages, ledger and practitioner parts and the crawler registry are lookup-only.

Load when

IDQuestion shapeOpen
ST1roadmap, strategy, "where do we start", which engines per marketstrategy-playbooks.md
ST2out-of-the-box ideasideas-register.md
ST3tools, docs, datasetsby H2: part 1 (official engine documents) or part 2 (tools by job, datasets, communities)
ST5which tactic for which jobtactics-by-job.md

Not mine

QuestionSkill
auditing a page or routeseo-optimizer
what an engine forbidsseo-engine-policies
does a tactic workseo-evidence
implementing a stepthe owning skill named in the playbook step

Rules

  1. Every playbook step carries an evidence label and passes the policy gate before it is planned.
  2. An idea row is a hypothesis with a test recipe and a kill condition, never a promise.
  3. Banned tactics appear only under "Tempting, and banned", with the policy cite and its condition; a refusal stricter than the policy is marked as a house rule.
  4. No traffic forecast from published numbers; only from the client's own demand data.
  5. Market share and engine reach are stated only with a dated source.

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