About this tool
Review authored meta refresh behavior before deployment with browser-style parsing evidence, conforming output, and explicit SEO and accessibility caveats.
Meta Refresh Redirect Checker statically inspects HTML meta refresh declarations or one raw content value. It follows the HTML declarative refresh parsing sequence, identifies the first declaration that can take control, distinguishes permissive runtime parsing from conforming author syntax, and resolves targets using the declared document and base URL context.
- Parses an HTML document, a meta tag, or one raw content value using the HTML declarative refresh algorithm and identifies the first effective declaration.
- Separates runtime parsing from conforming author syntax, resolves relative targets through the document URL and first base href, and checks protocol, credentials, loops, downgrades, fragments, and origin changes.
- Generates an escaped conforming tag and a bounded JSON evidence report while distinguishing Google's zero-second permanent signal from delayed temporary signals and surfacing timing accessibility review.
How to use Meta Refresh Checker
Choose HTML or Content value, paste the authored source, and supply the deployed document URL when relative resolution requires it. Run the inspection to review the controlling declaration, delay, page-refresh versus redirect behavior, authoring conformance, effective base, resolved target, and bounded findings before copying the normalized tag or downloading JSON evidence.
When this tool is useful
- Review legacy pages that use meta refresh redirects instead of server redirects.
- QA campaign or microsite transitions where client-side refresh behavior was configured in templates.
- Catch malformed content values, missing URL targets, or long delay settings before publishing.
Practical tips
- Prefer server-side 301 or 308 redirects for permanent URL moves whenever infrastructure allows it.
- Use zero seconds only when the intent is a permanent redirect signal; Google interprets every nonzero delay as temporary.
- Remove invalid and duplicate refresh declarations so the controlling behavior is unambiguous.
- Test deployed response headers, destination status, user controls, and assistive-technology behavior separately because this local inspector does not fetch or execute the page.
Examples you can test
Load an example, compare the result with the expected output, then replace it with your own input.
Detect a delayed meta refresh
Example input
<meta http-equiv="refresh" content="5; url=/new-page">
Expected output
Refresh delay and target URL detected
Delayed client-side redirects can confuse users and search crawlers.
Check an immediate refresh
Example input
<meta http-equiv="refresh" content="0; url=https://example.com/final">
Expected output
Immediate meta refresh target detected
Server-side redirects are usually cleaner for permanent URL moves.
Validation checklist
- Prefer HTTP redirects for migrations instead of meta refresh tags.
- Check refresh delay and target URL carefully.
- Avoid redirecting users to unrelated or unexpected destinations.