agentleFS
oegeyilmaz9oegeyilmaz9/seo-aeo-geo-ultimate/skills/seo-plan/SKILL.md

seo-plan

Skill6 starsChanged 3 months agoApache-2.0View on GitHub

Use when sequencing validated SEO findings and approved action-plan items into an owner-based roadmap with dependencies, review gates, measurable outcomes, and risk controls; do not use it to invent work, fixed uplift forecasts, or a one-size-fits-all calendar.

33 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-google, seo-flow 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.
  • 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 10 projects that use this

  • timruebenachSkill

    seo-flow

    FLOW framework integration — evidence-led SEO using the Find → Leverage → Optimize → Win loop. Surfaces stage-specific AI prompts from the FLOW knowledge base (41 prompts, CC BY 4.0). Use when user says "FLOW", "FLOW framework", "seo flow", "evidence-led SEO", "find leverage optimize win", or wants stage-specific SEO prompts.

    Also in 8 projects that use this

  • +3 more from timruebenach

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 25 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read markdown-delivery-contract.md for every task.

    line 10
  2. Very specific:

    Read references/roadmap-protocol.md before planning a cross-team program.

    line 19

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

Markdown delivery contract

Read markdown-delivery-contract.md for every task. Write a substantive .md document for every material work step and register its direct destination in the work index.md. For public-site work, apply the owner-required Markdown discovery profile across the full eligible inventory; preserve native standards and immutable evidence formats.

Lane outputs: roadmap.md; dependencies.md (combine small related steps with stable section links). Sequence query decisions, source content, inventory/maps, routing, parity review, local acceptance, authorized release and full delivery checks. Preserve both keyword ambition tracks, maintenance owners and direct document links.

Purpose

Turn validated evidence and approved actions into a delivery roadmap that a team can execute and review. This skill coordinates scope, sequencing, and measurement; it does not create technical/content facts, approve releases, or promise business outcomes.

Read references/roadmap-protocol.md before planning a cross-team program.

Input gate

Require current business goal, audience/market, constraints, owners/capacity, validated audit/research artifacts, approved action-plan items, baseline/report availability, and known dependencies. When inputs are incomplete, produce a discovery plan with explicit assumptions—not a fabricated quarter-long backlog.

Workflow

  1. Frame decisions. State the goal, target audience/market, change scope, non-goals, risk tolerance, and measures that are actually available.
  2. Use validated work only. Include confirmed issues and approved actions. Keep experimental work in a separate learning track. Declined/risky changes remain visible with their conditions.
  3. Sequence dependencies. Establish source data, site prerequisites, content/technical dependencies, product decision, separate implementation/release/provider approvals, rollout, verification, and rollback before downstream work. For compound work, preserve the router's chain from research and baseline through local acceptance, authorized release, live verification, any separately authorized provider operation, and delayed comparison. For broad organic growth, preserve two concurrent roadmap tracks: nearer-term capture/defense and high-volume head-term/category leadership. Put the leadership track's owner and foundation work into the active roadmap even when authority building and leading-position milestones span later stages; do not replace it with quick wins.
  4. Assign outcomes honestly. Give each initiative owner, acceptance criteria, verification method, guardrail, and review date. A roadmap may target a measurable behavior, but cannot forecast rankings, citations, traffic, or revenue as a guarantee.
  5. Report changes. Compare only like-for-like observations. Separate delivery status, technical state, search reporting, visibility observations, referrals, and conversions.

Output

Return a roadmap organized by decision gate and owner: prerequisite, approved action, dependency, delivery milestone, verification/guardrail, and unresolved risk. For broad organic growth, show the nearer-term and head-term leadership tracks separately, including the canonical owner, competitive gap, supporting work, and observable visibility bands. Use target dates only when supplied by a real owner/capacity plan; otherwise label the sequence rather than inventing timing.

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.