Quick answer
A meta refresh redirects or reloads a page from an HTML instruction such as <meta http-equiv="refresh" content="0;url=/new-page">. NOTABIS reports meta-refresh when that element is present in the measured HTML. Use a server-side redirect for URL moves and ordinary navigation for user-triggered actions whenever possible.
What the issue means
Meta refresh runs after a browser receives and parses the document:
<meta http-equiv="refresh" content="0;url=https://example.com/new-page">
It is different from an HTTP 301/308 or temporary 302/307 response, which tells the client where to go before the destination document is rendered. A delayed refresh can also surprise users and interfere with back-button behaviour.
Why it matters for SEO
Server redirects communicate URL changes clearly and avoid making a crawler process an intermediate HTML page. Search engines may interpret meta refreshes, but the signal is less direct and can be confused with a page that should remain accessible. The finding is a low-priority technical review, not proof that a URL cannot be indexed.
How NOTABIS detects it
The meta-refresh rule checks the measured DOM for meta[http-equiv="refresh"] and records a page-level issue when one exists. It does not parse the delay or destination, verify whether the refresh actually runs, or classify the intent of the page. An HTTP redirect is recorded separately through the redirected-page and redirect-chain rules.
How to check it yourself
Inspect View Source and the final DOM for http-equiv="refresh". Read the delay and destination, then request the URL with curl to see whether the server also sends a redirect. Test keyboard navigation, history, and no-JavaScript behaviour before changing a legacy page.
How to fix it
For a permanent move, return one direct 301 or 308 to the relevant replacement and update internal links and sitemaps. For a temporary move, use the appropriate temporary HTTP redirect. For an in-page action, replace the refresh with a visible link or application control and explain the destination.
HTTP/1.1 301 Moved Permanently
Location: https://example.com/new-page
Recheck the response and final page after deployment; do not redirect every old URL to an unrelated home page.
When this is intentional or does not need fixing
Legacy kiosks, simple static hosting, and carefully controlled announcements may still use a meta refresh. A no-JavaScript fallback can be useful, but it should not hide a permanent URL migration that an HTTP redirect can express more clearly. Document any exception and test it with assistive technology.
Related issues
Read redirected URLs, redirect chains, and HTTP error responses.
Run a NOTABIS audit
NOTABIS identifies pages containing a meta refresh element so you can replace accidental redirects with a clearer response or navigation path.