Record what changed
Keep a note of the WordPress, theme and plugin changes, along with the update date. Check that a suitable backup and recovery route are available before changing a production website. Use a staging copy where appropriate, especially for substantial changes to forms, payments or page-building tools.
Visit more than the homepage
Review important service or product pages, the contact page, a recent article and any page with a different template. Check the main navigation, footer, images and text. A homepage loading successfully does not prove every page or customer journey is working.
Check the mobile experience yourself
Open the website on a phone and a desktop. Look for clipped text, overlapping sections, menus that do not open, buttons that are hard to use and unexpected horizontal scrolling. Viewport metadata and a stylesheet can be present even when a layout is broken; an automated source check cannot replace this step.
Test the actions that matter
With permission and suitable test details, review contact submissions, booking steps and account journeys. Check whether the intended confirmation appears and whether the message arrives. For stores, use an appropriate testing approach for checkout rather than accidentally placing live orders. SiteCheckpath does not currently submit forms or test payment journeys.
Review the page’s search information
Check important page titles, descriptions and canonical URLs. Confirm that any intended indexability settings still match the purpose of the website. Do not remove a noindex instruction without understanding why it is there. Search Console can help investigate search access and indexing; the current SiteCheckpath audit does not verify indexing status.
Use a source audit as one part of the review
Run a fresh check if you want a new source snapshot and compare the evidence with your earlier report. Keep a note of visual or functional problems separately. Our planned monitoring will add historical comparisons, but it is not active yet. If a change caused a regression, use your change record to investigate or seek help from your developer.
Google: technical requirements for Search ↗
This guide is general information. Review changes in the context of your website and use the original documentation for your platform and tools.