JSON-LD Schema Reference
Understand how Geordy uses JSON-LD structured data to communicate with search engines and AI models.
The Schema JSON file is the most structured and search-engine-friendly of Geordy's formats. It describes entities, relationships, and page attributes using Schema.org vocabulary.
What is JSON-LD?
JSON-LD (JavaScript Object Notation for Linked Data) is a method of encoding structured data using JSON. It's the preferred format for Google and other search engines to understand your content's context and meaning.
Example Schema JSON
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "What is Generative Engine Optimization (GEO)?",
"author": {
"@type": "Person",
"name": "Geordy.ai Team"
},
"datePublished": "2025-10-01",
"dateModified": "2025-10-07",
"url": "https://example.com/geo-optimization",
"image": "https://example.com/images/geo-hero.jpg",
"description": "Learn how GEO helps your website become discoverable by AI models and generative search engines."
}JSON-LD Schema Structure
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "What is GEO?",
"author": {
"@type": "Person",
"name": "Geordy Team"
},
"datePublished": "2025-10-01"
}Key Fields Explained
@context
Always set to https://schema.org. This defines the vocabulary being used.
@type
Specifies the type of entity being described. Common types include Article, Product, Organization, WebPage, Person, Event, and more.
headline / name / description
Core descriptive elements that provide the main information about the entity.
author / datePublished / url
Metadata fields that provide provenance, timing, and location information for the content.
Common Schema Types
| Schema Type | Use Case | Key Properties |
|---|---|---|
| Article | Blog posts, news articles | headline, author, datePublished |
| Product | E-commerce product pages | name, price, availability |
| Organization | Company information | name, logo, contactPoint |
| WebPage | General web pages | name, description, url |
| Event | Conferences, webinars | name, startDate, location |
Validation
Use Google's Rich Results Test to validate your Schema JSON and ensure it's correctly formatted:
https://geo.yourdomain.com/schema.jsonAdvanced Example: Product Schema
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Eco-Friendly Water Bottle",
"description": "Sustainable stainless steel water bottle with 24-hour temperature retention.",
"image": "https://example.com/images/water-bottle.jpg",
"brand": {
"@type": "Brand",
"name": "EcoLife"
},
"offers": {
"@type": "Offer",
"price": "29.99",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"url": "https://example.com/products/water-bottle"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.8",
"reviewCount": "127"
}
}Best Practices
- Be Accurate: Ensure all information in your schema matches the visible content on your page.
- Use Specific Types: Choose the most specific schema type that applies to your content (e.g., BlogPosting instead of Article).
- Include Images: Always provide high-quality image URLs when applicable.
- Keep Updated: Geordy automatically updates your schema when you rescan pages, ensuring freshness.
Next Steps
Explore sample outputs for all supported formats to see what your generated files will look like.