Skip to main content
web60

Web60 Features

Review Website Changes Before Customers See Them: The Sign-Off Habit Small Teams Skip

Ian O'Reilly··17 min read
Two overlapping white document icons outlined in navy, with a curved teal shape cradling the front page, on a warm grey background

Nobody should be able to change your business website on their own. Not the part-time staff member who looks after the news page, not the relative who "knows computers", and not you either, at the end of a long day, fixing a price on your phone.

That sounds like bureaucracy. It is the opposite. A two-person check on anything a customer will read is the cheapest quality control a small business can run, and WordPress has quietly grown most of the tools to do it without slowing anyone down. Most small teams never switch them on.

Anyone who has worked a hosting support queue will recognise the pattern. A message arrives saying something is wrong with the website. We look at the server, the logs, the caches. Everything is healthy. The fault turns out to be a content change that went straight to production because nothing stood between the person editing and the Update button.

The Update Button Is the Riskiest Button on Your Website

Once a WordPress page is published, the Publish button becomes Update. Press it and the change is in production. Immediately. No queue, no holding area, no second opinion.

WordPress does save your work as you go. The WordPress.org revisions documentation explains that autosaves are enabled for all posts and pages "but do not overwrite published content" [5]. Useful if your browser crashes. It does nothing to stop a wrong change you meant to save.

One evening, one fees page

Consider a composite case, built from patterns rather than from one real business. A dance school in County Clare opens January enrolment online. The evening before, a part-time teacher updates the term fees page with new class times and a new fee for the junior grades. While tidying the page, the sibling discount line gets deleted and one fee picks up a typo. Update.

By the time anyone noticed, parents had screenshots of the wrong figure. The owner was left choosing between honouring a price they never set and starting the new term with an awkward conversation at the door.

Nobody did anything malicious, or even unusual. One person made a change, and nobody else looked at it before customers did.

Why the old model hid this problem

When a web agency controlled a site, every change went through someone else, slowly, at somewhere between €75 and €150 an hour. Sign-off happened as a side effect of the gatekeeping. Self-building with AI removed the gatekeeper, and rightly so: a site you build and run yourself is faster to change, far cheaper to keep, and closer to how your business actually works, because nobody knows your prices and your customers better than you do.

What it does mean is that the second pair of eyes now has to be a deliberate habit. It is no longer a by-product of an invoice.

What a Proper Sign-Off Process Looks Like

Start with the standard, before any tool. A sign-off process worth having does five things:

  1. Holds changes back until someone approves them. The person writing a change is not the person who makes it public.
  2. Lets the reviewer comment on the exact spot. "The second paragraph is wrong" in a text message is how errors survive review.
  3. Keeps a record and a way back. If something slips through, you can see what changed and rollback in minutes.
  4. Rehearses big changes away from production. A new menu, a new theme or a new booking plugin gets tried somewhere customers cannot see.
  5. Names one person for the final click. Shared responsibility for publishing tends to mean nobody's responsibility.

A platform that meets that standard should give a small team all five without extra subscriptions or add-ons. Full WordPress on a current version covers the first three out of the box, once you know where to look. A staging environment covers the fourth. The fifth is a decision only you can make, and it costs nothing.

WordPress is not a niche choice here. W3Techs currently puts it on roughly four in ten of all websites and well over half of the sites whose content management system it can identify [6], which is why the tools below are well documented and why any staff member you hire has a decent chance of having used them before.

Notes: Comments on the Page Without Touching the Page

The most useful sign-off feature in WordPress is also the newest. Notes arrived in WordPress 6.9 and gained more advanced features in 7.1, according to the official WordPress.org documentation [1]. They work like comments in a shared document. Select a block on a post or page, choose Add Note from the block's toolbar menu, and write your feedback. Since 7.1 you can also highlight a specific phrase and attach a note to just that text, or type @ to mention a colleague by name [1].

In plain terms: your reviewer stops sending you a screenshot with a red circle on it. They leave "this should be the junior rate" on the exact line, and you see it the next time you open the page. No hunting, no guessing which paragraph they meant.

A few details matter for a small team:

  • Notes never appear on the public site. The documentation is explicit that notes are "visible only in the editor and never appear in your published content" [1].
  • Visibility follows the user's role. Administrators and Editors can view and add notes on all posts. Authors and Contributors can do so only on their own. Subscribers cannot see them at all [1].
  • Email alerts are on by default. The author of a post gets an email when someone else leaves a note, and anyone mentioned gets one too. The control sits under Settings, then Discussion, as "Anyone posts a note" [1]. The original WordPress 6.9 developer note warns that a busy post can generate a lot of email, since one goes out for each new note left by someone other than the author [2].
  • Resolved notes do not vanish. They drop out of the active view but stay in the post's history, so you can see later what was queried and why [1].

Where Notes stop

Notes are not available in the Site Editor, which is where your header, footer and page templates live [1]. If the change you want reviewed is a new navigation menu or a redesigned footer, Notes will not help. There is also no view of the notes assigned to you; the documentation answers that question with "This currently isn't possible" [1]. For a three-person business that is a minor gap. For anything bigger, agree who checks the Notes panel each morning.

Stacked rounded bars in shades of teal and dark green with a navy marker pen resting against the lowest row, on an off-white background
Notes attach to the exact block or phrase under review, and only people who can edit the page ever see them.

Contributor and Pending Review: A Real Gate for Blog Posts

WordPress has had a proper approval gate for blog posts for years. Most owners hand every staff member Administrator access instead, because it is the quickest answer to "I can't see the button".

The Contributor role, as the WordPress.org roles and capabilities documentation describes it, is "somebody who can write and manage their own posts but cannot publish them" [3]. A Contributor sees Submit for Review where the Publish button would be. Pressing it sets the post status to Pending, which WordPress defines as awaiting a user with publishing rights, typically an Editor [4].

So the staff member who writes your Christmas opening hours post can draft it, but it waits in the queue until you approve it. They cannot publish it by accident late at night. By default they also cannot edit it once it is published, and they cannot upload files to your media library [3]. That last point is a security benefit as much as a quality one: fewer accounts that can upload anything means fewer ways for a compromised password to do damage.

Two more statuses help the person doing the approving:

  • Scheduled. WordPress calls this the future status: a post approved now and set to publish on a chosen date [4]. Approve the January sale post in December and it deploys itself on the day. On a very quiet site a scheduled post can appear a little late, so verify it on the morning it is due.
  • Draft. Visible only to logged-in users with the right role [4]. A safe place to leave half-finished work without anyone outside seeing it.

The gap nobody mentions: pages

Now the honest limitation. Contributors cannot create or edit pages, only posts [3]. Most small business websites are built mainly from pages: home, services, prices, contact, opening hours. Anyone you trust to edit those needs the Editor role or higher, and an Editor can publish anything.

Core WordPress also has no built-in way to hold a change to an already-published page for approval. You either press Update and the change is in production, or you switch the page back to draft, which takes it offline for customers while you work. Neither is a review process.

Three practical workarounds, in order of effort:

  1. Preview before Update. The Preview button shows your unsaved changes without touching production. The catch is that a preview only works for someone logged into your WordPress, so your reviewer needs their own account. Never share yours.
  2. Work on a copy. A duplicate-page plugin lets you clone the published page, edit the copy as a draft, get it reviewed with Notes, then replace the original. One extra plugin, and it closes the gap for price lists and service pages.
  3. Use staging for anything structural. Covered in the next section.

If most of your edits happen on the move, the same rule applies when editing your website from your phone: the preview on that phone is your review, and it takes about ten seconds.

Staging: Where the Bigger Changes Get Rehearsed

Notes and roles review words. They do not review a new theme, a new plugin, a rearranged menu or a booking widget. Those changes have dependencies, and a conflict between two of them is something you want to find where no customer is looking.

That is the job of a staging environment: a private copy of your site where you make the change, verify it on a phone and a laptop, and only then make it on production. We have written a full guide to how a staging environment works, so the short version here is a rule of thumb. If the change touches the header, the footer, the menu, a plugin or the theme, it goes to staging first.

The alternative is worth spelling out. A new booking plugin is installed straight onto production on the first Monday of January and clashes with the existing contact form. New enquiries stop arriving, and the first sign of trouble is silence. Nobody rings to tell you your form is broken. They ring the next business on the list.

Two matching teal circles with thick navy rims sitting side by side and touching at the centre, on an off-white background
A staging environment is a private copy of the site: rehearse the change there, verify it, then make it on production.

On Web60, staging is a one-click job from the dashboard and is included in the €60 a year along with hosting, SSL, backups and security, so "we do not have a test site" stops being a reason to skip it. If you are still weighing up whether to build your own site at all, you can see the Web60 dashboard and its staging tools in action before committing to anything.

What staging cannot do

Staging is a snapshot taken at a moment in time. If customers place bookings or orders on production while you work on the staging copy, those records exist only on production. Plan any big change to the parts of your site that hold customer data with that in mind, keep the staging session short, and make the final change on production at a quiet hour rather than overwriting live data with an older copy.

Revisions and Backups: The Rollback When Review Fails

Even a good process lets the occasional mistake through. What matters then is how quickly you recover.

WordPress keeps a revision every time a post or page is saved. The WordPress.org revisions documentation describes the revisions screen introduced in WordPress 7.0, which marks added blocks in green and removed blocks in red, with a Restore button against any earlier version [5]. For the dance school in the example, that is the difference between retyping the fees page from memory and restoring last week's version in under a minute, then fixing the one line that genuinely needed changing.

When revisions are not enough

Revisions have a boundary. By default they track a post or page's title, author, content and excerpt [5]. A deleted menu, a changed setting or a plugin configured wrongly sits outside that net. That is where backups come in.

Web60 takes automatic nightly backups with one-click restore, and you can take a manual backup on demand before a risky change. Automatic safety snapshots are taken before updates and before any restore, so rolling back never destroys the state you were rolling back from. One more trade-off to know: a nightly backup only holds what existed last night. A manual backup five minutes before a big edit costs nothing. Restoring last night's backup after an afternoon of changes costs you the afternoon.

Matching the Process to the Size of Your Team

Not every change needs the same ceremony. Overdo it and people route around the process. Underdo it and the fees page scenario is waiting. A workable split for a team of two to ten people:

ChangeWho makes itWho signs offWhere it is verified
Blog or news postContributorOwner or Editor, via Pending ReviewPreview
Page wording, prices, opening hoursEditorSecond person, via Notes on a draft copyPreview on a phone
Menu, header, footer, layoutOwner or EditorSecond personStaging environment
Plugin or theme changeOwnerOwner, after testingStaging, plus a manual backup

Every row has the same shape: two people, or two looks, and a place to see the result before customers do.

Sole traders have no colleague to ask, so the second look has to come from time instead. Make the change as a draft copy, walk away, and look at the preview on your phone the next morning before you press Update. Not as good as another person, but a great deal better than nothing.

Where This Approach Runs Out

Everything above is lightweight by design. If your content passes through legal review, a compliance officer and a marketing manager before it is published, with an approval trail a regulator may ask to see, the built-in Notes and Pending Review will not carry that load. Organisations running that kind of multi-stage editorial workflow, a financial services firm with an in-house compliance team for instance, are genuinely better served by enterprise managed hosts and dedicated editorial workflow platforms built around formal approvals.

That is not the dance school, the café or the five-person consultancy. For businesses like yours, the tools already inside WordPress plus one firm habit cover almost every change you will make in a year.

Two People, One Final Click

The case for building your own website is that nobody understands your business better than you do. That stays true. Understanding the business and spotting a deleted discount line late in the evening are different skills, though, and the second one works better with two people.

None of this needs new software or a bigger budget. It needs three decisions: who gets the final click, which role each person actually needs, and which changes go to staging first. Make those three this week, and the next mistake on your website gets caught by a colleague instead of a customer.

Frequently Asked Questions

How do I stop staff publishing changes to my WordPress website without approval?

For blog and news posts, give the staff member the Contributor role instead of Administrator. A Contributor can write and save their own posts but gets a Submit for Review button instead of Publish, so nothing appears on the site until an Editor or Administrator approves it. Pages are different: Contributors cannot edit pages at all, and anyone who can edit pages can also publish them. For page changes, ask staff to work on a draft copy of the page and leave the final Update to one named person.

Can customers or visitors see WordPress Notes?

No. Notes are visible only inside the WordPress editor, and only to people whose account can edit that post or page. Administrators and Editors can see notes on everything, Authors and Contributors only on their own posts, and Subscribers cannot see them at all. Nothing in a note is ever shown on your published website.

Why can my colleague not open the preview link I sent them?

A WordPress preview only works for someone logged into your website with permission to edit that content. If you copy the preview address and send it to someone without an account, they will not see your changes. Create them their own account with a suitable role, such as Editor or Contributor, rather than sharing your login, and they can open previews and leave Notes themselves.

Can I undo a change after pressing Update in WordPress?

Yes, for the content of a post or page. WordPress stores a revision every time you save, and the revisions screen shows what changed and has a Restore button for any earlier version. Revisions cover the title, author, content and excerpt by default. They do not bring back a deleted menu, a changed setting or a plugin configuration, so for those you need a backup taken before the change.

Do I need a staging site if I only change text and prices?

Usually not. Text and price changes are best reviewed with a draft copy, Notes and a preview on your phone. Staging earns its place when a change touches the structure of the site: a new plugin, a theme change, a new menu, the header or footer, or anything to do with booking and payment. Those changes can conflict with each other, and staging lets you find that out where customers cannot see it.

Will a scheduled post publish at exactly the time I set?

Normally it publishes at or very close to the scheduled time. WordPress checks for due tasks when the site is visited, so on a very quiet site a scheduled post can occasionally appear a little late. If timing matters, such as a sale that starts at a set hour, verify the post is live shortly after it is due.

Sources

IO
Ian O'ReillyOperations Director, Web60

Ian oversees Web60's hosting infrastructure and operations. Responsible for the uptime, security, and performance of every site on the platform, he writes about the operational reality of keeping Irish business websites fast, secure, and online around the clock.

More by Ian O'Reilly →

Ready to get your business online?

Describe your business. AI builds your website in 60 seconds.

Build My Website Free →
Buy NowTry Free
Review Website Changes Before Customers See Them | Web60