Who can edit the site after launch

“You’ll be able to update it yourself” is one of the most common claims made during a website sale, and it is true on every platform in a narrow sense and false on most of them in the sense a buyer actually hears it. What a platform genuinely lets a non-technical owner change, without calling a developer, varies enormously, and it is worth establishing precisely before the build rather than discovering the boundary afterwards.

The narrow sense in which the claim is always true

Every current platform lets someone log in and change text and swap images somewhere on the site. That is the sense in which “you can update it yourself” is technically accurate on WordPress, Shopify, Squarespace, Wix and Webflow alike, and it is also the sense in which the claim tells a buyer almost nothing useful, because it says nothing about layout, structure or anything beyond swapping content inside an existing block.

What actually varies platform to platform

On a hosted builder, editing generally happens inside the same visual interface used to build the site, so a reasonably confident owner can genuinely restructure a page, not just its text, within the builder’s own constraints. On WordPress, the block editor allows meaningful content and layout editing within a page’s existing structure, but a page built with a visual page-builder plugin often edits more awkwardly for someone without training in that specific tool, and structural template changes — the parts a theme controls — generally still require development skill regardless of platform.

The distinction that predicts the actual experience

Content editing — swapping words, images, adding a new blog post inside an existing template — is broadly achievable by a non-technical owner on any of these platforms with a short amount of training. Structural editing — adding a genuinely new type of page, changing global layout, adding functionality that did not exist before — is a development task on nearly all of them, platform notwithstanding, and treating the two as the same skill is where the mismatch between promise and reality actually comes from.

What to establish before the build, not after

Ask specifically what the intended day-to-day editor will need to do — publish blog posts, update a price list, add new service pages, change photos — and confirm each of those specific tasks against the actual editing interface, ideally with a short walkthrough before signing off, rather than accepting a general assurance. A business planning to add new page types regularly needs a different answer to this question than one planning only to swap seasonal photos.

Who else can edit the site, and why that also matters

This question is not only about the business owner. Who holds the keys to your website covers the separate question of who controls admin access at all, and user roles and permissions covers what happens once more than one person needs to edit the site, with different levels of access — a genuinely common requirement the moment a business grows past a single owner-operator.

Why a short recorded walkthrough is worth more than a written manual

A written handover document is easy to produce and easy to file away unread. A short screen-recorded walkthrough of the specific, real tasks the day-to-day editor will actually perform — adding a blog post, updating a price, replacing a photo — in the actual admin interface, is considerably more useful in practice, because it shows exactly what the editor will see rather than describing it in the abstract. Asking a supplier for this specifically, rather than accepting a generic PDF, is a small request that meaningfully improves how confidently a business can actually use its own site.

What changes as staff turn over

The person trained at launch is not always the person doing the editing a year later, and training that lived only in one departed staff member’s memory is training that no longer exists. Keeping a simple, current internal note — or the recorded walkthrough above — accessible to whoever holds the role next prevents a business from quietly losing its own ability to update its site every time a staff member moves on.

Why this question is worth asking again a year after launch

Editing needs frequently change as a business grows — a task that seemed rare at launch can become weekly within a year — and revisiting whether the current editing setup still matches actual day-to-day needs, rather than assuming the original answer still holds, is worth folding into a routine annual check.

Testing the handover before the supplier relationship ends

Asking the intended editor to actually perform a real task while the supplier is still available to help is a far better test than a walkthrough alone — problems surface immediately, while they are still cheap and quick to resolve, rather than weeks later when the person who could explain it has moved on to other work.

Where to go from here

If the honest answer is that meaningful editing will always require a developer, that is a legitimate outcome, not a failure — it is simply a reason to have a maintenance relationship in place rather than assume self-sufficiency, covered in maintenance. And the training a supplier should provide as part of handover, regardless of platform, is set out in staging sites and handover.