SEO strategies for thematic pages - Bloomreach Experience - Open Source CMS

SEO strategies for thematic pages

Thematic pages benefit your site's SEO value, using white hat methods to help position your site near the top of search results on major search engines. To maximize that SEO value, we have some requirements and recommendations.

Each product in a thematic page must have a title, image, price, and a quick view description.

✅ All of these elements must be visible to both site visitors and search engines — don't hide them! However, you can make the description accessible to your site visitors with a view more button or link.

Render your thematic pages server-side.

✅ You can't integrate your thematic pages on the client side. Use server-side integration methods only.

Consume all elements passed in the header section of the response.

✅ Consume all of the elements passed in the header section of your thematic API responses, including title, canonical URL, H1, robots index tags, and noindex tags.

Implement your thematic pages in HTML.

✅ Implement your thematic pages in HTML, not AJAX or JavaScript. Search engines don't understand or value AJAX and JavaScript as highly as HTML content: implementing your thematic pages in AJAX or JavaScript works against your goals of raising your site's ranking in search results.

This strong recommendation is specifically about your thematic pages on your site, not your thematic API responses. We definitely recommend that you use JSON for your thematic API responses.

Don't style any of the elements on the page in a way that masks them from sight.

 Site visitors and search engine bots must see the same content on the thematic pages. Don't apply styles like font colors that are similar to background colors or use other techniques to hide elements from site visitors. Search engines consider this kind of concealment as a black hat SEO trick, and they diminish your site's ranking in search results accordingly.

 

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?