Magento 2 SEO Checklist: Canonicals, Content and Validation
Start with the pages that matter to the business
A useful Magento SEO review starts with evidence: which product and category pages should be found, which URLs search engines currently index, and where customers encounter a problem. A checklist helps organise that work, but no set of settings guarantees rankings, sales or AI citations.
Use the checks below on a representative product, category, article and store view before applying changes across the catalogue. Magento Admin settings and the public storefront are separate layers: on a headless site, verify what the frontend actually renders.
1. Record a baseline and choose the intended URLs
For each important page, record its public URL, HTTP status, canonical, indexing rules, title and internal links. Compare this with Google Search Console and Bing Webmaster Tools. Record impressions, relevant queries, clicks and enquiries or purchases so later changes have a baseline.
| Finding | Next check | Useful outcome |
|---|---|---|
| Not found | Is the page retired, moved or accidentally missing? | Restore an accidental loss; redirect only to a genuinely equivalent replacement. |
| Duplicate or alternate canonical | Does the selected canonical represent the intended product or category? | Consistent preferred URLs in canonicals, internal links and sitemaps. |
| Crawled or discovered, not indexed | Is the page distinct, useful and discoverable? | Resolve a specific content or technical gap; request recrawling after a meaningful change. |
| Excluded intentionally | Is the URL a cart, account page, internal search or visual-only demo? | Keep the intended exclusion; do not make every URL indexable. |
2. Check canonicals, redirects and crawl access
Inspect the canonical link in the public page head and confirm its destination returns useful content. In conventional Magento Admin, catalogue canonical settings are under Stores → Configuration → Catalog → Catalog → Search Engine Optimization. Review Adobe's metadata documentation alongside the output of your installed theme or headless frontend.
Before changing category paths or URL keys, inventory existing links and redirects. A setting change can affect many established URLs. Keep HTTPS and hostname redirects consistent, avoid redirect chains, and do not redirect every retired offer to the homepage.
Review filtered category pages individually. Some may serve a useful search intent; others create repetitive combinations. Decide which should be discoverable and indexable. Canonicals are a signal, not a universal filter-control mechanism. A robots.txt block also prevents a crawler from reading a page's noindex instruction, so check how the controls interact.
3. Make useful pages easy to find
Include intended canonical, indexable URLs in the XML sitemap and submit the correct sitemap in the search-engine accounts. Verify that it excludes expired offers, redirects, errors and private journeys. An HTML sitemap serves a different purpose: it gives visitors a browsable route through the site.
Read HTML versus XML sitemaps for Magento for a worked check, and review HTML Sitemap for Magento for the module's current scope. Neither kind of sitemap guarantees indexing.
Give each important product a relevant route from a category or guide. Build supporting content around customer tasks: choosing between options, preparing an import, configuring a provider or diagnosing a fault. One detailed guide may support several related products. Do not create a near-identical blog for every keyword variation.
4. Validate product structured data
Inspect the public storefront's Product and Offer markup against the visible product, price, currency and availability. Include ratings only when genuine and eligible. Test discounted products, variants, products without reviews and other store-view currencies. Product snippets and merchant listings have different requirements; valid markup provides eligibility rather than guaranteed display.
Our Magento product structured-data guide explains the checks and links to Google's current documentation. GraphQL schema discovery concerns API fields and types; it is a different job from emitting schema.org JSON-LD. Do not select an API discovery tool on the assumption that it adds search markup.
Keep useful buyer FAQs, but remove promises of expandable FAQ results in Google. Google discontinued that search feature in May 2026, as recorded in its documentation updates.
5. Measure performance and the buying journey
Use field data where available, with lab tests to diagnose individual problems. Good Core Web Vitals thresholds are LCP at or below 2.5 seconds, INP at or below 200 milliseconds and CLS at or below 0.1, assessed at the 75th percentile. See the metric definitions. A Lighthouse score alone does not establish a field-data pass.
Check the actual slow element or interaction before choosing a fix. Serve appropriately sized images, reserve their display space, and avoid delaying the image that forms the main visible content. Defer below-the-fold images where appropriate. Recheck menus, product options, enquiry forms and checkout after performance changes.
6. Keep content and AI-search claims accurate
Write clear product specifications, limitations and purchase information. Keep descriptions grounded in verified facts and review AI-assisted drafts before publication. There is no E-E-A-T pass/fail test; see accuracy, E-E-A-T and human review.
Google says it does not use llms.txt to improve Search visibility, including its generative AI features. Maintaining the file for another service is a separate decision. Follow Google's current AI-search guidance and verify other providers' requirements separately. Structured data, fast pages and clear answers do not guarantee an AI citation.
Turn the audit into a repeatable release check
After changing a page, verify its public status, canonical, title, description, content and relevant links. Recheck representative pages after theme, module, pricing or cache changes. Keep a record of the change and compare later search and conversion data with the baseline; allow time for recrawling.
The AgenticEcom Suite combines an Astro storefront with Magento and the included modules described on its product page. Review the current scope, guides and visual storefront demos when assessing it. The demos illustrate design options; checkout, payments and orders are unavailable there. SEO remains ongoing work as the catalogue, software and search requirements change.