← All guides

You cannot edit your own website. Here is how to change that

Changing a headline should not need a developer. If it does, the site was built for the person who built it, not for you. Here is why that happens, what a site you can edit looks like, and the honest trade-offs of each option.

16 September 2026, 3 min read. From the owners who email us a new phone number to put on the site, because that is the only way they have ever been able to change it.

Some of the people we work with have never changed a word on their own website. Not because they could not learn, but because the site was built in a way that made it impossible: hardcoded pages, a builder only the developer had access to, or an admin so cluttered that touching anything felt dangerous. So every price change, every new team member, every phone number goes through an email and an invoice. And the site stays out of date, because who sends an invoice for a phone number.

Why sites end up like this

  • It was built as code. A developer built the pages directly in HTML, or in a framework, and there is no editing screen at all. Fast and clean for the developer. Locked for you.
  • It was built in a tool you do not have. The agency’s Webflow or Framer account, their page builder licence. When the relationship ends, so does your access.
  • It was built with a page builder that became a maze. Fifty nested boxes to change one heading, and a real risk of breaking the layout by clicking the wrong thing.
  • Nobody showed you. The site is perfectly editable and you were never given a login and a fifteen-minute walkthrough.

The last one is the cheapest to fix. Ask for the login.

What “you can edit it” should mean

A site you can genuinely run yourself has an editing screen where the text is text, the images are images, and the page looks roughly the same in the editor as it does live. Adding a page uses a layout that already exists rather than building one. Changing the phone number changes it everywhere. Nothing you do in the editor can break the design of the site, because the design lives somewhere you do not need to touch.

That last part matters. The reason page builders become mazes is that they hand you the design tools along with the content tools. A well-built site separates them.

The honest options

WordPress, built properly. The block editor with a small set of custom blocks made for your site: a “team member” block, a “service” block, a “project” block. You fill in fields, the design takes care of itself. This is what we build for most businesses, because the editing is familiar, there are no monthly platform fees, and any competent developer can work on it later. The trade-off is that WordPress needs updating and looking after, which is a monthly job.

A headless setup. Content lives in a content system such as Sanity or Payload, and the site itself is built in Next.js or similar. The editing screen is clean, the site is very fast, and it is the right answer when the site is more like an application. The trade-off is cost: it needs a developer for anything structural, and hosting has more moving parts.

A site builder you own. Squarespace, Wix, Framer. You can edit everything, and that is the problem as much as the benefit: there is nothing stopping you from breaking the layout. Fine for a small site. Limiting once you need speed, real SEO control or features the builder does not offer.

What to ask for

Whoever builds or rebuilds your site, ask for three things in writing: a login with full access, a written list of what you can change yourself and how, and a fifteen-minute recorded walkthrough. If they hesitate on any of those, the site is being built for them.

If you are not sure what you have now, we can tell you from the address. The scanner shows the platform in ten seconds, and the rest is one conversation.

See where your own site stands.

The scanner checks the things this guide talks about, in about ten seconds, no signup.

Tell us about the site.

A straight answer and a fixed quote, usually the same day.