WordPress 7.2 Beta 2: a marketing website test checklist

The official announcement explicitly says Beta 2 is not for production or mission-critical websites. It schedules the final release for December 8, 2026. That is a planned date, not a guarantee: testing can uncover problems and lead to changes.

The release includes further work on the Abilities API, admin interfaces and developer capabilities. None of that establishes that your website will automatically become faster or generate more leads. Your theme, plugins and custom code need their own compatibility checks.

Testing a beta is different from maintaining the stable software you currently run. Your live site still needs appropriate security updates. Waiting for WordPress 7.2 is not a reason to leave known issues in WordPress, plugins or the underlying PHP version unresolved.

WordPress also issued a separate PHP security notice on October 21. That is background, not a new announcement today. Ask your host which supported PHP version actually runs the site and whether required fixes have been applied. A hidden version number proves neither safety nor vulnerability.

1. Open an important landing page on a real phone.
2. Check the menu, buttons, readability and cookie choice.
3. Submit a test enquiry and confirm that it arrives.
4. For a store, test the basket, delivery choices and a test payment without charging real customers.
5. Check the thank-you page and intended conversion measurement.

Include more than the homepage. Search visitors often land directly on a service or product page. Test a browser your audience actually uses; a quick look on your own laptop is not a complete mobile test.

Before testing, make a backup and agree how to restore a working version. Keep staging out of search results and avoid real customer data where it is unnecessary. Check that payment, email and other connections remain in their intended test mode.

Record the page, device, expected behaviour and result. A screenshot helps with a layout problem; a received enquiry is stronger evidence for a form. Follow your normal testing and maintenance process for stable security updates instead of delaying them indefinitely for a future major release.

Before an actual update, record which important pages work and which findings already exist. Check the same pages afterwards. This helps distinguish an old issue from a new regression and makes it less likely that a broken journey goes unnoticed.

A free Marketing Scan account lets you save your website and findings. Download feedback as PDF or CSV for yourself or your web developer. A public website scan does not replace a test payment, a form submission or a full compatibility test. Use it alongside the customer-journey check. Read more about what a website audit can and cannot establish.