Product Schema Markup for Manufacturers: Setup Guide

Product schema markup is a block of code that describes, in a language Google understands, what each catalog page offers: name, image, description, manufacturer and identifiers. It does not guarantee a better ranking, but it helps the search engine interpret your content and can unlock rich results. Here is how to implement it in six steps.

Before you start

• Choose the JSON-LD format, the one Google recommends, which sits in a separate script apart from the visible HTML.
• Have the information already displayed on the page: the code may only describe what the visitor can really see.
• Pick one product page and the homepage to test first.

Step by step

1. Mark up the company with Organization on the homepage: name, logo URL, website, phone and official social profiles. This helps consolidate brand identity.
2. Mark up each product page with Product: name, description, image, brand, sku or mpn (manufacturer part number) and url. Use the same data that appears in the text.
3. Add the offers block only if there is a public price or visible availability. If the product is quote-only, leave offers out instead of inventing a value.
4. Mark up the visible questions and answers with FAQPage. Every question in the code must exist, with the same wording, in the page content.
5. Validate with Google's Rich Results Test and the schema.org validator, fixing errors and warnings.
6. Publish and follow the enhancements reports in Search Console, which flag errors at scale.

A simplified Product example

In essence, the script carries the schema.org context, the Product type, and fields such as the pump name, image URL, short description, brand and mpn. The recommended approach is to generate this code automatically from your catalog fields rather than writing it by hand for each item, which prevents mismatches between visible text and markup.

Doing it for large catalogs

With hundreds of products you cannot edit manually. Build a template that fills the JSON-LD from fields you already store: name, image, description, part number. On WordPress, SEO plugins handle part of this; for more custom setups, a developer can add the logic to the theme. See how it works in a structured digital catalog.

Mistakes worth avoiding

• Marking up ratings or reviews that are not on the page: it violates Google's guidelines and can cause a penalty.
• Filling in a zero or made-up price to look complete.
• Duplicating data blocks, one from the theme and one from a plugin, with conflicting information.
• Describing content that users cannot see.
• Forgetting to update the code when a product changes.

What to expect and how to measure

Rich results are not guaranteed: Google decides when to show them. The safest gain is clarity for the search engine. Track search appearance and valid-item reports in Search Console, and compare clicks and impressions of marked-up pages before and after.

If you have few products, start with just Organization and Product on your top five. Once validated, replicate the template across the rest of the catalog.

Frequently asked questions

Does structured data improve Google rankings?

Not directly. It helps Google understand the page and may enable rich results, but it is not a guaranteed ranking factor.

Can I use Product without a price?

Yes. If the product is quote-only, omit the offer block rather than entering a value visitors cannot see.

How do I test that it is correct?

Use Google's Rich Results Test and the schema.org validator, then follow the reports in Search Console.