Best practices 9 min read 2,038 words By LaiUse Editorial Team Reviewed 28 October 2026

How to Set Up a Redirect That Search Engines Respect

How to Set Up a Redirect That Search Engines Respect: When a page is moved, the old URL may already have links, bookmarks, appearances in search results…

Why this matters

When a page is moved, the old URL may already have links, bookmarks, appearances in search results, and references from other websites. A properly configured redirect tells search engines that the content has a new permanent address and helps them discover the replacement. The goal is not merely to make the old link open something; it is to preserve the relationship between the old URL and the new one without leaving search engines to guess.

Search engines commonly use redirects to follow a page to a new location. A permanent redirect is usually the right choice for a lasting migration, while a temporary redirect is more appropriate when the destination is expected to change back. In practice, a single, direct redirect is easier for a crawler to interpret than a sequence of intermediate URLs. A chain such as old-page to intermediate-page to final-page adds another request and can dilute or complicate the path that search engines use to identify the canonical destination.

A canonical tag and a redirect solve different problems. A canonical tag is a page-level instruction declaring which URL should be treated as the preferred version when similar or duplicate pages are available. It does not make a request to one URL physically become another URL. A redirect changes the response and sends the visitor or crawler to a destination. For a page that has permanently moved, a redirect is the stronger tool; a canonical tag can then be used to reinforce the preferred URL on the new page, provided it is not contradictory.

The tools in this guide are inspection and link-creation aids rather than a redirect-configuration system. The canonical-tag-checker and noindex-checker can help identify page-level signals that may interfere with a migration. The url-shortener can create a short link with an optional custom alias, but it is not a substitute for controlling permanent redirects on a website.

The process

  1. Record the old and new URLs.

    Write down the exact old address and its intended permanent destination. Include the protocol, hostname, path, and any important query parameters. If the old page has several meaningful variants, decide separately where each one should lead rather than sending every URL to the same home page.

  2. Determine whether the move is permanent or temporary.

    Use a permanent server-side redirect for a page that is expected to remain at the new address. Use a temporary redirect only when the change is genuinely temporary, such as a short-term campaign destination or a maintenance path. Choosing the wrong type can create an unnecessary later migration.

  3. Configure the redirect at the web server or hosting layer.

    The redirect must be part of the website's response, not just a note in a content-management system or a link change on one page. Configure the old URL to return a redirect response to the new URL, and avoid redirecting the old URL back to itself. If the site has a preferred trailing-slash, protocol, or hostname, account for that so that a single page has one clear destination rather than several competing versions.

  4. Keep the redirect path direct.

    If an old address already points to an intermediate address, change the old address to point directly to the final destination, or update the intermediate address so that the complete path is consistent. A crawler should not need to follow a long sequence of redirects to discover the page's real location. Avoid chains, loops, and redirect rules that send one old URL to different destinations depending on unrelated conditions.

  5. Update internal links where possible.

    Links within the site should point to the new URL instead of relying on the redirect. This improves navigation and reduces the number of requests needed to reach the page. Update important navigation, templates, XML sitemaps, and other references that you control. External links cannot usually be changed immediately, which is why the old URL still needs a valid permanent redirect.

  6. Check the canonical signal with canonical-tag-checker.

    Provide the old URL and the new URL to canonical-tag-checker so that the canonical declarations can be compared. The old page should not point to a different preferred version than the one being established, and the new page should identify itself as the preferred destination. The checker is for examining the page's canonical information; it does not create or configure a redirect.

  7. Check for indexing instructions with noindex-checker.

    Provide the relevant URLs to noindex-checker and verify that the new page is not accidentally excluded from indexing. A page that has been moved should not carry an unintended noindex directive merely because it was used to be hidden during an earlier stage of the migration. The checker helps reveal the directive; it does not remove it.

  8. Verify the response and follow the path.

    Request the old URL and confirm that it returns a redirect rather than an ordinary page, a not-found response, or a loop. Follow the entire path to the final URL. Then request the final URL and confirm that it responds normally. If the path contains an intermediate address, remove that extra step where possible. Finally, review the canonical and indexing results again after the server configuration and page content are in place.

Worked example

Suppose a company moves an article from https://example.com/old-guide to https://example.com/resources/new-guide. The old URL appears in search results and has received links from other sites. The migration should preserve that path by returning a permanent redirect from https://example.com/old-guide directly to https://example.com/resources/new-guide. The article's internal links, navigation entries, and sitemap entry should be updated to use the new address.

After the change, the publisher provides both addresses to canonical-tag-checker. The new page's canonical declaration points to https://example.com/resources/new-guide, while the old URL does not introduce a conflicting preferred destination. The publisher also provides the new address to noindex-checker to ensure that a noindex instruction has not been left in place from an earlier staging or review period. These checks are important because a valid redirect cannot fully do the work of an indexing instruction or a canonical declaration: the redirect tells a crawler where to go, while the other signals describe how the destination should be interpreted.

A separate contractor wants a short link for a campaign and opens url-shortener. The interface provides Long URL, Custom Alias (optional), and Copy to clipboard. Entering https://example.com/resources/new-guide and choosing a custom alias such as newguide can create a shortened campaign link. That may be useful for communication, but it does not replace the website's permanent redirect from the old article URL. The article should still use the full new address as its canonical and internal destination, with the old URL configured on the site itself.

Common mistakes

Limitations of this approach

Frequently asked questions

Is a canonical tag the same as a redirect?
No. A redirect sends a request to another URL. A canonical tag declares which URL should be preferred when multiple pages are similar or duplicate. For a permanent page move, use a redirect and ensure the new page's canonical signal is consistent.

What redirect should I use when permanently moving a page?
A permanent HTTP redirect is the usual choice for a page that is expected to stay at its new address. A temporary redirect is more suitable for a destination that is expected to change again. The final choice should match the actual migration plan and be implemented on the server or hosting platform.

Can I use a shortened URL instead of a permanent redirect?
Not for a normal page migration. url-shortener is designed to create a shortened link, with Long URL, Custom Alias (optional), and Copy to clipboard available in its interface. Use it for link distribution when appropriate, but configure the old page URL itself to redirect to the new page.

How do I check whether the new page has a canonical tag?
Provide the URL to canonical-tag-checker and review the reported canonical information. The tool helps identify the declared preferred URL; it does not edit the tag or create a redirect.

How do I check whether a page is marked noindex?
Provide the URL to noindex-checker. If the moved destination contains an unintended noindex instruction, correct it in the page or template source, then check the URL again. The checker only reports the condition.

What is a redirect chain?
It is a sequence in which one URL redirects to another, which redirects again before reaching the final page. For example, an old URL might point to a legacy URL that points to the current URL. Pointing the old URL directly to the final destination makes the path simpler.

Does updating every internal link remove the need for a redirect?
No. Internal links are only one source of traffic. The old URL may still be linked from external websites, bookmarks, messages, or outdated references, so a direct permanent redirect should remain in place.

What should I verify after configuring the move?
Verify that the old URL returns the intended redirect, that the path reaches the correct final URL without a loop or unnecessary chain, and that the final page loads normally. Then use canonical-tag-checker and noindex-checker to review the destination's canonical and indexing signals.

The tools in this guide: canonical tag checker · noindex checker · url shortener — each runs in your browser, so your data stays on your device.

Browse every guide · Read the blog · About LaiUse