A 301 redirect tells browsers and search engines that a page has moved for good. When someone requests the old URL, the server responds with a 301 status code and forwards them to the new address automatically. It's the standard way to preserve traffic and rankings when you change a URL, merge pages, switch domains, or move from HTTP to HTTPS. Because it passes along the bulk of the old page's authority, the 301 is the single most important tool for protecting SEO value during any site change.
What a 301 Redirect Is and Why It Matters for Local SEO
The "301" is an HTTP status code that means "Moved Permanently." Unlike a 302 (temporary), it signals to Google that the change is final, so the search engine should transfer indexing and ranking value to the destination and eventually drop the old URL from its index.
For a local business, that permanence protects hard-won equity. If a dental practice rebuilds its site or a plumber consolidates duplicate service pages, a proper redirect keeps the traffic, links, and local rankings intact instead of dumping visitors onto a 404.
- Preserves most link authority pointing at the old URL
- Keeps existing visitors and bookmarks from hitting dead ends
- Prevents duplicate content when the same page lives at two addresses
- Consolidates ranking signals onto a single canonical URL
How a 301 Redirect Works
When a browser or crawler requests the old URL, the server answers with a 301 status and a Location header pointing to the new URL. The client then loads the destination. Google follows the same path, updates its index over time, and shifts the ranking signals across.
Redirects can be set up in several places depending on your platform. The method matters less than getting a clean, single-hop 301 that points straight to the final destination.
- Apache servers: rules in the .htaccess file
- Nginx servers: directives in the site config file
- WordPress and other CMS: a redirect plugin or built-in tool
- Managed platforms like Shopify or Wix: a redirect settings panel
How to Set Up and Verify a 301
Map every old URL to its closest matching new URL before you flip the switch. A one-to-one map beats sending everything to the homepage, which Google often treats as a soft 404.
After launch, confirm each redirect returns a real 301 and resolves in a single hop. Google's own guidance on redirects in the Search Central documentation explains how crawlers handle each type.
- Build a spreadsheet mapping old URLs to new ones
- Check the status code with a browser inspector or a header-checking tool
- Test on mobile and desktop, and follow the chain end to end
- Submit the updated sitemap in Google Search Console after the change
Common Mistakes to Avoid
Most 301 problems come from sloppy setup, not the redirect itself. Redirect chains and loops waste crawl budget and slow users down, and irrelevant destinations frustrate everyone.
- Chaining redirects (A to B to C) instead of pointing A straight to C
- Creating a loop where two URLs redirect to each other
- Sending all removed pages to the homepage instead of a relevant match
- Using a 302 for a permanent move, which delays the transfer of signals
- Forgetting to update internal links so they point at the final URL
Best Practices
Treat redirects as part of any URL change, not an afterthought. Keep them clean, keep the map current, and monitor the results. When you move a whole site or restructure a local service area, a solid redirect plan is what keeps your rankings from cratering, and a platform like RankSphere can help you track local visibility before and after the move.
- Redirect at the URL level, one old page to one new page
- Keep 301s in place at least a year so Google fully processes them
- Update internal links, canonical tags, and sitemaps to the new URLs
- Monitor Search Console coverage and crawl stats for errors after launch
Related Terms
A 301 sits alongside a handful of concepts you'll run into whenever you change URLs. Knowing the difference keeps you from picking the wrong tool.
- 302 redirect: a temporary move that keeps the original URL indexed
- Canonical tag: signals the preferred version of similar pages without redirecting
- 404 error: a page that no longer exists with no forwarding address
- HTTP status codes: the family of server responses a 301 belongs to