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

seo-authority

Skill1 starsChanged 31 days agoMITView on GitHub

Builds and audits authority and off-site trust: what the evidence says about links, the link-spam line, linkable assets and digital PR, E-E-A-T and YMYL trust, entity and brand signals, Reddit/YouTube/forum distribution, disavow, site-reputation abuse. Use for "backlinks", "digital PR", "toxic links", "E-E-A-T", "brand mentions". Refuses link schemes, PBNs, link swaps and astroturfing. Not for per-engine penalty rules (seo-engine-policies).

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. oegeyilmaz9/seo-aeo-geo-ultimate★ 6same 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 repository7 other files it gives its agents.

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

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

seo-authority

Earned links, trust and brand signals — what the record supports, where the spam line is, and what we refuse.

<!-- 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
AU1links, the link-spam line, linkable assets, digital PRauthority-links-and-pr.md
AU2E-E-A-T, entity, brand, community distribution, site reputationauthority-trust-and-distribution.md

Not mine

QuestionSkill
a manual action, reconsideration, an engine's link policy textseo-engine-policies
study figures for a link tacticseo-evidence
AI-citation tactics and measurementseo-ai-search
roadmap and creative ideasseo-strategy

Rules

  1. Refused: link buying, PBNs and domain pools, link swaps and service-for-link exchanges, portfolio cross-linking beyond what a reader expects, undisclosed or astroturfed community posting.
  2. Editorial outreach is "alive by count" in the published record, with zero controlled tests — never promise a lift.
  3. Disavow only when both hold: a considerable number of spammy, artificial or low-quality links point to the site, and they have caused, or likely will cause, a manual action for unnatural links; try removal first; misuse can harm [documented: https://support.google.com/webmasters/answer/2648487, 2026-10-11]. Never on a third-party "toxic score" alone [unvalidated house heuristic].
  4. Third-party sections that ride the host's signals are a owner-level decision; the refusal stands on correctness and reputation.
  5. Mechanism stories about authority are [hypothesis].

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