Magento SEO and Adobe Commerce catalogue controls
Resolve Magento and Adobe Commerce SEO issues with scoped checks for URL rewrites, canonicals, layered navigation and product page output.
- Published
- Last updated
Magento SEO starts by matching catalogue settings to the correct store view, then checking the URLs and content your storefront actually serves. When a catalogue change creates duplicate product paths, inspect one affected product before changing settings across the store.
You’ll need access to catalogue and configuration settings, a safe test environment and someone who can restore the previous configuration or theme. Keep a record of the current values and affected URLs before saving changes. For checks on other platforms, use the platform SEO guides.
Identify the edition, store view and storefront
Identify whether you run Magento Open Source or Adobe Commerce, then record the installed version and the storefront that renders your pages. Adobe Commerce on cloud infrastructure and Adobe Commerce as a Cloud Service have different implementation guidance. A custom or headless storefront also needs its own rendering checks.
Adobe’s Commerce Storefront SEO guidance separates catalogue data from the HTML served by Edge Delivery Services. An Admin change alone doesn’t prove that a separate storefront publishes the new title or canonical.
Map the affected domain to its website, store and store view. A website contains stores, a store determines its root category and each store has one or more views. A view can carry translated product information. Adobe’s scope documentation explains which settings apply at each level.
The hierarchy doesn’t mean every field is editable at every level. Read the scope beside each setting. Under configuration inheritance, a lower scope uses the parent value until you override it.
For example, suppose a product’s default Meta Title is “Canvas weekend bag”. Its Australian view can inherit that title while another view has an explicit translation. Updating the default changes the inherited value, while the translated override stays separate. Check both pages after saving, including any title prefix or suffix added by the theme.
Set catalogue metadata and URL keys
Edit product metadata in the intended store view and check category metadata separately. Product and category forms can show inherited default values alongside view-specific overrides. Record whether each field inherits its value before replacing it, so a local correction doesn’t become a catalogue-wide change.
Follow this order on a small sample:
- Open the product through Catalog, then Products. Select the affected store view. Expand Search Engine Optimization and inspect the saved title and description.
- Compare inherited values with explicit overrides. Restore inheritance only when the default is the value that view needs.
- Open the affected category through Catalog, then Categories. Check its view-specific SEO fields and compare the resulting category page with the product page.
- Save one correction and inspect the public HTML. The expected result is the intended title and description on the correct view, with other views preserved.
Adobe’s SEO field reference for products lists product Meta Title, Meta Description and URL Key as store-view fields. Default metadata can also come from auto-generation settings. Changing an auto-generation mask is a different action from editing an existing saved value.
For a bulk change, filter the product grid and confirm the selected products before choosing Actions, then Update Attributes. Adobe’s bulk attribute procedure applies the chosen changes to that selection. Test the scope and resulting values on a small selection first. Applying one title to a whole range can replace useful product-specific information.
Treat a URL key change as a routing change. The key contributes to the public address, while the configured suffix is separate. A rewrite can map a friendly path internally without changing the address bar. A redirect sends the visitor to another address.
Before saving a new key, record the old path and intended destination. Review the Create Permanent Redirect for old URL option and the resulting entries under Marketing, then SEO & Search, then URL Rewrites. Adobe documents automatic permanent redirects, but you must still request the old URL and inspect its response. Expect a 301 leading to the intended working page, without a loop.
Resolve duplicate product and category paths
Trace every sampled product path to its final page and canonical before removing category paths or adding redirects. A canonical identifies your preferred version of similar pages. Google treats it as a signal and can choose a different canonical.
Consider a hypothetical bag sold under both travel and accessories. The storefront might expose /travel/canvas-bag.html, /accessories/canvas-bag.html and /canvas-bag.html. Request each address and inspect the canonical in the HTML head. If the preferred product address is /canvas-bag.html, each duplicate must identify that same working destination.
In the standard catalogue configuration, inspect Search Engine Optimization under Stores, then Settings, then Configuration, then Catalog and Catalog. Adobe’s catalogue configuration reference lists separate store-view canonical controls for products and categories. Inspect each control independently and verify its output in the deployed theme. A product canonical setting doesn’t establish the correct canonical for every category.
Layered navigation adds another source of URLs. Filter combinations change the product selection, while sort parameters change its order. Adobe distinguishes standard layered navigation from Live Search facets, so identify which implementation produces the URLs.
Choose which category pages deserve search visibility before applying parameter rules. A maintained “Waterproof travel bags” category can have its own useful content and stable URL. An arbitrary combination of size, colour and sort order doesn’t automatically need a search listing.
For unwanted filter combinations, assess crawl controls against the actual parameter patterns. Google’s faceted navigation guidance explains that canonical hints alone are less effective at controlling a large crawl space. Keep deliberate category destinations reachable, and test any proposed rule against them before release.
Check robots, sitemaps and indexing
Check crawler access and page-level indexing instructions before treating a sitemap as the fix. A sitemap helps discovery, but it doesn’t override blocked access or guarantee a search listing.
Use these checks in order:
- Request the affected page as a signed-out visitor. Confirm it returns the intended content without a login requirement or server error.
- Inspect the domain’s
robots.txtand the page’s robots meta tag orX-Robots-Tagresponse header. Identify any rule that blocks the intended public page. - Check the generated XML sitemap for that store view. Compare its product address with the canonical and the links customers follow.
- Use Search Console URL Inspection to compare Google’s indexed result with a live check. Record the selected canonical and any access or indexing exclusion it reports.
Google must be able to crawl a page to read its noindex instruction. Blocking the URL in robots.txt can prevent that instruction being seen. Decide whether you need to stop crawling or remove a page from search before combining those controls.
For the standard Admin workflow, configure XML Sitemap under Catalog in Configuration, then generate it under Marketing, SEO & Search, Site Map. Adobe’s sitemap instructions include a Store View field. Open the generated file and check that it contains the intended domain and routes.
Keep application indexing separate from Google indexing. Magento and Commerce indexers prepare catalogue data for storefront retrieval. A stale price or missing category assignment can require an application indexing investigation. A correct storefront page missing from Google requires a crawl and search-indexing investigation.
Caches store previously prepared output. If the saved change is absent from HTML, inspect relevant cache status and any storefront delivery cache. Reindexing or clearing caches doesn’t submit a page to Google. Avoid flushing all storage as a routine SEO step.
Inspect structured data and theme rendering
Compare the saved product with both the initial HTML response and the rendered page, because the theme or extensions can change what search engines receive. Adobe documents default product structured markup, but a customised storefront needs its own inspection.
Check the product name and description alongside its visible price and availability. Inspect the title, canonical and robots output. Then examine Product and Offer structured data for the same product and store view.
Run Google’s Rich Results Test against the page, using its structured data guidance for products to interpret errors. A valid result establishes eligibility for supported search features. It doesn’t promise that Google will display them.
If a theme and an SEO extension both emit markup, look for conflicting product identities, prices or canonical tags. Multiple structured data blocks can describe different entities legitimately. Repair inconsistent claims about the same product and assign one clear owner to each canonical output.
When company permissions or shared catalogues change what a visitor can see, also check signed-out output. The Magento B2B guide covers those catalogue boundaries separately.
Release changes with a recovery check
Release the smallest verified change and keep the previous values or template version available for recovery. Use the same URL sample before and after release, so a changed setting can be tied to an observable result.
Include a product reached through multiple categories, an edited URL with its old address and a deliberate indexable category. Add a filtered URL and a sorted listing. Repeat the checks across affected store views and sample both available and unavailable products.
For each sample, record the response status and final destination. Compare the title and canonical with the intended values, then check robots instructions, sitemap inclusion and structured data. Confirm that the visible availability matches the product state.
Roll back a URL or template change if it creates broken routes, redirect loops, incorrect store-view destinations or missing public product content. Restore the prior configuration or template through the normal release process, then repeat the failed requests. Preserve working redirects needed by existing links while repairing the change.
If one view still renders another view’s title or canonical, give the developer the affected URLs and saved scope values. Include response headers and the relevant HTML. Resume the rollout when the sample returns the intended pages and all old URLs reach their agreed destinations.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.