Blog
301 redirect: meaning and differences from 302
A 301 redirect is a server response that sends a request from one URL to another and signals a permanent move. The browser requests the old address and receives the destination it should visit. A 302 signals a temporary move. The right choice depends on whether you expect the original address to become the current one again.
Google treats permanent and temporary moves as different signals about which address should represent the content in search results. A 301 does not guarantee preserved rankings or an immediate index update. Google’s redirect documentation covers the options, including 308 for permanent moves and 307 for temporary ones.
Map the URLs before changing them
Imagine a bicycle repair shop reorganizing its website. This fictional map separates four situations that might look similar in a list of old addresses:
| Old URL | Situation | Proposed treatment |
|---|---|---|
/brake-service/ |
The same service moves to /repairs/brakes/ |
301 to the new service page |
/bookings/ |
Bookings temporarily move to another page during maintenance, then return to the original URL | Consider 302 to the temporary destination |
/april-offer/ |
The offer ended with no equivalent replacement | Consider removal with 404 or 410 |
/blog/chain-care/ |
The article remains current at its existing address | Keep the URL |
The site maintainer can use this map to configure the changes in the host or CMS. Each row needs a content check: the replacement service must answer what visitors expected from the old page.
Why the homepage is often a poor destination
Someone opening an old brake repair link expects information about brake repair. Sending them to a general homepage forces another search and can disguise the fact that the original material has disappeared. A redirect makes sense when the source and destination provide continuity. Without a relevant replacement, a useful error page may be appropriate.
If a destination changes again, aim to send the original address directly to the final one. A → B → C adds another hop for visitors and crawlers. A loop such as A → B → A prevents them from reaching the content. Update internal links to use the current URL, and remove redirected addresses from a sitemap listing canonical pages.
How to check a 301 redirect
Request the old URL and inspect its first HTTP response and Location header. Then examine the final response. Is it the intended address? Does the complete page load? Is indexing allowed if the destination should appear in search? Opening the new address on its own only checks the destination; it does not establish that the old one redirects correctly.
Ask the site maintainer to record source, initial status, destination and final status for each row. Include an unchanged URL to detect an overbroad rule. After release, repeat the checks on the public domain, since preview environments can use different routing rules.
When a canonical declaration fits
If several addresses need to stay accessible with duplicate content, a canonical declaration identifies the representative without moving visitors. When content has disappeared, examine the decision for a 404 URL. Decide what should happen to the content first; that makes the server response easier to choose.
Plan your next post in HeyMark.
Keep the idea, review the draft with your team, and see how it performed in the accounts you connected.