Permanent redirect: moving a page to a new address
A permanent redirect tells browsers and search engines that content at an old URL has moved to another address on a lasting basis. HTTP implementations commonly use 301 or 308 with a Location header identifying the destination. Visitors are automatically sent to the new address.
Also known as: 301 redirect · 308 redirect
At a glance
- A permanent redirect communicates a lasting move and sends requests onward.
- The replacement destination should match the old page’s purpose.
- Update your own links and sitemap to the new address as well.
On this page

When a change is a genuine move
An old guide URL can remain in bookmarks, emails and other websites after the content moves. A permanent redirect gives those entry points an appropriate destination without requiring visitors to search again.
Typical cases include a deliberate path rename or domain move. The change should be lasting and the destination a real successor. A temporary promotion or short maintenance period does not automatically qualify.
301 and 308
Both are permanent-redirect HTTP status codes. Google uses permanent redirects as strong signals of the preferred new address. Redirect guidance
Their HTTP semantics differ: 308 preserves the request method, while some clients may change the method after a 301. This may be invisible for an ordinary page visit but important for forms and APIs. HTTP redirections
HTTP/1.1 301 Moved Permanently
Location: https://example.com/guides/coffee-machine-cleaning
This is an illustrative response, not a universal rule for every removed page.
Different from canonical or noindex
A canonical URL signal suggests a preferred version while the current page can remain accessible. A redirect sends the visitor onward. Canonicalization
Noindex requests exclusion from search indexing; it neither identifies the new location nor takes visitors there. A temporary redirect communicates a temporary destination change. Choose according to the actual content decision.
Example: a cabinetmaker’s renamed service page
Imagine a fitted-wardrobe page moving from /service-2 to /custom-wardrobes. Customers have saved the old link, and a partner still references it.
The maintainer confirms that the new page represents the same service, redirects the old address directly to it and updates menus, articles and the XML sitemap. Existing external entry points continue to work, while internal navigation reaches the new page directly.
After a later rename, update older redirects to the current destination where possible instead of accumulating unnecessary intermediate steps.
Verify the complete route
Inspect the old URL’s initial response, Location destination and final content. The target should be accessible and should not loop back or replace formerly public content with a login barrier.
Test several examples when using pattern-based rules. A broad pattern can accidentally send unrelated pages to the wrong successor. The browser’s final address alone does not validate the whole rule set. Status-code guidance
What happens in search?
Google needs to process the relationship again. A redirect provides no guaranteed timetable or traffic preservation. Old and new URLs may temporarily appear differently in reports.
For a website migration, coordinate redirects with internal links and canonical signals. Prefer a direct appropriate destination over an avoidable redirect chain.