A CMS gets SEO right when it gives you control over URLs, metadata, redirects, sitemaps, page speed and structured data without a developer for every change. This checklist covers what to check before you commit to a platform, or before you migrate away from one.
URL control
You need to set your own URL slugs, not have the CMS generate them from IDs, dates, or category trees you can’t edit. Check for:
- Editable slugs on pages, posts, and product or category listings
- No forced date stamps or numeric IDs in the path
- Control over trailing slashes and case
- The ability to change a URL after publishing, with an automatic redirect from the old one
Some platforms lock URL structure to their taxonomy system. That’s a problem if you need flat URLs or a structure that doesn’t match how the CMS organises content internally.
Meta control
Every page needs its own title tag and meta description, set independently of the page’s H1 or the site’s default template. Look for:
- A field for title tag and meta description on every page type, including archive and category pages
- Support for canonical tags, ideally with a manual override
- Control over robots meta (index/noindex, follow/nofollow) per page
- Open Graph and Twitter card fields, or an easy way to add them
If meta fields are missing, you’re stuck with whatever the theme or template auto-generates, which usually means duplicate titles across similar pages.
Redirect handling
URLs change. Pages get deleted or merged. A CMS needs a built-in way to manage 301 redirects without editing server config files by hand. Check for:
- A redirect manager in the admin, with support for wildcards or pattern matching
- Automatic redirect creation when a slug changes
- A way to bulk-import redirects from a spreadsheet, useful when migrating content
- Logging of 404s so broken links surface without a separate crawl tool
If you’re planning a platform move, decide how redirects will be handled before content goes live on the new system.
Sitemaps
An XML sitemap should generate and update automatically as content is added, edited, or removed. Manually maintained sitemaps go stale within weeks. Check for:
- Automatic sitemap generation and updates
- The option to exclude specific pages, post types, or noindexed content
- Separate sitemaps for images and, if relevant, video
- A sitemap index file if the site has more than a few thousand URLs
Page speed
Page speed is a ranking factor and a usability issue. The CMS itself, not just the theme, affects this. Check for:
- Built-in image compression or resizing on upload
- Lazy loading for images and embedded content
- Minimal render-blocking scripts from the core platform
- Caching support, either native or through a well-maintained extension
- A reasonable database and hosting footprint, since bloated core code slows every page regardless of theme
Some page builders add heavy CSS and JavaScript to every page, even simple ones. Test a real page, not a marketing demo, before judging speed.
Structured data
Structured data (schema markup) helps search engines understand content type and can enable rich results. Check for:
- Automatic schema for common types: articles, products, FAQs, breadcrumbs, organisation
- A way to edit or add custom schema without hand-coding every template
- Validation, or at least no conflicting schema output from theme and plugins at the same time
Content checks
The platform controls how pages are served. It does not control what is on them, and an SEO audit should cover both. Check for thin pages, near-duplicate copy across similar URLs, and information that has gone out of date. Part of a modern content audit includes verifying that published content passes AI content detection tools, especially for sites that accept guest contributions. A CMS with a proper editorial workflow, meaning separate draft, review and publish states and user roles to match, makes it easier to run that check before anything goes live.
Quick reference
| Requirement | What to check |
|---|---|
| URL control | Editable slugs, no forced IDs, redirect on change |
| Meta control | Title, description, canonical, robots per page |
| Redirects | Built-in manager, bulk import, 404 logging |
| Sitemaps | Auto-generated, excludable, indexed for large sites |
| Page speed | Image handling, lazy load, caching, light core code |
| Structured data | Auto schema plus manual override |
| Content checks | Review workflow, duplicate and originality checks |
Using this checklist during a platform decision
Test each item against a real page on a trial or demo site rather than trusting a features list. Vendors describe SEO tools loosely, and “SEO-friendly” can mean anything from full field-level control to a single auto-generated sitemap. If you’re comparing specific platforms, check the platform index for details on what each one handles natively versus through add-ons.
Rankings built on an old CMS rarely transfer automatically to a new one. Redirect mapping, matching URL structure where possible, and reissuing sitemaps are the parts most often missed during a switch, and the parts most likely to cause a traffic drop if skipped.