Assembling schema by hand is where most teams give up. The Schema Validator at /tools/schema-validator/ tells you what's missing. Schema Completeness at /tools/schema-completeness/ lets you build up fields one at a time. Both assume you already know what to build.
The Schema Fix Bundle picks a page type and emits the whole thing at once: Organization + WebSite + BreadcrumbList + Person (author) + the page-specific node, all linked by @id, with every Google-required field pre-populated with REPLACE placeholders. Then it emits an AI prompt that fills in the REPLACE values from your actual page content.
The thirteen presets
One click each emits a complete, valid JSON-LD @graph:
- Article / BlogPosting, news, editorial, personal blog posts. Triggers headline + publish-date rich result.
- Product, physical goods with
shippingDetails,hasMerchantReturnPolicy,aggregateRating,review. The fields Google Search Console flags most often. - LocalBusiness, physical businesses with full
PostalAddress,openingHoursSpecification,geo,aggregateRating,sameAs. - Service, agencies, consultancies, B2B offerings.
- FAQPage, Q&A rich result. Pre-populated with three question stubs.
- HowTo, step-by-step rich result.
- Recipe, recipe card with nutrition, cook time, ingredients, instructions.
- Event, event carousel with location, offers, organizer.
- VideoObject, video thumbnail rich result.
- Book, knowledge-panel + author attribution.
- Course, education carousel with instructor and offer.
- SoftwareApplication, SaaS + apps with aggregate rating + offer.
- JobPosting, Google Jobs rich result with salary, location, validity window.
You can select multiple presets (a Product that's also FAQPage gets both blocks merged into one @graph). Identity nodes aren't duplicated.
The @id linking pattern
Every preset references shared identity nodes via @id:
Organizationathttps://yoursite.com/#organizationWebSiteathttps://yoursite.com/#websiteBreadcrumbListathttps://yoursite.com/page-url/#breadcrumbPerson(author) athttps://yoursite.com/page-url/#author
Every page in your site can reference the same Organization by @id, you define it once, link it everywhere. Google treats all @id references as the same entity. This is how large sites ship consistent Organization schema without duplicating the block on 10,000 pages.
The AI fill prompt
Every preset ships with REPLACE placeholders for content-dependent values (headline, image URL, price, ingredients, etc.). The tool emits an AI prompt that:
- Takes the page HTML (or URL)
- Extracts the actual values for every REPLACE placeholder (headline from
<h1>, image fromog:image, price from the pricing block, etc.) - Deletes placeholder fields that genuinely don't apply (a recipe without reviews should omit
aggregateRating, not ship"ratingValue":"REPLACE") - Returns the fully-populated JSON-LD block ready to paste into
<head>
Round-trip: 30 seconds to pick presets → 30 seconds to copy the prompt → 60 seconds to paste into Claude + page HTML → 30 seconds to copy the populated block. 2.5 minutes from blank page to validated schema, versus ~30 minutes to hand-assemble the same @graph.
Why this pairs with Schema Completeness
Schema Completeness is fine-grained, one @type at a time, pick every field. Good when you know exactly what you want. Bad when you're staring at 15 possible @types and need to know which triggers what rich result.
Schema Fix Bundle is opinionated, you pick the page purpose, you get the schema Google rewards for that purpose. Good when you're retrofitting schema onto 50 legacy pages and need a consistent template. Bad when you need something bespoke (e.g., a weird nested MedicalProcedure → MedicalEntity graph).
Use Schema Fix Bundle for the 80% case. Use Schema Completeness to hand-tune the 20%.
The ship workflow
- Pick page type(s) in the Fix Bundle → copy the JSON-LD block
- Paste into your page's
<head>(or your CMS schema field) - Copy the AI fill prompt + paste into Claude along with the page HTML
- Paste Claude's populated block back into
<head>, replacing the placeholder version - Validate at
/tools/schema-validator/?url=<your-url>and at Google's Rich Results Test - Deploy
Then the check on your Mega Analyzer dashboard goes green on the schema tab, and within 3-7 days Google's crawler re-indexes and the rich result starts appearing in SERPs.
Related reading
- Why E-E-A-T Schema Matters for Authority Signals
- Validate Your JSON-LD Against Google Rich-Result Requirements
- FAQ Schema Parity, Matching Visible Q&A to JSON-LD
- The Mega Analyzer's Schema Tab, What It Checks
If you want the full structured-data + E-E-A-T + entity-SEO playbook, the $100 Network walks through the network-scale approach: The $100 Network.
Fact-check notes and sources
- Google rich-result required fields per type: Google Search Central, Structured data gallery (accessed 2026-04-20)
- Schema.org specification: schema.org
@idcross-reference pattern: Schema.org, Using JSON-LD for structured data- Google Rich Results Test: search.google.com/test/rich-results
