SEO by Platform
"Best CMS for SEO" is a category of question the honest answer keeps deflating: every mainstream platform can rank, and execution beats platform in every dataset anyone has produced — the differences that matter are control ceilings, default hygiene, and operational fit, not some ranking blessing one vendor holds. This pillar is the comparison run on those real axes — anchoring a 14-guide series of per-platform playbooks, each written to its platform's actual controls and ceilings.
The axes that actually differ
- Control ceiling: what the platform lets you touch — URL patterns, robots/headers, markup, template code. Open-source self-hosted (WordPress, Drupal, Magento) tops out at "everything, at your responsibility"; hosted builders (Wix, Squarespace, Shopify) cover the fundamentals with named, documented ceilings — which stopped being disqualifying years ago and remain worth knowing before you hit one.
- Default hygiene: what's correct before you touch anything — modern hosted platforms ship sane canonicals, sitemaps and TLS by default (an under-credited virtue: the misconfiguration classes they simply prevent), while open-source power includes the power to break everything, per that silo's whole governance doctrine.
- Performance posture: hosted platforms fix infrastructure quality at their tier (good and untouchable); self-hosted puts the floor and the optimisation stack in your hands, both directions.
- Operational fit — the axis that should usually decide: your team's capacity to govern (updates, security, plugins) versus the platform's ceilings against your roadmap (the headless option being this axis at its most engineering-shaped).
The field, mapped to its guides
The general-purpose tier: WordPress (its own full silo — the control default), Webflow (designer-grade control, hosted), Ghost (the lean publisher), Drupal and Joomla (the veteran open-source pair), and the hosted builders Wix and Squarespace — both long past their old SEO reputations, per their guides. The commerce tier: Shopify and BigCommerce hosted, Magento self-hosted — the store silo's strategy on each platform's rails. The publish-elsewhere tier: Blogger, Medium, LinkedIn articles, Notion-as-website — platforms where the real question is rented-versus-owned, answered per guide. The architecture tier: headless — rendering responsibility relocated, with SEO consequences.
The decision, deflated to its real form
Choose by operations and roadmap, then execute the platform's playbook completely: teams with governance capacity and custom needs → open-source control; teams without → hosted hygiene and its ceilings accepted knowingly; stores → the commerce tier by scale and ops; and the migration question priced honestly per the standing checklist before any replatforming enthusiasm. What never decides it: the ranking-blessing myth — the case files hold winners on every platform listed, and the losers' autopsies name execution, not vendors.
Frequently asked questions
Does Google favour any CMS?
No — Google sees rendered pages, not platforms, and has said so for years. The folklore persists because platform populations differ (WordPress hosts everything from the world's best sites to its worst, builders skew small-business) — population effects misread as platform effects, per the standing correlation lesson.
We've outgrown our builder's ceilings. Migrate to what?
Name the actual binding ceiling first (URL control? markup? speed? scale?) — it shortlists the destination, and sometimes reveals workarounds cheaper than migration. Then the full checklist, because replatforming without SEO discipline converts a ceiling problem into a traffic loss.
What's the best platform for a new small business, honestly?
Whichever your team will actually operate: the builder they'll keep current beats the WordPress they'll neglect, and vice versa — the governance-capacity question answered truthfully. Every option ranks when fed the same two inputs this whole library keeps naming: content worth ranking and authority behind it (platform-agnostic, us).