ubricHelp

What is an HTTP Refresh header redirect?

Rubric check: Refresh header redirect (check id redirect_refresh_header)

A Refresh header redirect is a page that answers with a Refresh HTTP header, which tells the browser to load another address. Google reads it, but most other crawlers and AI fetchers don't, so they stop at the old page.

Free, no card. Your report opens with this check first.

Why it matters for SEO

Google treats an instant Refresh header like an instant meta refresh: as a permanent redirect. A delayed one counts as temporary. Google still advises a server-side 301 where you can, because it is the clearest signal that a page has moved and where its links should go.

Does this matter for ChatGPT and AI Overviews?

Many AI fetchers only follow real HTTP redirects (301, 302, 307, 308). When they meet a Refresh header, they read the near-empty page that sends it and find nothing to quote. A server-side redirect works for every crawler, so it's the safe choice.

How Rubric scores it

StandardStandard checks are the baseline every other tier is measured against.

Why this tier: Refresh-header redirects.

It is judged on every page Rubric scores.

Every Rubric score starts at 100. When this check fails, it takes up to 12 points off. Even one failing page costs at least 6 points (half of the most), and the rest comes off as the share of affected pages grows. A warning costs less than a failure.

This check doesn't cap your score. It only takes off its own points.

From the engine's scoring files, scoring 2026-v2.1 (engine d5c591d).

How common it is

Found on 0 of 300 sites where Rubric could judge it (0%). That is 0 of 287 judged sites in Rubric's 313-site test set and 0 of 13 sites audited on Rubric between 11 Nov 2026 and 17 Nov 2026 under the current check rules (scoring 2026-11k or later). Measured 17 Nov 2026 with scoring 2026-v2.1.

0% of the sites Rubric could judge have this problem. Check yours.

Free, no card. Your report opens with this check first.

How accurate the check is

Lab test: passed. On test pages built with this problem, it caught 2 of 2. On clean test pages, it stayed quiet 1 of 1 times. (Engine build d17c9d9.)

Lab as of 16 Nov 2026; judged findings as of 15 Nov 2026.

How to fix it

WordPress

  1. Find what sends the header. It's usually a redirect plugin set to a "refresh" or "delayed" type, a maintenance or coming-soon plugin, or a line of PHP like header("Refresh: 0; url=...") in the theme.
  2. Replace it with a 301 in a redirect plugin such as Redirection, or the redirect manager in Rank Math or Yoast Premium.
  3. Clear the page cache and check the old URL with curl -I to see a 301 and a Location header.

Shopify

Shopify doesn't send Refresh headers itself. If Rubric reports one, it usually comes from an app or a proxy in front of the store.

  1. Disable recently installed redirect or geolocation apps one at a time and re-check the URL.
  2. Add the move as a proper redirect: search for URL redirects in the admin and create one from the old path to the new page.

Webflow

Webflow doesn't send Refresh headers on sites it hosts. If one appears, check any proxy or CDN on your domain first.

  1. Add the move in Site settings > Publishing > 301 redirects.
  2. Remove any custom code that sends people on with a timer.
  3. Publish the site.

Custom code

Remove the Refresh header and send a real redirect instead. Nginx:

nginx
location = /old-page { return 301 https://example.com/new-page; }

Apache (.htaccess):

apache
Redirect 301 /old-page https://example.com/new-page

Use 302 or 307 only when the move is temporary.

More status codes and redirects checks · The full AI SEO glossary

Free, no card. Your report opens with this check first.