If you could check only three pages this month, which ones would cost a customer time or money if they were wrong? Start with the price, the promise, and the way to get in touch. Follow the links and try the forms as a customer would. A page can look current and still send people to last year’s order form.
A practical example
Start the monthly check at the point where an error would cost someone money or a wasted trip. For a workshop site, that might mean following a visitor from the price page to the booking form and then to the confirmation email.
| What the reviewer found | Who can fix it | How to verify |
|---|---|---|
| The price page says $45; checkout says $55. | The owner confirms the approved price before the editor changes either page. | Repeat the booking up to payment and compare both prices. |
| The directions link opens last year’s venue. | The event lead confirms the address; the editor updates the link. | Open it from the public page and compare the destination with the booking confirmation. |
| The contact form says “sent,” but the test message never arrives. | The site maintainer traces delivery; the editor posts a verified alternative contact. | Send a new test and confirm receipt in the monitored inbox. |
A working link can lead to the wrong place. Read the destination, not just the status code. Use test details, avoid unintended charges, and record the date, owner, and next check beside each finding. If you cannot establish the correct price or venue, flag it for a decision rather than guessing.
Next month, start with unresolved items and repeat one important visitor journey. Rotate less critical pages into later checks. A small check that closes real problems is more useful than a long list of pages marked “viewed.”
Start with the pages that matter most
Pick the pages that bring the most visitors, convert the most readers, or make the most important promises. For most small sites, this includes the home page, the main service or product pages, the pricing or booking page, and the three or four articles that are shared most often. Keep this list short and written down. If the list grows too long, the check will be skipped in the months when it is needed most, so it is better to start small and add pages only when a real reason appears.
Check every link on those pages
Broken links are the easiest problems to find and among the most annoying for visitors. Open each high-value page and click the links, or use a link checker that reports status codes for every address on the page. Pay attention to internal links, which you control, and to outbound links to suppliers, partners, and tools, which change without notice. Record each broken link with the page address and the destination. Fix internal links right away, since they are usually a quick edit. For external links, decide whether to replace the source, remove the link, or leave it in place with a note explaining why.
Review stale claims and dates
Links are only part of the check. Read each page for statements that may no longer be accurate. Look for prices, deadlines, opening hours, team names, screenshots of old interfaces, and phrases such as “this year” or “recently” that have quietly aged. Also check footers and copyright years. Old details are harder to spot than broken links, because the page still loads and looks finished. If a claim depends on a law, a regulation, or an official rate, confirm it against the current source before you change or keep it, and write down the date you checked it.
Log every fix with an owner
A monthly check only works if the results are recorded. Keep one simple log with four columns: the page, the problem, the fix, and the person responsible. Note the date you checked each page, even when nothing needed changing. A clean entry is useful evidence that the page was reviewed, and it helps the next person see what has already been handled. When a fix needs a developer, a supplier, or a professional review, put that in the log with a target date rather than leaving it in your memory.
Keep the check small enough to repeat
The goal is consistency. A check that takes ninety minutes every month will eventually be dropped, so set a time limit and stick to it. If you find more problems than you can fix in one session, do not expand the check to cover the whole site. Fix the most visible problems first, schedule the rest, and keep the monthly list the same so that trends become clear. After three or four months, the log will show which pages change most often. Those pages may need a shorter review cycle, while the rest can stay on the monthly schedule.
Handle fixes that take longer than a month
Some problems cannot be fixed in one session. A product page may need new photographs, a supplier may take weeks to answer a question, or a page may need a developer to repair a template that affects dozens of addresses. Do not let these items disappear from the log. Mark them as open, record who is working on them, and set a date for the next review. Review open items at the start of each monthly check, so that they do not vanish between visits. If an item stays open for three months, ask whether it still matters. Sometimes the right decision is to remove the page, redirect it to a current one, or accept the risk and note it. A visible decision, even one that says nothing will change, is better than an item that is forgotten.







