Testing Schema

Always test schema markup before publishing. Errors can prevent rich results and may even cause issues.

Testing Tools

Google Rich Results Test

URL: https://search.google.com/test/rich-results

Features:

• Tests if page qualifies for rich results
• Shows which rich result types are detected
• Displays errors and warnings
• Mobile and desktop testing

Best For: Checking if Google will show rich results

Schema.org Validator

URL: https://validator.schema.org

Features:

• Validates against Schema.org specification
• Shows all detected types
• Highlights syntax errors
• More comprehensive than Google's tool

Best For: Checking technical validity

Google Search Console

Location: Enhancements section

Features:

• Shows schema performance over time
• Identifies pages with errors
• Tracks rich result impressions
• Site-wide monitoring

Best For: Ongoing monitoring

How to Test

Step 1: Use Rich Results Test

1. Go to Google's Rich Results Test
2. Enter URL or paste code
3. Run test
4. Review results

Step 2: Check Schema.org Validator

1. Go to validator.schema.org
2. Paste your JSON-LD code
3. Run validation
4. Fix any errors

Step 3: Verify in Search Console

After implementation:

1. Go to Search Console
2. Check Enhancements reports
3. Monitor for new errors

Understanding Results

Valid (No Errors)

• Schema is properly formatted
• All required properties present
• May or may not generate rich results

Warnings

• Non-critical issues
• May affect rich result eligibility
• Should be fixed but not urgent

Errors

• Must be fixed
• Prevent rich results
• May indicate broken code

Common Errors

Missing Required Properties

Error: Missing field "name"

Fix: Add the required property.

Invalid Value Type

Error: Property "telephone" expects type "Text"

Fix: Use correct data type.

Syntax Errors

Error: JSON parse error

Fix: Check for missing commas, brackets, or quotes.

Unknown Property

Warning: Property "businessType" not recognized

Fix: Use correct property name from Schema.org.

Testing Workflow

Before Publishing

1. Paste code into validator
2. Fix all errors
3. Test URL with Rich Results Test
4. Verify on staging site
5. Publish to production

After Publishing

1. Test live URL
2. Request indexing in Search Console
3. Monitor Enhancements report
4. Check for errors weekly

Testing Tips

Test the Live Page

Don't just test the code—test the actual URL where it's implemented.

Check Mobile and Desktop

Some rich results differ between mobile and desktop.

Test All Page Types

If you have different schema on different pages (location pages, service pages), test each template.

Test After Updates

Re-test whenever you modify schema or page content.

Debugging Common Issues

Schema Not Detected

Possible causes:

• Code not on page
• JavaScript not rendering
• Code has syntax errors

Debug:

• View page source
• Check browser console
• Validate JSON syntax

Rich Results Not Showing

Possible causes:

• Page not indexed
• Doesn't meet requirements
• Google chose not to display

Debug:

• Check indexing status
• Review guidelines
• Give it time (not instant)

Errors After Changes

Possible causes:

• Introduced syntax error
• Changed required property
• CMS override

Debug:

• Compare before/after
• Check CMS settings
• Review recent changes

Monitoring Over Time

Search Console Alerts

Set up email alerts for:

• New schema errors
• Coverage issues
• Rich result changes

Regular Audits

• Monthly: Check for new errors
• Quarterly: Full schema audit
• After updates: Re-test affected pages

Key Takeaways

1. Always test before publishing
2. Use both Google's tool and Schema.org validator
3. Fix errors before warnings
4. Monitor ongoing via Search Console
5. Re-test after any changes