Deprecated Meta Refresh Redirect

Meta refresh is a legacy redirect method that is bad for accessibility, confuses Google, and can be mistaken for cloaking.

Why it matters

Meta refresh is a legacy redirect method that is bad for accessibility, confuses Google, and can be mistaken for cloaking.

Address when convenient — notices usually mark a polish opportunity rather than a defect. Estimated SEO impact: medium — measurable effect on click-through or relevance.

How to fix

• Replace with a server-side 301 redirect (permanent) or 302 (temporary)
• Remove <meta http-equiv="refresh"> from the page

Common causes

If the rule is firing across many pages, the root cause is almost always one of these:

• noindex applied broadly during a redesign and never removed for live pages.
• Robots.txt blocks a path that contains canonical pages along with the unwanted ones.
• CMS publishes a draft URL with a self-referential canonical pointing to a different slug.
• Tracking-parameter URLs proliferate and dilute crawl budget.

Anti-patterns to avoid

Even with the best intentions, these "fixes" make the issue worse — recognise them so you don't ship them:

• noindex applied to a directory that also holds canonical pages.
• Self-canonical pointing at a redirect chain.
• Robots.txt disallowing paths Google needs to render the page.

How atlookup detects this

Our crawler renders each page with a real headless browser, then reads robots directives, canonical tags, sitemap entries, and tests fetchability. Pages where the rule fires for deprecated meta refresh redirect are flagged on the report.

If you'd like to see this rule fire on your own site, run a free 60-second audit — every page is reported with the exact lines that triggered it.

Tools to verify the fix

Once you've applied the fix, double-check with these external validators:

• Google Search Console — URL Inspection shows exactly how Google treats the page.
• robots.txt Tester — Live test of disallow rules against your URLs.

Frequently asked questions

Related issues