If Google Search Console shows a Product snippet error such as “Either offers, review, or aggregateRating should be specified,” do not immediately add fake prices or five-star ratings just to remove the warning.
First, find out why Google thinks the page contains a Product entity at all.
During a recent technical SEO audit, we found six Product snippet errors on pages that were not individual ecommerce product pages. Google was detecting Granite, Marble, Quartz Stone, Sandstone, Slate and Porcelain Tiles as separate Product entities.
The root problem was not six individual products. It was one site-wide schema configuration generating Product markup across the entire website. Once we found the source, the solution became much simpler.
For businesses dealing with indexing, structured data or crawl issues, Piyshef’s SEO services include technical SEO and Google Search Console diagnostics.
What Is a Product Snippet in Google Search?
Product structured data helps Google understand information about a specific product. Depending on the implementation and eligibility, Google may use details such as:
- Product name
- Price
- Availability
- Ratings
- Reviews
- Brand
- Images
- Offers
However, simply declaring something as a Product does not automatically make the markup complete enough for a Product rich result. That is where many Google Search Console errors begin.
What Does “Either Offers, Review, or AggregateRating Should Be Specified” Mean?
This is one of the most common Product structured-data errors. Google has detected an entity marked as a Product, but the markup does not contain enough information for the Product snippet experience.
A simplified incomplete example looks like this:
{
“@context”: “https://schema.org”,
“@type”: “Product”,
“name”: “Granite”
}
The page may therefore appear in the Product snippets report with a critical issue. Before adding more properties, ask one important question:
Is this actually a product page that should use Product structured data?
That question can prevent unnecessary or misleading schema implementation.
Product Schema Is Not Required on Every Website Page
Suppose your company sells natural stone. Your website may mention Granite, Marble, Quartz and Sandstone on the homepage, About page, Contact page, blog posts, service pages or factory page.
That does not mean every mention should become a Product entity.
Product structured data should represent what is genuinely present on the page. A website-wide schema template that automatically declares every product category as a Product can create structured-data errors across hundreds or thousands of URLs.
Schema therefore needs to be planned with your page templates and overall website design and development, not inserted once and forgotten.
The Real Product Schema Error We Found
During the website audit, Google Search Console showed six invalid Product items:
- Granite
- Marble
- Quartz Stone
- Sandstone
- Slate
- Porcelain Tiles
Each item showed the same critical issue: “Either offers, review, or aggregateRating should be specified.”
At first, it appeared that six separate Product Schema implementations needed to be fixed. Further investigation showed that all six errors came from one global schema configuration.
How to Fix Product Snippet Errors Step by Step
Step 1: Check the Affected Page in Google Search Console
Go to Google Search Console → Shopping or Enhancements → Product snippets. Open the error and select an affected URL.
Review the following details:
- Error type
- Detected items
- Number of invalid items
- Example fields
- Last crawl date
If Google detects six Product entities on a page where you expected zero or one, that is an important clue. Do not immediately add the missing fields. First determine where those Product entities are coming from.
Step 2: Test the URL With Google’s Rich Results Test
Run the affected URL through Google’s Rich Results Test. The test shows which structured-data entities Google can detect on the page.
You may expect to find Organization, WebSite and Breadcrumb markup. If Google also detects multiple Product entities, investigate their source.
On WordPress websites, structured data can come from several systems at the same time. The plugin you normally use for SEO may not be the only source.
Step 3: Check Your SEO and Schema Plugins
Review plugins such as:
- Rank Math
- Yoast SEO
- All in One SEO
- Dedicated schema plugins
- WooCommerce
- Review plugins
Check whether Product Schema is selected for the affected page or post type. If it is, confirm whether the page is genuinely about one specific product.
Do not stop after checking one plugin. In our audit, the dedicated structured-data plugin did not contain the Product entities causing the issue. The schema was coming from another location.
Step 4: Inspect the Live HTML Source
Open the affected page, right-click and select View Page Source. Search for application/ld+json and “@type”: “Product”.
If the names in the source match the invalid items reported in Search Console, you have found the markup Google is reading. The live source matters more than a plugin’s settings screen because it shows the final HTML delivered to users and search engines.
Step 5: Check Elementor Custom Code and Global Scripts
On Elementor websites, schema may be inserted through Elementor → Custom Code. Also check the theme header, footer scripts, tag managers and other global code areas.
In our audit, a custom-code entry called Website schema was configured with these settings:
- Location: Head
- Display condition: Entire Site
The code included several Product entities inside a makesOffer section. Because the display condition covered the entire site, the same six Products were injected into every page.
The broader lesson is important: a well-built website should keep global code, page-level markup and technical SEO settings clearly separated. This is one reason Piyshef focuses on integrated growth systems, as explained in How Piyshef Technologies Helps Businesses Grow Online in 2026.
Step 6: Do Not Add Fake Reviews, Ratings or Prices
One tempting response is to think, “Google wants aggregateRating, so let us add five stars.” Do not do this.
Never invent the following information simply to remove a Search Console warning:
- Ratings
- Reviews
- Review counts
- Prices
- Availability
- Offers
Structured data should represent genuine information that users can verify on the page. If the page does not contain real reviews, do not manufacture aggregateRating. If the business does not publish a fixed product price, do not invent one for schema.
The correct solution may be to remove the Product entity entirely.
Step 7: Decide Whether Product Schema Belongs on the Page
Ask these four questions before editing the markup.
1. Is This Actually a Product Page?
If the answer is no, remove the unnecessary Product markup.
2. Can a User Understand the Specific Product From This Page?
A genuine product page normally includes clear product-specific information such as:
- Product name
- Images
- Description
- Specifications
- Brand
- Model or SKU, where applicable
- Availability or enquiry details
An About page that briefly mentions six product categories is not automatically a suitable page for six Product entities.
3. Is the Product Information Visible to Users?
Structured data should match information users can access on the page. Do not create detailed hidden markup that is disconnected from the visible content.
4. Does the Page Need Product Rich-Result Eligibility?
Not every page does. Organization schema can describe the company, WebSite schema can describe the website, Breadcrumb schema can describe navigation and Product schema can remain on genuine product pages.
Step 8: Remove Incorrect Global Product Entities
In our case, the site-wide schema also contained useful details such as Organization, WebSite, LocalBusiness, address, contact information and business information. Those parts could remain.
We removed only the unnecessary Product entities inside the global makesOffer implementation. This prevented every page from declaring the same six Products.
Do not delete your entire schema because one section is wrong. Remove or correct the problematic entity.
Step 9: Validate the JSON-LD After Editing
Removing part of a JSON-LD block can create a syntax error. For example, an unnecessary trailing comma can make the markup invalid.
After changing the schema:
- Save the code.
- Check the JSON syntax.
- Inspect the live page source.
- Run the page through a structured-data test.
- Confirm that no malformed JSON remains.
A syntax error can cause Google to ignore the entire structured-data block.
Step 10: Purge Every Relevant Cache
This step is easy to miss. You may update the schema in WordPress and still see the old markup in Google’s test.
The old version may be stored in:
- WordPress cache
- Server cache
- CDN cache
- Elementor cache
- Browser cache
- Optimization-plugin cache
After making the change, purge all relevant cache layers and inspect the source again. Saving a WordPress page does not always mean visitors and Googlebot are immediately receiving the latest HTML.
Step 11: Search the Live Source for the Old Schema
If the problematic markup contained makesOffer, search for that exact text in the live source.
If it still appears after you removed it, the fix is not live. This is faster and more reliable than repeatedly clicking buttons in Search Console while the old HTML is still being served.
Step 12: Retest Before Clicking “Validate Fix”
Only after the live HTML is corrected should you test the page again. Confirm that:
- The incorrect Product entities are gone.
- The correct schema remains.
- The JSON-LD parses properly.
- The visible page content matches the markup.
- The Product errors are no longer generated.
Then click Validate Fix or allow Google to recrawl the affected URLs. Editing code is only the first step; the final live output is what Google evaluates.
When Should You Use Product Schema?
Product Schema makes sense for a page genuinely focused on one product. For example, a natural-stone website may have a dedicated page for Absolute Black Granite.
That page could include:
- Product name and images
- Description and origin
- Available thicknesses
- Finish options
- Sizes
- Applications
- Availability
- Brand or manufacturer information
This is much more suitable for a Product entity than a generic company page or a site-wide template.
Can B2B Products Without Public Prices Use Product Schema?
A B2B website can have genuine Product pages even when customers request quotations instead of buying through a shopping cart.
However, you should not invent price information just because Google supports price-based Product enhancements. First decide what structured data accurately represents the visible page and which search feature you are trying to qualify for.
If richer Product search eligibility is not appropriate, do not force the page into that format.
Product Schema vs Organization Schema
These schema types are not interchangeable.
Organization Schema
Organization schema describes the company. It may include:
- Business name
- Website
- Logo
- Contact information
- Social profiles
Product Schema
Product schema describes a specific product. It may include:
- Product name
- Image
- Description
- Brand
- SKU
- Offers
- Reviews
- Ratings
A common mistake is trying to list every business service or product inside Organization schema as a full Product entity. This creates unnecessary complexity and can trigger validation problems.
Product Schema vs Service Schema
SEO, website development, Google Ads and Local SEO are services, not physical products. Do not mark a service as a Product simply because you want a richer search appearance.
The page purpose should guide the markup. For example, Piyshef’s Local SEO services page explains a service, so its schema should accurately reflect that purpose.
Site-Wide Schema vs Page-Level Schema
A clean schema architecture usually separates markup by purpose.
Site-Wide Markup
- Organization
- WebSite
Relevant Business or Location Pages
- LocalBusiness, where appropriate
Blog Posts
- Article
- Breadcrumb
Product Pages
- Product, where genuinely appropriate
Service Pages
- Relevant service or business markup
This structure is cleaner than injecting every schema type across every URL.
Why Schema Errors Can Appear Across the Entire Website
Suppose one incorrect Product schema block is inserted into the head of every page and the site contains 500 URLs. You do not necessarily have 500 different schema problems. You may have one template problem appearing 500 times.
Instead of fixing the URLs individually, find the system generating the error. One global template, plugin setting or custom-code rule may be responsible for every affected page.
Schema Problems on WordPress Websites
WordPress websites can receive structured data from many sources:
- Theme
- Rank Math
- Yoast SEO
- WooCommerce
- Elementor
- Schema plugins
- Custom code
- Header or footer scripts
- Ecommerce plugins
- Review plugins
Duplicate or conflicting schema is therefore common. Do not assume that the first schema plugin you find is responsible. Always check the final HTML output because that is what Google reads.
Common Product Schema Errors
Product-related Search Console issues may include:
- Missing offers
- Missing review
- Missing aggregateRating
- Missing price
- Missing priceCurrency
- Missing availability
- Invalid rating values
- Incorrect price format
- Duplicate Product entities
- Schema on inappropriate pages
- Product markup that does not match visible content
- Old cached structured data
- Invalid JSON-LD
Each issue requires diagnosis before correction.
Do Schema Errors Affect Google Rankings?
Structured-data errors and organic rankings are not the same thing. A page can still be indexed without being eligible for a specific rich-result enhancement.
However, broken or misleading structured data can prevent Google from using that markup for enhanced search appearances. It can also reveal a wider technical implementation problem.
The goal is not to fix schema because it guarantees the first position. The goal is to help Google understand the content accurately and make eligible pages technically valid for relevant search experiences.
Do Rich Results Guarantee Better Rankings?
No. Adding structured data does not guarantee first position, rich results, star ratings or more traffic. Google decides whether an enhanced search feature appears.
Schema should support your content, not replace helpful information, authority, internal linking, search intent, backlinks, technical SEO or page experience. Our guide to SEO authority clusters in 2026 explains how related pages work together to build topical authority.
Product Schema and Internal Linking
Structured data does not replace website architecture. A strong product page still needs contextual internal links from:
- Product categories
- Related products
- Blogs
- Buying guides
- Homepage
- Navigation
Use descriptive anchor text whenever it fits naturally. For example, Absolute Black Granite communicates more than click here when it accurately describes the destination.
Schema helps search engines understand entities. Internal links help users and search engines understand the relationships between pages.
Product Schema for Local Businesses
Most local service businesses do not need Product markup across every page. A taxi company offering airport transfers, outstation taxis, sightseeing and local cab services should not automatically label every service as a physical Product.
Its SEO priorities are more likely to include local relevance, service pages, Google Business Profile optimization, reviews, location signals, internal linking and conversion-focused content. The same principle applies to other location-based companies looking for an experienced SEO company in Udaipur.
Product Schema for Travel Websites
Taxi, tour and travel websites often use WordPress templates that insert unnecessary schema.
Their more useful SEO structure is generally:
- Destination
- Service
- Route
- Tour package
- Booking intent
This structure is usually more meaningful than placing Product markup on every page. For a complete travel-focused approach, read Piyshef’s guide to SEO for taxi, cab and tour businesses.
Product Schema Troubleshooting Checklist
Before validating a Product error, check the following:
- Is this genuinely a Product page?
- How many Product entities does Google detect?
- Is Product markup visible in the live source?
- Which plugin or template generates it?
- Is Elementor Custom Code adding it?
- Is the schema applied site-wide?
- Does the markup match the visible content?
- Are the offers genuine?
- Are the reviews genuine?
- Is aggregateRating based on real reviews?
- Is the JSON-LD valid?
- Is an old schema version cached?
- Does the live source contain the corrected markup?
- Does the Rich Results Test detect the new version?
Only after answering these questions should you decide whether to correct the entity, remove it or validate the fix.
A Reliable Structured Data Diagnosis Process
Follow this order:
- Open the Search Console warning.
- Select an example URL.
- Identify the detected entity.
- Inspect the live page source.
- Find the schema generator.
- Decide whether the entity should exist.
- Correct or remove the markup.
- Purge every relevant cache.
- Check the live source again.
- Test the structured data.
- Allow Google to recrawl the page.
This process is safer than blindly adding missing fields.
What We Did Not Do
During the audit, we did not:
- Add fake five-star ratings
- Invent review counts
- Add fake prices
- Put Product Schema on every page
- Assume the schema plugin was responsible
- Delete all website schema
- Validate before checking the live HTML
- Fix six entities individually when one global rule created them
This is the difference between hiding a warning and fixing its root cause.
Product Schema Is Only One Part of Technical SEO
Structured data works alongside other technical requirements, including:
- Correct indexing
- Canonical tags
- Redirects
- XML sitemaps
- Clean internal links
- Correct HTTP status codes
- Mobile usability
- Crawlable website architecture
- Helpful content
When these systems are managed separately, problems are easily missed. Businesses comparing SEO, development and digital partners can use this guide to IT companies in Udaipur to understand how the services should work together.
Final Takeaway
When Google Search Console says “Either offers, review, or aggregateRating should be specified,” do not immediately ask which property you should add.
First ask: Why is this page being declared as a Product?
If it is a genuine product page, implement Product structured data accurately using real information. If it is not a product page, remove the unnecessary Product entity. If hundreds of URLs show the same error, look for a site-wide template, plugin or custom-code problem.
One incorrect schema block can create hundreds of Search Console warnings. Good technical SEO fixes the system creating the error, not only the warning displayed on the screen.
Frequently Asked Questions
What does “Either offers, review, or aggregateRating should be specified” mean?
Google has detected Product structured data, but the Product does not contain one of the relevant properties required for Product snippet eligibility.
Do I need to add reviews to fix the error?
Not necessarily. Never invent reviews. First determine whether Product structured data should exist on the page at all.
Can I add a fake five-star aggregateRating?
No. Ratings and review information must reflect genuine content and data visible to users.
Why is Product Schema appearing on every WordPress page?
A plugin, theme, Elementor Custom Code entry, header script or global template may be injecting Product markup site-wide.
Should a B2B website use Product Schema?
It can be appropriate for genuine product pages, but the implementation must accurately describe the information available on the page. Do not invent prices or reviews simply to satisfy a rich-result requirement.
How do I find which plugin is creating Product Schema?
Inspect the live HTML source first. Then check SEO plugins, schema plugins, WooCommerce, Elementor Custom Code, theme code and other scripts until you identify the source.
Should I click “Validate Fix” immediately after editing the schema?
No. First purge the caches, inspect the live source and test the page again. Validate only after confirming that the corrected markup is being served.
