Permanent move
Text version
- /old-guide
- HTTP 301 · Location
- /new-guide
Why it matters
It is used when a page has genuinely moved or an old URL should permanently lead to a new one. Visitors and crawlers receive a working destination.
How it works
A request to the old URL receives a 301 response and a new address. Google treats a permanent redirect as a signal that the target should become canonical. Internal links and sitemaps should be updated to the destination.
Example
Example: /old-guide returns HTTP 301 with Location: https://example.com/new-guide. The new address should provide corresponding content.
Common mistakes
Do not redirect unrelated old pages to the homepage simply to avoid 404 responses. Avoid chains and loops. Choose an appropriate temporary status when the move is temporary.
How can you check this in practice?
For a permanently moved page, return 301 with Location pointing to the best corresponding new URL. Update internal links, the sitemap and destination canonical. Check the complete chain and that the final response contains corresponding content, not a generic homepage.
Distinctions and limitations
301 is permanent; 302 temporary. 308 is also permanent and preserves the method. Choose according to the move's intent. Redirects do not replace canonicals for versions that need to remain accessible to visitors.
Official sources
Editorial responsibility: Martin Zhelyazkov · Founder of Z-Consult
Updated: 05/11/2026
For a correction or question: office@z-consult.bg
