Canonical Tags in Magento (Adobe Commerce)

Are canonical tags on by default in Magento (Adobe Commerce)?

In Magento and Adobe Commerce, canonical tags are not something you get out of the box on catalog pages. Community consensus among Magento developers — this isn't a single documented Adobe statement so much as the near-universal, hands-on-the-admin-panel experience — is that both canonical settings ship set to No. A fresh Magento install, or a store nobody has revisited since setup, is very likely serving product and category pages with no rel=canonical tag in the head at all.

The two settings live under Stores > Configuration > Catalog > Catalog > Search Engine Optimization, and they're named plainly: "Use Canonical Link Meta Tag for Categories" and "Use Canonical Link Meta Tag for Products." Each is an independent toggle — you can enable canonicals for categories, products, both, or neither, and Magento treats them as unrelated switches even though they address the same underlying problem: Magento's URL structure often makes the same product or category reachable through more than one URL.

Treat "off by default" as the working assumption for any Magento site audit, since it's the consistently reported pattern rather than a documented guarantee — but confirm it by viewing source on an actual product or category page rather than assuming.

How to enable canonical tags for products and categories

Enabling canonical tags in Magento is a configuration change, not a code change — though a cache flush afterward is not optional. In the Admin panel, go to Stores > Configuration > Catalog > Catalog > Search Engine Optimization. You'll find the two toggles described above. Set the ones you want to Yes, then click Save Config.

Two details matter more than they look like they should:

• These settings are scoped per store view. If you run multiple store views — different languages or different brands under one Magento instance — check, and if needed set, this toggle separately for each one. Enabling it at the default scope doesn't guarantee every store view inherits it if a view-level override already exists.
• After saving, flush the cache. Magento's configuration and full-page cache will keep serving the old head markup until you clear it, which is the single most common reason someone enables the setting, checks the page, sees no change, and concludes the toggle doesn't work.

There is no admin field anywhere in Magento to hand-edit the canonical URL for one specific product or category. Once the toggle is on, the canonical tag is generated programmatically from the entity's URL key — there's no text box to override it the way there is in, say, a WordPress SEO plugin. Per-entity control beyond what Magento generates requires custom code or a third-party extension.

What Magento generates

Once "Use Canonical Link Meta Tag for Products" is enabled, Magento builds the product canonical from the store domain plus the product's URL key — and nothing else. It deliberately omits any category path, regardless of which URL a visitor actually used to reach the page. So if a product is browsable at both a category-nested URL and a flat URL, the canonical always points to the flat form, something like:

http://mystore.com/driven-backpack.html

That holds even if the page was requested at a category-prefixed path. The canonical tells search engines "index this bare URL," not "index whatever URL you happened to crawl."

For categories, enabling the equivalent toggle produces a canonical pointing to the category's full path — the category canonical is not stripped down the way the product canonical is.

This interacts directly with a separate setting, "Use Categories Path for Product URLs," which controls whether product URLs themselves are built to include the category path (for example /gear/backpacks/driven-backpack.html instead of /driven-backpack.html). When that setting is on, a single product becomes reachable at both the category-nested URL and the bare URL — and the product canonical still resolves to the bare form. The "Use Categories Path" setting changes what URLs Magento builds and links to; the product canonical setting changes what URL Magento tells search engines is authoritative. They aren't the same lever, and it's easy to assume turning on one automatically coordinates with the other.

Why the built-in setting doesn't fix layered navigation

This is the part that trips people up most: Magento's built-in canonical does not solve the layered-navigation (faceted search) duplicate-content problem, and it was never designed to.

Layered navigation — the filter sidebar that lets shoppers narrow a category by color, price, size, and so on — generates URLs with query string parameters: ?color=blue, ?price=10-20, ?sortby=price, and combinations of all three. Even with the built-in category canonical setting turned on, Magento does not strip these parameters when it builds the canonical tag for a filtered page. Instead, a filtered URL emits a self-referencing canonical — pointing at itself, filters and all — rather than back to the clean, unfiltered category page.

That means every color, price, and sort combination a shopper can construct through the filter sidebar is treated by the canonical tag as its own canonical page rather than a variant to be consolidated into the parent category. The built-in setting solves the product/category duplicate-URL problem it was built for; it does not solve the much larger surface area of filtered-URL duplication layered navigation creates.

Because Magento's own canonical mechanism won't do this work, practitioners typically reach for one or more of the following instead:

• Noindex on low-value filter combinations — letting them exist and be crawlable, but excluding them from the index.
• Robots.txt and crawl controls to keep bots from spending crawl budget on parameter combinations that add no unique value.
• Dedicated landing pages for filter combinations with real search demand — a proper "blue backpacks" category page, rather than relying on a filter parameter.
• Canonical-management extensions (Amasty, Mageplaza, and similar) that add parameter-stripping logic Magento core doesn't include.

One caution on older advice: Google deprecated the URL Parameters tool in Search Console in 2022, so any guidance that tells you to configure parameter handling there is out of date. Pagination canonicals (?p=2 and similar) are also handled inconsistently across Magento versions, so verify actual behavior on your version rather than assuming.

Common Magento canonical mistakes

• Assuming canonicals are on by default. They're generally not — check the two SEO toggles rather than assuming Magento is already handling this.
• Believing the category canonical toggle fixes layered navigation. It doesn't strip color, price, or sort parameters; filtered URLs still self-canonicalize.
• Turning on category-path product URLs without also enabling the product canonical toggle. This can leave a product reachable at multiple URLs with nothing tying them together.
• Relying on the canonical tag alone to control faceted-navigation crawling and indexing. It needs to be paired with noindex, crawl controls, or dedicated landing pages.
• Forgetting to flush cache after changing the setting. Old head markup can persist and make a correctly changed setting look like it didn't take effect.

Frequently Asked Questions