Skip to main content
Resilience Auditor: follows the redirects of a domain you own and checks that they end on the site you chose.

Traffic

Makes sure visitors and links on your other domains reach your main site.

Search

Confirms the redirect uses the code you chose, so search rankings move to the right address.
Companies often own several domains for one site: country domains, old brands, common misspellings. Each one should send visitors to the main site. A redirect that is removed in a DNS or hosting change, or left pointing at an old site, goes unnoticed because nobody visits those domains on purpose. This auditor follows the redirects of the monitored URL and compares where they end with the goal domain you set.

Preferences

How it works

  1. Preferences: an invalid goal (502), an invalid expected code (504) or a goal on the same address as the monitored URL (503) ends the audit before any request.
  2. Follow: sends a GET request as 37AuditsBot and follows each Location by hand, up to 10 hops. Only HTTP redirects count: meta refresh and JavaScript redirects are not followed.
  3. Blocks: a block on any address before the goal ends the audit with 590. An HTTP 403 or 429 on the goal itself does not, because the redirect has already arrived.
  4. Compare: the scheme, host and port where the redirects end must match the goal exactly. www.nuplia.com.br and nuplia.com.br are different hosts. The landing path is ignored, so https://www.nuplia.com.br/en matches the goal https://www.nuplia.com.br.
  5. Arrival hop: the redirect code is judged on one hop only, the first one whose target is on the goal. Hops before it are the source domain’s own housekeeping (http to https, apex to www; see the HTTP Redirect auditor). Hops after it are the goal site’s own routing, such as / to /en.
  6. Aggregate: ERROR wins, then FAIL, then WARNING. When every rule passes the audit is SUCCESS (200).
For nuplia.com with the goal https://www.nuplia.com.br:
With expectedRedirectCode blank this warns (300), because the arrival hop is temporary. With expectedRedirectCode set to 302 it passes.

What it audits

Every row maps to one checkRule* method and one CheckCode, in the order the auditor runs them. CheckCode suffixes use status ranges: 200 success, 300–399 warning, 400–499 fail, 500–599 error.

Output documentation

Risks and considerations

Why secondary domains break silently

  • Nobody on your team visits these domains, so a redirect lost in a hosting, DNS or CDN change can stay broken for months while old links and ads keep sending people there.
  • Registering a domain and forgetting its redirect leaves traffic on a parked page, or on an old site you no longer maintain.

Choosing the redirect code

  • Use 301 or 308 when the move is final: search engines transfer rankings to the goal and browsers remember the redirect.
  • Use 302 or 307 when the destination may change, for example while a country site is being launched. Set Expected redirect code so the audit does not warn about it.
  • Browsers can remember a permanent redirect for a long time, so changing its destination later does not reach every returning visitor.

What this auditor does not check

  • Only the monitored URL is followed. Add each variant you care about (http://, www.) as its own monitored URL.
  • A temporary redirect before the arrival hop is not reported.
  • Meta refresh and JavaScript redirects count as no redirect (400). Search engines handle them less reliably than HTTP redirects.