Permanent and temporary URL changes
A redirect helps an existing address lead to another destination. Server responses such as 301 and 308 indicate a permanent move, while 302 and 307 are used for temporary changes. The appropriate choice depends on whether the original location is expected to return.
For search, permanent redirects are a signal that the destination should be treated as the canonical URL. Google recommends server-side redirects where possible. Its redirect documentation explains the supported options and their intended uses.
Example: replacing an old service URL
If an old web development page is replaced with an equivalent page in a new service hierarchy, map the old address directly to that new page. Update navigation, body links and sitemap entries to use the destination itself. Visitors following an old bookmark still have a route to the relevant information.
Keep a migration table showing each old URL, its decision and its destination where applicable. Do not assume that every retired page belongs on the homepage. A replacement should serve the original request closely enough to make sense to the visitor.
Checking redirects after implementation
- Confirm the intended response code and final destination.
- Check that the destination loads successfully and describes the right subject.
- Remove loops and unnecessary intermediate hops.
- Review important query parameters before discarding them.
- Check internal links and canonical tags for old addresses.
Redirect rules deserve particular care around forms, APIs and account pages because requests can carry actions as well as page views. Review those flows separately from ordinary content navigation, and keep the redirect inventory available for later site changes.
Common questions about redirect
Can I replace internal links instead of using redirects?
Update internal links to their final addresses. Existing external links, bookmarks and search results may still use the old URLs, so a migration can need both direct links and suitable redirects.
Is a canonical tag a redirect?
No. A canonical tag states a preferred indexing URL while leaving the current page accessible. A redirect changes where the request is sent.
Related definitions
- Canonical URL — The preferred URL for a page when identical or substantially similar content is accessible through multiple addresses. A canonical link communicates a preference rather than forcing a redirect.
- HTTP status code — A response code communicating the result of a request. Examples include 200 for a successful response, 301 for a permanent redirect and 404 for a resource not found.
- Internal link — A hyperlink between pages on the same website. Useful internal links connect related subjects, explain the site structure and give readers a relevant next step.
- Technical SEO — Improving the technical foundations of search access and understanding, such as crawlability, indexing signals, URL handling, rendering and performance.
Related SEO guides
Use a direct permanent redirect when a page genuinely moves, and check that it reaches the most relevant destination without a chain.
For help connecting these decisions with your website, explore our SEO services or start with an SEO audit.
Put it into practice
Explore our technical seo service or talk with Refined IT about applying this to your website or business systems.