Magento SEO checker: diagnose URLs and metadata

A Magento SEO check should sample a product assigned to multiple categories, a filtered category, and two store views where available. This exposes inheritance and catalog-routing issues that a homepage audit cannot establish.

Follow product paths through the catalog

Reach the product from each category and record its final URL and canonical. If different routes serve the same item, review URL keys, category paths, and canonical settings before proposing deletion. When an old address fails after a catalog import, compare it with the deployed redirect map. Sending all legacy product URLs to the homepage does not preserve their original purchasing purpose.

Exercise a filter shoppers actually use

Compare one filter combination and a sorted view with the base category. Record robots directives, canonical targets, and meaningful text instead of treating every query string as an error. If combinations lacking independent value are advertised in the sitemap, document the affected group before changing catalog or storefront rules. Avoid a broad block that also prevents access to valuable categories.

Compare metadata across store views

Request the same SKU in two languages and inspect title, description, and canonical output. A translated page showing the default title suggests an inheritance or scope issue. With a headless storefront, compare returned HTML with the metadata supplied by Commerce to locate the failing layer. Clear relevant caches and retest the original SKU plus another item sharing its configuration. This checks the scope of the fix rather than relying on one corrected page.

A worked publishing scenario

Illustrative scenario: an English SKU page displays Vietnamese descriptive text even though a translation was saved. Inspect the store-view scope and the rendering storefront before clearing relevant caches. Request a second product in the same store view to distinguish a bad record from a shared inheritance problem. Preserve both outputs in the report so a successful correction on the first product is not mistaken for evidence that every catalog item is fixed.

Run a check and interpret the evidence

Submit one representative public URL to the free SEO checker below. Record its status, title, description, and canonical alongside the exact address and time of the check. Group repeated issues by their responsible template or configuration so a single targeted fix can be retested on multiple pages. A missing field and an intentional exclusion need different decisions.

An HTTP/HTML audit observes public responses. It does not sign into the platform, inspect every administrative setting, reproduce every client-side rendering behavior, or prove that Google has indexed a page. For search-engine evidence, compare Search Console URL Inspection and subsequent crawl data. Recheck the original URL after publication and cache refresh instead of interpreting a changed score alone as proof that the underlying issue is resolved.

Tools and related guidance

• Read the Magento configuration guide
• Check a public URL
• Inspect a redirect chain

Official references

• Adobe Commerce: catalog URLs
• Adobe Commerce: catalog SEO configuration