agentleFS
Sign inStart free
bestdeejay-designbestdeejay-design/agent-skills/skills/seo-schema/SKILL.md

seo-schema

Skill6 starsChanged 3 months agoMITView on GitHub

Structured data and meta markup for SEO: JSON-LD schema.org (Product, Article, Organization, Breadcrumb, FAQ — extraction + validation) and title/description/OG/Twitter meta generation (lengths, uniqueness, CTR). Script seo_schema.py: --meta (title/description/OG/canonical/h1/img audit) and --jsonld (extract + validate JSON-LD blocks). Triggers: 'seo schema', 'json-ld', 'schema org', 'structured data', 'meta tags', 'title description', 'разметка', 'jsonld', 'структурированные данные', 'meta теги'.

38 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-agentic, seo-sxo and 10 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.
  • AgriciDanielSkill

    seo-agentic

    Audit and fix agent readiness: the Lighthouse Agentic Browsing fraction, accessibility tree for agents, robots.txt and Content-Signal for AI agents, WAF treatment of agent traffic, llms.txt, Markdown delivery, ai-catalog.json, /.well-known discovery files, and WebMCP tools. Use when the user asks whether AI agents can use or browse the site, or about llms.txt or WebMCP. Exclude AI citability and brand signals (seo-geo) and commerce protocol depth (seo-ecommerce).

    Also in 5 projects that use this

  • timruebenachSkill

    seo-sxo

    Search Experience Optimization: reads Google SERPs backwards to detect page-type mismatches, derives user stories from search intent signals, and scores pages from multiple persona perspectives. Identifies why well-optimized pages fail to rank by analyzing what Google rewards for each keyword. Use when user says "SXO", "search experience", "page type mismatch", "SERP analysis", "user story", "persona scoring", "why isn't my page ranking", "intent mismatch", or "wireframe".

    Also in 14 projects that use this

  • 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 13 projects that use this

  • mangollcSkill

    seo-backlinks

    Backlink analysis and link building strategy: competitor backlink profiling, outreach plan generation, monthly SEO reporting framework, toxic link identification, link opportunity scoring, and unlinked mention discovery.

    Also in 15 projects that use this

  • mangollcSkill

    seo-local

    Local SEO optimization: Google Business Profile post generation, 30-day posting calendars, NAP consistency checks, local citation audits, review response templates, local keywords.

    Also in 19 projects that use this

  • indranilbanerjeeSkill

    seo-drift

    Compare two SEO exports (Search Console, two dates): gainers, losers, drift classes. \"what moved after the core update\"

    Also in 13 projects that use this

  • +6 more from timruebenach

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 36 edited versions we read keep these.

  • 2

    Distinctive

    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:

    Use this skill for the markup layer of SEO: structured data (JSON-LD / schema.org) and meta tags (title, description, Open Graph, Twitter …

    line 14
  2. Very specific:

    Do not use for a full technical crawl or content rewrite.

    line 52
  3. Distinctive:

    Run the local script or a JSON parser after generation.

    line 60

“Common” is measured: kept by at least 6 in 10 of the 36 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 Schema — structured data & meta markup

Use this skill for the markup layer of SEO: structured data (JSON-LD / schema.org) and meta tags (title, description, Open Graph, Twitter Cards).

Commands (documented in commands/)

CommandWhat it does
seo-schemaJSON-LD schema.org: Product, Article, Organization, Breadcrumb, FAQ — validation
seo-metaTitle/description generation: lengths, uniqueness, CTR, Open Graph, Twitter Cards

Script

python3 scripts/seo_schema.py --meta file.html      # title/desc/OG/canonical/h1/img audit
python3 scripts/seo_schema.py --jsonld file.html    # extract + validate JSON-LD blocks
  • --meta: title + length, description, canonical, og:title/description/image, twitter:card, robots, heading order, missing img alt.
  • --jsonld: extracts application/ld+json blocks and validates @context (schema.org), @type, and type-specific required fields (Product→offers+name, Article/BlogPosting→headline+author, FAQPage→mainEntity, Organization→name+url).
  • Pure Python stdlib; stdin supported.

When to use

  • User asks for "seo schema", "json-ld", "schema org", "structured data", "meta tags", "разметка", "структурированные данные".
  • A page needs its schema.org markup and meta layer checked or written.

Do NOT use

  • For the full technical audit / CWV / reports / fixes — that is seo-audit.
  • For content / keywords / headings / images — that is seo-content.
  • For crawlability / linking structure — that is seo-crawl.

Boundaries

  • Do not use for a full technical crawl or content rewrite; use seo-crawl or seo-content.

Markup workflow and output contract

Identify the page type and source-of-truth values before generating JSON-LD. Parse every block independently, validate JSON and required fields, check absolute URLs and ISO dates, then report the exact block or file location. Generated markup must be valid JSON, use only facts present in the project, and be previewed as a diff before applying.

Verification

Run the local script or a JSON parser after generation. Report validation errors separately from optional recommendations and distinguish schema.org validity from Google's rich-result eligibility. Never promise a rich snippet or fabricate ratings, offers, authors, or dates.

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