Hello,
If this isn't the correct place to post this, my apologies.
After Google's most recent core update I've been going through the Search Console checking how my sites, one site version 1.0.8.4 and the other 1.0.7.15, have been affected. Under the Enhancements >> Products section I notice some issues were detected with product schema. I advise everyone to check Google Search Console.
So my question is this an issue with the Product Schema JSON-LD module or somewhere else in the code? Does this module need revision, and if so, is it in the making?
Thank you for reading.
Questions about Product Schema JSON-LD module. Screenshots included
-
ecartz
- Core Team
- Posts: 3084
- Joined: Tue Nov 05, 2019 6:02 pm
- Phoenix Version:
- Has thanked: 4 times
- Been thanked: 208 times
Re: Questions about Product Schema JSON-LD module. Screenshots included
Only products on special should have a priceValidUntil. So if your products are not on special, then it's the warning that's broken. If you just want the warning to go away, give the product a permanent price and a special price.
The aggregateRating and review fields only apply if your product has at least one review. So add a review to make the warning go away.
I'll look into brand, url, and sku.
The aggregateRating and review fields only apply if your product has at least one review. So add a review to make the warning go away.
I'll look into brand, url, and sku.
-
lecarlb
- Contributor
- Posts: 316
- Joined: Mon Oct 26, 2020 5:26 pm
- Phoenix Version:
- Has thanked: 48 times
- Been thanked: 9 times
Re: Questions about Product Schema JSON-LD module. Screenshots included
Thank you for your reply and checking on this.ecartz wrote: ↑Mon Jun 28, 2021 2:04 am Only products on special should have a priceValidUntil. So if your products are not on special, then it's the warning that's broken. If you just want the warning to go away, give the product a permanent price and a special price.
The aggregateRating and review fields only apply if your product has at least one review. So add a review to make the warning go away.
I'll look into brand, url, and sku.
-
14Steve14
- Senior Contributor
- Posts: 923
- Joined: Fri Oct 25, 2019 7:01 pm
- Phoenix Version: v1.0.9.1
- Has thanked: 17 times
- Been thanked: 103 times
Re: Questions about Product Schema JSON-LD module. Screenshots included
@ecartz Has there been any progress on these warnings?
I am getting lots of these in Google Search console. I am not worried about all of them but things like Brand should be filled as all products have a manufacturer listed.
I am getting lots of these in Google Search console. I am not worried about all of them but things like Brand should be filled as all products have a manufacturer listed.
You do not have the required permissions to view the files attached to this post.
-
heatherbell
- Senior Contributor
- Posts: 2540
- Joined: Mon Oct 07, 2019 4:39 am
- Phoenix Version:
- Has thanked: 35 times
- Been thanked: 243 times
Re: Questions about Product Schema JSON-LD module. Screenshots included
Looking at https://schema.org/Product
brand and manufacturer are different properties and only manufacturer is shown in ht_product_schema.php
- tessthepup
- Certified Developer
- Posts: 383
- Joined: Mon Mar 01, 2021 5:55 pm
- Phoenix Version:
- Has thanked: 47 times
- Been thanked: 62 times
Re: Questions about Product Schema JSON-LD module. Screenshots included
Hi Guys,heatherbell wrote: ↑Wed Oct 20, 2021 10:28 amLooking at https://schema.org/Product
brand and manufacturer are different properties and only manufacturer is shown in ht_product_schema.php
Was this ever progressed as I am having the same issues. Do we need to rename manufacturer to brand or add an extra tag for brand
After a bit of reading on the Big G the alerted fields are optional so do we need to bother?
- burt
- Core Team
- Posts: 4561
- Joined: Tue Oct 29, 2019 9:37 am
- Phoenix Version: v1.1.0.8
- : Buy Me A Beverage
- Has thanked: 252 times
- Been thanked: 413 times
Re: Questions about Product Schema JSON-LD module. Screenshots included
I never bothered with coding for all the optional fields. There seemed no point at the time when the list of other to-do's was so long.
You would need to worry about about "red" errors, but "orange" warnings is advice only.
You would need to worry about about "red" errors, but "orange" warnings is advice only.
I am not here to build for you.
I am here to build with you. Let's help each other.
I am here to build with you. Let's help each other.
- tessthepup
- Certified Developer
- Posts: 383
- Joined: Mon Mar 01, 2021 5:55 pm
- Phoenix Version:
- Has thanked: 47 times
- Been thanked: 62 times
Re: Questions about Product Schema JSON-LD module. Screenshots included
Thank you Gary.
I do have this error as well
Custom query parameter not defined in target URL
-
lecarlb
- Contributor
- Posts: 316
- Joined: Mon Oct 26, 2020 5:26 pm
- Phoenix Version:
- Has thanked: 48 times
- Been thanked: 9 times
Re: Questions about Product Schema JSON-LD module. Screenshots included
@ecartz or whomever.
If adding products to Facebook, they will automatically add, update or delete products if the product schema is correct. My only issue is "id" or sku.
After running a scan, Facebook can detect both Open Graph and JSON-LD. They say the only error is missing id. I looked at both header tag modules and there isn't anything indicating id or sku in the codes.
It looks less time consuming to add sku code to open graph. Is this an easy tweak? If so, will you please reveal code to add to at least open graph? When you get time please.
Thank you.
If adding products to Facebook, they will automatically add, update or delete products if the product schema is correct. My only issue is "id" or sku.
After running a scan, Facebook can detect both Open Graph and JSON-LD. They say the only error is missing id. I looked at both header tag modules and there isn't anything indicating id or sku in the codes.
It looks less time consuming to add sku code to open graph. Is this an easy tweak? If so, will you please reveal code to add to at least open graph? When you get time please.
Thank you.