Treat a website as a maintained resource
Services, opening hours, contact routes and team responsibilities change. If a website is only reviewed during a redesign, an outdated page can keep answering a customer’s question incorrectly. A content workflow sets out who notices a change, who approves the wording and who checks the published result.
The process does not need to be complicated. A small business can maintain a simple shared list rather than buying another system. The important point is to make responsibility visible and provide a way for the website to be updated when the usual person is unavailable.
Make an inventory of important pages
List each major page’s address, purpose, business owner and next review date. Mark pages that contain time-sensitive details such as prices, opening hours, service areas, staff information or downloadable forms. Include landing pages used in advertising and links shared by staff; a page may be easy to overlook if it is not in the main menu.
Record where the source information comes from. A treatment description may need specialist approval, while a venue’s opening hours may need confirmation from the operations team. Do not put personal or sensitive information in a broadly shared inventory. The register is there to coordinate work, not to become a second uncontrolled source of truth.
Define an update request
A useful request identifies the page, the proposed change, why it is needed and who can confirm the facts. Include the intended start and end dates for a temporary offer, along with the correct destination for any button or download. If the change affects an image, supply the approved file and its use permission.
Ask whether the change affects other pages. A new phone number, for example, might appear in the footer, a contact page, a downloadable document and an external business profile. The appropriate person can plan those updates together rather than fixing one visible instance and leaving contradictory information elsewhere.
A simple content update workflow
- RequestRecord the page and change
- ApproveConfirm wording and evidence
- PublishUpdate the agreed locations
- CheckReview the live page and log
Separate drafting, approval and publishing
Choose a responsible person to prepare the update and someone appropriate to approve factual or specialist claims. In a very small business the same person may hold both roles, but a short pause to review the final version is still useful. If a supplier publishes on your behalf, agree how the owner signs off and how urgent corrections are handled.
Use account roles that fit the work instead of giving every contributor full administrative access. Keep access under business control and protect accounts with suitable sign-in security. A content editor may need to change a page but not alter payment settings, user accounts or the hosting configuration.
Check the published page, not just the editor
After publishing, open the live page in a browser and check the text, headings, links, image crop and contact options. Look on a phone as well as a larger screen. If caching or a scheduled update is involved, confirm that the intended version is actually visible. Test any form or booking flow only with the recipient’s agreement.
Check the page in context: follow the link from the service overview, confirm the page title describes the content and make sure an old offer is not still visible elsewhere. If a link opens an external site, check the destination rather than assuming that a saved address still leads to the intended resource.
An illustrative update
Imagine a Hertfordshire studio changing the days when customers can visit. The studio owner confirms the new hours and effective date, and the person responsible updates the website, relevant business profiles and any booking instructions. They also check whether a downloadable visitor guide contains the old opening times.
The team reviews the published contact page on a phone and records who approved the change. If an older page remains visible because of caching, the publisher investigates before telling customers the update is complete. This is a hypothetical process and does not claim a particular business or outcome.
Set a sensible review rhythm
Review dates should reflect how quickly information changes and the consequences of being wrong. A frequently changing event page may need attention after each event; a stable background article may need a less frequent review. Do not change a page date merely to make old information appear fresh. Make a meaningful correction when the content requires it.
For each review, decide whether the page remains accurate, useful and necessary. Assign follow-up work rather than quietly marking an issue as complete. If a service has ended, plan the most helpful destination or response for the old page and update the internal links that used to point there.
A one-page process to start with
Keep five fields in a shared request: page address, change needed, evidence or source, approver and target date. Add a simple status such as requested, drafted, approved, published and checked. For recurring pages, add the next review date and a named owner. The tool can be a spreadsheet, project board or another system your team already uses.
Keep credentials and confidential customer details outside the request. Review the system after a few updates: if approvals are delayed or changes keep missing related pages, improve the checklist. The aim is accurate information that customers can rely on, supported by a process the business can realistically maintain.
Build a small release record
For a time-sensitive change, add the effective date, the person who confirmed it and the places it must appear. A service-area update, for example, may affect a service page, a location directory and a downloadable brochure. Mark each location only after checking the published version. If an announcement expires, assign someone to remove or replace it instead of relying on a reminder that nobody owns.
For a correction, record the old statement, the approved replacement and where it appeared, while avoiding unnecessary personal data. If the page address changes, add the new URL and the agreed handling of the old one. Record the final page address and who confirmed each related business profile or downloadable document. A short release record helps the next editor understand what happened and gives the business a way to check that the website, customer documents and relevant external profiles remain consistent.
