WordPress Redirects and SEO: What You Need to Know
Redirects are essential for site maintenance, migrations, and affiliate marketing. But done wrong, they can hurt your search rankings. Here's what actually happens when search engines encounter redirects, and how to use them correctly.
How Search Engines Process Redirects
When Googlebot (or any crawler) requests a URL and receives a redirect response, it makes decisions based on the HTTP status code:
301 Moved Permanently
The canonical signal for permanent moves. Google's response:
- Updates the index to reflect the new URL
- Transfers ranking signals (PageRank, link equity) to the destination
- Caches the redirect for efficient future crawling
- Stops showing the old URL in search results
302 Found (Temporary)
Indicates a temporary situation:
- Keeps the original URL in the index
- Does not transfer link equity (historically, Google's handling has evolved)
- Rechecks the redirect regularly
- May show either URL in results depending on signals
307 and 308
HTTP/1.1 additions that preserve the request method:
- 307: Temporary redirect (like 302, but stricter)
- 308: Permanent redirect (like 301, but stricter)
For most WordPress use cases, 301 and 302 are sufficient.
Link Equity Transfer
"Link equity" (or "link juice") refers to the ranking power that backlinks provide. When sites link to your content, they pass authority. This authority is a major ranking factor.
With 301 redirects:
- Google now passes nearly 100% of link equity through 301s
- Historical penalties for redirect chains have been minimized
- The destination URL inherits the link profile of the source
Google's Official Position
In 2016, Google confirmed that 301, 302, and 307 redirects all pass full PageRank. The historical "30% loss" myth is outdated. However, 301 remains best practice because it sends the clearest signal about permanence.
Common Redirect Scenarios
Site Migration (HTTP to HTTPS)
When moving to HTTPS, every HTTP URL needs a 301 to its HTTPS equivalent. WordPress handles this automatically if you update your Site URL, but verify:
# .htaccess rule for Apache
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
Domain Change
Moving from oldsite.com to newsite.com requires redirecting every URL pattern. This is high-stakes: get it wrong and you lose years of SEO work.
- Map old URLs to new URLs (ideally 1:1)
- Implement 301 redirects on the old domain
- Keep the old domain active for at least a year
- Use Google Search Console's Change of Address tool
Content Consolidation
Merging multiple thin posts into comprehensive guides:
- Create the new comprehensive post
- 301 redirect old posts to the new URL
- Combined link equity strengthens the new page
Affiliate and External Links
Redirect posts for affiliate marketing are SEO-neutral:
- The redirect URL won't rank (it immediately redirects)
- Link equity passes to the external destination
- You're not trying to rank the redirect, you're managing the link
Redirect Chains and Loops
Redirect Chains
When URL A redirects to B, which redirects to C:
A → B → C
Google will follow chains (up to about 5 hops), but each hop adds latency. Best practice: point directly to the final destination when possible.
Redirect Loops
When A redirects to B, and B redirects back to A:
A → B → A → B → ...
This breaks crawling entirely. Browsers show "too many redirects" errors. Always test redirects after implementation.
WordPress-Specific Considerations
Canonical URLs
WordPress adds <link rel="canonical"> tags to pages. These tell search engines which URL is authoritative. Redirects and canonicals should align:
- If you redirect A to B, B's canonical should be B (not A)
- Conflicting signals confuse crawlers
Permalink Changes
Changing your permalink structure (Settings → Permalinks) doesn't automatically create redirects. Old URLs return 404. You need to:
- Create manual redirects for high-value old URLs
- Or use a plugin that automatically handles permalink changes
Plugin Conflicts
Multiple redirect plugins can conflict. If Plugin A redirects /page to /new-page and Plugin B redirects /new-page to /other, you create a chain. Audit your redirect rules periodically.
Testing Redirects
Always verify redirects work correctly:
Browser Developer Tools
- Open Network tab (F12 → Network)
- Visit the redirect URL
- Look for 301/302 status codes
- Verify the Location header points to correct destination
Command Line
curl -I https://yoursite.com/redirect-url
# Output shows:
# HTTP/2 301
# location: https://destination.com/page
Online Tools
Tools like httpstatus.io and redirect-checker.org test redirect chains and show each hop.
When NOT to Use Redirects
Temporary Content
For maintenance pages or A/B tests, use 302. You want Google to remember the original URL.
Internal Navigation
If users should land on Page A, don't secretly redirect to Page B. It's confusing and potentially manipulative.
Cloaking
Showing different content to Googlebot than to users (including via redirects) violates guidelines. Don't redirect bots differently than humans.
Need Post-Level Redirects?
External Redirect Pro adds 301 redirect functionality to WordPress posts. Perfect for affiliate links and content curation. SEO-friendly with proper headers.
Get External Redirect Pro - $19Summary
301 redirects are the correct choice for permanent moves, affiliate links, and content consolidation. They pass link equity and send clear signals to search engines. Avoid chains when possible, always test your implementation, and keep redirect rules documented for future reference.