Updates fix security holes and bugs, and you should keep running them. Most go smoothly. But when an update does break something, it is rarely the whole site. It is usually something small: a button that moves, a form that loses a field, a page title that resets, a page that suddenly asks search engines to ignore it. Small problems like these do not trigger an error message, so they can sit unnoticed for days.
This checklist covers what to do before an update, the five-minute check to run straight after, a deeper check for bigger updates, and how to keep watching in the days that follow. It applies to WordPress itself, plugins and themes, whether you update by hand or let updates run automatically.
Which updates deserve the most care
- Theme and page-builder updates change how pages are laid out, so they are the most likely to move or hide a button.
- Form, booking and SEO plugin updates touch exactly the parts of the site that bring in customers and search traffic.
- Major WordPress releases (the ones where the first or second number changes) can affect older plugins and themes.
- Small security and maintenance releases rarely break anything, but still deserve the five-minute check.
Before you update
- Make sure you have a recent backup and know how to restore it. Many hosts make daily backups; check that yours does, and when the last one ran.
- Write down what “normal” looks like for your most important pages: the page title, the main button wording, the phone number, and the fields on each form. If you have never done this, do it once now and keep it in a note.
- Read the update notes for big theme or plugin updates. Developers often warn about changes that need attention.
- Pick a quiet time. Update when you have twenty minutes to check the result, not just before a busy weekend.
- Use a staging site if your host offers one. A staging site is a private copy of your website where you can try an update first. It is not essential, but it is the safest option for big updates.
Straight after: the five-minute check
Do this in a private (incognito) browser window, and then again on your phone. Your logged-in admin view can hide problems, because you may be seeing a different version of the page from a visitor, or a cached old copy.
- Homepage: it loads, it looks right, and your main button is still there with the same wording.
- Booking or quote link: tap it and confirm it opens the right page, not an error.
- Contact page: it loads and shows your phone number and form, with all the fields you expect and a submit button.
- Your top service pages: open each one and make sure none shows an error or a broken layout.
- Search settings: check that important pages are not set to noindex, and that page titles have not reset to something generic.
How to do the search settings check
This is the step people skip, because nothing looks wrong to a visitor. It takes two minutes:
- In WordPress, go to Settings > Reading and make sure “Discourage search engines from indexing this site” is not ticked.
- On a computer, open one of your important pages, right-click and choose “View page source”.
- Search the source (Ctrl+F, or Cmd+F on a Mac) for
noindex. If it appears in arobotsline, that page is asking search engines not to list it. - Search for
<title>and compare the title with the one you wrote down. - Search for
canonical. The address next to it should be the page’s own address.
For bigger updates: the deeper check
After a theme change, a page-builder update or a major WordPress release, add these steps:
- Send a test enquiry through each form and confirm it arrives, including in the spam folder. A form plugin update can change how messages are sent.
- Check the menu on mobile. Open it, tap each item, and confirm each one works.
- Check the header and footer on several pages, since phone numbers and contact links often live there.
- Try an old link. Open a page from a past email newsletter or a Google result to confirm older addresses still work.
- Clear any cache (in your caching plugin or hosting dashboard) and check the key pages once more, so you are looking at what visitors now get.
If something broke
- Note what changed and where, with a screenshot.
- Work out which update caused it. If you updated several things at once, that is harder, which is a good reason to update big plugins one at a time.
- Fix small things directly: re-add a button, correct a link, untick a noindex setting.
- For bigger breakage, roll back the plugin or theme to its previous version, or restore your backup, and contact the developer or your web designer.
- Run the five-minute check again once fixed.
Automatic updates need checking too
Automatic updates are a good idea for security, but they happen when you are not looking. WordPress can email the site administrator after automatic updates; make sure those emails reach someone who reads them, and treat each one as a prompt to run the five-minute check. If several plugins update automatically every week, a weekly check on a fixed day is a sensible habit.
In the days after: keep watching
Some problems appear later: a cache expires and serves the new layout, a scheduled task runs, or a setting takes effect on the next visit from a search engine. The hard part is remembering to keep checking, especially when updates run automatically.
PageNora is built for exactly that. You choose the pages that matter and approve what “normal” looks like: the page loads, the wording and button text you rely on, up to three important links, your form fields, the page title, search description and canonical address, and that the page is not marked noindex. It checks every day, and you can press Check now straight after an update for a fresh check. If a check finds a problem, PageNora checks again within minutes to confirm it, then emails you what was expected, what was found and what to try first, and emails again when it is fixed. No plugin is needed for the checks: it reads your public pages from outside.
It does not replace the whole checklist. It does not run JavaScript, so it cannot see parts of a page that only appear after scripts run. It never submits forms, so keep sending a test enquiry after big updates. It does not judge how a page looks or works on a phone, so keep your quick look on mobile. And it does not back up or restore your site. See exactly what it checks, and what it does not.
The free plan covers 1 website and 3 pages, checked daily, with no card needed and no end date: Start free.