301
http://example.com
Moved Permanently
Build and simulate redirect chains visually. See every status-code hop, spot loops, and quickly identify long redirect paths.
Keep redirect chains as short as possible. Each extra hop adds avoidable latency for users and crawlers.
Use 301 for permanent moves and 302 only when the redirect is genuinely temporary and should not replace the indexed URL.
Update old redirects to point directly to the final destination instead of stacking multiple historical redirects together.