Framer vs WordPress: which should you actually use?

If the people who write should never see Git, you still need a CMS. That CMS does not have to be WordPress. Read do you still need a CMS if the question is desk versus files, not Framer versus WordPress.

WordPress won because it let anyone publish. The theme was a skin. The product was the post, the draft, the user role, the media library, and a plugin directory that could become the business. Twenty years later that is still its strength — and why marketing sites drown in it. You installed it for a blog and now the site is WooCommerce, a form plugin, an SEO plugin, a redirect plugin, and a builder nobody on the team opened this year.

Framer is the opposite shape. You design the page in the file that goes live. Collections handle the repeating work. A code component is the escape hatch. There is no plugin directory to quietly become the architecture. That is a feature until you actually needed one of those plugins.

Count the real updates, not the ones in the kickoff deck. Four thoughtful pieces a year is a Framer collection or a Git workflow. Two posts a week with three approvers is WordPress — or a headless store you will pay to keep in sync. Do not install WordPress "in case we blog." That is how you buy a year of updates for a site that changed four times.

A WordPress marketing site can look expensive. It usually took a custom theme, a builder, and a developer who still picks up the phone. The last ten percent is type, spacing, a hover, a CMS bind that does not break the card. That is where it dies. Every new page is a negotiation with the theme.

Framer's advantage is the same as in the Webflow comparison: the first review is the website. Stakeholders see the real page in week one. Motion is cheap, which is dangerous; Core Web Vitals are a launch gate, not a report you read after the campaign starts. How we keep that gate is in Framer speed in practice.

WordPress hosting looks cheap. The bill is the person who patches it, the plugin licences, and the rebuild you buy when the theme author disappears. Framer Pro is $30 a month per site on the yearly list we checked in Sep 2026. That line is not the build. The build is the person who can still change the site — which is supposed to be your marketer, if we modelled the CMS.

• New marketing site, no newsroom. Framer. Faster path from taste to live.
• WordPress, marketing pages only, theme fighting you. Migrate. You are not leaving a publishing desk. You are leaving a skin.
• WordPress, daily publishing, many authors. Stay — or go headless and keep the desk. Framer is the wrong house.
• WooCommerce is the business. Stay on a commerce stack, or Shopify. Framer is not your store. See Butter for the shape we actually ship: store elsewhere, designed surface where it earns it.

Search will offer you a plugin that "moves WordPress to Framer." That is how you get a prettier site with the wrong URLs and a blog that nobody can edit. The work is a rebuild: information architecture, a content model, redirects, metadata, and the pages that deserve to exist. Rankings drop when you change a URL and forget the map, or when you replace a useful page with an empty hero.

1. 01
   Keep the URLs that earn

   Export the inventory. Anything with traffic, links, or a sales conversation keeps its path — or gets a 301 to the page that replaced it. Vanity URLs you invented in week two can die.

2. 02
   Model collections before visuals

   Posts, cases, jobs — fields first, template second. If a WordPress post is a blob of Gutenberg, decide which bits become fields and which stay as one rich-text body.

3. 03
   Redirect the rest as a list, not a hope

   One spreadsheet, one redirect map, tested before DNS. "We'll add them after launch" is how you donate the quarter's organic.

4. 04
   Copy the metadata you already won

   Titles, descriptions, canonicals, the schema that is real. Do not invent a Product on a blog post because someone heard it ranks.

5. 05
   Launch the site, not a thinner site

   If a page converted, it needs a Framer equivalent on day one. A staged blog you "add later" is a migration you did not finish.

The work does not change because the logo on the login did. Squarespace and Wix are WordPress without the plugin cliff — a designed skin, a simple desk, a ceiling you hit when the site has to look like a product. Drupal is WordPress with a worse hiring problem. Contentful or Sanity to Framer is not a migration of pages; it is a decision to stop running a headless store for one marketing site.

We will not give each of those its own article. The questions are the same: who publishes, which URLs earn, what becomes a collection, what is a 301. If you are on Squarespace or Wix, read this page as yours. If you are on Webflow, read Framer vs Webflow — that desk is a different culture.

1. 01
   Name who publishes next month

   A newsroom stays on WordPress. A marketer who needs a form gets Framer collections. Two people who already ship the site can publish direct.

2. 02
   Ask what the plugins are for

   If you can name three you actually use, you might need them. If the list is "SEO, forms, backups, the builder," you are paying for a theme.

3. 03
   Open the pages that earn

   If they are marketing pages fighting a theme, migrate. If they are a ten-year archive a team still writes into, stay.

4. 04
   Refuse the re-platform with no pain

   If nobody can name what is broken, we will not sell a migration.