Critical error after a Yoast update: “Request_Helper” not found

Does your public website show a critical error after a Yoast update, while you can still open the administration area? If the error log contains Class "Yoast\WP\SEO\Helpers\Request_Helper" not found, that gives you a specific starting point. First preserve the complete error message and the versions of the plugins involved. A general “plugin conflict” is not a sufficient explanation for this case.

One documented report identifies this error after an update to Yoast SEO 28.7. The call that triggered it was reported in wpseo-woocommerce/classes/woocommerce-seo.php. According to the follow-up, manually reinstalling the plugin did not resolve the issue; no conclusive, confirmed repair is documented publicly. Q1

What the message tells you

The error names a class that the calling code expects but cannot load. Two questions therefore matter: which component provides the class, and which component is trying to use it? The file path in the error log helps answer the second question.

For version 28.7, released on 13 October 2026, Yoast announced the removal of previously deprecated interfaces. The linked, merged source-code change explicitly removes Request_Helper. This establishes a specific connection to a version change. On its own, it does not prove which version of the calling extension is installed on your website or how that extension was updated. Q2 Q3

The task is therefore to check the combination that is actually installed. An update to the main plugin, an older add-on, custom code and incompletely replaced files need to be treated as separate possibilities.

First steps: restore availability and preserve the evidence

1. Document the outage. Record the time, the most recent change and two affected URLs. Check whether only product pages fail, or whether the homepage and other public pages are affected too. A working administration area does not prove that visitors can use the website.

2. Preserve the relevant log excerpt. You need the error type, class name, calling file and associated stack trace. Replace usernames and private directory details before sharing it. Do not otherwise alter the substance of the log. Record different errors occurring within the same period separately.

3. Record the versions as a complete set. Include WordPress, PHP, Yoast SEO, Yoast SEO Premium if present, and Yoast WooCommerce SEO. Note whether any custom extensions call Yoast code. A single version number labelled “Yoast” does not describe the combination adequately.

4. Use an available, safe way to access the site. WordPress provides Recovery Mode for certain fatal errors. It can provide access for troubleshooting; the absence of a recovery link does not rule out the error. The official guide also explains why the corresponding email might not arrive. Q5

5. Plan a limited recovery action. If the public site is down, first establish the backup available, the previous versions and the extension actually involved. Then decide whether a particular component needs to be temporarily disabled or a verified earlier state restored. Record which functionality will be temporarily unavailable and how the return to normal operation will be checked.

6. Investigate the combination in a test environment. Yoast recommends a controlled conflict test and describes the use of staging or a troubleshooting mode. For this error, first examine the relationship between the main plugin and the Yoast add-on. Indiscriminately disabling every store feature on the public site is not a useful basis for comparison. Q6

7. Check the actual page content afterwards. Open the previously affected pages as a visitor who is not logged in. Check product display, navigation and the intended SEO output. An HTTP status alone cannot show whether the expected content is present. Then check whether the same error appears in the log again.

Which version should I install?

The right decision depends on the complete combination. As checked on 4 November 2026, the official changelog for Yoast WooCommerce SEO 17.0, released on 27 October, requires at least Yoast SEO 28.8 and WordPress 7.0. Updating the add-on alone to 17.0 while keeping Yoast SEO 28.7 would therefore not be an appropriate recommendation. Q4

The exact installed version of the WooCommerce SEO add-on is not established in the original case. The thread therefore does not support a reliable claim that “updating from version X to version Y fixes it”. Q1

Check the requirements of your intended target version, whether a complete backup is available, and the result in your test environment. Do not replace the missing class with an empty class copied from the internet: that would leave unresolved what functionality the calling code expects and whether the site is behaving correctly.

Frequently asked questions

Why does the administration area still work when visitors see an error?

Different page requests can execute different code paths. The specific affected URL and its stack trace are therefore what matter for investigation. Test the public site separately and check it again after a change.

Does “Class not found” always mean that the installation is damaged?

No. In this case, the class removal can be traced in the official change history. An incomplete update remains a general possibility, but it needs to be checked against the actual installed package. Q3

Does a forum thread marked “Resolved” prove that a fix was found?

No. The public discussion directs the user to the support team responsible for the affected add-on. A referral does not replace a documented successful test of a specific version combination. Q1

Can I simply go back to an older Yoast version?

A verified earlier state can form part of a limited recovery. A lasting solution, however, requires a current, compatible combination. Document the recovery route and the subsequent update plan; do not overwrite changes you have not identified merely because you suspect a particular cause.

What is the difference between a deprecated warning and this error?

An older, related discussion describes a warning about Request_Helper::is_rest_request, which had been deprecated since Yoast 23.6. The case covered here concerns a class that is no longer present. A historical warning can point to an old caller, but it is not the same failure. Q7

What information should I include in a support request?

Provide the separate versions of the main plugin and add-on, the time of the change, and a sanitised error message that includes the calling file. Add which public pages fail and whether a tested recovery is available. Login credentials and a complete database do not belong in the initial request.

Describe your issue

Describe the most recent change and include the exact error message and your plugin combination. This helps establish whether the removed helper, a different caller or a separate error needs to be investigated. The next step should fit the versions actually installed on your website.