Schema Markup Implementation Guide with Auditite

Overview

Schema markup helps search engines understand your content and can unlock rich results like FAQ dropdowns, review stars, product prices, and how-to panels. This guide covers planning, implementing, validating, and monitoring structured data across your site.

Step 1: Audit Existing Schema

1. Run Auditite’s schema validation audit across your entire site.
2. Document which schema types are currently implemented and on which page templates.
3. Identify pages with invalid or incomplete schema markup.
4. Note rich results you are currently earning versus those you are eligible for but missing.

Step 2: Identify Schema Opportunities

Schema Types by Page Template

Page Template	Recommended Schema	Rich Result Potential
Homepage	Organization, WebSite, SearchAction	Sitelinks search box
Product pages	Product, Offer, AggregateRating	Product rich results
Category pages	ItemList, BreadcrumbList	Carousel, breadcrumbs
Blog posts	Article, BreadcrumbList	Article rich results
FAQ pages	FAQPage	FAQ dropdowns
How-to content	HowTo	How-to panels
Contact page	LocalBusiness, ContactPoint	Knowledge panel info
Event pages	Event	Event rich results

Priority Order

Focus on schema types that directly generate rich results first. BreadcrumbList and Organization provide foundational context but do not generate standalone rich results.

Step 3: Implementation Method

JSON-LD (Recommended)

Use JSON-LD script blocks in the page head. This is Google’s preferred format because it separates structured data from HTML content.

<script type="application/ld+json">
  {
    "@context": "https://schema.org",
    "@type": "Article",
    "headline": "Your Article Title",
    "author": {
      "@type": "Person",
      "name": "Author Name"
    },
    "datePublished": "2026-01-15",
    "dateModified": "2026-03-20"
  }
</script>

Dynamic vs. Static

• For CMS-driven pages, generate JSON-LD dynamically from page data.
• For static pages, embed JSON-LD directly in templates.
• Never hardcode values that should be dynamic (prices, ratings, dates).

Step 4: Implement Core Schema Types

Organization Schema (Sitewide)

Place on every page. Include your logo URL, social profiles, and contact information. This builds your knowledge graph presence.

BreadcrumbList (All Interior Pages)

Map your site hierarchy. Each breadcrumb item should have a name and URL. The last item represents the current page and should not have a URL.

Article Schema (Blog/Content Pages)

Include headline, author, datePublished, dateModified, and image. Use the full author entity (Person type) rather than just a name string.

Product Schema (E-commerce)

Include name, description, image, sku, brand, offers (price, currency, availability), and aggregateRating if reviews exist. Ensure price and availability are always current.

Step 5: Validate Your Implementation

1. Test individual pages with Google’s Rich Results Test.
2. Run a site-wide schema audit with Auditite to catch issues at scale.
3. Check Google Search Console’s Enhancements reports for each schema type.
4. Fix all errors before addressing warnings — errors prevent rich results entirely.

Common Validation Errors

• Missing required properties (e.g., Product without offers)
• Invalid date formats (use ISO 8601: YYYY-MM-DD)
• Image URLs that return 404
• Mismatched schema type and page content (FAQ schema on a non-FAQ page)

Step 6: Monitor Rich Results

1. Track which pages earn rich results in Google Search Console.
2. Monitor click-through rates on pages with and without rich results.
3. Set up Auditite alerts for schema validation failures on new and updated pages.
4. Review schema markup quarterly as Google updates its supported types and requirements.

Best Practices

• Only mark up content that is visible on the page. Do not add schema for content users cannot see.
• Keep schema data consistent with on-page content. If your schema says the price is $49, the visible price must also be $49.
• Do not use schema to describe content on other pages. Each page’s schema should describe that page only.
• Nest related schema types properly. An Article’s author should be a Person entity, not a plain string.