geo-schema
Schema.org structured data audit and generation for rich results and entity clarity — detect, validate, and generate JSON-LD markup. Schema is NOT an AI-citation lever (Ahrefs controlled study, May 2026); it earns rich results and keeps entity data unambiguous.
TheSmokeDev · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add TheSmokeDev/geo-skills --skill geo-schema技能说明
name: geo-schema description: Schema.org structured data audit and generation for rich results and entity clarity — detect, validate, and generate JSON-LD markup. Schema is NOT an AI-citation lever (Ahrefs controlled study, May 2026); it earns rich results and keeps entity data unambiguous. metadata: version: "1.0.0" author: geo-seo-claude tags: [geo, schema, structured-data, json-ld, entity-recognition, ai-discoverability]
GEO Schema & Structured Data
Purpose
Structured data does two jobs well: earning Google rich results and keeping entity data unambiguous (who the organization is, what it offers, which profiles belong to it). That is the scope of this skill.
What schema does NOT do: lift AI citations. In the Ahrefs controlled study (1,885 pages that added JSON-LD, reported May 2026 via Search Engine Journal), citation rates moved ChatGPT +2.2%, AI Mode +2.4%, AIO -4.6% — all within noise. Adding markup alone produced no citation lift on any platform. Do not sell schema as a GEO tactic.
The nuance worth keeping (SSRN, Feb 2026): schema that carries concrete, extractable facts (dates, prices, locations, specs) can still correlate with citation — but the lift comes from the quotable data, not the markup itself. Put the facts in visible, well-structured page content first; schema is the machine-readable echo, not the signal.
With that framing, complete and accurate structured data remains worthwhile: rich results still win SERP real estate, and clean entity data (Organization, sameAs, contactPoint) removes ambiguity for every system — search engines, knowledge graphs, and AI platforms alike.
How to Use This Skill
- Fetch the target page HTML using curl or WebFetch
- Detect all existing structured data (JSON-LD, Microdata, RDFa)
- Validate detected schemas against Schema.org specifications
- Identify missing recommended schemas based on business type
- Generate ready-to-use JSON-LD code blocks
- Output GEO-SCHEMA-REPORT.md
Step 1: Detection
Scan for JSON-LD
Look for <script type="application/ld+json"> blocks in the HTML. Parse each block as JSON. A page may contain multiple JSON-LD blocks — collect all of them.
Scan for Microdata
Look for elements with itemscope, itemtype, and itemprop attributes. Map the hierarchy of nested items. Note: Microdata is harder for AI crawlers to parse than JSON-LD. Flag a recommendation to migrate to JSON-LD if Microdata is the only format found.
Scan for RDFa
Look for elements with typeof, property, and vocab attributes. Similar to Microdata — recommend migration to JSON-LD.
Priority Order
JSON-LD is the strongly recommended format for GEO. Google, Bing, and AI platforms all process JSON-LD most reliably. If the site uses Microdata or RDFa exclusively, flag this as a high-priority migration.
Step 2: Validation
For each detected schema block, validate:
- Valid JSON: Is the JSON-LD syntactically valid? Check for trailing commas, unquoted keys, malformed strings.
- Valid @type: Does the
@typematch a recognized Schema.org type? Check against https://schema.org/docs/full.html. - Required Properties: Does the schema include all required properties for its type? (See per-type requirements below.)
- Recommended Properties: Does the schema include recommended properties that improve rich-result eligibility and entity clarity?
- sameAs Links: Does the schema include
sameAsproperties linking to other platform presences? - URL Validity: Do all URLs in the schema resolve (not 404)?
- Nesting: Is the schema properly nested (e.g., author inside Article, address inside Organization)?
- Rendering Method: Is the JSON-LD in the server-rendered HTML or injected via JavaScript? Per Google's December 2025 guidance, JavaScript-injected structured data may face delayed processing. Flag any schema that requires JS execution.
Step 3: Schema Types for GEO
Organization (CRITICAL — every business site)
The backbone of unambiguous entity data: it states WHAT the business is in a form every search engine and knowledge graph can parse without inference.
Required properties:
@type: "Organization" (or subtype: Corporation, LocalBusiness, etc.)name: Official business nameurl: Official website URLlogo: URL to logo image (ImageObject preferred)
Recommended properties for GEO:
sameAs: Array of ALL platform URLs (see sameAs strategy below)description: 1-2 sentence description of the organizationfoundingDate: ISO 8601 datefounder: Person schemaaddress: PostalAddress schemacontactPoint: ContactPoint with telephone, email, contactTypeareaServed: Geographic areanumberOfEmployees: QuantitativeValueindustry: Text or DefinedTermaward: Array of awards receivedknowsAbout: Array of topics the organization is expert in (entity clarity signal)
LocalBusiness (for businesses with physical locations)
Extends Organization. Critical for local AI search results and Google Gemini.
Additional required properties:
address: Full PostalAddresstelephone: Phone numberopeningHoursSpecification: Operating hours
Recommended for GEO:
geo: GeoCoordinates (latitude, longitude)priceRange: Price indicatoraggregateRating: AggregateRating schemareview: Array of Review schemashasMap: URL to Google Maps
Article + Author (CRITICAL for publishers)
Author markup supports E-E-A-T presentation and article rich results; it also keeps byline facts consistent for any system parsing the page.
Article required:
@type: "Article" (or NewsArticle, BlogPosting, TechArticle)headline: Article titledatePublished: ISO 8601dateModified: ISO 8601 (critical for freshness signals)author: Person or Organization schemapublisher: Organization schema with logoimage: Representative image
**Author (Person) requi
阅读完整来源 ↗