Meta Refresh Checker
Paste your page HTML and find http-equiv refresh tags, delayed timers and JS-only redirects that leak crawl budget.
What this tool gives you
Check meta refresh
Paste your page HTML. Analysis runs locally in your browser — nothing is sent anywhere.
Any http-equiv=refresh leaks crawl budget — replace it with a server-side 301/308.
What this checker looks for
Timed client-side refreshes split ranking signals and trap users without a real redirect.
Refresh tags
Find every http-equiv=refresh tag, its delay and its target URL.
Delayed timers
A delay above 0s is a fail — crawlers treat it as a soft, leaky redirect.
Single mechanism
Meta refresh plus JS location redirects competing on one page.
JS redirects
location.href / replace fallbacks that crawlers may render late.
Server fix
Replace refresh with a 301/308 so link equity passes cleanly.
0–100 score
Track refresh hygiene across templates, not just the homepage.
How to kill a meta refresh
Three steps move the redirect to the server where crawlers trust it.
Find the tag
Paste the HTML and note every http-equiv=refresh delay and target.
Add a 301/308
Redirect the old URL server-side so equity passes before HTML ships.
Delete the tag
Remove the meta refresh and any JS location fallback from the page.
Why answer engines penalize refresh redirects
Client-side redirects force every crawler and citation extractor to render first and guess later.
| Signal | What engines infer | Why it helps |
|---|---|---|
| No meta refresh | The URL answers directly. | Extractors quote the page instead of chasing a timer. |
| Server 301/308 | Equity moved permanently. | Citations consolidate on the canonical URL. |
| No JS-only redirect | The page works without rendering. | Faster discovery means fresher citations. |
| Single mechanism | One redirect path exists. | No competing targets split ranking signals. |
| Instant cleanup | Old URLs resolve server-side. | AI-referred visits land instead of bouncing. |
Related GEO pages
Refresh cleanup pairs with redirect chains and canonicals so equity lands in one place.
Meta Refresh FAQs
Is meta refresh bad for SEO?
Yes. Even a 0-second refresh is a weak redirect that passes less equity than a server 301/308, and delayed refreshes trap users while crawlers partially index the wrong URL.
What should replace a meta refresh?
A server-side 301 (permanent) or 308 redirect. It fires before any HTML ships, passes ranking signals cleanly, and never flashes stale content to the visitor.
Are JavaScript redirects any better?
Barely. Crawlers must render the page to discover them, which delays indexing and can strand deep pages. Keep JS redirects as a last-resort fallback behind a real server redirect.