Schema markup is a set of labels added to a page so machines can read facts without guessing. It does not create rich results on demand, and it does not fix a weak page. It clarifies what is already there. Used narrowly, it removes ambiguity about a business name, a price, a product, or an article. Used carelessly, it creates a mismatch between the label and the page, which is worse than having no markup at all.

What structured data is for

Search engines read text well but they read facts badly. A page that says we open at nine and close at five contains times, but not obviously which day, which timezone, or which location. Schema attaches names to those values: opening hours, price, availability, author, date published.

The benefit is clarity, not decoration. If your markup is accurate, you give engines a cleaner description of the page. Whether a rich result appears is up to the engine and the query.

Pick three types and stop

Most small businesses need a handful of types, not a catalogue. Start with Organization or LocalBusiness on the homepage, Article or BlogPosting on editorial pages, and Product or Service on commercial pages. If you publish recipes, events, or courses, add those too. Everything else can wait.

Resist adding a type because a plugin offers it. Every type you add is a claim you have to keep accurate as the site changes.

The fields that actually matter

For a local business: name, address, phone, opening hours, and the same URL you use everywhere. For an article: headline, author, date published, and date modified. For a product: name, image, price, currency, and availability. That is most of the value.

Keep the format consistent. A phone number written one way in the markup and another in the footer creates doubt. An address split differently from your Google Business Profile creates the same doubt.

Markup should describe the page, not the page you plan to build next quarter.

Where teams overreach

Two failures are common. The first is marking up reviews the site does not display, or displaying a rating that was collected elsewhere without permission. The second is marking up prices, stock levels, or delivery times that are stale.

A third failure is quieter: adding FAQ markup to pages that do not show the questions and answers. The markup may be ignored, and repeated mismatches reduce trust in everything else you publish. If a fact is not visible on the page, do not label it.

Accuracy has a shelf life. A page that listed four team members in January may be wrong by June, and the markup will keep repeating the old list long after the page has changed. Treat structured data as part of the content, not as a one-time technical task. When a price or a person changes, the markup changes in the same edit.

Test before and after

Validate each template with a structured data testing tool, then check the enhancements reports in Search Console after a few weeks. Errors there are specific: a missing field, an invalid date format, a price missing a currency. Fix them at the template level so every page inherits the correction.

Keep one example URL per template in a document, with the date it was last validated. That page is your regression test after any site change.

Maintenance is the real work

Schema drifts when a site changes. Prices update, staff leave, opening hours shift for a holiday, and the markup keeps the old values. Add schema checks to your quarterly site review, and put the fields that change most often, such as price and availability, in the same system that updates the page content.

Implementation checklist

  • List the page templates on the site and the single schema type each one needs.
  • Confirm every marked-up fact is visible to a normal visitor.
  • Use the same business name, address, and phone as your other listings.
  • Validate one URL per template and record the date.
  • Check the enhancements reports in Search Console monthly.
  • Remove markup for reviews, ratings, or stock you cannot verify.
  • Re-validate after any template redesign.

Good markup is boring, accurate, and maintained by whoever edits the page. That is the whole point.