What Are Redirects?
A redirect sends someone from one web address to another. If an old page moved, the redirect tells the browser and search engines where the useful page now lives. Redirects matter because broken or messy routes can waste crawl time, split signals and send buyers to the wrong place.
Simple answer: A redirect is a forwarding rule for a URL. Use it when a page moves, a URL changes, duplicate versions need consolidation or an old page should point to a better replacement.
- What a redirect means in plain English
- When to use a permanent or temporary redirect
- Why redirect chains and loops create risk
- How redirects differ from canonical tags
- What to check during a redesign or migration
- Why sitemaps and internal links should point to final URLs
- How redirects support Revenue Infrastructure
Plain meaning: this lesson connects the beginner definition to the business system Groew builds around it.
A redirect is a forwarding rule for a URL
Think of a redirect like a sign on an old shop door. The shop has moved, so the sign tells visitors where to go next.
On a website, the old URL responds with a redirect status code and a new location. The browser follows that route. Search engines follow it too and decide which URL should stay in search results.
The redirect should point to the closest useful replacement. Sending every old URL to the homepage usually creates confusion because the destination does not answer the same need.
Permanent and temporary redirects send different signals
The main beginner choice is permanent or temporary. A permanent redirect tells search systems the move should last. A temporary redirect says the old page may come back.
Google treats permanent redirects as a signal that the new target should become the canonical page. Temporary redirects usually keep the source URL as the one search should remember.
Use the status code that matches the business decision. Do not use a temporary redirect for a page that is gone forever.
| Redirect type | Common code | Plain meaning | Use when |
|---|---|---|---|
| Permanent | 301 or 308 | This page moved for good | A URL changed, a page merged, or an old service page has a final replacement |
| Temporary | 302 or 307 | Use this other page for now | A page is unavailable for a short time or a campaign needs a short route |
| Meta refresh | Page level refresh | The page tells the browser to move | Only when server side control is not available |
| JavaScript redirect | Script based route | A script changes the page location | Only when cleaner server side redirects are not possible |
Use redirects when the old URL still has value
Redirects are useful when a page moves, a site changes domain, two pages merge, a product or service page is replaced, or duplicate URL versions need one preferred destination.
They are also important during redesigns. A redesign often changes URLs, navigation and templates at the same time. Without a redirect map, the site can lose the routes that carried search value and buyer bookmarks.
Not every deleted page needs a redirect. If there is no relevant replacement, a clean 404 page can be more honest than sending people to an unrelated page.
Redirect chains and loops make routes harder to trust
A redirect chain happens when URL A redirects to URL B, then URL B redirects to URL C. A loop happens when redirects send visitors in a circle.
Chains add friction for browsers and crawlers. Loops can stop the page from loading at all. Both usually appear after migrations, CMS changes or years of small URL updates.
The cleaner fix is to update the old URL so it redirects directly to the final destination. Internal links should also point to the final URL instead of relying on the redirect.
| Problem | What it looks like | Better fix |
|---|---|---|
| Redirect chain | Old page to middle page to final page | Point old page directly to final page |
| Redirect loop | Page A to page B to page A | Break the circular rule and choose one final destination |
| Homepage dump | Many old pages point to homepage | Map each old page to the closest matching useful page |
| Internal redirect | Site links point to an old URL | Update the internal link to the final URL |
Redirects are not the same as canonical tags
A redirect sends people and bots to another URL. A canonical tag keeps the page accessible while asking search systems to treat another URL as the main version.
Use a redirect when the old page should no longer be used. Use a canonical when similar pages still need to exist but one version should represent the group.
If a page both redirects and declares a different canonical target, the site is sending mixed signals. Keep the route simple.
A redesign needs a redirect map before launch
The safest time to plan redirects is before the URL change goes live. Export current URLs, decide which pages stay, which pages merge, which pages disappear and which new URL each old page should reach.
After launch, crawl the old URL list and confirm each important old URL returns the intended redirect. Then inspect priority pages in Search Console after Google has recrawled them.
This is basic website governance. It prevents a design launch from becoming an organic traffic loss event.
| Old URL status | Redirect decision | Check after launch |
|---|---|---|
| Same page, new URL | 301 to new matching page | Old URL resolves to final URL in one hop |
| Merged page | 301 to strongest relevant page | Destination answers the same intent |
| No replacement | 404 or 410 when appropriate | Custom error page gives useful next routes |
| Temporary outage | 302 or 307 to temporary page | Old URL can return when the outage ends |
Check redirects with final URLs, sitemaps and internal links
A redirect is not finished when the rule is added. You still need to check whether the final URL is the correct destination, loads with a clean status and appears consistently in internal links, canonicals and the sitemap.
For important pages, test the old URL, the destination URL and the internal routes that point there. If the sitemap lists redirecting URLs, update it to the final canonical URL.
The practical rule is simple. Search systems should see the final preferred URL everywhere the business controls.
Redirects protect Revenue Infrastructure during change
Revenue Infrastructure depends on owned pages staying findable through redesigns, migrations and content cleanup. Redirects protect that ownership when URLs change.
A weak redirect plan turns old search value into dead ends. A strong redirect plan keeps buyer routes, search signals and reporting history connected to the new structure.
For Groew, redirects are not background technical admin. They are part of keeping the acquisition system intact while the website improves.
Working notes from Groew
Use these notes when you turn the lesson into a real page, campaign or acquisition decision. This is where the idea becomes operational.
2026 research and expert notes
Use these notes to understand how current search updates, AI answer surfaces and audit platforms change the way this topic should be checked.
Search standards to keep in mind
Use these rules as guardrails before changing page structure, links or crawl settings. They keep the lesson connected to current search standards instead of one off tactics.
Redirect problems usually show up after the celebration of a new website. The pages look better, but the old routes are broken. In one redesign recovery, the team had more than 200 technical issues, broken redirect paths and weak internal links. Fixing the foundation helped stop the decline within 90 days, and the business later reached 111 percent more marketing qualified leads within 12 months. Redirects mattered because they protected the route between old demand and the new website.
Questions about What Are Redirects?
Where this connects next
Use these links after the core lesson is clear. Each route takes the internal linking idea into a file, tool, service or next decision.
Learn the next topic here.
These lessons continue the same business problem from a different angle. Use them to move from one definition to a working acquisition system.
Read the deeper Groew analysis.
These insights connect the lesson to search visibility, AI answers, and Revenue Infrastructure decisions.
Check what this means for my business.
Use Groew's free tool to turn this lesson into a practical next step for your website, ads or acquisition system.
Run My Free Check