SEO and structured data
- Keep storefront HTML structure clean and streamlined.
- Inline CSS and
!importantare not permitted in ways that break maintainability or override core semantics (see also Storefront, performance, and errors). - Public content pages intended for indexing must integrate with
sitemap.xmland provide valid canonical tags, meaningful meta descriptions andtitletags (via Administration or snippets). Private pages, tokenized links and utility endpoints must not be included merely because they have a storefront URL. - All images need meaningful
alttext (or media manager defaults). - All links need meaningful
titleattributes where appropriate. - Do not use
<h1>–<h6>in templates that are served with<meta name="robots" content="index,follow">for non-content chrome; you may use something like<span class="h2">for visual hierarchy instead. - Do not break Storefront SEO, structured data, or canonical logic that Shopware provides.
Rich snippets (home, listing, product)
Required when the extension changes products or product pages:
- Structured data (schema.org) must stay valid.
- Existing rich snippets must not break; new or changed content must be marked up correctly.
- Applies to product, category, and home templates as relevant.
Storefront XHR and non-indexable routes
- XHR and similar requests must work without errors.
- Set response header
X-Robots-Tag: noindex, nofollowon URLs that must not be indexed, including relevant invalid or expired-link responses. See Google’s robots meta tag / X-Robots-Tag documentation. - Indexing directives do not restrict access. Protect private resources through authentication and ownership checks.
External links
Use target="_blank" together with rel="noopener".
Lighthouse and structured-data checks
Run Google Lighthouse before and after activating the extension. No new console errors; avoid significant regressions in the SEO category when your extension touches markup.
Rich-result and schema checks
Use Schema Markup Validator and Google’s Rich Results Test on home, category, and product detail pages. Cover cases such as: available and unavailable products, products without reviews, single and multiple reviews, varied ratings, out-of-stock, future release dates, and product attributes (EAN, MPN, dimensions, weight) where applicable. Watch for duplicate structured data and regressions after your changes.