{"id":874,"date":"2025-05-18T23:04:58","date_gmt":"2025-05-18T15:04:58","guid":{"rendered":"https:\/\/virtualcardx.com\/?p=874"},"modified":"2026-07-07T00:29:32","modified_gmt":"2026-07-06T16:29:32","slug":"translatepress-gsc-redirect-error-fix","status":"publish","type":"post","link":"https:\/\/virtualcardx.com\/en\/2025\/05\/18\/translatepress\u5bfc\u81f4gsc\u4e2dredirect-error\u9519\u8bef\u7684\u5904\u7406\u65b9\u6cd5\/","title":{"rendered":"How to deal with Redirect error in Google Search Console caused by TranslatePress"},"content":{"rendered":"

Recently, I was using TranslatePress to add multi-language support to my website, and after I added English, I suddenly found that a lot of Redirect errors appeared in GSC, as shown in the following figure<\/p>\n

\"\"<\/figure>\n

Here's a look at the errors all appearing on the English page<\/p>\n

\"\"<\/figure>\n

Initially, the error is caused by the multi-language plugin<\/p>\n

Testing with curl<\/p>\n

\"\"<\/figure>\n

The server reports a 301 code, meaning redirection.<\/p>\n

To deal with this, I rummaged around in the TranslatePress backend and finally found the SEO related settings<\/p>\n

\"\"<\/figure>\n

Here's the last one.<\/p>\n

Load legacy SEO Pack Add-On<\/p>\n

In case the recent migration to the new slug rewrite is causing trouble, set this to Yes to use the old method
after checking<\/p>\n

Testing with curl again<\/p>\n

\"\"<\/figure>\n

bingo, problem solved!<\/p>\n

Re-submit the verification in the GSC backend<\/p>\n

\n

\n
\n

How to Resolve Redirect Errors Caused by TranslatePress in Google Search Console: Additional Notes and Usage Recommendations<\/h2>\n

This type of resource-based content is worth saving, but it also needs to be reviewed periodically. Tools, platforms, links, and rules are subject to change\u2014especially free resources, temporary services, and third-party platforms, which often become unavailable, undergo redesigns, or have regional access restrictions.<\/p>\n

Recommendations Before Use<\/h3>\n