Status codesยท
206 Partial Content: what it means in your logs
A 206 partial content status means the server sent only the byte range a client asked for. When 206 codes in your logs are normal, and when to look closer.
What each status code means for SEO and how to fix redirect problems.
Status codesยท
A 206 partial content status means the server sent only the byte range a client asked for. When 206 codes in your logs are normal, and when to look closer.
How to do a 301 redirect step by step. Map old URLs to new ones, set the rule in Nginx, Cloudflare, WordPress or Next.js, then fix links and verify it.
A 307 redirect is temporary, a 308 is permanent, and both keep POST as POST. The HSTS 307 in Chrome, how Google treats them and who sends them.
A 404 error means the server has no page at that URL. Why 404s don't hurt rankings on their own, which ones to fix, which to leave and how to find broken links.
404 vs 410 explained. What 410 Gone means, how Google treats both codes, when a 410 is worth setting up, and how to send one on Apache and Nginx.
A 408 Request Timeout means the server gave up waiting for the client to finish sending its request. How it differs from 504, its causes and fixes.
Error 520 means your origin sent Cloudflare an empty or malformed response. See the documented causes, how to find the fault and what Google does with it.
Copy-paste .htaccess redirect examples for Apache. Move a page, a folder or a domain, force HTTPS, pick www, fix trailing slashes, all in one hop.
What HTTP status codes mean to Googlebot, class by class, with a table of the 2xx, 3xx, 4xx and 5xx codes that change how Google crawls and indexes a URL.
How to set up an HTTP to HTTPS redirect without losing rankings. One 301 per URL, updated canonicals and sitemaps, HSTS, mixed content and how to verify.
What the 424 status code means, plus 402, 412, 416, 417 and 425. What triggers each rare 4xx response and whether it matters for SEO and crawlers.
A redirect chain sends a URL through two or more redirects before it loads. Why chains slow users and Googlebot, how to trace one, and how to flatten it.
What status code 403 means, how it differs from 401 and 404, why Googlebot and AI crawlers get 403s from firewalls, and how to find the rule.
What status code 429 means, how Googlebot reacts to it, why rate limiters and CDNs throttle search and AI crawlers, and how to find 429s in your logs.
What status code 503 means, how long Google tolerates it, why robots.txt must never return it, and Nginx and Cloudflare maintenance page setups.
Trailing slash SEO in plain terms. Google treats /page and /page/ as two URLs, so pick one, redirect the other and keep canonicals and links in line.
www vs non-www has no SEO winner. See the real differences in cookies and DNS, then redirect one host to the other in a single hop with HTTPS.
301 vs 302 redirects: when each one fits, how Google treats them, where 307 and 308 come in, and working nginx, Apache and Next.js rules.
A 502 Bad Gateway means your proxy got a bad answer from the app behind it. Find the cause in nginx or Cloudflare, fix it, and see how Google reacts.
Too many redirects means a URL sends visitors in a loop. Get the visitor fix, the real causes on your site, and fixes for nginx, Apache and WordPress.
What status code 500 means, how it differs from 502, 503 and 504, where to find the real cause, and how Google treats URLs that keep returning it.
Enter a URL to see how ready the site is for search engines, answer engines and AI search, with the fixes in order.
Check your website