agentleFS
LittlpinguinLittlpinguin/marketing-cockpit-template/.claude/skills/seo-schema/SKILL.md

seo-schema

Skill9 starsChanged 14 days agoMITView on GitHub

Détecte, valide et génère les données structurées Schema.org (JSON-LD) de {{COMPANY_NAME}} selon les types actifs chez Google. À utiliser sur « schema », « données structurées », « rich results », « JSON-LD », « balisage », ou après publication d'une page.

40 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 9 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 15 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 14 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 16 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 20 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 14 projects that use this

  • +5 more from timruebenach

The file

Files
SKILL.md

seo-schema — données structurées

Skill d'analyse et de génération technique (pas de copy — pas de doctrine de marque requise, mais les données injectées doivent venir de sources réelles : site, 01-brand/messaging-framework.md). Adapté du plugin claude-seo (AgriciDaniel, MIT) — voir docs/vendored-seo.md.

Détection

  1. Scanner la source de la page : JSON-LD <script type="application/ld+json"> (format à privilégier — préférence déclarée de Google), Microdata (itemscope/itemprop), RDFa.
  2. Valider : @context présent, @type valide, propriétés requises par type, URLs absolues, formats de date ISO, aucun texte placeholder résiduel.
  3. Signaler les types dépréciés ou restreints (liste ci-dessous).

Statut des types (état février 2026 — re-vérifier à chaque re-sync)

ACTIFS (recommander librement) : Organization, LocalBusiness, SoftwareApplication, WebApplication, Product, Offer, Service, Article, BlogPosting, NewsArticle, Review, AggregateRating, BreadcrumbList, WebSite, WebPage, Person, ProfilePage, ContactPage, VideoObject, ImageObject, Event, JobPosting, Course, DiscussionForumPosting.

RESTREINTS :

  • FAQPage : rich results réservés aux sites gouvernementaux et de santé faisant autorité (restriction août 2023). Le balisage reste utile pour la compréhension machine (GEO), mais ne pas promettre de rich result.

DÉPRÉCIÉS (ne jamais recommander) :

  • HowTo (rich results supprimés sept. 2023), SpecialAnnouncement (juil. 2025), ClaimReview, VehicleListing, CourseInfo, EstimatedSalary, LearningVideo (retirés 2025).

Rendu JavaScript : du JSON-LD injecté en JS peut être traité avec retard. Pour un balisage sensible au temps (Event, Offer), l'inclure dans le HTML servi côté serveur.

Génération

  1. Identifier le type de page (article, événement, page entreprise, offre…).
  2. Choisir le(s) type(s) de schema appropriés.
  3. Générer un JSON-LD valide avec propriétés requises + recommandées.
  4. Uniquement des données véridiques et vérifiables. Marquer clairement [À COMPLÉTER] ce qui manque — ne jamais inventer un téléphone, une adresse, une note.
  5. Valider avant de livrer (parse JSON + propriétés requises).

Gabarits usuels pour {{COMPANY_NAME}}

Organization (page d'accueil / à propos)

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "{{COMPANY_NAME}}",
  "url": "{{COMPANY_WEBSITE}}",
  "logo": "[URL logo]",
  "sameAs": ["[LinkedIn]", "[autres profils]"]
}

Article / BlogPosting (articles 09-seo/)

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "[Titre]",
  "author": { "@type": "Person", "name": "[Auteur]" },
  "datePublished": "[YYYY-MM-DD]",
  "dateModified": "[YYYY-MM-DD]",
  "image": "[URL image]",
  "publisher": {
    "@type": "Organization",
    "name": "{{COMPANY_NAME}}",
    "logo": { "@type": "ImageObject", "url": "[URL logo]" }
  }
}

Event (webinaires, événements 07-events/)

{
  "@context": "https://schema.org",
  "@type": "Event",
  "name": "[Nom]",
  "startDate": "[YYYY-MM-DDTHH:MM+01:00]",
  "eventAttendanceMode": "https://schema.org/OnlineEventAttendanceMode",
  "location": { "@type": "VirtualLocation", "url": "[URL]" },
  "organizer": { "@type": "Organization", "name": "{{COMPANY_NAME}}", "url": "{{COMPANY_WEBSITE}}" }
}

Sortie

  • Tableau de validation : | Schema | Type | Statut ✅/⚠️/❌ | Problèmes |
  • Opportunités manquantes par page
  • Snippets JSON-LD prêts à intégrer (fichier à côté du livrable concerné, ex. 09-seo/articles/… ou 05-web-content/…)

Gestion d'erreur

CasAction
Aucun balisage détectéLe dire, puis recommander les types adaptés au contenu de la page
JSON-LD invalidePointer l'erreur de syntaxe précise et fournir la version corrigée
Type déprécié détectéSignaler avec la date de retrait, proposer remplacement ou suppression

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.