← All posts
8 November 2026

Product structured data: 2.6% of Latvian shops show it on the homepage, Estonia 14.7%

Product markup was found on the homepage of 2.6% of Latvian shops, 14.7% of Estonian and 3.3% of Lithuanian. How to check your own product pages.

A shop’s product page shows a person the price, the photo and whether the item is in stock. A search engine reads the same page and has to guess, unless the page also carries a short machine-readable description of what it sells. The Baltic Web Audit, our near-census of the Latvian, Estonian and Lithuanian web in July and August 2026, looked for that description on the homepage of every shop it could identify. In two of the three countries it was almost never there.

In short

The product label, the structured data that tells a search engine a page sells a product, was found on the homepage of 2.6% of Latvian shops, 14.7% of Estonian and 3.3% of Lithuanian. That is 177 of 6,888 sites the audit classified as shops in Latvia, 1,280 of 8,708 in Estonia and 449 of 13,600 in Lithuania. It is a homepage reading and a minimum, so it understates shops that carry the markup only on product pages, but all three countries were measured the same way and Estonia is more than five times ahead. An owner can check their own product pages in Google’s Rich Results Test in a minute; fixing what it reports usually needs a developer.

What the audit found

Structured data is a set of labels a page can carry in its code to tell search engines what it is about. Some of it exists on 34.0% of Latvian homepages, 43.8% of Estonian and 40.7% of Lithuanian. The most common labels say only “this is a website”, “this is an organisation” or “this is a page”, the boilerplate an SEO plugin writes on install. Labels that describe the actual business are rare, and the rarest relative to need is the one for products. Every audit figure here is from the report’s basics chapter and its sector cuts.

LatviaEstoniaLithuania
Sites classified as shops6,8888,70813,600
Product label found on the homepage1771,280449
Share2.6%14.7%3.3%
Any structured data on the homepage (all sites)34.0%43.8%40.7%

Read the product figure for what it is. The audit made one full browser visit per site, to the homepage, and the report states that every detection count is a minimum: a check that does not fire is not proof of absence. Google’s markup for products that can be bought belongs on the product page itself, so a shop whose homepage carries no product label may still label every product page correctly. What the figure does show cleanly is the gap between countries. The same reading, on the same kind of page, finds product labels on one Estonian shop in seven and on one Latvian shop in forty.

What the markup does

Google’s product structured data documentation says that with it, “your product information can appear in richer ways in Google Search results (including Google Images and Google Lens)”, and that people “can see price, availability, review ratings, shipping information, and more right in search results.” Google splits it in two:

  • Merchant listings, for pages where customers can buy the product. These carry the detail a shopper compares on: price, shipping, returns, sizes.
  • Product snippets, for pages that describe a product without selling it, such as a review.

For a merchant listing, Google’s required properties are short: the product’s name, an image, and offers, the offer itself, with a price and a priceCurrency. Everything else, stock, shipping and returns, is recommended rather than required.

Two limits are worth knowing before spending money on it. Google’s structured data policies state plainly that it “does not guarantee that your structured data will show up in search results”, even when the markup is correct. And Google recommends a Merchant Center product feed alongside the markup: “Providing both structured data on web pages and a Merchant Center feed maximizes your eligibility to experiences and helps Google correctly understand and verify your data.”

The same shops have two other problems

The audit’s sector cuts put e-commerce at the bottom on two more measures. It is the slowest sector in every country, with an average mobile performance score of 62.5 in Latvia, 63.2 in Estonia and 61.5 in Lithuania, and a “poor” main-content load time on 85.8%, 86.0% and 85.1% of shops with a speed measurement. It is also the least likely to wait for permission: 91.5% of rendered Latvian shops, 91.1% of Estonian and 91.8% of Lithuanian set cookies before the visitor consents. Speed is covered in the six-second web and consent in cookies before consent.

What you can check yourself, and what needs a developer

Three checks need no developer:

  • Run one product page through the Rich Results Test. Paste the address of a product page, not the homepage. If the test detects merchant listings or product snippets, the markup is there; if it detects neither, it is not. Note anything it marks as an error.
  • Check the page source. Right-click the product page, choose View page source and search for "Product". A <script type="application/ld+json"> block containing it is the markup. Two such blocks describing the same product usually mean a theme and a plugin are both writing it.
  • Compare it with the page. The price and currency in the markup should be the price a customer sees. If they differ, Google is reading something your shoppers are not.

What needs a developer is everything the test turns up. On WooCommerce the core plugin already writes Product markup on single product pages, from the product page template (its source), so a WooCommerce product page with none has had that template replaced or the output switched off somewhere, and the fix starts with finding where. Missing images, prices or currencies come from how products are stored, variable products need variant markup, and shipping and returns details have to match the shop’s real policy. Changing WooCommerce’s output is done through its woocommerce_structured_data_product filter in code the shop owns, never in the plugin files, which the next update replaces. This is the kind of work our WooCommerce development covers.

Why we can say any of this

The figures come from a near-census rather than a sample. We measured 293,806 of the 306,872 Baltic domains in our frame across July and August 2026, from one fixed location, with a crawler that identified itself honestly on every request. Sector labels come from fixed rules where those are reliable and from a language model elsewhere, and any site the classifier was less than 0.7 confident about is reported as unclassified rather than guessed. Everything is published as an aggregate and no individual site is named beside a weakness.

If you want to know what your own shop tells search engines, send us the address and we will tell you what we see.

Tell us what’s broken.
We’ll tell you the truth.

Book a free call →
Reply within one business day · EN / LV
↑↓ navigate · ↵ open · esc close