Structured data helps machines interpret page entities and can make some pages eligible for richer search appearances. Valid JSON-LD is only the first step. The markup must match the visible page, use an appropriate supported type and follow the specific feature guidelines if you want eligibility for a Google rich result.
Choose a type that matches the page
Do not select a schema type only because its search appearance looks attractive. A tool page, article, product, event and organization represent different things. Start from the real page purpose and mark up only the entities that are actually present.
Keep markup consistent with visible content
Names, ratings, prices, dates and other properties should describe information users can see or reasonably verify on the page. Hidden or misleading structured data can fail quality guidelines even when the syntax is valid.
Fix required-property errors first
A validator may report required and recommended properties. Resolve syntax and required fields first, then decide whether recommended fields are genuinely available. Do not invent values merely to remove a warning.
Make referenced assets crawlable
If markup references an image or page URL, search engines need to be able to access it. Avoid using private, blocked or temporary asset URLs for properties intended for search features.
Validate both code and live deployment
Test the markup before publishing, then test the live URL. Templates, escaping, caching or server-side conditions can change the final structured data after deployment.
Remember that eligibility is not a guarantee
Even correct markup does not force a rich result to appear. Use structured data for accurate machine-readable context and treat search appearance as a possible outcome rather than the only reason to add it.
Worked example
Example review
An article guide can use Article structured data with its real headline, author organization and dates. A free browser utility can use WebApplication markup instead of pretending to be a Product with a made-up price review.
Practical checklist
Before you finish
- Mark up the page users actually see.
- Use a schema type that matches the real content.
- Do not fabricate optional values to silence warnings.
- Test the live URL after deployment.
- Keep images and URLs referenced by markup crawlable when appropriate.
Common mistakes
What to avoid
- Adding Product markup to a page that is not a product.
- Marking up ratings that are not shown to users.
- Assuming valid JSON-LD guarantees a rich result.
- Leaving copied template values on unrelated pages.
Further reading from authoritative sources
Use these references when you need the underlying specification or platform guidance.