
SEO CMS: 25 features to demand before you sign
Caroline Girard
Key takeaways
- An SEO-friendly CMS lets the marketing team manage SEO settings on its own: URLs, redirects, canonicals, robots.txt, sitemap, titles and meta descriptions.
- On an enterprise site, the most expensive mistakes are the least visible: an error page that returns a 200 code, the same page available at several addresses, a redirect forgotten during a redesign.
- The more pages, languages and sites you run, the more these settings need to be automatic and applicable everywhere at once.
- Server-side rendering ensures every crawler can read your content, including those from AI assistants that do not execute JavaScript.
- Before you sign, check the 25 features below and ask to see each setting done without a developer.
Editing the robots.txt, creating a redirect, fixing a canonical: in many companies, each request still goes through a ticket to the developers, and technical SEO moves more slowly than planned. That makes sense for risky changes. But in many cases, the team could handle it itself: skilled people in the marketing team, or specialist profiles, can fix a redirect or a canonical without breaking the site, as long as the CMS gives them access to those settings.
And a CMS is something you usually keep for years. So before you sign, make sure it will simplify your teams' technical work, for SEO as well as GEO, rather than slow it down: here are the 25 features to demand, and how to test them.
What is an SEO-friendly CMS?
An SEO-friendly CMS (also called a CMS optimized for organic search) is a content management system that lets the team handle a site's technical and editorial SEO without writing code.
The difference shows mostly on large sites: several languages, several brands, dozens of contributors. The marketing or SEO team manages URLs, redirects, canonicals, the robots.txt and the sitemap itself, as well as titles, meta descriptions and structured data. Behind the scenes, the CMS generates clean, server-side rendered HTML without anyone having to think about it.
Why the CMS matters for SEO
SEO is often broken down into several pillars:
- Technical: how well search engines can crawl, render and index pages.
- Content: how relevant the content and copy are to search intent.
- Authority: the links pointing to the site from other sites.
- User experience: page speed, readability and usability.
The first pillar depends largely on the CMS and on how it was implemented. The CMS produces the HTML, builds the URLs and decides what can be indexed. But if the templates were poorly built in the first place, the SEO options in the interface won't make up for everything: a good CMS that is badly implemented is still a hard site to rank. The CMS also affects content and user experience.
An editor that makes it hard to structure a page, or turns every publication into a chore, slows the team down, however good the strategy.
Authority, on the other hand, does not depend on the CMS, but it carries more and more weight. In highly competitive sectors, where dozens of technically sound sites target the same queries, links and brand awareness often make the difference. Every hour a good CMS saves on technical work is an hour you can spend on it.
With generative engines, the topic matters even more. For its own AI features, Google is clear (even if it should be taken with a grain of salt): the usual SEO best practices are the foundation of good GEO. There is no need to rewrite your content to "please AI" or to add an llms.txt file (it does no harm, but many analyses have found that AI tools do not use it).
Other assistants, however, send their own crawlers. At the end of 2024, a study by Vercel and MERJ found that crawlers from OpenAI, Anthropic and Perplexity did not execute JavaScript: content loaded in the browser stayed invisible to them.
The 25 SEO features to demand from a CMS
Tags, URLs, heading hierarchy, sitemaps, speed: every guide covers them. On an enterprise site (web portals, multisite, multilingual…), though, it is the less visible settings that cost the most. An error page that responds like a normal page, for example. Or two versions of the same URL competing with each other.
Here are the 25 features to demand, on two levels: 17 essentials, grouped into four families, then 8 features that make the difference on an enterprise site.
The 17 essentials
Meta tags and content structure
- Title and meta description: editable per page and per language, directly in the editor, without a plugin.
- Open Graph tags: a share title, description and image defined for each page.
- Heading structure: an H1, H2 and H3 hierarchy that the editor respects and the template does not break.
- Semantic HTML: lists for lists, tables for data and dedicated elements for secondary content, which crawlers and screen readers can interpret.
- Structured data: the ability to add Schema.org markup consistent with the visible content.
URLs and redirects
- Readable, editable URLs: a short address built from the page's words, which the team can correct.
- Flexible site tree: a URL structure that follows the site's organization instead of a pattern imposed by the tool.
- Manageable 301 redirects: the team creates and tracks redirects without asking developers.
- Single host: only one accessible version of the site (HTTPS, with or without www), reached in a single redirect.
- Consistent case and trailing slash: URLs redirected to lowercase and a single convention for the trailing slash.
Crawling and indexing
- Editable robots.txt: a file present on the site that the SEO team can edit itself.
- Controllable XML sitemap: an automatically generated sitemap from which pages or folders can be excluded.
- Default canonical tag: a canonical URL generated on every page and filled in correctly, to avoid duplicate content.
- Per-page meta robots: noindex and nofollow directives, and ideally those that control the snippet shown (nosnippet, max-snippet).
- Proper error pages: customizable error pages that return the expected HTTP code, 404 or 410, rather than a 200 code that makes them look like valid pages.
Rendering and performance
- Server-side rendering: the main content present in the HTML sent to the browser, without waiting for JavaScript to run.
- Page speed: lightweight pages, compatible with caching and a CDN, measured with Core Web Vitals.
The team works on meta tags every day. They belong in the authoring interface, not in template code.
On the URL side, without these rules, the same page ends up living at several addresses. The links it earns get split, and Google has to guess which one to show.
Crawling and indexing is where the quietest errors hide. A noindex forgotten on a template, an error page that returns a 200 code (what Google calls a soft 404), and pages drop out of the index without anyone noticing.
One last, often overlooked point: every guide talks about speed, almost none about server-side rendering. Yet it determines what crawlers that do not execute JavaScript actually read.
8 features that make the difference on an enterprise site
None of these features is required to rank well. However, they remove the small requests that land in the developers' backlog every month, and cut the time your teams spend fixing errors.
- Automatic redirects and safeguards: when a URL changes, the CMS creates the 301 redirect itself and updates internal links. The redirect manager lets you choose the code (301, 302 or 410), create pattern-based rules and test a rule on a sample of URLs before saving it, so that a single mistake doesn't redirect the whole site.
- Broken link report: a list of internal links returning errors, with bulk fixes rather than page by page.
- Images optimized on upload: resizing, compression, WebP or AVIF formats, declared dimensions to avoid layout shifts, and a single stable address per image.
- MCP server and agentic content management: an MCP server connects the CMS to AI assistants, which can then edit content in bulk, fill in metadata or prepare translations from a simple prompt, always with approval before publishing.
- Header scripts managed in the CMS: add a tracking tool or markup without a ticket, with code review and an approval workflow.
- Role-based access rights: give each profile (writer, SEO, developer, agency) control over what they master, for example redirects for the SEO team, without opening up the rest of the site. Simple fixes no longer go through IT, and nobody touches what they don't master.
- Approval workflows: every SEO change is reviewed and approved by the right person before it goes live, with a workflow suited to the type of content.
- A/B testing and personalization: compare two versions of a page and tailor content to each visitor, while following Google's rules (no content reserved for crawlers, a canonical pointing to the original page on each variant).
How to check a CMS's SEO features before choosing it
A sales demo rarely shows the settings that hurt. Come with precise questions and a few tests to run yourself.
During the demo, ask who can edit the robots.txt, create a redirect, change a canonical URL or set a page to noindex. Then ask to see it done, with no developer in the room. If the answer is "there's a plugin for that", ask who maintains it and what happens with every CMS update.
On an enterprise site, add three questions. Can the same redirect, sitemap and indexing rules be applied to every site and every language at once? What happens to internal links when a page changes address? And who approves an SEO change before it goes live?
On an existing site built with the tool, or on the test environment provided, five checks are enough:
- View a page's source code and check that the main text is there, which indicates server-side rendering.
- Request an address that does not exist and check the HTTP code returned using the browser's developer tools.
- Try the variants of the same URL (http and https, with and without www, in uppercase, with and without a trailing slash) and check that they all redirect to a single address, in one step.
- Open the XML sitemap and the robots.txt, then check that they match the published pages.
- Check that the canonical tag and hreflang tags are present in the head of a translated page.
One last point: not everything depends on the CMS. A host redirect or a caching policy is often set at the server or CDN level. A flaw spotted on a reference site may therefore come from the integrator rather than the tool, and so may a strength. Ask the question before deciding.
Multilingual, multisite and redesigns: where the CMS makes the difference
The bigger a site gets, the more SEO settings pile up: every new language, every new site and every redesign adds hundreds of tags, URLs and redirects to manage. At that scale, anything that isn't automated ends up forgotten. Three points deserve priority.
First, hreflang tags: they tell Google which version to show to which audience. Written by hand, page by page and language by language, they always end up with gaps. The CMS should generate them on its own, from the translations it already knows.
Second, metadata: the title, meta description and URL are translated along with the page, not copied from one language to another. For a group running several brands or countries, there is also a governance question: the team must be able to apply the same redirect, sitemap and indexing rules to every site at once, rather than redoing everything site by site.
Third, redesigns, the other high-risk moment. Changing CMS often changes thousands of URLs. Without a tested redirect plan, an updated sitemap and robots.txt, and close monitoring of Search Console in the weeks that follow, a site can lose in a few weeks the visibility it took years to build. The steps to prepare are covered in our guide to enterprise website migration.
What a CMS won't do for you
Even the best CMS in the world won't do everything for you. What a good SEO-friendly CMS does is take care of tedious technical tasks: generating hreflang tags, keeping the sitemap up to date, creating a redirect when a URL changes, flagging broken links. Your team knows how to do all this, but by hand these tasks take time and always end up containing errors. The CMS frees you up for strategy, research and data analysis.
You still need to know what you want. The CMS applies the rules it is given: a bad redirect rule, a misplaced noindex or a poorly chosen canonical will be applied just as fast, across hundreds of pages. Answering search intent, choosing keywords, writing expert and useful content, building internal links: this work takes real SEO expertise. A page that does not answer the question won't rank better because its tags are perfect. It is your strategy and your command of SEO that will drive your visibility on Google and in AI engines.
And of course, nothing goes live without review. Have every SEO change approved by an expert before publishing, for example with the CMS workflows, then check the result once the page is live. An SEO plugin helps fill in tags and spot omissions, but it won't fix poorly structured HTML, rendering that hides content from crawlers, or a poor understanding of what your customers search for. And monitoring continues after launch: crawl errors, broken links and redirect chains come back with every redesign.
What Jahia brings to SEO teams
Jahia natively covers a large part of this checklist. The team edits the robots.txt from a dedicated interface, sets noindex and nofollow page by page, and has a configurable, automatically generated sitemap that takes languages and noindex pages into account.
On the URL side, the team manages vanity URLs and each page's canonical URL, with a self-referencing canonical by default. Hreflang tags are generated automatically for translations, and dedicated fields hold the meta description and Open Graph image.
For content, the Semji module brings editorial SEO into Jahia: while writing, the team sees a keyword's actual search volume, improves the title, content depth, how well the page answers search intent and internal links, and tracks a live content score. Publishing workflows let you have a change approved before it goes live. A/B testing and personalization, which teams choosing an enterprise CMS often look for, are part of Jahia's DXP offering. On the rendering side, Jahia applies a server-side-first approach to its JavaScript modules.
SEO CMS FAQ
What is the best CMS for SEO?
What are the SEO requirements for a CMS?
What are the pillars of SEO?
Does an enterprise CMS need SEO plugins?
Is a headless CMS SEO-friendly?
What is the difference between SEO and GEO?
Discover








