seo-ops
Skill0 starsChanged 21 days agoMITView on GitHub
Use when you need an SEO execution workflow, research table, content brief, metadata variants, structured data, citation review, or bulk content plan.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- juanpulag/seo-ops-studiotheir own version, first seen Nov 15, 2026
- LazyIsEfficient/agentic-ostheir own version, first seen Oct 22, 2026
- ericosiu/ai-marketing-skillstheir own version, first seen Sep 2, 2026
- tigerless-labs/seo-opstheir own version, first seen Aug 26, 2026
- varunk130/ai-marketing-claude-skillstheir own version, first seen May 18, 2026
- admdanielpaulino/claude-codestheir own version, first seen Apr 9, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- ericosiu/ai-marketing-skills★ 3.8ksame name
- tigerless-labs/seo-ops★ 986same name
- LazyIsEfficient/agentic-os★ 17same name
- admdanielpaulino/claude-codes★ 1same name
- varunk130/ai-marketing-claude-skills★ 1same name
- juanpulag/seo-ops-studio★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- internal-linkingSkill
- seo-auditSkill
- seo-quick-winsSkill
- verified-seo-article-writingSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 10 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
10
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
- Distinctive: line 15
Use current official documentation for changing platform behavior, rich-result eligibility, crawler controls, and measurement definitions.
- Distinctive: line 16
Every statistic needs a named source, date, and relevant context.
- Distinctive: line 19
Use plain sentences, natural headings, and no em dashes in generated copy.
- Distinctive: line 24
Read only the reference needed for the current job.
- Distinctive: line 42
Do not present a citation, recommendation, referral, or conversion as interchangeable evidence.
- Distinctive: line 44
Treat proposed metadata as drafts until the deployed HTML and canonical URL are checked.
- Distinctive: line 45
Keep a baseline, changed-URL cohort, untouched comparison cohort where useful, and rollback copy for bulk work.
- Distinctive: line 46
Never apply blind body-copy replacements to title or description fields.
- Distinctive: line 47
Keep hostname and canonical distinctions during analysis.
- Distinctive: line 59
Do not add a schema block, FAQ, statistic, product mention, or extra page merely to fill a template.
“Common” is measured: kept by at least 6 in 10 of the 6 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.
Files
SEO Ops
Turn an SEO request into a finished, evidence-backed deliverable. This is an execution toolbox for operators with a defined site, audience, and goal.
Operating contract
- Execute the requested operation when inputs and access are sufficient. Return a reusable prompt only when the user asks for one.
- Confirm the target URL or keyword, audience, market, language, deliverable, and permitted actions. Ask only for missing inputs that affect the result.
- Inspect the actual page and available search data. Distinguish observed findings from hypotheses and unavailable data.
- Use current official documentation for changing platform behavior, rich-result eligibility, crawler controls, and measurement definitions. Record the verification date.
- Every statistic needs a named source, date, and relevant context. Never invent a number, quote, testimonial, credential, or observation.
- Mark unresolved evidence as
[VERIFY: evidence needed]in working material. Resolve or remove it before calling a deliverable ready for publication. - Preserve uncertainty and source attribution. A vendor's claim is a claim, not independent proof.
- Use plain sentences, natural headings, and no em dashes in generated copy.
- Reading and drafting do not authorize publishing, changing settings, outreach, or bulk edits. Respect existing authorization and prepare a reviewable result before requesting any missing approval.
Choose the operation
Read only the reference needed for the current job.
| Job | Reference | Related workflow |
| Search results, question demand, keyword clusters, content scope | Research prompts | seo-audit for a broader diagnosis |
| AI answer citations and search-surface priorities | Research prompts | Use observed citations, not promised lift |
| Article, comparison, definition, or expert brief | Content prompts | verified-seo-article-writing for a sourced draft |
| Snippet rewrite, content refresh, or link plan | Content prompts | internal-linking for implementation detail |
| Answer summaries and citation-friendly rewrites | Citation prompts | Separate citations from recommendations |
| Titles, descriptions, CTR review, schema, or image specifications | Metadata and schema prompts | seo-quick-wins for site-wide prioritization |
| Full workflow, bulk processing, or pre-publication review | Workflow prompts | Keep batches reversible and measurable |
Evidence and measurement guardrails
- A search result is a dated observation for a query, location, language, device, and session. Do not present one result as universal.
- Label generated questions and keywords as hypotheses unless demand is observed in search results or supplied data.
- Benchmark content by useful facts and answered questions. Do not turn competitor word counts, keyword density, or link counts into targets.
- Separate valid schema vocabulary from a search platform's current display eligibility. Validate both before promising a rich result.
- Do not present a citation, recommendation, referral, or conversion as interchangeable evidence.
- Inspect snippet directives and crawler policies before changing them. Search crawling, training access, and user-triggered retrieval can have different controls. Verify the relevant product's current docs.
- Treat proposed metadata as drafts until the deployed HTML and canonical URL are checked. A saved field does not prove what the public page serves.
- Keep a baseline, changed-URL cohort, untouched comparison cohort where useful, and rollback copy for bulk work.
- Never apply blind body-copy replacements to title or description fields. Preview structured fields separately and sample the rendered output.
- Keep hostname and canonical distinctions during analysis. Aggregate rows only after verifying they represent the same page, and sum metrics instead of overwriting rows.
- Falling impressions with stable position can have several causes. Inspect query mix, demand, tracking, and search features before deciding to rewrite.
Output contract
Return:
- Scope and evidence: inputs, sources, observation dates, limits, and assumptions.
- Finished artifact: the table, brief, copy, markup, or plan requested.
- Verification: checks completed, unresolved items, and any deployment boundary.
- Next action: one concrete recommendation, owner if known, success measure, and regression guardrail.
Do not add a schema block, FAQ, statistic, product mention, or extra page merely to fill a template. Keep only what serves the reader and is supported.
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
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.

