WordPress hosting for sites published from Notion.
Notion is a document tool that can publish pages, which is not the same as a CMS. The export shows it: expiring image links, filenames nobody chose, and databases with no equivalent.
What a Notion export does not carry.
The writing comes across. Almost everything that makes it a website has to be decided rather than imported.
Image links that stop working
Images in an export are frequently signed URLs with an expiry. Left to be fetched later, they return an error instead of a picture, so assets are downloaded as the first step rather than the last.
Filenames nobody chose
Notion names pages with a long identifier appended, and a published site inherits it. Those become readable slugs here, with redirects from whatever the old addresses were.
Databases with no counterpart
A Notion database is the closest thing the tool has to structured content. Mapping it to post types and taxonomies is a decision, not an import step, and it is made before anything moves.
Blocks that only exist there
Toggles, callouts, synced blocks and inline mentions have no WordPress equivalent. Each needs a deliberate answer, because the default outcome is a page of undifferentiated paragraphs.
The publishing layer in between
Most Notion sites are served through a third-party tool that adds the domain, theme and SEO tags. Those settings live in that service, not in Notion, and they are captured separately.
Get the assets before anything else.
Every other part of this migration can be retried. Images referenced by an expiring link cannot, once the link has expired and the export is all you have.
- Assets downloaded before the export goes stale
- Slugs made readable, old addresses redirected
- Databases mapped to post types with you
- Publishing-service settings captured
A site that renders on your own server.
A published Notion page is an application rendering a document. Once it is WordPress, the page is cached HTML and the difference is not subtle.
What this move needs that a host migration does not
Notion was never a website tool, so nearly every row here is a decision that Notion never asked you to make.
| Setting | What we do | Why |
|---|---|---|
| Asset capture | Images and files downloaded as the first step of the export | Notion serves attachments through signed links that expire, so an export processed days later contains references that have already stopped resolving to anything. |
| URL structure | Identifier-suffixed addresses replaced with readable slugs and redirected | Notion appends a long page identifier to every address, so keeping the old URLs means keeping something no reader can type and no editor can recognise. |
| Content model | Notion databases mapped to post types and taxonomies before import | A Notion database has no WordPress counterpart, so without a mapping decision every structured collection arrives as a flat run of ordinary pages. |
| Block conversion | Toggles, callouts and synced blocks given explicit equivalents | These are Notion-specific constructs, and an import that has no rule for them silently flattens the structure into plain paragraphs that read as though information is missing. |
| Publishing service settings | Domain, theme and meta tags captured from the third-party layer | Notion itself does not provide the domain or the SEO tags, so those live in whichever service publishes the site and disappear when the subscription ends. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Why do my images break when I import a Notion export?
Can I keep my Notion URLs?
What happens to my Notion databases?
I use super.so to publish my Notion site. Does that move too?
Will toggles and callouts survive?
Turn a published document into an actual site.
Free migration, assets captured before they expire, and a content model chosen on purpose.