SEO Suite for Magento 2

Yes. Everything the module adds to the storefront is rendered on the server, in the page <head> or as JSON-LD, so it works the same on Luma and Hyvä (tested with Hyvä 1.5). It also switches off Hyvä's own BreadcrumbList JSON-LD and removes the schema.org microdata that Luma and Hyvä templates write, so search engines see one Product and one BreadcrumbList per page. The checkout is not touched.

The head data is built once per page render and stored in the full-page cache with the page. On product pages it uses a handful of indexed queries; the ItemList on category pages reuses the product collection the page has already loaded. The redirect router only runs on GET and HEAD requests that are not served from the full-page cache. No JavaScript files are added to the storefront.

Organisation (Organization, OnlineStore, Store or Corporation), WebSite with SearchAction on the home page, BreadcrumbList on product, category and CMS pages, Product with offers, identifiers, ratings and reviews, ProductGroup for configurable products (one hasVariant Product per child), ItemList on category pages, and an optional LocalBusiness on a CMS page you choose. Shipping details and a return policy can be added from your settings.

No tool can. Google decides whether to show rich results. The module outputs markup that follows Google's documentation for merchant listings, product variants, breadcrumbs and organisations, and the Structured Data Test page links each sample page to Google's Rich Results Test so you can check it yourself.

No. Templates fill empty fields on the storefront, for example {{name}}[ | {{category}}]. Text in square brackets is dropped when a variable inside it is empty. If you want the values stored in the catalogue (for feeds or other tools), the Meta Generator writes them into products, categories or CMS pages, with a preview mode.

Add redirects under CommerceGears > SEO Suite > Redirects, or import them as CSV (columns source,target, redirect_type,match_type,store,is_active,priority,note; only source and target are required). Wildcard rules such as blog/* to news/* carry the matched part over, and regular expressions are supported for anything more complex. Use the check-only mode to validate a file before importing it.

By default the module creates a 301 redirect for every URL the product had, to its deepest category (you can choose search results for its name, the home page, or nothing). A deleted category redirects to its parent category or the home page. If a new product or category later uses the same URL, the page is shown and the automatic redirect is skipped.

When rule A points to B and rule B points to C, visitors get one redirect straight to C. Loops between rules are ignored on the storefront, logged once a day in var/log/system.log, and reported in the admin when you save such an exact rule.

The log is capped at 50,000 entries. When it is full, only URLs already in the log are counted until old entries are removed by the daily clean-up (90 days by default) or in the admin. Patterns such as *.php and wp-* are not logged by default, and you can add your own.

Yes. Hreflang links connect the store views of a website (optionally across websites) with an x-default, in the page head and optionally in the XML sitemap. Store views can be left out, the language code can be set per store view, and CMS pages with different URLs can be paired with a Hreflang Key. Most settings work per store view.

Yes. With "Keep Store-wide NOINDEX" on (the default), a site whose Magento default robots setting is NOINDEX,NOFOLLOW is left alone, so the robots rules do not turn staging pages back to INDEX.

Magento Open Source and Adobe Commerce 2.4.6 to 2.4.9 on PHP 8.2 to 8.5 (Magento 2.4.6: PHP 8.2). The module requires commercegears/module-core, which Composer installs automatically.