Schema markup is structured information added to a page using a shared vocabulary to describe things such as an organisation, product, article or breadcrumb trail. It helps machines interpret facts that should already be represented accurately on the page.
Choose the type around the real content
Start with what the page contains and what useful search feature, if any, Google currently supports. Google’s structured-data gallery lists supported appearances; the broader Schema.org vocabulary contains types that do not necessarily trigger a Google feature. An ordinary service page should not be labelled as a product or review merely to pursue stars. Keep the page’s meaning consistent for people and machines.
Make every property defensible
Match names, prices, availability, authors and other properties to the visible information and current business facts. Avoid invented reviews, hidden claims or unsupported affiliations. Structured data cannot repair a misleading offer. Google’s structured-data policies make clear that valid markup alone does not guarantee a rich result. Syntax, content accuracy, eligibility and display selection are separate questions.
Validate the actual published page
Use the Rich Results Test for supported Google features and inspect representative live URLs. Check that template output does not create conflicting or stale objects. Re-test after changes to the CMS, product data or theme. Technical SEO implementation can connect markup checks with crawl access and visible content, so a passing test is understood within its practical limits.
Separate a test pass from a release decision
A validator can report syntactically correct markup while the underlying facts remain wrong. Compare a sample object with the visible page and the responsible business record before approving a template. Include expired offers, unavailable products and missing author information in the sample where relevant. Keep an owner for future updates. Structured data should remain accurate throughout the page’s life, not only on the day the initial implementation passes a tool.
A product page example
Suppose a Perth retailer publishes a drill with a specific model number, price and availability. Product markup should describe that exact offer and remain aligned with the buying page as stock changes. A generic service article should not inherit the same product object from a sitewide template. Monitor relevant reports in Google Search Console after release. Even accurate eligible markup may appear as an ordinary result; its presence does not guarantee higher rankings or sales.
Common questions
Does schema markup directly guarantee better rankings?
No. It can aid interpretation and feature eligibility, but Google controls appearance and ranking through broader systems.
Can I rely on an old list of rich-result types?
No. Feature support changes. Check current Google documentation, including retirements such as FAQ rich results in May 2026.
Terms in this guide
- Structured data — Machine-readable information describing a page’s content in a supported format, such as JSON-LD. It should use accurate, relevant properties.
- CMS — A content management system used to create and maintain website content. It can separate day-to-day editing from the underlying templates and application code.
- Google Search Console — Google’s tool for monitoring a website’s presence in Search, including performance, indexing reports and URL inspection.
Related SEO guides
Apply this to your website
Explore Technical SEO for help planning and implementing the relevant changes, or discuss your website with Refined IT.