Auditite
All playbooks
Playbook Technical SEO Specialist

Schema Markup Implementation Playbook for SEO

Step-by-step playbook for implementing structured data across your site to win rich results and improve search visibility.

Overview

Structured data helps search engines understand your content and can unlock rich results like star ratings, FAQs, breadcrumbs, and product details directly in SERPs. This playbook covers planning, implementation, and validation of schema markup.

Step 1: Audit Existing Schema

  1. Crawl your site with Auditite to identify pages that already have structured data.
  2. Run each template type through Google’s Rich Results Test to check for errors and warnings.
  3. Document which schema types are currently implemented and where gaps exist.
  4. Check Google Search Console’s Enhancements reports for any existing structured data issues.

Step 2: Identify Opportunities

Map schema types to your page templates:

Page TypeRecommended SchemaRich Result Potential
HomepageOrganization, WebSite, SearchActionSitelinks search box
Product pagesProduct, Offer, AggregateRatingProduct rich results
Blog postsArticle, BreadcrumbListArticle rich results
FAQ pagesFAQPage, QuestionFAQ accordions
How-to contentHowToStep-by-step results
Local pagesLocalBusinessKnowledge panel
Event pagesEventEvent listing
Review pagesReview, AggregateRatingStar ratings
Recipe pagesRecipeRecipe cards
Video contentVideoObjectVideo carousel

Prioritize schema types that have visible rich result features — these directly impact CTR.

Step 3: Implementation Guidelines

Format Selection

Use JSON-LD exclusively. It is Google’s recommended format and is easier to maintain than Microdata or RDFa because it is decoupled from the HTML markup.

Placement

Place JSON-LD in the <head> section of each page or just before the closing </body> tag. Use one script block per schema type or nest related types within a single block.

Data Accuracy

  1. Schema data must match the visible content on the page. Do not include information in schema that users cannot see.
  2. Prices must be current and accurate, including currency codes.
  3. Ratings must reflect genuine, aggregated user reviews — never fabricate numbers.
  4. Dates must be in ISO 8601 format (YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS).

Step 4: Template-Level Implementation

Rather than adding schema to individual pages, implement it at the template level:

  1. Create JSON-LD templates in your CMS or static site generator that dynamically populate from page data.
  2. Use conditional logic to include optional properties only when data exists (do not output empty strings).
  3. Test with a sample page from each template before deploying site-wide.
  4. Document which CMS fields map to which schema properties for content team reference.

Step 5: Advanced Schema Patterns

Nesting and Relationships

Connect schema entities to create a richer graph:

  • Link Article to the author’s Person schema
  • Link Product to the brand’s Organization schema
  • Link BreadcrumbList items to the actual page URLs
  • Use @id references to connect entities across the page

SameAs and Knowledge Graph

For your Organization schema, include sameAs links to your official social profiles and Wikipedia page (if you have one). This helps Google connect your brand entity to its Knowledge Graph.

Speakable Schema

For news and blog content, add Speakable schema to identify sections that are suitable for voice assistant reading. This positions your content for voice search features.

Step 6: Validation and Monitoring

  1. Validate every template with Google’s Rich Results Test before deployment.
  2. After deployment, monitor Google Search Console’s Enhancements section for new errors.
  3. Set up Auditite’s schema monitoring to catch issues introduced by CMS updates or content changes.
  4. Re-validate after any CMS update, theme change, or content template modification.

Step 7: Track Rich Result Performance

In Google Search Console:

  1. Filter the Performance report by search appearance to see clicks from rich results.
  2. Compare CTR on pages with rich results versus pages without.
  3. Track which rich result types generate the most clicks in your niche.
  4. Monitor for rich result loss — a sudden drop indicates a schema error or Google policy change.

Stop copy-pasting. Start automating.

Auditite turns playbooks into live audit workflows. Get started to see how.

Get insights delivered weekly

Join teams who get actionable playbooks, benchmarks, and product updates every week.