agentleFS
6t9xstar6t9xstar/one-step-seo/skills/entity-optimization/SKILL.md

entity-optimization

Skill5 starsChanged 35 days agoMITView on GitHub

Audit and align Knowledge Graph entity disambiguation, E-E-A-T authorship, content freshness signals, Organization/Person/Article JSON-LD @graph linking, and title/H1/og:title consistency.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    Ensure date-sensitive articles expose <time datetime="YYYY-MM-DD"> and matching JSON-LD datePublished + dateModified (G06-freshness P3).

    line 31

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

entity-optimization — Entity SEO, Authorship & E-E-A-T Signals

1. Description & Activation Criteria

Activate entity-optimization when the user wants to:

  • Strengthen brand, author, and topic entity disambiguation for Google Knowledge Graph and LLM retrieval systems.
  • Audit E-E-A-T trust signals on editorial, medical, financial, technical, or B2B content: explicit authorship (G10-author P3), publication/review freshness dates (G06-freshness P3), <title> vs og:title entity consistency (G04-entity P3), <title> vs <h1> alignment (O03-h1-drift P3), and unified @graph structured data (S01-none P1, S01-json-invalid P1, S02-organization P2, S02-article P2).

2. Inputs & Prerequisites

  • Target: Editorial articles, whitepapers, About/Team pages, or corporate homepages (live URL or local HTML).
  • Key CLI filters:
    • --skills entity-optimization (aliases: eeat, entity-seo).
    • schema --generate organization|website|article: Generates starter entity JSON-LD blocks grounded in the page's actual metadata.

3. Step-by-Step Workflow

  1. Run an entity-scoped audit:
    • Execute npx one-step-seo page <url> --skills entity-optimization --out ./seo-report and npx one-step-seo ai <url> --json.
  2. Eliminate entity naming drift (G04-entity, O03-h1-drift):
    • Inspect report.page.title and report.page.h1. When O03-h1-drift (P3) or G04-entity (P3) fires, align <title>, <h1>, and og:title so search engines and LLMs associate every fact on the page with one unambiguous entity name.
  3. Establish explicit authorship & publisher authority (G10-author):
    • On substantive pages (>= 300 words), verify <meta name="author"> or JSON-LD author (Person or Organization with name, url, and verified sameAs profile links) is declared (G10-author P3).
  4. Surface machine-readable freshness signals (G06-freshness):
    • Ensure date-sensitive articles expose <time datetime="YYYY-MM-DD"> and matching JSON-LD datePublished + dateModified (G06-freshness P3).
  5. Link entities in a single JSON-LD @graph (S01, S02):
    • Connect Organization (#organization) -> WebSite (#website) -> Person (#author) -> Article (#article) via stable @id URIs so crawlers resolve the publisher, author, and subject graph without ambiguity.

4. Tools & CLI Commands

# Audit entity consistency, authorship, freshness, and JSON-LD on an article
npx one-step-seo page https://example.com/blog/distributed-consensus --skills entity-optimization --out ./seo-report

# Generate starter Organization and Article JSON-LD nodes
npx one-step-seo schema https://example.com --generate organization
npx one-step-seo schema https://example.com/blog/distributed-consensus --generate article

# Multi-page editorial E-E-A-T audit across blog posts
npx one-step-seo audit https://example.com/blog --pages 20 --profile blog --skills eeat --out ./seo-report

5. Evidence Requirements

  • Quote G04-entity, G06-freshness, G10-author, O03-h1-drift, S01-*, and S02-* evidence strings from report.findings.
  • Cite signals.schemaTypes and signals.hasAuthor from one-step-seo ai <url> --json alongside report.page.title and report.page.h1.

6. Expected Outputs

  1. Entity & E-E-A-T Alignment Table: Comparison of <title>, <h1>, og:title, author metadata, freshness dates, and JSON-LD @type nodes.
  2. Unified @graph JSON-LD Block: Copy-paste <script type="application/ld+json"> linking Organization, Person, WebPage, and Article via @id.

7. Limitations & External Data

  • On-page vs off-page authority: one-step-seo verifies machine-readable entity, authorship, and freshness declarations in HTML/JSON-LD; external backlink authority, Wikipedia/Wikidata notables, and brand search volume require external off-page datasets.
  • Offline support: 100% supported offline (--offline).

8. Safety & Approval Rules

  • Never fabricate author credentials, biographies, sameAs social URLs, or fake dateModified timestamps: Only bump dateModified when substantive editorial updates were actually made, and never invent fictional expert personas.

9. Examples

# Inspect the entity-optimization skill checks and aliases
npx one-step-seo skills entity-optimization

# Audit an offline static blog export for E-E-A-T and entity alignment
npx one-step-seo audit ./dist/blog --pages 15 --skills entity-optimization --offline --out ./seo-report

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.