Schema markup labels the people, products, articles, ratings, and media on your pages in a format search engines can interpret consistently. Google calls this structured data. It can make relevant content eligible for richer search presentations, but it does not improve the underlying quality of a page.
The visibility opportunity is real when markup fits the content. In a case featured in Google’s structured data documentation, Rotten Tomatoes added markup to 100,000 pages and measured a 25% higher click-through rate on enhanced pages than on unenhanced pages. Food Network marked up 80% of its pages and reported a 35% increase in visits, although neither result is a universal forecast.
Schema is not a ranking shortcut. It provides explicit information, creates eligibility for supported features, and may help a result communicate its value to someone deciding where to click. Perfectly valid code can still produce a standard blue link if Google considers that presentation more appropriate for the query.
Current support matters as much as technical validity. In 2025, Google retired seven lesser-used structured data displays without changing how the affected pages ranked. Build against Google’s current search feature documentation, not an old plugin menu or a list of every vocabulary available through Schema.org.
Product Markup and Merchant Result Eligibility
Product markup can turn a plain ecommerce result into a more informative entry with price, availability, ratings, shipping details, or return information. Your first decision is not which plugin to install. Decide which product experience matches what a visitor can actually do on the page.
An SEO agency reviewing a large catalog should separate editorial product content from pages where customers can complete a purchase. Google’s Product documentation treats these as related but distinct use cases: product snippets suit review-oriented or non-transactional pages, while merchant listings serve pages that sell the item directly.
Match the markup to the page’s commercial purpose
A product snippet may show review information, ratings, price, availability, or editorial pros and cons. A merchant listing can qualify for commerce-focused placements across Search, Google Images, popular product results, and shopping knowledge panels, with additional support for shipping, return policies, sizing, and product variants.
Start with a Product entity that names the exact item shown on the page. A purchasable page normally needs a valid Offer with accurate price and priceCurrency; add properties such as availability, url, itemCondition, brand, sku, gtin, images, and ratings only when the page and your source systems support them truthfully.
Do not apply one generic Product block to category pages, internal search results, or bundles that do not represent a specific offer. Google’s dedicated product snippet guide and merchant listing guide use different property combinations, so validate the actual template instead of copying a universal example.
Keep commerce data synchronized
Price and stock mismatches can make technically valid markup untrustworthy almost immediately. Compare the rendered page, JSON-LD, backend catalog, and Merchant Center feed for representative in-stock, out-of-stock, sale, variant, and discontinued products.
Google distinguishes active, strikethrough, and member pricing. Active prices should not carry a priceType; a strikethrough price belongs in a UnitPriceSpecification identified as StrikethroughPrice, while a member price uses validForMemberTier. Test promotional transitions before launch so an expired sale does not remain in the markup after the visible price changes.
Repeat the checks after product imports, theme releases, currency changes, and inventory migrations. Product markup should be a dependable output of your commerce data, not a static SEO layer that somebody remembers to update later.
Article Markup and Enhanced Search Presentation
Article markup helps Google identify who created a piece, when it was published or revised, which headline describes it, and which images represent it. Google supports Article, NewsArticle, and BlogPosting, so choose the most specific type that accurately describes the visible page.
The current Article structured data guide lists recommended rather than required properties. Useful fields include headline, author, datePublished, dateModified, and image, but a concise set of accurate fields is more useful than a long block that gradually becomes stale.
Make authorship and dates verifiable
Use a Person entity for an individual writer and an Organization entity when the byline genuinely belongs to an organization. Represent every visible author separately, add an author profile URL or sameAs reference where appropriate, and connect repeated entities with a stable @id so templates do not create conflicting versions of the same person.
Visible bylines, biographies, publication dates, and update dates should agree with the JSON-LD. Reserve dateModified for meaningful editorial changes rather than refreshing it whenever a template renders; a synthetic “fresh” date may pass a syntax test while weakening reader trust.
Images need similar care. Google recommends multiple crawlable, indexable, high-resolution images in 16:9, 4:3, and 1:1 aspect ratios, with each version reaching at least 50,000 pixels when width is multiplied by height. Each image should represent the article rather than displaying a generic logo or unrelated stock asset.
Treat Article markup as clarification, not admission
Article markup can help Google present stronger title, image, and date information across its properties, but it is not required for Google News features such as Top stories. Content quality, accessibility, editorial transparency, and policy compliance still determine whether a page deserves exposure.
Audit your CMS at the template level, then spot-check unusual pages such as guest posts, co-authored research, live blogs, sponsored content, and migrated archives. These edge cases often expose duplicate authors, impossible dates, missing images, or a BlogPosting block that describes a different canonical URL.
A human-first article page should make the same core facts obvious without requiring anyone to inspect its source. Schema reinforces that experience for machines; it should never be the only place where authorship or publication context exists.
Breadcrumb Markup and Result Path Display
Breadcrumb markup explains where a page sits within your information architecture. Google may use it to categorize a desktop result and replace a raw URL path with a more readable trail, giving searchers useful context before they click.
A BreadcrumbList contains an ordered itemListElement array. Each ListItem needs a position and name, with an item URL for linked levels; the final page can be represented without linking back to itself.
Model the path a person would recognize
Google’s breadcrumb guidance recommends a typical user path rather than a mechanical copy of URL folders. A product at /p/7842 might belong to “Home > Running Shoes > Trail Shoes,” even though those words never appear in the address.
Keep the visible breadcrumb, internal links, canonical URL, page heading, and structured trail logically aligned. The labels do not have to match word for word, but they should not describe competing hierarchies or send users to irrelevant parent pages.
Multiple trails are valid when a page belongs naturally in more than one route. A science-fiction award winner could sit under both “Books > Science Fiction” and “Literature,” provided each path reflects genuine navigation rather than an attempt to insert extra keywords.
Audit breadcrumb templates across page states
Test the deepest templates first because skipped positions and missing parent URLs often appear there. Check products assigned to several categories, articles moved between sections, localized paths, paginated archives, faceted pages, and pages whose title changes after JavaScript executes.
Pay close attention to canonicalization. A breadcrumb trail on a parameterized duplicate should describe the canonical page consistently, and every linked level should resolve without a redirect chain, soft 404, or accidental noindex directive.
Breadcrumb markup is simple enough to automate but visible enough to influence a person’s interpretation of the result. A clear hierarchy also makes the site easier to navigate after the click, which is the more durable benefit.
Video Markup and Video Feature Eligibility
Video markup helps Google discover a video and understand the information needed for video-oriented search features. Eligible media can appear in the main results, Video mode, Google Images, and Discover, but the page still needs to offer a useful viewing experience.
The strongest candidate is a dedicated, indexable watch page where the video is prominent and playable. Adding VideoObject to a thin article with a minor background clip does not turn the page into a strong video result.
Supply the properties Google can verify
Google’s current VideoObject documentation requires name, thumbnailUrl, and uploadDate. Recommended details include a unique description, ISO 8601 duration, contentUrl for the actual media file, or embedUrl for the player when the content file is unavailable.
Ensure Google can fetch the page, thumbnail, player resources, and media URL without a login or blocked request. Use a stable, representative thumbnail, keep dates and durations synchronized with the visible player, and avoid reusing one title and description across an entire video library.
A video sitemap can reinforce discovery, especially when playback assets sit on a separate host. Inspect representative URLs after deployment to confirm that Google detects both the page markup and the intended video rather than a decorative embed elsewhere in the template.
Add advanced features only when playback supports them
Clip can define named segments with precise start and end times. SeekToAction describes a timestamp URL pattern that lets Google identify key moments, but the player must support deep links and the video must be at least 30 seconds long for these features.
YouTube-hosted videos can use clear timestamps and labels in the YouTube description. Livestream publishers can nest BroadcastEvent for LIVE badge eligibility and use Google’s Indexing API at the start, end, and material update points; Indexing API support in this context is limited to livestream video pages.
Key moments are useful when they help someone reach a relevant section quickly. Artificial chapter labels, inaccessible timestamp URLs, or markup for segments that do not exist create friction for viewers and unreliable data for Google.
Review Snippet Markup and Rating Eligibility
Review markup can make an eligible result more informative with a rating, review excerpt, and aggregate summary. It also attracts shortcuts, which is why the gap between “valid JSON-LD” and “eligible review feature” matters so much here.
Google’s review snippet documentation supports specific reviewed types, including products, books, recipes, movies, software applications, events, and certain creative works. A Review describes an individual evaluation, while AggregateRating summarizes ratings collected for one specific item.
Publish ratings people can inspect and trust
An individual review needs a real author, a supported reviewed item or an appropriate parent entity, and a reviewRating with a numerical ratingValue. An aggregate needs a truthful ratingValue plus ratingCount or reviewCount; declare bestRating and worstRating when the scale differs from the default one-to-five range.
Every marked-up rating and review must be readily visible on the page. Do not hide a score in source code, mark up a category average as if it belongs to one item, select only favorable reviews, or aggregate ratings copied from other websites.
Self-serving business ratings have a specific restriction. Pages controlled by the reviewed LocalBusiness or Organization are ineligible for the star review feature, even when the business embeds a third-party review widget; eligible business-review publishers must collect ratings about other entities directly from users.
Validate eligibility before measuring impact
Test each template in Google’s Rich Results Test, fix critical errors, and investigate warnings that reveal missing useful information. Deploy to a small URL cohort, then use URL Inspection to compare the live rendered page with Google’s indexed version.
Monitor the relevant Search Console enhancement or shopping report after Google recrawls the pages. Report totals count structured-data items rather than URLs and provide a sample rather than a complete inventory, so maintain your own template-level crawl and inspect pages that appear to be missing.
Measure the outcome with matched page groups, not a celebratory screenshot of one rich result. Compare clicks, impressions, click-through rate, and average position across a meaningful pre- and post-launch period while accounting for ranking changes, seasonality, and concurrent content releases.
Prioritize the type with the clearest user value and cleanest source data, then expand after the first template remains stable. If you want a practical schema plan, implementation review, and measurement framework built around your site rather than a generic checklist, contact our team to arrange an audit.
About the author:
Adsy is a Content Marketing Platform with expertise in SEO, Digital PR Distribution & Content Distribution, founded in 2018. We started as a blog posting platform with a goal to continually develop our capabilities to offer a wide range of features to meet clients’ needs to improve SERP rankings, build high-quality backlinks, and broaden brand recognition.
