The Magento SEO Checklist
Magento puts almost every SEO setting in one place, which makes it the easiest platform to get right and the easiest to break. Ten of these checks are in a single admin screen. This checklist covers the 20 settings and field values that decide whether a large catalogue is indexed cleanly, ranked distinctly, and found by buyers.
20 checks for a Magento site, each with the exact admin path, the frequency, and the time it takes.
What Magento Already Handles
Magento is the only platform on this list where the recommended configuration is a single screen. Under Stores, then Configuration, then Catalog, then Search Engine Optimization, there are six fields that together decide how every product URL in the store looks, whether it is canonical, and what happens to it when you rename it.
That is why Magento SEO problems tend to be large rather than subtle. A store with 4,000 products and the wrong category path setting has 4,000 URLs that disagree with the canonicals, and no amount of on-page work recovers from that. The settings are the job, and the copy on the product page is the second job.
This page sits inside the complete technical SEO checklist, and the platform-specific work it covers is the same work the general pages cover, with the exact admin path to each setting.
Handled by Magento
The 20 Magento SEO Checks
Every check with the admin path it lives in, how often to run it, and how long it takes.
| # | Check | Frequency | Tool | Time |
|---|---|---|---|---|
The URL Setting That Rewrites a Whole Catalogue
Two settings in the same admin screen can change the URL of every product in the store. Both are safe on the day you launch and expensive afterwards.
1 The two settings that rewrite URLs
Use Categories Path for Product URLs and the Product and Category URL Suffix fields live under Stores, then Configuration, then Catalog, then Search Engine Optimization. Turning the category path on gives a product one URL for every category it sits in, and the suffix change adds or removes .html from every URL in the catalogue. Both rewrites the whole store at once.
2 Why the category path causes a canonical mismatch
With canonicals on, Magento points the canonical at the product URL without the category path. Turn the category path on and the internal links point to one URL while the canonical names another, which is exactly the split the canonical is supposed to prevent.
3 The order that makes it safe
Test on staging, export the current URL list, prepare the bulk 301s, update the sitemaps, and only then deploy. For a bulk change the redirects belong at the web server or CDN rather than in the admin, because a large catalogue will not fit through the URL rewrites table in reasonable time.
What Magento Cannot Do For You
The limits worth knowing before you start.
It cannot write the product copy for you
The masks fill in a title from the product name and the brand, which is fine for one product and boilerplate for four thousand. The masks are the default, and the products that earn traffic need their own.
It cannot translate the metadata for you
On a multi-language store you switch the store view and provide a localised meta title and description per view, which is manual work on every product you care about.
It cannot clean a catalogue that grew by accident
Filter parameters, sort options, and search URLs are generated rather than authored, so the crawl has to be managed. The search engine robots instructions are where you control it.
It cannot keep the sitemap honest
A sitemap that lists a different URL from the canonical is a known failure mode, and extensions or custom code can reintroduce it. The check is comparing twenty lines of the file against twenty live pages.
It cannot keep the rewrite table small
Every product rename adds a row, and on a large catalogue the table slows down saves and reindexing. It needs an audit rather than a setting.
It cannot run the sitemap without cron
The generation schedule is cron driven, and a host where cron is not running produces a sitemap that silently stops updating, with no error anywhere.
Get the Full Checklist as a Template
Every checklist in the library, in a printable PDF and a spreadsheet with a Status and an Owner column, so the work can be assigned and tracked between passes.
The data is open source under CC BY 4.0 on GitHub. The broader platform work is in the technical SEO checklist.
Magento SEO FAQs
Direct answers on the platform, the settings that get missed, and the AI layer.
Yes, and it has more native SEO configuration than any other platform. The canonical tags, the redirects on a URL key change, the product field templates, and the sitemap are all built in. The risk is the same as everywhere else on this page: a large catalogue exposes the effect of a single wrong setting.
Under Stores, then Configuration, then Catalog, then Catalog, then Search Engine Optimization, set Use Canonical Link Meta Tag for Products and for Categories to Yes. Then verify rather than trust, because a canonical is a strong signal and a wrong one is a strong signal in the wrong direction.
There is no SEO advantage to the suffix, and it creates friction when you add API endpoints alongside the same paths. Set it at launch rather than after, because changing it on a live store needs a 301 for every URL that exists.
For a handful, use Marketing, then SEO and Search, then URL Rewrites, and add them there. For a catalogue-wide change, put the redirects at the web server or CDN level instead, because the admin table is not built for thousands of rules and slows the catalogue down when it grows.
The Use Categories Path for Product URLs setting is on, and it gives every product a separate URL for each category it belongs to. Turning it off gives one URL per product, which is what the canonical already assumes, and the two need to agree.
Not for the settings, because they are in the core admin. An extension earns its place on a catalogue with thousands of products, where filling in the metadata by hand is the bottleneck rather than the configuration of the settings themselves.
Under Stores, then Configuration, then Catalog, then Catalog, then Product Fields Auto-Generation, set a mask for the meta title and one for the description. A title mask of the name, the brand, and a fixed suffix prefills every new product. Skip the meta keywords mask, because Google ignores it.
The generation is cron driven, and a host where cron is not running produces a file that quietly stops changing. Check the generation settings for the frequency and the start time, then confirm cron is scheduled. On cloud infrastructure the web root is often read-only, so the sitemap has to be written to the media path instead.