WordPress站点出现302状态码问题，.htaccess中301规则该如何处理？

Hey there! Let's walk through this together—first off, don't delete or modify that 301 rule in your .htaccess file. Let me explain why, then help you track down the actual cause of your 302 issue.

先说说那个301规则的作用 #

The line RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L] is a default WordPress multisite rule. It simply ensures that anyone visiting yourdomain.com/wp-admin (or yoursubsite.com/wp-admin for multisite) gets redirected to yourdomain.com/wp-admin/ (with a trailing slash). This is a standard, harmless 301 permanent redirect that only affects the wp-admin path—it's not the reason your entire site is returning 302s.

导致全站302状态码的常见原因 #

Your SEO tool's warning about 302s is likely coming from your main site pages, not the wp-admin area. Here are the most common culprits to check:

• Mismatched Site URLs: Go to your WordPress dashboard → Settings → General. Verify that both the "WordPress Address (URL)" and "Site Address (URL)" are identical (including http/https and www/non-www). A mismatch here often triggers unintended redirects.
• Plugin Conflicts: Temporarily deactivate all plugins, then recheck your site's status code. If the 302 goes away, reactivate plugins one by one to find the culprit (cache plugins, security plugins, or redirect plugins are frequent offenders).
• Theme Issues: Switch to a default WordPress theme like Twenty Twenty-Four. If the 302 disappears, your current theme might have custom redirect code using wp_redirect() (which defaults to 302) that's causing problems.
• Server Configuration: Check if your host has any forced redirects set up (e.g., from HTTP to HTTPS, or www to non-www) that's misconfigured. If you're using Nginx instead of Apache, make sure your server block doesn't have incorrect redirect rules.
• Custom Code: Look for any custom functions in your theme's functions.php file or a custom plugin that uses wp_redirect() without specifying a 301 status.

如何排查具体跳转目标 #

To get more clarity on where your site is redirecting to, run this command in your terminal (replace yourdomain.com with your actual site URL):

curl -I https://yourdomain.com

The output will show the 302 status and the Location header, which tells you exactly where the redirect is pointing—this is super helpful for narrowing down the issue.

Remember: The 301 rule in your .htaccess is doing exactly what it's supposed to, so leave it as is. Focus on the above checks to fix your site-wide 302 problem.

内容的提问来源于stack exchange，提问作者Alisha