A 301 redirect sends visitors and search engines from an old web address to a new one automatically, set up either in the server configuration, in the hosting control panel, or through a plugin in your content management system. Set up correctly, Google passes along nearly all of the ranking value the old page had built up. Businesses that lose rankings after a site move almost always lost them to missing or misconfigured redirects, not to the move itself. Anyone renaming a single page, relaunching a full site, or moving to a new domain needs this one technical setting in place first.
301 versus 302: why the difference matters
Status code 301 means “moved permanently” and is the right choice whenever an old address is being replaced for good. Browsers and search engines remember that response and go straight to the new address on future visits. Status code 302 means “moved temporarily” and belongs in situations where the old address will come back soon, such as a short maintenance page or a seasonal promotion. If a permanent change gets set up as a 302 by mistake, Google keeps treating the old address as a separate page for longer and passes along ranking value more slowly. For a domain move, a relaunch, or a deleted page, 301 is almost always the right code.
When a home service business actually needs one
Four situations come up regularly for contractors and other local service businesses:
- Domain move. The business switches from an old domain to a new one, often after a rebrand or a change in who manages the site.
- Relaunch with a new URL structure. Pages get more descriptive addresses, for example moving from
/services.htmlto/kitchen-remodeling/. - Merging pages. Two similar service pages get combined into one longer, more useful page.
- Deleting a single page. A seasonal promotion, an old service area page, or a discontinued service disappears from the site for good.
The same rule applies in all four cases: every old address that had visitors, backlinks, or a Google ranking needs its own redirect to the closest matching new page.
How to set up a 301 redirect
Which method fits depends on your hosting and your platform.
| Method | Where | Effort | Typical use |
|---|---|---|---|
.htaccess file | Server root on Apache hosting | Medium, requires exact syntax | Single pages, small moves |
| Hosting control panel | Provider dashboard (SiteGround, Bluehost, GoDaddy) | Low, form-based | Domain move without server access |
| CMS plugin (e.g. Redirection for WordPress) | Plugin settings in the admin area | Low, form-based | Ongoing maintenance as URLs change |
| Nginx server config | nginx.conf or the site’s server block | High, needs server access | Larger migrations with many rules |
For a single .htaccess redirect, one line does the job:
Redirect 301 /old-page/ https://www.example-business.com/new-page/
A full domain move rarely works with single rules like that alone. It usually needs either a wildcard rule that mirrors every old path onto the same path on the new domain, or a full mapping table of old to new addresses when the URL structure changes at the same time. Businesses that run their site through Mr.Site do not have to maintain that mapping themselves. It is handled as part of ongoing managed website service whenever a move happens.
The most common redirect mistakes
- Redirect chains. Address A points to B, and B points to C, instead of pointing A straight to C. Googlebot follows a chain up to ten hops according to its own documentation, but often only about five per crawl attempt, after which the attempt gives up and treats the page as unreachable.
- Everything routed to the homepage. A discontinued service page gets redirected to the homepage by default instead of to the matching service category. Google often treats a mismatched redirect like a soft 404 and passes along no ranking value.
- Forgotten addresses from old sitemaps. Redirecting only the links currently visible in the menu misses addresses that still live in old sitemaps, email signatures, or printed materials.
- Turning redirects off too soon. The redirect gets removed after a few weeks, even though backlinks and bookmarks keep pointing to the old address for much longer.
What actually happens to your ranking
Google confirmed back in 2016 that a 301 redirect by itself no longer costs any ranking value, as long as the old and new pages match in content. In practice the transfer still takes some time: Google has to crawl the new address, confirm the redirect, and carry over the existing ranking signals, which rarely happens overnight. For a full domain move, the Change of Address tool in Google Search Console helps track progress. It spot checks the redirect on the site’s top addresses and marks the move as active for a 180 day window. Search Console’s coverage and crawl reports are also where you can see which old addresses are still getting crawl requests.
How to test that a redirect actually works
- Open the old address directly in a browser and confirm it lands on the expected new page, not just the homepage.
- Check the actual status code from the command line:
curl -I https://www.example-business.com/old-page/shows a line with301or302in the response. - Use a free redirect checker tool if a terminal is not available. It shows the same status code in a simpler format.
- Test again about a week after the change, since hosting or CMS updates sometimes reset redirect rules without warning.
Your next step
A 301 redirect is a one time technical setup that needs little attention afterward once it is configured correctly. Before a relaunch, it is worth deciding whether a full rebuild even makes sense, which the article on redesign or rebuild walks through in more detail. Mr.Site manages several hundred business websites and handles redirects during a relaunch, domain move, or page cleanup as part of ongoing service, so no ranking and no backlink gets lost along the way.