Cara Redirect 301 dan 302: Kapan Menggunakan Masing-Masing

Artinya:
"Halaman ini PERMANENT pindah ke lokasi baru"

SEO Impact:
- Mentransfer link equity (~90-99%)
- Google updates index ke URL baru
- Bookmark users akan tetap work

Use when:
- URL change permanen
- Domain migration
- HTTPS migration
- Site restructure

Artinya:
"Halaman ini SEMENTARA dialihkan"

SEO Impact:
- Link equity TIDAK ditransfer
- Google keeps original URL in index
- Temporary by design

Use when:
- A/B testing
- Maintenance mode
- Geolocation redirects
- Temporary promotions

+------------------+-------------+-------------+
| Aspect           | 301         | 302         |
+------------------+-------------+-------------+
| Duration         | Permanent   | Temporary   |
| Link equity      | Transfers   | No transfer |
| Google indexing  | New URL     | Old URL     |
| Cache            | Long        | Short       |
| Use case         | URL changes | Temp moves  |
+------------------+-------------+-------------+

Old: /old-page-name/
New: /new-page-name/

Setup 301 dari old → new.

Old: oldsite.com/page
New: newsite.com/page

Redirect semua URLs dengan 301.

http://example.com
→ https://example.com

Always use 301.

Old structure:
/category/subcategory/page/

New structure:
/page/

301 redirect old to new.

Thin content consolidation:
Page A + Page B + Page C
→ New comprehensive page

301 all old pages to new.

Original: /landing-page/
Test: /landing-page-v2/

302 temporarily redirect some users.
Switch back when done.

During maintenance:
/page/ → /maintenance/

Use 302 so original page returns to index.

/page/ → /page-id/ (for Indonesian users)
/page/ → /page-en/ (for English users)

302 because it's conditional, not permanent.

/sale/ → /summer-sale/

302 because it will change again.

# Single 301 redirect
Redirect 301 /old-page/ https://example.com/new-page/

# Pattern redirect
RedirectMatch 301 ^/blog/(.*)$ https://example.com/articles/$1

# 302 redirect
Redirect 302 /temp-page/ https://example.com/other-page/

server {
    # Single 301
    location = /old-page/ {
        return 301 https://example.com/new-page/;
    }

    # Pattern 301
    location ~ ^/blog/(.*)$ {
        return 301 https://example.com/articles/$1;
    }

    # 302 redirect
    location = /temp/ {
        return 302 https://example.com/other/;
    }
}

// 301 redirect
function my_redirects() {
    if (is_page('old-page')) {
        wp_redirect('/new-page/', 301);
        exit;
    }
}
add_action('template_redirect', 'my_redirects');

Popular options:
- Yoast SEO Premium (built-in)
- Redirection (free)
- Safe Redirect Manager
- 301 Redirects

Easy to manage without code.

// Avoid for SEO
window.location.href = "/new-page/";

// Google may not follow JS redirects.
// Use server-side redirects instead.

<!-- Avoid for SEO -->
<meta http-equiv="refresh" content="0;url=https://www.tirinfo.com/new-page/" />

<!-- Not treated as 301 by Google -->

Mistake:
302 redirect for permanent URL change

Impact:
- Link equity not transferred
- Old URL stays in index
- SEO loss

Fix:
Change to 301.

Bad:
A → B → C → D

Impact:
- Slow page load
- Link equity loss
- Crawl budget waste

Fix:
A → D (direct)

Bad:
A → B → A

Impact:
- Page won't load
- Crawl errors
- Users stuck

Fix:
Remove circular redirect.

Missing:
http://example.com/page/
http://www.example.com/page/
https://www.example.com/page/

All should redirect to canonical URL.

1. Open DevTools (F12)
2. Network tab
3. Visit old URL
4. Check Status Code column
5. Verify 301 or 302

curl -I https://example.com/old-page/

# Output shows:
HTTP/1.1 301 Moved Permanently
Location: https://example.com/new-page/

Options:
- httpstatus.io
- redirect-checker.org
- Screaming Frog

Check redirect type and chains.

Coverage report:
- Check "Redirected" pages
- Look for errors
- Monitor indexed pages

Make sure redirects working.

Screaming Frog:
Response Codes tab → 3xx

Find:
- Redirect chains
- Wrong redirect types
- Missing redirects

Redirect Strategy:
✓ Use 301 for permanent changes
✓ Use 302 only for temporary
✓ Avoid chains (max 2 hops)
✓ Test after implementation
✓ Update internal links to new URLs
✓ Monitor in GSC

Common Redirects:
✓ non-www to www (or vice versa)
✓ HTTP to HTTPS
✓ Trailing slash consistency
✓ Old URLs to new structure

Before redirect:
☐ Confirm it's needed
☐ Choose 301 or 302
☐ Document old and new URLs
☐ Backup .htaccess

Implementation:
☐ Add redirect rule
☐ Test redirect works
☐ Check status code
☐ Verify no chains

After redirect:
☐ Update internal links
☐ Update sitemap
☐ Monitor GSC for errors
☐ Check traffic to new URL