पाठ 23 / 34
रीडायरेक्ट्स और 404 हैंडलिंग
301 redirects aur sahi 404 responses se moved aur deleted pages handle karein, aur crawl budget barbaad karne wali redirect chains se bachein.
लेखक: Rahul Agarwal · 15 साल से वेब डेवलपर · अपडेट: 1 अक्टू॰ 2026
रीडायरेक्ट स्थिति कोड
301 (Permanent) search engines ko batata hai ki page hamesha ke liye move ho gaya; link juice naye URL par transfer hota hai. 302 (Temporary) ka matlab hai ki purana page wapas aa sakta hai; juice poori tarah transfer nahi hota. Permanent moves ke liye hamesha 301 use karein.
रीडायरेक्ट उदाहरण
Behtar performance ke liye redirects server level par implement karein. Redirect chains (A→B→C) slow hoti hain; inse bachein.
# Nginx example: Permanent 301 redirect
server {
listen 80;
server_name old-domain.com;
# Redirect entire domain
return 301 https://new-domain.com$request_uri;
}
# Redirect single page
server {
listen 80;
server_name example.com;
# Old page moved
location = /old-article.html {
return 301 https://example.com/blog/new-article/;
}
# Remove trailing slash
location ~ ^(.*)/$
{
return 301 $scheme://$server_name$1;
}
}404 पेजों को हैंडल करना
Jo pages exist nahi karte unke liye sacha 404 status code return karein. Homepage par redirect na karein aur 200 OK na bhejein; crawlers sochenge ki page maujood hai. Navigation aur suggestions ke saath ek helpful 404 page banayein.
Canonicalization बनाम रीडायरेक्ट्स
Canonical tags duplicate content handle karte hain; redirects moved pages handle karte hain. Same content ke variants (www vs non-www) ke liye canonical, permanent page moves ke liye redirects use karein.
रीडायरेक्ट चेन की निगरानी करें
A→B→C chains crawlers ko slow karti hain. Quarterly apne redirects check karein aur chains fix karein. curl ya DevTools se test karein ki responses HTTP 301/302 hain, meta refresh nahi.