Geo-IP Redirect (Temporary)

What This Means

The site implements temporary (302) redirects based on the visitor's IP geolocation. This is the less-severe version of geo redirection compared to 301, but it still creates potential indexation issues where the wrong regional URL is indexed for different search markets.

Why It Matters for SEO

A 302 geo-redirect means the redirected URL (the regional version) retains the original URL as its "canonical" in Google's view. If Googlebot is redirected from / to /en-us/ via a 302, Google may index / as the canonical URL for the US version, which may conflict with how hreflang is configured.

The preferred solution for international SEO is to serve different content from different URLs without redirection (using hreflang to signal the relationship) or to redirect consistently to the user's regional URL with correct hreflang implementation.

What the Platform Checks

Detects 302 redirects targeting locale or country-specific URL variants. Fires when temporary geo-based redirects are found.

How to Fix It

• Implement hreflang correctly for all regional variants — this tells search engines which version to show in which country without relying on redirection.
• If geo-redirects are retained: use Vary: Accept-Language in the response headers to signal to caches that the response varies by visitor language/location.
• Ensure Googlebot can access the regional URL variant without requiring geo-detection — use a dedicated URL per region rather than detecting and redirecting.