Schema Markup Guide: Which Types Matter and Which Are Noise

Schema markup is structured data you add to your website to help search engines understand your content. It uses a standardised vocabulary from schema.org. When implemented correctly, certain schema types trigger rich results in Google: star ratings, FAQ dropdowns, product prices, event dates, and more.

The problem is that schema.org lists over 800 types. SEO tools flag "missing schema" as an issue without distinguishing between types that affect search visibility and types that do absolutely nothing in the SERPs. This guide cuts through that noise.

How Google Uses Schema Markup

Google does not treat all schema equally. Some types trigger visible rich results. Some inform the Knowledge Graph. Some are read but produce no visible effect. And many are simply ignored.

Google maintains an explicit list of supported structured data types in their Search Gallery documentation. If a schema type is not on that list, Google may read it but will not produce a rich result from it. That does not mean it is useless, but it does mean you should not prioritise it over types that produce visible SERP enhancements.

Schema Types That Directly Impact Search Results

These are the schema types worth implementing because Google actively uses them to generate rich results, Knowledge Graph entries, or enhanced search features.

FAQPage

FAQPage schema can trigger expandable FAQ dropdowns directly in Google's search results. Each question and answer appears under your listing, taking up more SERP real estate and increasing click-through rates.

When to use it: On any page with genuine frequently asked questions. Blog posts, service pages, product pages. We use it on virtually every content page we build for partners.

Implementation tip: Each question must be visible on the page, not hidden behind a tab or accordion that requires interaction to reveal. Google's guidelines require that FAQ content is visible to users, not just present in the markup.

You can see this in action across our own site, including our GEO guide and every service page at ASPIRED Digital.

LocalBusiness

For any business with a physical location or service area, LocalBusiness schema is non-negotiable. It feeds into Google's Knowledge Graph and reinforces the data in your Google Business Profile.

What to include:

• Business name, address, phone number (matching your GBP exactly)
• Opening hours (use OpeningHoursSpecification)
• Geo coordinates (latitude and longitude)
• Business type (use the most specific subtype: Dentist, Plumber, LegalService, etc.)
• URL, logo, and social media links

Common mistake: Using the generic "LocalBusiness" type when a more specific subtype exists. Google's algorithms match specific types more accurately to relevant search queries. "Dentist" is better than "MedicalBusiness" which is better than "LocalBusiness".

Article and BlogPosting

Article schema helps Google understand your content's headline, author, publication date, and featured image. It can trigger the "Top Stories" carousel for news content and improves how your articles appear in standard search results.

Key properties:

• headline (your H1, under 110 characters)
• author (link to an author page or use Person schema)
• datePublished and dateModified
• image (at least 1200px wide for optimal display)
• publisher (your organisation)

Product and Offer

Product schema triggers rich results showing price, availability, review ratings, and more. If you sell products online, this is one of the highest-impact schema types available.

Required properties for rich results:

• name
• image
• offers (with price, priceCurrency, availability)

Optional but valuable: aggregateRating, review, brand, sku, gtin. The more product detail you provide, the more information Google can display in your search listing.

Review and AggregateRating

Review schema triggers star ratings in search results. Those gold stars dramatically increase click-through rates. They catch the eye in a wall of blue links.

Important restriction: Google only supports review schema on certain page types: products, local businesses, books, courses, events, recipes, and software applications. Self-serving reviews (reviewing your own business on your own homepage) violate Google's guidelines and can result in a manual action.

BreadcrumbList

Breadcrumb schema replaces the raw URL in your search listing with a clean, clickable breadcrumb trail. Instead of seeing "example.com/services/seo/technical-audit", users see "Home > Services > SEO > Technical Audit". This improves both click-through rates and user understanding of your site structure.

Implementation is straightforward and the benefit is immediate. If you have breadcrumbs visible on your site, add the schema to match.

HowTo

HowTo schema can trigger step-by-step rich results with images for each step. It works well for instructional content, tutorials, and process guides. Our technical SEO audit checklist is the kind of content where HowTo schema adds real value.

Event

If your business runs events, workshops, webinars, or courses, Event schema triggers rich results showing dates, location, ticket prices, and availability. This appears prominently in both search results and Google's dedicated Events search.

Schema Types That Are Mostly Noise

These are types that SEO tools often flag but that produce little or no visible impact in Google's search results.

Organisation

Organisation schema feeds the Knowledge Graph, but for most businesses, your Google Business Profile and Wikipedia entry (if you have one) are the primary Knowledge Graph sources. Adding Organisation schema to your homepage is fine. Spending significant time on it is not worthwhile unless you are a large brand trying to control Knowledge Panel information.

WebSite

WebSite schema with a SearchAction property can trigger a sitelinks search box in Google. But Google decides whether to show this based on your site's authority and relevance, not just whether the schema is present. For most small to mid-sized businesses, it produces no visible result.

WebPage

WebPage schema is extremely generic and does not trigger any rich results. Some SEO plugins add it automatically. It does no harm, but it adds no visible value either.

ImageObject and VideoObject (Standalone)

When embedded within Article or Product schema, image and video properties are valuable. As standalone schema on arbitrary pages, they rarely produce rich results. The exception is VideoObject on pages with embedded videos, which can trigger video thumbnails in search results. That specific use case is worth implementing.

SpeakableSpecification

This was designed for Google Assistant voice search results. It is currently limited to news publishers in the US. For most businesses, it does nothing.

How to Implement Schema Markup

There are three methods, and the right one depends on your technical setup.

JSON-LD (Recommended)

JSON-LD is Google's preferred format. You add a script block to your page's HTML head (or body) containing the structured data as a JSON object. It is clean, does not interfere with your visible HTML, and is easy to update.

WordPress Plugins

If you use WordPress, plugins like Yoast SEO, Rank Math, or Schema Pro can generate schema automatically. The risk is that plugins sometimes generate incorrect or bloated schema. Always validate the output rather than trusting the plugin blindly.

Manual Microdata

Adding schema attributes directly to your HTML elements. This works but is harder to maintain and more error-prone than JSON-LD. Avoid this approach unless you have a specific reason for it.

Validating Your Schema

After implementing schema, test it before relying on it.

• Google Rich Results Test: Shows which rich results your page is eligible for and flags any errors or warnings. This is the most important validation tool.
• Schema.org Validator: Checks your markup against the schema.org specification. Useful for catching syntax errors.
• Google Search Console: The Enhancements section shows schema errors and warnings across your entire site over time. Check this monthly.

Prioritisation: What to Implement First

If you are starting from zero, implement in this order:

• First: LocalBusiness (if you have a physical location) and BreadcrumbList
• Second: FAQPage on your key content pages
• Third: Article/BlogPosting on your blog
• Fourth: Product and Review schemas (if applicable)
• Fifth: Everything else based on your specific content types

The first three will cover the majority of the available benefit for most service businesses. Do not let the remaining 800+ schema types distract you from getting these right first.

Frequently Asked Questions

Does schema markup directly improve rankings?

Google has stated that structured data is not a direct ranking factor. However, the rich results it triggers (star ratings, FAQ dropdowns, breadcrumbs) significantly improve click-through rates. Higher click-through rates mean more traffic from the same ranking position. And there is ongoing debate about whether user engagement signals from rich results indirectly influence rankings over time. Even without a direct ranking boost, the increased SERP visibility makes schema worth implementing.

Can incorrect schema markup hurt my site?

Yes. If your schema contains misleading information (fake reviews, incorrect prices, schema for content that does not exist on the page), Google can issue a manual action that removes all rich results for your site. Spammy schema is treated like any other form of webspam. Keep your markup accurate and ensure it reflects content that is genuinely present on the page.

How often should I update my schema markup?

Schema should be updated whenever the content it describes changes. If you change your business hours, update the LocalBusiness schema. If you change product prices, update the Product schema. For Article schema, update the dateModified property when you significantly revise content. Beyond content changes, audit your schema quarterly using Google Search Console's Enhancement reports to catch any errors that have crept in.

Do I need schema markup on every page?

No. Focus on pages where schema produces a visible benefit. Your blog posts benefit from Article and FAQPage schema. Your service pages benefit from LocalBusiness and FAQPage. Your product pages benefit from Product and Review schema. Utility pages like your privacy policy or terms of service do not need schema because they are not competing for search visibility.