Website operations · 21 Nov 2026 · 7 min read
Content workflow for your website: drafts, review and publishing
Most publishing mistakes come from unclear ownership, not from bad tools. A short content workflow makes it clear who writes, who checks and who presses publish.
The short answer
A website content workflow is the set of steps a change follows from draft to live page. Keep it short: one person drafts, a second person reviews against a checklist, a named person approves and publishes, and the change is checked on the live page afterwards. Smaller sites can combine roles but should still separate writing from checking.
Why a website needs a content workflow
A content workflow is the route a change takes from idea to live page. It can be as light as a shared note saying who does what, or as formal as a staged system with approvals. What matters is that the route exists and that everyone who edits the site knows it.
Without one, the usual problems appear slowly. A price changes on one page and not another. An old offer stays live for months. A draft is published by accident because it was saved in the wrong state. A well-meaning team member rewrites a service page and removes the phrase that was bringing enquiries. None of these needs bad intent. They happen because nobody was asked to check, and nobody was clearly responsible.
The aim is not paperwork. It is to make publishing a calm, repeatable task with a small number of checks, so that mistakes are caught before visitors see them. A site that is edited by several people, or by a person and an agency, needs it most.
The stages of a simple publishing process
Most websites need only five stages. Smaller teams can combine them, but it helps to name them so each one has an owner.
| Stage | What happens | Who usually does it |
|---|---|---|
| Draft | The change is written or edited, kept out of public view | Writer or the person who knows the subject |
| Review | A second person checks facts, spelling, links and tone against a checklist | Colleague or editor |
| Approval | One named person agrees the page can go live | Owner or manager |
| Publish | The change is made live, at a chosen time | Whoever has publishing rights |
| Check | The live page is opened and tested, and the change is recorded | The person who published, or the reviewer |
The separation between drafting and review is the most valuable part. Writers do not see their own mistakes, because they read what they meant to write. A second pair of eyes catches the wrong phone number, the broken link and the sentence that no longer makes sense after an edit.
Most content management systems have a draft state, a scheduled state and a published state. Learn how yours behaves. In particular, find out whether saving an edit to a live page changes it immediately, because on many systems it does. If it does, edit a copy or use a preview where you can.
Who should approve website changes?
One named person, and a named backup. The approver does not have to be senior, but they must know the business well enough to say whether a page is accurate and on message. For a small company that is often the owner or a manager. For a larger one it might be a marketing lead for general pages and a specialist for legal, technical or pricing content.
Not every change needs the same weight. A useful habit is to sort changes into three kinds. Small corrections, such as fixing a typo or updating opening hours, can be done by a trusted editor with a quick check. Normal changes, such as a new blog article or an edited service page, follow the full process. Sensitive changes, such as prices, legal wording, privacy notices, claims about results and anything involving safety, need approval from the person responsible for that subject. For legal pages, ask a qualified lawyer, because rules differ by country and change over time.
Make the rules visible. A one-page document saying who can publish what, and who approves each kind of change, removes most arguments. It also protects the person who says no, because the rule is the business's, not theirs.
If an agency or developer manages your site, agree in writing what they may publish without asking, and what they must send for approval. The same applies to who holds the logins, which our guide to keeping control of analytics and Search Console access covers in more depth.
How do I avoid publishing mistakes?
Most errors are repeats. The same ones turn up again and again: broken links, missing images, the wrong page selected, text pasted with strange formatting, a draft published too early, an old price left in a different place. A process that targets those few problems prevents most of the damage.
- Work on a draft or preview, never directly on a live page, unless the change is a trivial correction.
- Use a preview to look at the page on a phone-sized screen as well as a desktop one.
- Click every link you added, including the ones in buttons.
- Search the whole site for old wording, names or prices before you change them, so that every instance is updated.
- Schedule important changes for a time when someone is available to check them, not for the middle of the night.
- Keep a copy of the previous version, so a bad edit can be reversed quickly.
Pasting is a quiet source of trouble. Text copied from a word processor can bring hidden styles with it that make a page look different from the rest of the site. Paste as plain text and apply the site's own heading and list styles instead. That keeps pages consistent and avoids layout surprises on small screens.
Finally, remember that a live change can affect more than one page. Changing a heading, a menu label or an address can alter links and search listings elsewhere. If you are editing existing pages rather than adding new ones, use a content review first, such as the one in our guide to reviewing your website pages in a content audit, so you know what each page is for before you change it.
What should a simple checklist include?
A good checklist is short enough to use every time. If it runs to two pages, people will skip it. Aim for a list that takes a few minutes and covers the checks that matter most. Here is a starting point you can adapt.
- Is the purpose of this page or change clear, and does it match something in the content plan?
- Are names, prices, addresses, dates and contact details correct and the same everywhere?
- Does the page have one clear heading, a useful title and a short description?
- Do all links work, and do they go where the text says?
- Do images have meaningful descriptions, and are they a sensible size for loading?
- Does the page read well on a phone, and can a keyboard user reach every link and button?
- Has someone other than the writer read it?
- Has the right person approved it?
- After publishing, was the live page opened and checked, and was the change recorded?
Add items that reflect your own history. If a form has failed before, add a line to submit it once after publishing. If legal text has been changed by accident, add a line about who signs off on it. A checklist that grows from real mistakes is more useful than a generic one.
The checklist should also link to the plan behind the pages. If you do not yet have a plan for what the site should say, start with deciding what to write first for your website, so that each new page has a reason to exist before it enters the workflow.
Keep a change log and review the process
A change log is a plain list recording what changed, when, who did it and who approved it. A shared spreadsheet is enough. It takes seconds to update and saves hours when you need to work out when a page changed and why. It also helps when traffic or enquiries move suddenly, because you can look at what was published just before.
Review the workflow itself every few months. Ask the people who use it what slows them down and what mistakes still get through. Remove steps that nobody follows, and add steps for problems that keep recurring. If the process is too slow, people will bypass it, so keep it as light as safely possible.
The same thinking applies to your brand. Voice, design and claims should stay consistent as many people edit, and a regular look at the whole identity, like the one described in how to audit and review your brand, keeps the site in line with everything else. Finally, if you want help setting up a publishing process alongside a new site, the website development service from Liftup Technologies can include editor roles, previews and a staging copy as part of the build, and monitoring such as uptime alerts can tell you if a change breaks something.
Related guides
- Website development
- Website content audit how to review your pages
- Website content plan what to write first
- Brand audit how to review your brand
- Website Uptime Monitoring: How to Set Up Alerts
- Analytics and Search Console Access: Who Should Hold the Keys
Questions and answers
Who should approve website changes?
One named person who knows the business well enough to judge accuracy and tone, with a named backup. Sort changes by weight: minor fixes need a quick check, normal content needs full review and sensitive changes such as prices and legal text need the person responsible for that subject.
How do I avoid publishing mistakes?
Work in draft or preview, have someone other than the writer review it, click every link and search the site for old wording before changing it. Schedule changes for when someone can check them, and keep the previous version so a bad edit can be reversed.
What should a simple website checklist include?
Check accuracy of names, prices and contact details, a clear heading and title, working links, sensible images, how the page reads on a phone, a second reader, approval and a check of the live page afterwards. Add items drawn from your own past mistakes.
Does a small business really need a workflow?
Yes, though it can be very light. Even one person benefits from separating drafting from checking by waiting before publishing and reading the page again on a phone. If more than one person edits the site, write down who does what.
Should I let several people publish directly?
Only where it is safe. Give most editors the ability to draft and send for review, and keep publishing rights with a few trusted people. Many systems let you set roles for this, so check the current documentation of yours.
How do I handle urgent changes?
Agree in advance what counts as urgent and who can approve it quickly. Use the shortest safe route, such as a single reviewer, and record the change afterwards. Do not let urgency become a reason to skip checking the live page.
Tell us what you are building.
A short call, a written plan and a fixed quote. No obligation.