SEO strategies for related categories, related items and related products widgets - Bloomreach Experience - Open Source CMS

SEO strategies for related categories, related items and related products widgets

Put widgets on your mobile pages.

✅ Widgets must be integrated on your mobile pages. Bloomreach supports widgets on mobile devices if your mobile URL structure after the domain name is the same as the structure for your desktop URLs. We use relative URLs in our widget links. If you have a separate mobile site, please ensure widgets are integrated on there as well.

Make server-side calls.

✅ Widget API calls are always server-side calls.

 Don't create client-side calls.

Use all three widgets.

✅ All three of the Related Categories, Related Items and Related Products widgets are required on the page to realize maximum value from the product.

Don't hide the widgets.

✅ Make sure that the widgets are visible upon page-load for both site visitors and search engines. 

 Don't hide the widgets inside a tab or other locations that require interaction with the page before they appear. Attempting to hide or obscure these widgets is contrary to the guidelines provided by search engines.

✅ Site visitors and search engine bots must see the same widget in the same location upon page-load.

✅ Make sure you show all elements of the widgets, including text and images, to both visitors who access your site and search engine bots who crawl your site.

 Never place the widgets in obscure locations on the site, such as the footer.

 Don't style widgets in a way that masks them from sight, such as using a font color that's similar to the background color.

Don't use JavaScript nor AJAX in widget content.

✅ Widgets must be implemented in HTML. Search engines don't understand or value JavaScript and AJAX as highly as HTML content.

 Don't implement widget content in JavaScript nor AJAX.

Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?