Websites drift. Pages go out of date, links break, images slow things down and accessibility problems creep in with every change. The improved process checks the site on a regular cycle, lists problems in plain language with the page affected, prepares the fixes and content changes, and puts them in front of a person.
Nothing goes live until a named person has reviewed and approved it.
The job today
The website gets attention when someone notices a problem or a customer complains. Changes are made directly on the live site, sometimes by whoever has the login. Nobody checks speed or accessibility, and old pages with wrong prices, staff or opening hours stay up for months.
Where it breaks
- Problems are found by customers rather than by the business.
- Out-of-date information stays live.
- Changes go straight to the live site with no review.
- Accessibility and speed are never checked, which affects both visitors and search.
The improved process, step by step
- Check the site on a cycleOn a regular schedule the system checks every page for broken links, slow pages, missing descriptions and common accessibility problems.
- Spot out-of-date content AI preparesIt flags pages that mention old dates, people who have left, or details that differ from your agreed facts.
- Explain in plain language AI preparesEach problem is listed with the page, what is wrong, why it matters and a suggested fix.
- Prepare the changeFixes and content updates are prepared on a copy of the site that only you can see, never on the live site.
- A person approves what goes live A person approvesThe marketing or operations manager reviews the prepared changes in the private copy and approves them before they go live.
- Check again afterAfter each change goes live, the same checks run again to confirm the problem is fixed.
Where a person must approve
Nothing is published to the live site until a named person has approved it. Anything that sends, changes or cannot be undone waits for that approval.
Changes to prices, legal pages and privacy information are always reviewed by the person responsible for them.
The data boundary
- The checks read the public website. Fixes are prepared on a private copy with no access to the live site.
- The system does not hold website admin passwords or payment settings.
- Every change is kept, so it can be reversed if needed.
- Every check, change and approval is logged.
Checklist before you start
- We know who owns the website and who can approve changes.
- We can make a private copy of the site for checking changes.
- We have an agreed set of facts: services, hours, contact details and team.
- We know which pages are legal or privacy pages.
- We agree how often the site should be checked.
- We can reverse a change if it goes wrong.
This is an illustrative walkthrough of a common pattern. It is not a client case study, and the details will differ in your organisation.