Are the redirects on my page clean?
A redirect should send a crawler to the right address in few steps and say whether the move is permanent. We look for a temporary redirect on the way to your page, a long chain from the http:// address, a refresh tag that fires after a delay, and a Refresh response header. We show what we find and do not score it.
What it actually is
Most pages are reached through at least one redirect, such as http to https or the bare address to www. We read the redirects we followed to reach your page and note whether each one said it was permanent or temporary. We read how many redirects the http:// version of your address passes through before it reaches https. And we look at the two redirects that do not use the status code at all: a refresh tag in the page that fires after a delay, and a Refresh header on the response.
Why it matters
A crawler treats a permanent redirect as a move and a temporary one as a detour, so a temporary redirect that was meant to be permanent leaves the old address standing as the real one. Every extra step in a chain is another request that can fail or be dropped, and a crawler only follows so many. A refresh tag or header redirects without saying whether it is permanent, and different readers handle it differently, so the page may be reached by some machines and missed by others.
What good looks like
Reaching the page takes one permanent redirect at most. The http:// address reaches https without a detour. Nothing on the page refreshes or redirects itself after a delay, and the response carries no Refresh header.
Being honest about it
A temporary redirect is the right answer for something that really is temporary, such as a campaign page or a maintenance notice, and we say nothing about whether yours is. A chain that has grown through several migrations still works for a browser. We report them because the question this product asks is whether a machine can reach the page reliably. Redirects that already count toward your score are not counted again here, and this check is shown in your report and does not change your score.
Where most sites go wrong
A host sets its redirects as temporary by default and nobody changes them after the move is final. An http:// rule, a www rule and a trailing-slash rule each add a step, so an old address takes several. A template adds a refresh tag for a countdown page that outlives the countdown.
On the web
State of the Web · November 2026In November 2026, 99% of the sites where it applies (91% of the sites we could read) passed the “Redirects are clean and permanent” check.
SvelteKit sites pass it most often, at 100%. Joomla sites pass it least often, at 93%.
Not enough history yet.
Based on the sites Bot Appétit has scanned. Most of these sites come from lists we scan for research. Not a random sample of the web.
Not sure where yours stands?
A free scan checks this and everything else in about 20 seconds — no signup. Or if it's already flagged and you'd rather it were simply handled, we do that too.
Flagged for this one? We handle it. No pitch, just a plain-English chat.
Book a call