Magento SEO: Settings, Product Data and a Checklist for Magento 2

Magento SEO is the work of configuring Magento 2 (Magento Open Source and Adobe Commerce) so that search engines find one clean URL per product and category, and of filling the product data that those pages are built from. Magento ships with the settings you need: URL keys, URL rewrites, canonical tags, meta fields per store view, an XML sitemap and robots.txt. Several of them are switched off or set to a risky value by default.

The short answer: turn on canonical tags for products and categories, keep category paths out of product URLs, keep simple products that belong to a configurable product out of the catalog, write the URL key, meta title and meta description per store view, add hreflang for multilingual stores, and check what your theme outputs as structured data. This guide covers the Magento-specific settings and data. For the general method, see our ecommerce SEO audit and the field-by-field guide to product page SEO.

The Magento SEO settings to check first

Most of the catalog settings sit under Stores > Settings > Configuration > Catalog > Catalog > Search Engine Optimization. The Adobe configuration reference describes each field. The defaults below come from the Magento 2.4 Catalog module configuration, so a fresh install starts here unless your agency changed them:

Two more places matter. Under Content > Design > Configuration, the HTML Head section holds the default page title, title prefix and suffix, and the Search Engine Robots section holds the Default Robots value and the custom robots.txt instructions. A staging site copied to production with NOINDEX, NOFOLLOW still set is one of the most expensive Magento mistakes there is. Under Marketing > SEO & Search you find URL Rewrites, Search Terms and the Site Map, where you generate the XML sitemap per store view.

The product fields that drive Magento SEO

Open any product and expand the Search Engine Optimization section. According to the Adobe product settings documentation, it has four fields, all with Store View scope:

• URL Key: the product's address, lowercase with hyphens and without the suffix. Magento builds it from the product name when you leave it empty.
• Meta Title: shown in the browser tab and as the search result title. Adobe advises a unique title under 70 characters.
• Meta Keywords: Google has said since 2009 that it does not use the keywords meta tag in web ranking. Do not spend time on it.
• Meta Description: the snippet text in search results. Adobe advises 150 to 160 characters, with a maximum of 255.

The rest of the page is product data too, and it carries more weight than the meta fields:

• Product Name: becomes the H1 on most themes. Write it as product type plus the attributes that set it apart, not as an internal code.
• Description and Short Description: unique text per product. Supplier copy that dozens of other stores also import gives Google no reason to rank your page.
• Images: each image has an Alt Text field in its detail panel. Fill it per image, describing what the image shows.
• Attributes: set Visible on Catalog Pages on Storefront for the specs buyers search for (material, capacity, dimensions), so they render in the More Information tab as crawlable text.
• Visibility: Catalog, Search for products that should have their own page. Not Visible Individually for products that only exist as part of another product.

Product Fields Auto-Generation: useful defaults, weak copy

Under Stores > Settings > Configuration > Catalog > Catalog > Product Fields Auto-Generation, Magento sets masks that fill empty fields. Out of the box, Mask for Meta Title is {{name}}, Mask for Meta Keywords is {{name}} and Mask for Meta Description is {{name}} {{description}}.

These defaults stop pages from going live with empty meta fields, which is good. They also produce a meta title that is just the product name and a meta description that starts with the name and then pastes in the first part of the long description, often supplier text. Treat the masks as a safety net. You can add fixed text and other placeholders to the mask, but the products that bring traffic deserve a written title and description. Our meta description generator gives you a draft to edit.

Configurable products: keep child simples out of the index

A configurable product in Magento is a parent with simple products as children, one per size and color combination. The simple products are separate catalog records with their own SKU. If they are set to Catalog, Search, each one gets its own URL with almost the same content as the parent, and Google has to guess which page to show.

The usual setup: set the children to Not Visible Individually, so the configurable parent is the only page, and put the variant attributes (color, size, capacity) in the parent's description and attribute list so the page still matches searches for a specific variant. When a variant needs its own landing page, for example because "black 750 ml" gets its own search volume, give it a real page with unique content rather than a visible duplicate of the parent. The product page SEO guide covers canonicals and structured data for variants in more detail.

Canonical tags only help when they are switched on, which is why the two canonical settings above matter. Google's documentation on consolidating duplicate URLs calls rel="canonical" a strong signal, not a command, so the cleanest fix is still to avoid the duplicate URLs in the first place.

Layered navigation: every filterable attribute is an SEO choice

Magento's layered navigation adds filter parameters to category URLs for every attribute set to Use in Layered Navigation. Left alone, a category with a dozen filterable attributes can produce thousands of crawlable combinations. We covered which filter pages to index, which to block and how to handle the parameters in faceted navigation SEO. The Magento-specific point: every attribute you mark as filterable is an SEO decision as well as a UX decision, so only make attributes filterable when their values are filled consistently across the category.

Layered navigation is also where Magento speed and crawling meet. Every filter combination a crawler can reach is a page your server has to render, and on a store without a warm full page cache those uncached requests are the slow ones. Settings fix the URLs; theme code, image sizes and caching fix the load time, which is why the ecommerce SEO audit checks speed per template rather than per site.

Store views and multilingual Magento SEO

Magento puts language in the store view. Product name, descriptions, URL key and all meta fields have Store View scope, so a Dutch store view can have its own URL key and its own meta title. If you leave them empty, the store view inherits the default values, which usually means English URL keys and English meta titles on a Dutch page.

The Magento admin has no hreflang setting for store views, so most multilingual Magento stores add the tags with an extension or a few lines of theme code. Whatever you use, follow Google's rules for localized versions: every language version lists itself and all the others, and if two pages do not point to each other, Google ignores the tags. That works only when every product has a translated URL key and a matching page in each store view. Our guide to multilingual SEO covers URL structures and translation quality.

What Luma prints as structured data, and the missing GTIN

The default Luma templates mark up part of the product page with schema.org microdata: the product name, SKU, main image, price and currency, and review ratings when reviews are on. Custom and third-party themes vary, so check your own product page in Google's Rich Results Test rather than assuming.

Magento Open Source also ships without a GTIN attribute: the core catalog setup includes manufacturer, but nothing for GTIN, EAN or UPC. If you sell branded products, create one (for example gtin as a text attribute in your attribute sets), fill it per simple product and make sure your theme or feed extension outputs it. Fill brand the same way. You can draft the JSON-LD for a product with the product schema generator and compare it with what your theme prints.

Worked example: one configurable product in two store views

Take an insulated stainless steel water bottle, 750 ml, sold as a configurable product in four colors, in an English and a Dutch store view. Here is a common starting point after a supplier import, next to the same product after a pass through the settings and fields in this guide:

The keep-cold and keep-hot hours in the example are product specs from the manufacturer. Copy them from the data sheet, never from a guess. Every other line is configuration or data entry: no theme work, no extension beyond hreflang.

Eight Magento defaults and data gaps that cost rankings

• Canonical tags left on No. It is the default, and many stores never change it.
• Category paths in product URLs. One product, three categories, three URLs.
• Visible child products. Every size and color of a configurable product indexed as its own thin page.
• Store views inheriting English URL keys and meta titles. The Dutch page ranks for nothing in Dutch.
• Robots set to NOINDEX after a staging copy. Check Content > Design > Configuration after every environment copy.
• Meta keywords as a task. Time spent on a field Google does not use.
• Masks as final copy. Thousands of meta descriptions that start with the product name and continue with supplier text.
• Filterable attributes with half-filled values. Filter pages that show five products out of fifty because the attribute is empty on the rest.

Ten-step Magento SEO checklist per store view

Most of this checklist is product data, and that is where WISEPIM helps. The Magento 2 connection imports your categories, products and configurable variants, lets you fill attributes, write and translate names, descriptions and SEO fields with AI and review them, then exports them to the store view you map for each language. To pick which products to fix first, SEO optimization puts Search Console clicks and impressions next to each product.