Bigger Rebuilds, Draft Editing, Sharper Audits

We ship changes to SOSEI continuously, and a few recent ones change how a rebuild actually feels day to day: what gets imported, how edits land on your live site, and what the chat editor can now do on its own. Here's what's new, grouped by the part of the process it touches.

Nothing from your old site goes missing quietly

The importer that reads your existing site during a rebuild now pulls in up to 50 pages, up from 20, plus your blog articles and catalogue items. If you want the mechanics of how that import works end to end, we covered it in How SOSEI Rebuilds a Website in Under Three Minutes.

The bigger change is what happens to the pages it still can't bring over. Instead of dropping anything that doesn't fit cleanly, the importer now keeps a record of what it couldn't migrate. You're not left guessing whether a page vanished or was never there to begin with.

From there, your dashboard lists any pages your old site had that the rebuild didn't include, with a way to add them back. A few things worth knowing about how that works:

• Every plan covers 20 pages in total. Blog posts, legal pages, and catalogue items don't count against that number.
• Adding pages is free until your site reaches 20.
• Each page beyond that is charged from your credit, never more than the price shown to you up front, and anything you don't use is refunded.

If you're weighing a rebuild against patching up an old site yourself, it's worth reading What a Website Redesign Really Costs in 2026 alongside this, since the page-count mechanics above are part of what makes a subscription predictable rather than a surprise invoice.

Edits are drafts until you say otherwise

Page and design changes in SOSEI now save as drafts. Nothing changes on your live site until you click Publish. That applies whether you're editing through the visual tools or through chat.

There's one deliberate exception: site-level settings, like the "Hide from search engines" toggle mentioned below, take effect immediately. Those aren't content changes, they're switches that affect how your site is treated right now, so they don't sit in a draft queue waiting for review.

In practice this means you can experiment with layout or copy changes without worrying about a half-finished edit going live, and it means a client, a colleague, or future-you can review a draft before it becomes the version visitors actually see.

The chat editor does more than move text around

The studio chat editor picked up a set of changes aimed at making it less like a text box and more like an actual control panel:

• Messages are clearer, and the editor now understands which page you're targeting rather than treating every instruction as site-wide.
• Image handling is improved, and you can now remove an image cleanly from the chat itself.
• You can set up redirects (301s) from old addresses to their new pages, directly in the chat.
• You can run the same 40-point site audit that's available from the dashboard, without leaving the conversation.
• The toolbar shows the pin for your first build, and what used to be multiple status pills is now a single control.

The redirect and audit additions are the ones worth pausing on. Redirects matter most right after a rebuild, when URLs change and you don't want old links, bookmarks, or indexed search results breaking. Being able to set one from chat, in the same place you're already making edits, means it gets done instead of deferred. Being able to run a full audit mid-conversation means you can check the effect of a change right after making it, instead of switching context to the dashboard. If you're not sure what a full audit actually checks, see the accessibility side of it in WCAG 2.1 AA: The Accessibility Checklist.

Audits catch more, and your brand comes through correctly

Site audits got more thorough in a few specific ways:

• Contrast issues are now detected below the hero section, not just at the top of the page.
• Audits run at 1920px resolution.
• Detection of footer and layout patterns has improved.
• There's now a "Hide from search engines" toggle for your whole site, which, as noted above, takes effect immediately rather than waiting for a publish.

Separately, rebuilds now detect your logo colors from the actual pixels of your logo file, and identify your footer's display type automatically. Both of these remove incorrect suggestions that used to show up during a rebuild, which matters if you've spent time getting your brand consistent. We've written more generally about what's involved in keeping a brand intact through a rebuild in Preserving Your Brand During a Full Website Rebuild, and this logo and footer detection work sits squarely in that effort.

Last on the list, but not small: every SOSEI site now includes EU AI Act Article 50(2) marking, and lists every third-party script and embed in its privacy policy. That's a compliance detail that's easy to miss when a site is handled piecemeal, and it's one of the things we generate automatically rather than leaving to you to track down. If you want to see what else lives in those generated legal pages, that's covered in Auto-Generated Legal Pages: What's In Them.

What this adds up to

None of these changes are dramatic on their own. Together, they close a few gaps that matter in practice: pages that used to get silently dropped during import now get tracked and can be added back, edits no longer go live by accident, the chat editor can fix the kind of post-rebuild issues (broken links, stray images, contrast problems) that actually come up, and your site's audits and legal pages stay aligned with current rules without you having to notice the rules changed.