In order for you to offer Google users an excellent user experience alongside your data feeds and thus be guaranteed a good return on investment by Google, your product data sent to Google Shopping must accurately describe your shop's product range and correctly reflect the current status of your goods on the landing pages.
Since in the past there were always problems with latency, i.e. differences in the data at Google and the data in the shop systems, Google has decided to make the product data directly readable from the target pages of the shops by means of micro data. The advantage is obvious, even if your data feed is already a certain time behind, Google can read out by crawling the URL whether the data is still up to date and if differences are found, Google can update instead of temporarily blocking the article in question in Google Shopping.
Google recommends the use of this microdata for Google Shopping landing pages.
This screenshot shows the microdata recommended by the Google Merchant Center as it can be embedded in the shop invisibly for the visitor.
OXID module: Google Merchant Center
Until now, the Google Merchant Center OXID module only added some views and setting levels to the backend of the OXID eShop. In the latest version of the module, it is now also possible to extend an OXID template of the article detail page in the shop with micro data that is invisible to visitors. The option can be switched on and off in the module settings in the OXID administration, depending on whether you have already integrated microdata or not. The microdata is attached to the template block "details_productmain_tobasket", where the "Add to cart" button is normally found. Visually, the code does not affect any design or functionality and is completely invisible. Only the source code contains the information for the Google Shopping Crawler. The implementation was carried out exactly according to Google's specifications.
