Which Structured Data Types Should Each Page Template Get?

Structured data is a standardized format for describing what a page contains, such as a recipe's ingredients or a product's price.

Google uses it to understand your content and can show it as a rich result, a more engaging search appearance than a plain text link.

The practical question for most teams is not whether to add it, but which types belong on which page template.

This article maps the common templates on a marketing or commerce site to the structured data types Google documents, and explains how to decide what to implement first.

What structured data can and cannot do

Adding structured data can make a page eligible for rich results.

It does not guarantee any specific appearance.

Google states that a text result may display differently depending on the device, the query and other factors.

You will not see a text result that includes every possible visual element.

Two rules from Google's documentation shape every decision in this article.

First, the structured data on a page must describe content that is visible to that page's users.

Do not create blank pages just to hold markup, and do not mark up information the visitor cannot see.

Second, validate with the Rich Results Test during development and monitor the Rich result status reports after deployment.

Templating or serving issues can break markup after launch.

Site-wide types every template can carry

Some types are not tied to one template.

They describe your site and organization, so they can appear on many or all pages.

• Organization. Information about your organization, such as logo, legal name, address and contact details, can show up in knowledge panels and other visual elements like attribution.
• Breadcrumb. Breadcrumb markup indicates a page's position in the site hierarchy and controls the trail shown in search results.
• Site name. You can provide the site name shown with your results using structured data.

Because these describe the site rather than a specific page, they are usually implemented once in a shared template or layout.

Getting them right first means every result, rich or plain, can carry correct attribution.

Blog posts and news articles

Article markup applies to news, sports and blog articles and can surface in features such as larger-than-thumbnail images.

If your posts embed video, Video markup adds video information to search results, with options to specify video segments and thumbnails.

If you publish audio news content, Speakable lets applications identify news content to read aloud on Google Assistant-enabled devices.

Byline dates also matter here.

Google estimates when a page was updated or published, and you can provide that date explicitly rather than leaving it to estimation.

Product and category pages

Product markup covers information about a product, including price, availability and review ratings.

Review snippet markup adds a short excerpt or an average rating, and Google lists it as applicable to products among other types.

Google's ecommerce guidance treats structured data as a way to help Google understand and appropriately present your content, which helps shoppers find your site and products.

Category and listing pages are a different case.

Google's Carousel feature displays rich results in a sequential list or gallery from a single site.

It must be combined with Recipe, Course list, Restaurant or Movie.

A generic product grid does not map to a documented carousel type.

On category pages, use clean internal linking and accurate breadcrumbs instead of forcing markup that does not fit.

Local business and location pages

Local business markup displays business details in the Google knowledge panel, including open hours, ratings, directions and actions to book appointments or order items.

If a location page also collects customer reviews, review snippet markup applies to local businesses as well.

Event, job and course pages

Several templates map directly to a single type:

• Event. An interactive rich result showing organized events people may attend at a particular time and place.
• Job posting. An interactive result for job seekers; the job search experience can feature your logo, reviews, ratings and job details. If you publish hiring reviews, employer aggregate rating is an evaluation of a hiring organization compiled from many users.
• Course list. A list of educational courses from the same provider, including title, provider and short description.

These types are template-specific in a strong sense: the markup only makes sense on pages that genuinely contain that content.

An event page without a date and venue has nothing valid to mark up.

Support, FAQ and community pages

Q&A markup is for pages containing one question followed by its answers.

Discussion forum markup covers user-generated threaded or non-threaded discussion about a topic.

If your help center or community platform generates these page shapes, the markup usually belongs in the platform's templates rather than added page by page.

Recipes, movies and software

Some content types have dedicated markup even though they are less common on B2B sites:

• Recipe. Displays as an individual rich result or part of a host carousel.
• Movie. The movie carousel helps users explore lists of movies, with details such as title, director information and images.
• Software app. Information about an app, including rating information, a description and a link.
• Vacation rental. Name, description, images, location, rating and reviews for a vacation property.
• Dataset. Large data sets that appear in Google Dataset Search.

Profile and about pages

Profile page markup is for a page that primarily focuses on information about a single person or organization affiliated with the website.

Founder and team member pages are the natural fit.

Organization markup, covered above, handles the company-level details.

A decision process for your own templates

Rather than memorizing the full list, work through your templates in order:

1. List your templates. Most sites have fewer than ten: home, article, product, category, location, event, and so on.
2. Match each template to visible content. Ask what a visitor can see on that page. A price on the page supports Product markup; a published event date supports Event markup. If the answer is generic prose, the site-wide types may be all that fit.
3. Check Google's feature list. Google's structured data gallery documents which types it supports and what each one requires. Rely on Google's documentation as definitive for Google Search behavior rather than the schema.org documentation, since schema.org contains attributes Google Search does not require.
4. Validate before and after launch. Use the Rich Results Test during development, then watch the Rich result status reports, because pages can break after deployment due to templating or serving issues.

Where to start when time is limited

Start with the types that match your highest-value templates and have visible content to describe.

For a commerce site, that is usually Product and Review snippet on product pages plus the site-wide Organization and Breadcrumb types.

For a content-led site, it is Article markup on posts plus the same site-wide layer.

Google's case studies report measured gains, including Rotten Tomatoes measuring a higher click-through rate on pages enhanced with structured data.

Your results depend on your content and queries, so treat those figures as context rather than a forecast.

Skip markup that does not match visible page content.

Invalid or misleading markup risks a manual action, and markup for content users cannot see violates Google's guidelines directly.

A page with no matching type is better served by clear titles, breadcrumbs and internal links than by forced schema.

Keeping markup healthy over time

Structured data is not a one-time project.

Template changes can silently remove required properties, which is why Google recommends monitoring the status reports after deployment.

When you redesign or migrate templates, re-run validation as part of the launch checklist.

If you coordinate SEO with broader automation and reporting work, the same template inventory feeds other decisions.

One example is which sitemap extensions to enable per content type.

The short version: inventory your templates, match each to documented types describing its visible content, implement the site-wide layer everywhere, and validate continuously.

That sequence turns a long feature list into a small, checkable plan.

For related decisions, see which sitemap extensions to enable per content type, whether lazy loading content is safe for SEO, and which single-object report to build first.

• Google's structured data feature gallery lists every type Search supports and links to each implementation guide.
• The visual elements gallery explains how attribution, breadcrumbs, byline dates and rich attributes appear in results.
• The introduction to structured data covers the format, the visibility rule and validation tooling.
• Google's ecommerce best practices describe how sharing product data and site structure helps shoppers find your products.

How Meshline can help. Connect automation, Organic Marketing (demand generation), and customer lifecycle management (Revenue Intelligence).

Bring topic planning, content publishing and performance feedback into the conversation about your workflow. Book a Meshline demo.