For SEO agencies

Static pages, metadata you set page by page, and a migration that keeps the structure.

The controls are the product. What you do with them is your job, and we are not going to claim a ranking on your behalf.

Free plan available. No credit card required.

What this page will not claim

No rankings. No traffic numbers. No percentages.

Every SEO claim on a website builder's own site is either unverifiable or an anecdote about somebody else's client. So this page lists what the platform gives you control over and stops there. The results are the part you are being paid for, and we would rather you found the gaps here than three clients in.

Per page, not per site

The metadata belongs to the page.

Each page carries its own title and description, and the site produces its sitemap and structured data. Nothing important is inherited from a template you cannot reach.

Page titlePer pageEvery page on the site, including pages added after launch.
Meta descriptionPer pageWritten per page rather than lifted from the first paragraph.
SitemapPer siteGenerated with the site and regenerated when the pages change.
Structured dataPer pageEmitted with the page output.
Page outputPer siteStatic HTML on our CDN. No plugin layer between the crawler and the page.

If your process needs a control that is not on this list, ask before you move a client rather than after. That is a cheaper conversation than a migration.

What the crawler gets

A page, not an application booting.

Sites compile to static pages and are served from our global CDN. There is no plugin stack to keep patched, no theme update to break a template at the wrong moment, and no server left unmaintained between retainers.

No plugin stack

Nothing to update every month, and nothing that stops working when its author moves on.

The same page for everyone

What a crawler is served is what a visitor is served. There is no second rendering path to keep honest.

Version history on every change

A content change that goes wrong is one restore away, which matters more on a page that already ranks than on a new one.

Moving a client

Off WordPress with the structure intact.

Point it at the client's current address. The existing pages and content come across, and a WordPress site brings its pages and its posts. You review everything it found before a single design is generated, so nothing is quietly rewritten underneath a page that is already earning. A redesign keeps the pages and the content and rebuilds the design around them.

  • Pages and postsBoth come across from WordPress, so an archive built over eight years is not left behind.
  • Review before anything is generatedYou see the pages and the content it found and approve them first. Design generation happens after that, not before.
  • The design changes, the structure doesn'tA redesign keeps the pages and the content it imported and rebuilds only the design around them.

What it does not bring across is a plugin's behaviour. If a client's site depends on one, that is a conversation before the migration.

A site Mondovo generated from a commercial construction brief.
A site Mondovo generated from a commercial construction brief.

The economics of a content site

A forty-page site costs the same as a five-page one.

Pricing is per live site, not per page and not per visitor. Publishing the long tail your content plan calls for does not change the invoice, and form submissions are not counted either.

What it isWhat it costs
Each live client site$20 / month
PagesNot billed
VisitorsNot billed
Form submissionsNot billed
Draft sites while you plan the migrationFree
White-label, API access and the outreach tools$99 / month, flat

Before you move a client

What search teams ask.

Will this improve a client's rankings?

We are not going to say yes. Nobody can promise that, and a platform that does is telling you something it cannot know. What we will say is what the output is and what you can set: static pages on a CDN, titles and descriptions per page, sitemaps and structured data.

Which SEO fields can I actually set?

Titles and descriptions, page by page. Sitemaps and structured data are generated with the site. If your checklist has a field that is not on that list, ask us before you commit a client to a migration.

What happens to a client's WordPress posts?

Pages and posts come across. You review what the import found before any design is generated, so you can see exactly what made the trip and what did not while the old site is still up.

Is the published output really static?

Yes. Sites compile to static pages and are served from our global CDN. There is no plugin layer and no application to boot before a page can be read.

Who updates the content after the migration?

Anyone with a seat. Click an element and change it, or describe the change. Both land in version history, which is what makes editing a ranking page bearable — a bad edit is a restore, not an incident.

What does a client account cost?

$20 a month per live site, with the first live site included in the first $20. Drafts are free, so a staged migration costs nothing until you cut over.

Test it on one client

Import a site, look at what came across, and decide from there.

The draft is free, and the old site stays where it is until you say otherwise.

The wider agency case