Notes on building client sites
What we have learned building and handing over websites for other people, and the decisions behind the way Contentive works.
-
What an AI-ready website actually means
What an AI-ready website actually means: a crawler policy, a sitemap, an llms.txt and clean structured pages. What matters, what's hype, and what we serve.
-
How to build a website with Claude Code: a client site in an afternoon
How to build a website with Claude Code for a client: brief, content model, pages, theme and staging, step by step, with a human reviewing before launch.
-
Should you block AI crawlers? Allow, block or cite
Should you block AI crawlers on a client's site? Training bots, search bots and user-triggered agents are different, and each deserves its own decision.
-
An MCP endpoint for websites: why we're putting one on every site we host
Agents are starting to visit websites, not just people. Why an MCP endpoint for websites matters, what it should expose, and how we're building one.
-
AI content operations: what to automate and what a human must still click
AI content operations for client sites: what an agent should draft, tag and tidy, and the publish, delete and launch clicks a human must still make.
-
What should website maintenance cost in 2026?
What should website maintenance cost in 2026? How to price a care plan from what the work really takes, what to include and what to bill as change requests.
-
Webflow migration: what transfers to Contentive and what doesn't
A Webflow migration to Contentive, honestly: what our importers bring across, what you rebuild by hand, and how to keep the client's URLs and rankings.
-
The real cost of a WordPress website over three years
The real cost of a WordPress website over three years: hosting, plugins, updates, security and the unbilled fixes, added up honestly before you quote.
-
How to choose a CMS for a client site: a 10-question checklist
How to choose a CMS for a client site: ten questions to answer before you pick, covering who edits, who hosts, what breaks and what happens when you leave.
-
What is MCP, and what it means for building websites
What is MCP? The open protocol that lets an AI agent use real tools. What it changes about building client websites, and what it doesn't change at all.
-
Multilingual website projects: what to decide before you build
Building a multilingual website for a client? Decide the languages, URLs, fallbacks and who translates before you build. Each is hard to change later.
-
The website pre-launch checklist for client sites
A website pre-launch checklist for client sites: content, routes, redirects, forms, search settings and the domain, all checked in staging before go-live.
-
How to run a productised website service
A productised website service sells a fixed site at a fixed price. How to package one without it becoming a custom build in disguise by the third client.
-
Website contact form spam, notifications and where submissions go
Contact forms are the part of a client site that quietly fails. How to stop website contact form spam, route notifications and keep every submission findable.
-
Website staging for clients who want to see it first
Website staging for clients who want to see it first: give them a private preview address, review changes there, then promote to live when they say yes.
-
Staging vs production: what a deployment is on a client site
Staging vs production, explained for client sites: what a deployment is, why changes land somewhere private first, and what promoting to live actually does.
-
Client feature requests: when to say no to a custom build
How to handle client feature requests you shouldn't build: when to say no, when to say yes at a price, and the sentence that keeps the relationship intact.
-
Liquid themes explained: one theme, every page
Liquid themes explained: a layout, a template per content type and a template per section. Write it once and every page on the site renders from it.
-
The website handover checklist for agencies
A website handover checklist for agencies: accounts, access, ownership and the five things to check on the day, so launch week doesn't become support month.
-
What is a headless CMS? An agency's answer
What is a headless CMS? Content stored separately from the site that shows it. What that means for an agency, in plain terms, without the developer jargon.
-
How to scope a website project so it doesn't creep
How to scope a website project so it doesn't creep: name the content types, the sections and the edits up front, and price everything outside that list.
-
What is structured content, and why your clients need it
What is structured content? Content stored as named fields instead of formatted pages, and why it's the thing that keeps a client site tidy for years.
-
CMS user roles and permissions: who should change what
CMS user roles and permissions for client sites: who should change words, who should change structure, and why "admin for everyone" is the expensive default.
-
What is a content model? A plain-English guide
What is a content model? The list of things a site contains and the fields each one has. A plain-English guide, with the decisions that matter on day one.
-
Content control, not design control
Every client-editable site tool lets you change the words by also letting you change the layout — Contentive makes that constraint structural, not a permission.
-
The unbilled hours
Small unbilled client fixes add up to real money every month, and the fix is removing the possibility, not charging for it or training harder.
-
Moving a WordPress site to Contentive: what transfers and what doesn't
Posts, pages, media, taxonomies and slugs transfer from WordPress. Plugin data and theme customisations don't — here's how to plan around that.
-
Should you charge a retainer for site maintenance?
A retainer turns unbilled fixes into revenue, and it also prices a problem instead of removing it. Both sides of the argument, properly.
-
Why we don't have a drag-and-drop editor
A drag-and-drop canvas produces layouts only that canvas can read. We compose structured blocks instead, and we think that's the right trade.
-
Why there's no AI chat box for building your site
There's no prompt box for building sites in our Studio. You point your own agent at our tools instead — better context, and no markup on tokens.
-
Every plugin is a decision you have to keep making
A plugin isn't a one-off decision. It's a subscription to someone else's release schedule, paid in your attention, on every site you ever shipped.
-
How to write a handover that doesn't come back to you
A handover document isn't the fix. What to write down, what to restrict, and what to agree about who changes what.
-
What to do when a client breaks their own website
Triage first, blame never. What to do in the hour after a client breaks their site, and the conversation to have the week after.
-
Building a CMS an AI agent can actually drive
What it takes to let an agent drive a CMS without guessing: self-describing tools, structured errors, scoped tokens, and no second code path.
-
Why our content model is a graph, not a table
Documents are nodes and references are edges. Why a graph beats a table the moment a client asks for the same content somewhere else too.
See how Contentive compares to WordPress, Webflow and the headless CMSs →