Related Products Block Breaks Rich Snippets Price on Product View

[hewgim]

Preconditions (*)

We are running on Magento 2.3.5-p1

When the product view related products block is generated after a cache clean, it appears that it generates cached price blocks for each of the related products (without any schema.org offer price rich snippets). If you then click on one of these products and go to the product view for that product, the main price field is loaded from cache, and therefore the schema.org offer price rich snippets are missing. We noticed this because Google was showing incorrect prices for our products as a result of the missing rich snippets.

Steps to reproduce (*)

Set up a simple product A with one related simple product B
Go to product A's product view
Clear the cache
Refresh product A's product view
Look in your web inspector tools at the main price field for product A and you will see the offers rich snippet
From product A's related products block go to product B
Look in your web inspector tools at the main price field for product B and the offers rich snippet is missing. I believe this is because the price block for product B was cached without the offers rich snippet when product A's product view was created.

Expected result (*)

The offers rich snippet should always be present on the main price field on the product view

Actual result (*)

The offers rich snippet is sometimes missing from the main price field on the product view which means that Google often displays incorrect prices on its search results.

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @hewgim. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant]

Hi @engcom-November. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[hewgim]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @hewgim. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @hewgim, here is your Magento Instance: https://68eca8f2b00f7e60c19e11e476cbee14-2-4-develop.instances.magento-community.engineering
Admin access: https://68eca8f2b00f7e60c19e11e476cbee14-2-4-develop.instances.magento-community.engineering/admin_b0c2
Login: 1416741c
Password: 71ceb0f56311

[hewgim]

I can confirm that this issue exists on the 2.4-develop instance. Not quite sure how this process works. I see that @engcom-November has self assigned this, so I'm not sure if there is anything else I need to do. I did run the 2.3.5-p1 code through a debugger and it looks to me like getCacheKeyInfo() in Magento/Catalog/Pricing/Render/FinalPriceBox.php needs to include a flag that indicates whether the price block includes the offers rich snippet or not.

[engcom-November]

Verified the issue on Magento 2.4-develop branch and the issue is reproducible:

Steps to reproduce:
Create a Simple Product A from admin and Save
Create another simple product B and add Simple A as Related Product to it and Save
Front-end - Open Simple Product B
Clear the cache - > bin/magento cache:flush
Refresh product B's product view
Inspect Element - Look in your web inspector tools at the main price field for product B and you will see the offers snippet
From product B's related products block go to product A
Look in your web inspector tools at the main price field for product A and the offers rich snippet is missing.
Note: This issue is happening after clearing Cache for existing Related products as well when viewed related product from main product.
Expected Results
The offers rich snippet should always be present on the main price field on the product view

Actual Results
The offers rich snippet is sometimes missing from the main price field on the product view which means that Google often displays incorrect prices on its search results.