agentleFS
Infinite-Labs-AIInfinite-Labs-AI/infinite-skills/skills/seo-strategy/SKILL.md

seo-strategy

Skill43 starsChanged 4 months agoMITView on GitHub

Use when planning SEO pages, content clusters, site architecture, comparison pages, programmatic pages, or search-driven acquisition.

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 5 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

  • webrenewSkill

    seo-technical

    Audit and improve technical SEO in Next.js apps. Use this skill for metadata, structured data, Open Graph, sitemaps, robots rules, canonical URLs, hreflang, redirects, search visibility, and crawlability.

    Also in 3 projects that use this

  • garri333Skill

    seo-content

    Guía completa de SEO y estructura editorial para contenido web. Usa cuando crees blog posts, landing pages o cualquier contenido web que necesite posicionamiento en buscadores.

    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

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use any supplied keywords, URLs, Search Console exports, competitor pages, product docs, or customer language.

    line 12
  2. Distinctive:

    Do not make a separate page for every keyword variation.

    line 26
  3. Distinctive:

    Avoid pages where the company has no evidence, no product fit, or no realistic way to be useful.

    line 53

“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

Plan SEO pages around real search intent, useful proof, and a clear conversion path.

Intake

Use any supplied keywords, URLs, Search Console exports, competitor pages, product docs, or customer language. If no data exists, ask for the market, target customer, competitors, and 5-10 seed queries.

Classify Intent

Group queries by the job behind them:

  • Learn the problem.
  • Compare options.
  • Choose a vendor.
  • Implement a workflow.
  • Troubleshoot a failure.
  • Calculate or estimate.
  • Find a template, example, or tool.

Do not make a separate page for every keyword variation. Create pages for distinct intent.

Make Page Decisions

For each page opportunity, define:

  • Primary query job.
  • Reader stage.
  • SERP evidence: what current results reward.
  • Decision: create, update, merge, redirect, or no-build.
  • Best page type: guide, comparison, alternative, template, calculator, glossary, integration, use case, benchmark, migration, troubleshooting.
  • Required proof: screenshots, data, examples, expert byline, customer story, product demo.
  • Cannibalization risk.
  • Internal links needed.
  • Conversion path.

Prioritize

Rank opportunities by:

  • Business fit.
  • Pain intensity.
  • Ranking realism.
  • Proof availability.
  • Conversion proximity.
  • Ability to produce something meaningfully better than existing results.

Avoid pages where the company has no evidence, no product fit, or no realistic way to be useful.

Output

Query decisions:
| Cluster | Query job | SERP evidence | Decision | Page type | Proof needed | CTA | Priority |

First 5 pages to create:
1. [page] - [why now]

Page brief:
URL:
Reader job:
Promise:
Sections:
Proof:
Cannibalization risk:
Internal links:
CTA:

Do not build:
- [query/page] - [reason]

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.