---
title: "Automatically Fix 404s with AI - Serpwise Documentation"
description: "Detect recurring 404s, let AI choose the closest live replacement page, and create safe redirects with review controls and daily digests."
url: "https://serpwise.ai/docs/auto-redirects/"
source: "https://serpwise.ai/docs/auto-redirects/"
---
[Back to Serpwise](/)

Serpwise Documentation

Connect · Configure · Execute

Search documentation

`/`

No documentation found.

↑↓ Navigate Enter to open

Browse documentation

**AI Auto-Redirects** helps recover traffic and link equity from recurring 404s. Serpwise watches recent human 404 traffic for a domain, infers what the missing page was about, finds the closest live replacement page, and creates a redirect when the match is safe enough.

The feature is opt-in per domain from **Domains** -&gt; **Redirects** -&gt; **Auto-redirect 404s**. Scans run in the background, so a brand-new dead URL may still return 404 before Serpwise has enough signal to act.

* * *

## How It Works

```
404 traffic -> AI match -> confidence check -> auto-apply or review queue -> redirect at the gateway
```

1. **Detect** recurring 404 paths from gateway request logs
2. **Filter** bot traffic, scanner paths, known attack URLs, and legitimate 404 classes
3. **Infer intent** from prior crawl history, URL slug tokens, and Search Console signals where available
4. **Find candidates** among live indexed pages on the same domain
5. **Choose safely** with a structured AI decision and confidence score
6. **Apply or queue** based on your auto-apply settings

High-confidence redirects become active after gateway cache invalidation. Lower-confidence matches wait in the [review queue](/docs/auto-redirect-review).

## Turn It On

Open the domain dashboard and go to **Redirects** -&gt; **Auto-redirect 404s**.

| Setting                   | What it controls                                        | Default |
|---------------------------|---------------------------------------------------------|---------|
| **Enable auto-redirects** | Turns the scanner on for this domain                    | Off     |
| **Auto-apply**            | Lets high-confidence suggestions go live without review | Off     |
| **Confidence threshold**  | Minimum confidence required for auto-apply              | 90%     |
| **Default redirect type** | Redirect status code for suggestions                    | 301     |
| **Daily digest**          | Sends owners/admins a domain summary email              | On      |
| **Minimum human hits**    | Required recurring human 404s before acting             | 3       |
| **Look-back window**      | Recent traffic window scanned for unresolved 404s       | 7 days  |

Use **301** for permanent replacements. Choose **302**, **307**, or **308** only when your redirect semantics require it.

## Auto-Apply vs. Review

Auto-apply is threshold-driven:

| Match confidence                          | Auto-apply on                     | Auto-apply off              |
|-------------------------------------------|-----------------------------------|-----------------------------|
| At or above threshold                     | Redirect is created automatically | Suggestion waits for review |
| Below threshold, above minimum confidence | Suggestion waits for review       | Suggestion waits for review |
| Below minimum confidence                  | No suggestion is created          | No suggestion is created    |

Lowering the threshold applies more suggestions automatically. Turning auto-apply off sends every valid suggestion to review first.

## What Serpwise Will Not Do

AI Auto-Redirects is conservative by design:

- It never overwrites redirects you created manually or imported by CSV
- It never redirects a dead page to the homepage as a fallback
- It prevents loops and chains before writing a redirect
- It skips bot-only 404s, AI crawler noise, exploit probes, and scanner paths
- It re-checks the chosen target before applying the redirect
- It keeps candidates inside the same locale subtree where possible

Every AI-created redirect is marked with an **AI** badge and can be reverted in bulk.

## Bulk URL Migrations

When Serpwise sees many 404s that follow the same structural move, it can suggest one regex redirect instead of many individual exact redirects.

Example:

```
/blog/* -> /articles/*
```

Bulk suggestions show the covered paths in the review queue. Approving the suggestion creates a single regex redirect rule.

## Search Console Prioritization

If Search Console data is connected, Serpwise prioritizes 404s with lost search value. Suggestions and digests can show estimated recovered impressions per month so you can review the highest-impact fixes first.

## Broken Target Re-Validation

When re-validation is enabled, Serpwise checks AI-created redirect targets after they go live. If a target later returns 404, becomes noindex, or otherwise stops looking valid, Serpwise disables the redirect and flags it in the next digest.

## Daily Digest

The daily digest is sent per domain to organization owners and admins when there is activity. It groups:

- **Applied automatically** - high-confidence redirects that went live
- **Needs review** - queued suggestions waiting for a decision
- **Re-validation warnings** - AI redirects whose targets later broke

Each row includes the source path, suggested target, confidence, hit count, Search Console impact where available, and a dashboard link.

## Credits

Each AI redirect evaluation uses credits. The exact cost is shown in the Auto-redirect settings panel before the feature is enabled. See [Credits & AI Pricing](/docs/credits) for how credit balances and ledger entries work.

[**Reviewing AI Redirects**  
→  
\
Approve, reject, apply, and bulk-revert AI redirect suggestions.](/docs/auto-redirect-review)

[**AI Auto-Redirect FAQ**  
→  
\
Costs, safety behavior, timing, reversibility, and matching details.](/docs/auto-redirect-faq)

[**Redirects**  
→  
\
Manual exact and regex redirects served by the gateway.](/docs/redirects)