2 versions of the site redirect only temporarily
Another version of your site's address (with or without www, or over the other protocol) redirects with a temporary status, 302, 303 or 307, instead of a permanent 301 or 308; the finding lists each one and where it points. Change these redirects to 301.
What it means
A temporary redirect (302 or 307) between site versions tells search engines the old address may come back, so they may keep both. Use a permanent 301 or 308.
Why it matters for AI search
A temporary redirect tells search engines that the old address will come back. They may keep it indexed next to the main one and keep checking it, so signals stay split for longer. A permanent redirect says the main version replaces the other for good.
Only the first response at the home page is checked, so a 302 that leads on to a 301 is still reported. Many tools use 302 by default: the plain redirect() in Express or Flask, rewrite ... redirect in nginx, R without a code in Apache, or a hosting panel's domain forwarding set to "temporary".
How to fix it
- Find where the redirect is set: the web server config, the host's domain or forwarding settings, a CDN rule or the application.
- Change the status to 301, or 308 if the request method must be kept. In nginx use
return 301; in Apache useR=301; in Cloudflare redirect rules choose 301. - Redirect straight to the final address in one step, not through a chain of redirects.
- Run the site audit again from your account to confirm the result.
Example
# nginx
return 301 https://example.com$request_uri; # not 302, not "rewrite ... redirect"
# Apache (.htaccess)
RewriteCond %{HTTP_HOST} ^www\.example\.com$ [NC]
RewriteRule ^ https://example.com%{REQUEST_URI} [L,R=301] How to confirm the fix
After the change, press "Check again" on the report: it lists what was fixed and how the score changed.