What is a 301 redirect?

301 is the HTTP status code for “Moved Permanently”. The server answers the old URL with a 301 and the new address in the Location header, and the browser or search engine follows it. Temporary moves use 302 or 307. With a permanent redirect, Google gradually passes signals to the new URL and drops the old one from the index.

#Why it matters

If you change a URL, delete a page or move domains without a 301, links and visitors to the old address hit a 404 and the rankings you earned disappear. Correct 301s carry that value over to the new page.

#Where you see it in SEOAsist

Technical Audit follows redirects on internal links: a single hop is reported as Redirected internal link (Info), two or more hops as Redirect chain (2+ hops), and rules that point at each other as Redirect loop. The hint for Broken internal link (4xx) also suggests fixing the target or redirecting it with a 301.

Ways to set up redirects from the panel: a redirect rule in Site API returns a server-side 301 by default, and the WordPress plugin performs 301 redirects. Pixel's Redirect rule, by contrast, is a client-side bridge that runs in the browser, not a real 301. Details: Connect Site API.

#Example

GET /old-boiler-page HTTP/1.1

HTTP/1.1 301 Moved Permanently
Location: https://site.com/boiler-service

#Common mistakes

• Using a 302 for a permanent move.
• Redirecting every deleted page to the homepage; Google may treat these as soft 404s. Redirect to the closest relevant page.
• Adding the redirect but leaving internal links on the old URL; update links to point straight at the new address.
• Stacking new redirects on old ones and creating chains.