PrestaShop 1.7 SEO: Mastering Heading Structure in Classic Theme Product Miniatures

This community insight addresses a common SEO concern for PrestaShop 1.7 store owners using the Classic theme: inconsistent and semantically incorrect heading tags (

and

) for product titles within product miniature listings. A user identified that product titles were rendered as

on the homepage but

on other pages, disrupting the page's semantic hierarchy. The proposed solution involved replacing these heading tags with
elements while retaining the original CSS classes to preserve design.

The discussion clarified crucial aspects:

  • Core/JS Dependency: It was confirmed that PrestaShop's core and JavaScript do not rely on the actual

    or

    tag selectors for product titles in the Classic theme; styling and functionality are tied to CSS classes (e.g., .h3.product-title).

  • Modification Scope: The primary file for this change is themes/mon-theme/templates/catalog/_partials/miniatures/product.tpl. It was also confirmed that this single modification effectively covers product listings across the homepage (including the "Featured Products" module), new products, best sellers, and category pages, as these modules typically include product.tpl.
  • Best Practice: Modifying theme files should always be done within a child theme to ensure changes persist through theme updates.
  • SEO Impact: While heading-map tools might flag the original structure, the actual SEO impact on search engine rankings is likely minimal, as Google is sophisticated enough to understand content hierarchy beyond strict heading tag usage. However, implementing a cleaner semantic structure is still considered a good practice for overall site health and accessibility.

The Problem

The original poster, dagmara j, observed that product titles in the Classic theme's product miniatures displayed inconsistent heading tags. On the homepage, they appeared as

, but on category and other listing pages, they became

. This led to an abundance of

tags, potentially diluting the semantic value of primary page headings. For instance, a category page's main title might be

, followed by product titles as

, which is acceptable, but if other content also uses

, the hierarchy can become messy.

Proposed Solution & Community Validation

The user proposed modifying the product.tpl file to replace the dynamic

or

tags with a generic
tag, while ensuring the original styling is maintained by keeping the class="h3 product-title" attribute.

Original structure (example):


{block name='product_name'} {$product.name|truncate:30:'...'} {/block}

Proposed modification:


{block name='product_name'} {/block}

Community experts confirmed this approach is valid and safe. The styling in the Classic theme is primarily driven by the CSS class h3 product-title, not the semantic

or

tag itself. This means replacing the tag with a
will not break the visual presentation. Furthermore, a thorough check revealed no hidden PrestaShop core or JavaScript dependencies on these specific heading tags for functionality.

Scope of Modification

The modification primarily needs to be applied in themes/mon-theme/templates/catalog/_partials/miniatures/product.tpl. This file is widely included across various product listing contexts in the Classic theme, including:

  • Homepage (e.g., "Featured Products" module, which simply includes product.tpl)
  • New Products page
  • Best Sellers page
  • Category listing pages

Other related files like pack-product.tpl, brand.tpl, and category.tpl were confirmed not to contain relevant heading tags for product miniatures, simplifying the modification process to a single file.

Key Takeaways for PrestaShop Merchants and Developers

  • Child Theme is Essential: Always implement theme modifications in a child theme to prevent losing changes during PrestaShop or theme updates.
  • Semantic HTML vs. Visual Styling: Understand that in PrestaShop's Classic theme, visual styling for product titles is often decoupled from the semantic HTML tag, relying instead on CSS classes.
  • SEO Impact: While a cleaner semantic structure is good practice, don't expect dramatic ranking changes from this specific modification alone. Focus on overall content quality and other critical SEO factors.
  • Targeted Modifications: For template changes affecting multiple areas, identify the core partials being included to make efficient, centralized modifications.

This thread provides a clear, actionable solution for a specific technical SEO concern in PrestaShop, demonstrating the power of community collaboration in refining e-commerce store optimizations.

Start with the tools

Explore migration tools

See options, compare methods, and pick the path that fits your store.

Explore migration tools