Use this guide as a starting point, then validate recommendations against your website, current search documentation, and the needs of your audience.

1. Match the markup to the page

Choose a schema type that accurately describes the visible page and its purpose. Examples include Organization for a business identity, Article for editorial content, BreadcrumbList for navigation, and Product for a product page. Do not add types just because they seem attractive in search results.

2. Prefer maintainable JSON-LD

JSON-LD is commonly used because it can be placed in a script element without changing the visible page layout. Keep the data accurate and consistent with the content users can see. Avoid generating the same entity with conflicting details in multiple places.

3. Include only supported, truthful properties

Use the properties that apply to your content and follow the relevant search engine documentation. Never invent reviews, ratings, prices, availability, author credentials, or other facts to qualify for a feature.

4. Validate before and after publishing

Use the Rich Results Test for supported Google rich-result types and a Schema.org validator for broader vocabulary checks. Fix syntax errors, then inspect the live page and confirm that the markup matches the rendered content.

5. Monitor eligibility rather than assuming results

Search engines decide whether to display enhancements. Monitor Search Console reports when available, review manual actions, and recheck markup after template changes or content updates.

Put this into practice

Use the relevant SEOmate tool to support your workflow, then verify the result on your live website.

Open Schema Markup Generator →

This article is general educational guidance. Search engine systems change, and individual results depend on the site and query. Verify important changes with current documentation and your own data.