Hyvä SEO: clean markup, structured data, crawl efficiency

Store owners often ask whether moving to Hyvä will improve their rankings. The honest answer is that Hyvä removes obstacles, but rankings still depend on content, links and technical care.

This post covers the technical SEO points we check on Hyvä stores: markup, structured data and how efficiently search engines can crawl the catalogue.

What Hyvä changes for SEO

Hyvä replaces Luma’s RequireJS, KnockoutJS, jQuery and LESS frontend with Tailwind CSS and Alpine.js. For SEO, three things follow from that:

• Content is in the HTML. Hyvä templates are rendered by PHP on the server. Product names, prices and descriptions are in the page source, not built later in the browser.
• Pages are much lighter. In our benchmark, Hyvä pages made 15 to 19 requests against 251 to 275 for Luma, with about 26 KB of JavaScript.
• Core Web Vitals are easier to pass. Mobile LCP was 1.5 to 1.6 seconds on Hyvä against 2.3 to 2.5 seconds on Luma, on the same server and catalogue.

Page experience is one signal among many. A faster store helps most where it improves what visitors do, such as bounce and conversion.

What Hyvä does not change: URL structure, meta data, canonical settings, sitemaps and robots rules. Those are Magento configuration and stay your responsibility.

Clean markup and headings

Hyvä templates are plain and readable, which makes it easy to keep the HTML tidy. A rebuild is a good moment to check the basics:

• One h1 per page, holding the product or category name.
• A logical heading order in descriptions and CMS content.
• Descriptive alt text on product images.
• Real links, with href attributes, for navigation and pagination, not click handlers only.
• Product and category text visible in the page, not hidden in tabs that load later.

Alpine.js tabs and accordions are fine, as long as the content is already in the HTML when the page loads.

Structured data: check, don’t assume

Structured data helps search engines understand products, prices, stock and breadcrumbs. It is also what makes rich results possible.

What a store outputs depends on the theme version, child theme overrides and installed modules. After a migration, we test real product and category pages rather than assuming the old markup carried over.

The types we usually check are:

• Product with name, image, description and SKU.
• Offer with price, currency and availability, matching what the page shows.
• BreadcrumbList on product and category pages.
• Organization and WebSite on the home page.

We prefer JSON-LD, added from a small block in the child theme, so it stays separate from the visual templates:

<script type="application/ld+json">
<?= /* @noEscape */ json_encode([
    '@context' => 'https://schema.org',
    '@type' => 'Product',
    'name' => $product->getName(),
    'sku' => $product->getSku(),
    'offers' => [
        '@type' => 'Offer',
        'price' => $product->getFinalPrice(),
        'priceCurrency' => $currencyCode,
    ],
], JSON_UNESCAPED_SLASHES) ?>
</script>

Avoid printing two different sets of product data from two modules. Conflicting prices or availability can stop rich results from showing.

Crawl efficiency on large catalogues

Search engines have limited time for each site. On Magento, layered navigation can create a very large number of filter URLs that waste it.

• Canonical tags. Enable canonical link meta tags for categories and products in the catalogue SEO settings.
• Filter URLs. Decide which filter combinations deserve to be indexed. Keep the rest out of the index and out of the sitemap.
• Product URLs. Choose whether product URLs include the category path, and stay consistent so one product does not live at many URLs.
• XML sitemap. Generate it per store view and include only indexable pages.
• robots.txt. Block search, checkout, account and cart paths.

Lighter pages also help here. Fewer requests per page means less work for every crawler visit. Our Magento SEO checklist covers these settings in more detail.

Speed, images and SEO together

Speed work and SEO work overlap more than most teams expect. A few points help both at once:

• Image file names and alt text. Descriptive names and alt text help image search, and they cost nothing in page weight.
• Light, correctly sized images. Serving WebP copies and loading the main image first improves LCP. See our product image strategy for Hyvä stores.
• Fewer third-party scripts. Every tag manager container, chat widget and tracking pixel adds weight. Hyvä’s lean base only helps if you keep it lean.
• Stable layouts. Width and height on images and reserved space for banners prevent layout shifts.

On a real Luma store with extensions and tracking, these extra scripts are often the reason scores are much lower than on a clean test install. The same can happen on Hyvä if old scripts are carried over.

Languages and hreflang

For stores with several languages or countries, hreflang tells search engines which version to show to which visitor.

Magento does not output hreflang tags by default, so this needs a module or a custom block that links each page to its equivalents in other store views. We cover the store setup in multi-language Hyvä stores.

Protecting rankings during a migration

A Luma to Hyvä migration changes the theme, not the catalogue. Your URLs can and should stay the same.

• Keep every product, category and CMS URL unchanged.
• Carry over titles, meta descriptions and on-page text.
• Compare structured data before and after on the same pages.
• Check that tracking and analytics still fire.
• Watch Search Console coverage and performance closely after launch.

When we migrate stores to Hyvä, we keep URLs and tracking intact and switch over at a quiet hour.

FAQ

Will Hyvä improve my Google rankings?

It removes technical obstacles and makes Core Web Vitals easier to pass. Rankings still depend on content, links and correct Magento SEO settings.

Is Hyvä content visible to search engines?

Yes. Hyvä renders pages on the server, so product and category content is in the HTML that crawlers receive.

Does a Hyvä migration change my URLs?

It does not need to. Hyvä is a frontend theme, so URLs come from the same Magento catalogue and rewrites, and they should stay the same.

Planning a migration and want to protect your rankings? See our Hyvä theme development service and our Magento SEO service.