What Reloque reads from WordPress
Reloque reads posts, pages, your own post types, media, categories, tags, your own taxonomies, authors, menus, comments, SEO data, the Redirection plugin's redirects and custom fields through the REST API, an export file or the bridge file. The REST API shows only the fields a plugin registers, such as ACF's; the export file and the bridge read every one. SEO data comes from Yoast SEO or Rank Math: the SEO title and description you set, the focus keyword, the canonical address, noindex and nofollow, and the social title, description and image, but not what the plugin makes from its templates.
How it lands in Webflow
Records go into the site's own collections, matched by name, or into the collections of Webflow's blog template, which Reloque adds when the site has none: Blog Posts, Pages, Categories, Tags and Authors. Bodies stay rich text, with images uploaded as assets and links between records pointing at the new items. Categories, tags and authors become items of their collections, and SEO data goes into the collection's SEO fields. Published records are published, and drafts stay drafts.
What to plan for
Better to know now than after the switch. The free scan names anything on your site that cannot move.
- WordPress: Rank Math's REST API does not show its SEO data, so connect a Rank Math site with its export file or the bridge file to move it. Yoast's REST API takes SEO data on posts only, and of it only the SEO title, description and focus keyword (older Yoast, such as 19.6, takes none); what a WordPress destination with Yoast cannot take is named in the run report.
- WordPress: Page-builder layouts move as the HTML they render, not as builder settings.
- Webflow: Webflow's API cannot create static pages, menus or redirects, so pages moving in become items of a Pages collection, and menus and redirects are left out. Add 301 redirects in the site's settings.
- Webflow: A static page moving out takes its text and images; its layout, styles, interactions and forms stay in Webflow.
- Webflow: Only the site's primary language is written into Webflow for now.
- Webflow: Webflow's CMS has no members or comments, so neither moves into or out of it.
- Webflow: A site on the free Starter plan holds about 50 CMS items, and Webflow allows 60 API requests a minute on Starter and Basic plans, so larger moves need a paid site plan and take longer.
- Webflow: Collections and fields Reloque adds to a site stay after an undo, as other CMSs keep types it adds.
Versions checked
WordPress: Checked on WordPress 7.1 and 6.0, and 5.5 as a source.
Webflow: One hosted service, so there are no versions to choose. Reloque uses Webflow's Data API (v2).
Questions
Can Reloque migrate WordPress to Webflow?
Yes. Reloque moves content from WordPress to Webflow, for early-access members now. Checked on WordPress 7.1 and 6.0, and 5.5 as a source. One hosted service, so there are no versions to choose. Reloque uses Webflow's Data API (v2).
What does a migration from WordPress to Webflow cost?
The assessment is free and gives your exact price: you pay for the records a migration writes, and media files do not count. Packages start at £99, and records are shared across any number of migrations for 12 months.
Will my addresses and SEO survive the move?
Every address that changes gets a redirect, written to Webflow where it keeps redirects, or ready as a CSV for your host or front end. SEO titles, descriptions and social images move where Webflow has a place for them.
Is anything written to Webflow before I approve it?
No. You see every record in the Preview first, then a small sample is written to Webflow so you can check it on the real site, and undo it. WordPress is only ever read.