Title: Digsil 404 SEO Guardian
Author: Murad Ali (DigSil)
Published: <strong>November 10, 2026</strong>
Last modified: November 10, 2026

---

Search plugins

![](https://ps.w.org/digsil-404-seo-guardian/assets/banner-772x250.png?rev=3795503)

![](https://ps.w.org/digsil-404-seo-guardian/assets/icon-256x256.png?rev=3795503)

# Digsil 404 SEO Guardian

 By [Murad Ali (DigSil)](https://profiles.wordpress.org/digsil/)

[Download](https://downloads.wordpress.org/plugin/digsil-404-seo-guardian.1.1.3.zip)

 * [Details](https://wordpress.org/plugins/digsil-404-seo-guardian/#description)
 * [Reviews](https://wordpress.org/plugins/digsil-404-seo-guardian/#reviews)
 *  [Installation](https://wordpress.org/plugins/digsil-404-seo-guardian/#installation)
 * [Development](https://wordpress.org/plugins/digsil-404-seo-guardian/#developers)

 [Support](https://wordpress.org/support/plugin/digsil-404-seo-guardian/)

## Description

Digsil 404 SEO Guardian is more than a redirect manager. It is a decision assistant
for broken URLs: it separates the few 404s that matter from the noise, and for each
one it recommends the response Google’s documentation calls correct, a 301 to an
equivalent page or a 410 Gone.

A typical 404 log is mostly junk: code fragments, missing script files, scanner 
probes. A typical fix is a blanket redirect to the homepage, which Google treats
as a soft 404. This plugin is built to avoid both.

#### How it is different

 * **Junk is classified, not just logged.** Each new 404 is checked against 19 patterns(
   code fragments, CSS selectors, minified-JS tokens, MIME types, script/style/font
   files, scanner probes, relative-link garbage under real posts and more). Junk
   goes to its own list with the reason shown, so real broken pages are not buried.
 * **Real pages are ranked by evidence.** URLs that look like articles are listed
   first, ranked by signals: a deleted article, Googlebot hits, links from other
   sites.
 * **Deleted articles are caught before anyone hits them.** When you trash, delete
   or unpublish a published post, its live URL is recorded at that moment, with 
   its title, so you can decide what happens to it before Google or a visitor reaches
   a 404.
 * **Each URL gets a recommendation, not just a text box.** One click on “Redirect”
   shows the same article at a new URL (same slug or a slug WordPress remembers 
   as renamed), related articles and topic archives with a match score, or “410 
   Gone” when nothing equivalent exists.
 * **Targets are proven before a rule is saved.** The target is checked with WordPress
   itself (posts, pages, custom post types, terms, authors, archives) and stored
   in its canonical form, so there are no redirects to missing pages and no trailing-
   slash chains.
 * **A working page can never be hijacked.** Rules only act on URLs that currently
   return 404, and targets must be on your own site.

#### Features

 * 404 log with a hit counter, a Googlebot hit counter and the referring page (no
   IP addresses, no user agents stored).
 * Filters for likely real, other open, fixed, ignored and junk URLs, with search
   and sorting.
 * Redirect loops are blocked and existing chains are flattened when a new rule 
   is added.
 * Homepage redirects are possible but need explicit confirmation.
 * Manual redirect rules (301, 302, 410) in a separate Redirects screen.
 * “SEO Guide” screen with the decision rules and links to Google Search Central.
 * Modern admin interface with light, dark and automatic theme, fully responsive
   and keyboard accessible.
 * Search Console import: upload the “Not found (404)” CSV from Google Search Console(
   nothing is connected to Google; the file is parsed in memory) so URLs Google 
   already knows are broken rank first. A live check asks your own site what each
   URL returns now.
 * Redirect health check: finds loops, chains, redirects to removed pages, homepage
   targets and rules that no longer run. One-click fixes; a local-only check also
   runs weekly.
 * Export for server or CDN: nginx map rules, Apache RedirectMatch lines or a Cloudflare
   Bulk Redirects CSV. Entries that cannot be written safely are skipped, never 
   guessed.
 * Impact report: daily counters of served redirects and 410 responses for the last
   30 days (no visitor data).
 * Notice right after you trash or unpublish an article, with a direct link to choose
   its redirect.
 * Automatic log retention cleanup and row caps that protect your database from 
   scanner floods.

#### Privacy

The plugin stores the path of URLs that return 404, hit counters, daily redirect
counters (kept for 90 days) and, optionally, the referring page without its query
string. If you import a Search Console CSV, the URL paths, click and impression 
counts and last-crawl dates from that file are stored; the file itself is not kept.
It does not store IP addresses, user agents or cookies, and it does not contact 
any external service (the live check only sends a request to your own site). A suggested
text is added to Settings > Privacy.

#### Security

Capability checks (manage_options) and nonces on every action, prepared SQL statements,
escaped output, sanitized input, same-host redirect targets, log size caps and automatic
retention cleanup.

## Installation

 1. Upload the plugin through Plugins > Add New > Upload Plugin, or install it from
    the plugin directory.
 2. Activate it from the Plugins screen.
 3. Go to Tools > Digsil 404 SEO Guardian. New 404s appear automatically as visitors
    and search engines hit them.
 4. Click “Redirect” next to a broken URL and apply the suggested fix.

## FAQ

### Should I redirect every 404 to my homepage?

No. Google treats irrelevant homepage redirects as soft 404s and passes no ranking
signals. Redirect only to the same or a closely related page; otherwise let the 
URL return 410 Gone. The plugin follows this rule by default.

### Why are so many of my 404s listed as “Junk”?

Bots and broken scripts request many URLs that never existed (code fragments, missing.
js files, scanner probes). Google says these 404s are normal and need no fix. If
a real section of your site is filtered by mistake, add it under Settings > “Never
treat as junk”.

### Can a redirect rule take over a page that works?

No. Rules are only applied when the requested URL returns 404. If you publish a 
page at that address again, the page wins.

### Does it slow down my site?

The plugin only runs extra code on requests that already return 404, plus one lightweight
check when a post is trashed or deleted. Normal page views are not affected.

### What happens to my data when I delete the plugin?

By default the log and redirect rules are kept, so reinstalling does not lose your
redirects. Enable “Delete all plugin data on uninstall” in Settings to remove everything.

### Does it work on multisite?

Yes. Each site has its own log, rules and settings.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“Digsil 404 SEO Guardian” is open source software. The following people have contributed
to this plugin.

Contributors

 *   [ Murad Ali (DigSil) ](https://profiles.wordpress.org/digsil/)

[Translate “Digsil 404 SEO Guardian” into your language.](https://translate.wordpress.org/projects/wp-plugins/digsil-404-seo-guardian)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/digsil-404-seo-guardian/),
check out the [SVN repository](https://plugins.svn.wordpress.org/digsil-404-seo-guardian/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/digsil-404-seo-guardian/)
by [RSS](https://plugins.trac.wordpress.org/log/digsil-404-seo-guardian/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 1.1.3

 * Renamed to “Digsil 404 SEO Guardian” (slug digsil-404-seo-guardian) so the name
   is distinctive. No change in behavior or data.

#### 1.1.2

 * New: Search Console CSV import with live verification against your own site.
 * New: Redirect health check (loops, chains, dead targets, homepage targets) with
   one-click fixes and a weekly local check.
 * New: export of redirect rules for nginx, Apache and Cloudflare Bulk Redirects.
 * New: 30-day impact report and a notice with a direct redirect link right after
   an article is removed.
 * Fix: a 410 rule is no longer overridden by WordPress core’s “guess a similar 
   post” redirect.
 * Fix: the Search Console live check no longer removes URLs that answer 200 without
   a real WordPress page (soft 404) or that redirect to the homepage.
 * Fix: URLs containing an encoded # or ? are checked at the correct address.
 * Fix: a large Search Console import stops before PHP’s time limit and can be continued
   by importing the same file again.
 * Fix: “Point to final page” never creates a homepage redirect without confirmation.
 * Database upgrade (version 3) runs automatically: new columns on the log table
   and a small statistics table.

#### 1.0.6

 * Plugin author is now listed as Murad Ali Shah.
 * Readme: new “How it is different” section describing the junk classifier, evidence
   ranking, deleted-article capture, recommendations and target verification.
 * No change to code behavior.

#### 1.0.5

 * Plugin Check: the 404 log query now uses fixed SQL text; filter, search and sort
   values are passed only as placeholders.
 * Plugin Check: removed suppress_filters from the same-slug lookup.
 * Plugin Check: nonce note for the read-only Redirects page number.

#### 1.0.4

 * Tested with WordPress 7.1. Requires WordPress 6.2 or newer.
 * Text domain changed to digsil-404-seo-guardian to match the plugin slug.
 * Security hardening: identifier placeholders in all SQL queries, explicit nonce
   and capability checks in every handler, SVG icons passed through wp_kses, theme
   script printed with wp_print_inline_script_tag().
 * The self-check request for redirect targets now always verifies SSL.
 * Fix: a deleted article whose URL already had a redirect rule was shown as “open”
   instead of “fixed”.
 * Fix: on multisite, uninstall now removes the data of every site that opted in.
 * Redirect type labels are now translatable.
 * Readme: installation steps and FAQ.

#### 1.0.3

 * Redesigned admin interface in a modern SaaS style: app shell with header and 
   tabs, KPI cards, filter segments, signal badges, slide-over “Fix this broken 
   URL” drawer, toasts, empty states.
 * Light, dark and automatic theme (no flash on load); fully responsive down to 
   phone width; RTL-safe; keyboard focus rings, focus trap in the drawer and reduced-
   motion support.
 * No change to redirect, logging or security behavior.

#### 1.0.2

 * New: junk filter. Code fragments, CSS selectors, minified-JS tokens, MIME types,
   script/style/font files, scanner probes and relative-link garbage are moved to
   a separate “Junk” list. URLs that look like real pages (“Likely real”) are shown
   first, ranked by signals (deleted article, Googlebot, linked from elsewhere).
 * New: “Not junk” button, allow-list setting, “indexed?” Google check link per 
   URL.
 * Fix: a redirect to a target that does not exist could be saved when the server
   blocked the plugin’s self-check (firewall / Cloudflare). Targets are now proven
   with WordPress itself (posts, pages, custom post types, categories, tags, authors,
   archives); if that is impossible the redirect is refused unless “Skip verification”
   is ticked.
 * Fix: targets are stored in their canonical form, so visitors never hit a second
   trailing-slash redirect.
 * Database upgrade runs automatically and classifies existing log rows.

#### 1.0.1

 * Fix: redirect chains are now really flattened (trailing-slash mismatch).
 * Fix: targets with a query string (e.g. /?p=12) were treated as the homepage; 
   plain-permalink sites are now supported (404s logged, rules matched).
 * Fix: the plugin’s own target-verification request no longer creates a fake 404
   log entry.
 * Improve: drafts / private / pending (unpublished) articles and direct status 
   changes are now remembered, not only trashing.
 * Harden: admin JS only offers preview links on exactly the site’s own origin.

#### 1.0.0

 * Initial release.

## Meta

 *  Version **1.1.3**
 *  Last updated **21 hours ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 6.2 or higher **
 *  Tested up to **7.1.4**
 *  PHP version ** 7.4 or higher **
 * Tags
 * [301](https://wordpress.org/plugins/tags/301/)[404](https://wordpress.org/plugins/tags/404/)
   [broken links](https://wordpress.org/plugins/tags/broken-links/)[redirect](https://wordpress.org/plugins/tags/redirect/)
   [seo](https://wordpress.org/plugins/tags/seo/)
 *  [Advanced View](https://wordpress.org/plugins/digsil-404-seo-guardian/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/digsil-404-seo-guardian/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/digsil-404-seo-guardian/reviews/)

## Contributors

 *   [ Murad Ali (DigSil) ](https://profiles.wordpress.org/digsil/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/digsil-404-seo-guardian/)