seo-authority
Skill6 starsChanged 3 months agoApache-2.0View on GitHub
Use when auditing backlinks, referring domains, source citations, brand mentions, unlinked mentions, linkable assets, digital PR evidence, or off-site source landscapes from authorized first-party, Bing, vendor, or public evidence; preserve vendor metric definitions, detect manipulative risk, and never treat a proprietary authority score as universal truth or recommend link schemes.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- yeer0s/ultimate-seo-collectiontheir own version, first seen Oct 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- yeer0s/ultimate-seo-collection★ 1same 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 repository27 other files it gives its agents.
- llms.txtllms.txt
- ai-search-researchSkill
- ai-visibility-monitorSkill
- optimise-seoSkill
- seo-action-planSkill
- seo-aeoSkill
- seo-agenticSkill
- seo-architectureSkill
- seo-auditSkill
- seo-commerceSkill
- seo-competitor-pagesSkill
- seo-contentSkill
- seo-geoSkill
- seo-hreflangSkill
- seo-imagesSkill
- seo-localSkill
- seo-news-discoverSkill
- seo-pageSkill
- seo-performanceSkill
- seo-planSkill
- seo-programmaticSkill
- seo-researchSkill
- seo-schemaSkill
- seo-sitemapSkill
- seoSkill
- seo-technicalSkill
- seo-videoSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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
- Very specific: line 10
Read markdown-delivery-contract.md for every task.
- Distinctive: line 17
Read authority-evidence-protocol.md before a formal audit.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Authority and Source Landscape
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: authority-review.md; source-landscape.md (combine small related steps with stable section links). Record source ownership, expertise, referring evidence and claims directly in Markdown handoffs; distinguish owned citations from independent endorsement. Keep paid/organic/affiliate relationships explicit and no fabricated authority metrics.
Audit off-site evidence that helps users and systems verify an entity: genuine links, mentions, citations, source coverage, and risk. This skill does not manufacture authority.
Read authority-evidence-protocol.md before a formal audit.
Procedure
- Define entity, domains, markets/locales, comparison scope, authorized data sources, time window, and the decision to make.
- Preserve each link/mention row with source URL/domain, target URL/entity, anchor or mention text, first/last seen date when supplied, link attributes, source type, collection method, and limitations.
- Normalize URLs without discarding raw values. Separate backlinks, citations, unlinked mentions, syndication, scraper copies, social/profile links, and self-controlled properties.
- Evaluate source relevance, editorial independence, claim support, topical/locale fit, target-page usefulness, and visible context. Keep proprietary authority/risk/traffic metrics labeled with vendor and date.
- Identify broken earned links, incorrect entity facts, missing first-party evidence, unsupported claims, spam patterns, paid/sponsored disclosure, and link-scheme risk.
- Recommend source-worthy first-party assets, corrections, reclamation, documentation, partnerships, or editorial outreach only when truthful and policy-safe. Do not prescribe volume quotas or paid/manipulative links.
- Route entity/citation suitability to
seo-geo, competitor-page copy toseo-competitor-pages, content assets toseo-content, and internal links toseo-architecture. - Package findings as SEO Findings
1.1.0withbacklink_profile,content_set,web_page, orsitetargets andauthority,entity,content, orpolicycategories.
Formal evidence handoff
Package only supported observations as SEO Findings 1.1.0. Let <suite-root> mean ${CLAUDE_PLUGIN_ROOT} in Claude Code. In Codex, read .seo-suite-runtime.json beside this SKILL.md when present and use its suite_root value; otherwise use the absolute repository checkout, then run python "<suite-root>/scripts/validate_seo_findings.py" validate-findings <bundle>/seo-findings.json --bundle <bundle>. Keep the handoff provisional until this command passes.
Output
Return the source and scope, normalized link/mention inventory, source-quality and claim-support observations, risk patterns, evidence gaps, owners, verification, and limitations. Never collapse the result into a universal domain-authority score.
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.

