In the google search console detection, these two problems appeared, but my website has these two functions（I installed the comment plugin）, but why is it still warning?
Hope someone can answer it, thank you
Those warnings show up when you have product schema, but no aggregateRating or review defined within.
There’s a few schema apps that can take care of it for you, otherwise edit the theme code and manually edit schema. Depends on how your theme is coded as to how to go about this.
The reason you should fix this isn’t to remove the “warnings” in GSC. The actual benefit to having product reviews correctly setup in schema is that you can get organic ratings displayed which can help organic CTR.
Like this:
Sounds good, except, how do I “fix” this error? I’m using the Empire theme and am not seeing anywhere to add product reviews. BTW, the other error is Missing field “Review”
Fix by adding product schema containing correct aggregateReview schema.
From a quick Google search, I found this:
So here are some different approaches off the top of my head:
- Empire theme ‘default’ option
- Add SPR (Shopify Product Reviews) default app if not already using it.
- Add the review block in empire following that doc
- Schema should now work for products that have reviews in SPR
- Probably the easiest option to “fix” for you
- But thinking a little more broadly, the SPR review app has so many feature-gaps that I never recommend it.
- Use 3rd party review app + its own schema
- My go-to recommend is Judge.me for its balance of features and entry level price point.
- Add a review app that supports product and aggregateRating app
- Enable its “JSON-LD injection” feature
- Optional: Developer level - remove any duplicate schema from the theme files.
- Probably the best balance of difficulty and cost option.
- Use 3rd party review app + 3rd party schema app
- Similar to above, but disable the review app from injecting schema
- This is my preferred setup, done well with the right context and implementation - it can lead to much greater flexibility (things like FAQ schema, recipe schema on blog posts for eg) and richer, cleaner schema output overall.
- A little more challenging to get setup initially, but reasonable balance of price, complexity and benefit imo.
- Custom dev
- It’s always an option to build your own custom schema setup and integrate it into the theme, but you’d need a pretty strong reason for doing it this way, as it’s the most technically challenging out of these. But for a good developer it should be an easy task.
1 Like