KOZ 404 Guard & URL Intelligence
| 开发者 | ramirkz |
|---|---|
| 更新时间 | 2026年10月19日 22:18 |
| 捐献地址: | 去捐款 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
KOZ 404 Guard & URL Intelligence finds the addresses on your site that return 404 and helps you fix them, without collecting personal data.
What it does
- 404 log with actions. Every missing address is recorded once and counted. You see the path, how often it is requested, whether a visitor or a bot asked, and which page of your site links to it. One click creates a redirect (with a suggested target), a 410 rule, or hides the row.
- Redirects. Same-site 301, 302, 307 and 308 redirects for exact paths or whole sections (path prefix), optionally keeping the query string. Hit counters, editing, turning rules off, CSV import and export. Loops, duplicates and redirects of WordPress system paths are rejected.
- Address changes. When a published post or page changes its slug, parent or date, the plugin suggests a 301 redirect from the old address, or creates it automatically if you prefer.
- 410 rules. Tell search engines that content was removed on purpose: exact path, path prefix, query key or query key=value.
- Lightweight 404 responses. Missing images, scripts, styles and fonts get a plain 404 instead of a full theme page. Obvious bots get a small page without the theme.
- Internal link check. Scans recently changed content for links to addresses that do not exist and shows which of them already have 404 hits.
- Site Health and dashboard. A Site Health test lists internal links that lead to 404; a dashboard widget shows the top 404 addresses of the week.
- Multilingual sites. Works with KOZ Static Translate language routes and stops WordPress from guessing /de/old-page/ into an unrelated page.
- No IP address, User-Agent, query value or external referrer is ever stored.
- Paths and the linking page of your own site are stored only while "Show paths" is on (default). Turning it off removes them and keeps salted fingerprints only.
- The JSON report contains counters and salted fingerprints only.
- No external requests, no telemetry. Data is kept when the plugin is deleted.
- KOZ SEO Core — technical SEO, schema, sitemaps, AI discovery and OpenAI Vision image ALT.
- KOZ Copy Actions — accessible copy-to-clipboard actions for selected WordPress content.
- KOZ URL-Only Comment Spam — privacy-first local moderation for URL-only comment spam.
- KOZ Static Translate — AI-powered multilingual translation with Microsoft Azure AI Translator and static language routes.
- KOZ Translate Diagnostics — read-only health checks and privacy-safe diagnostic reports for KOZ Static Translate.
- KOZ 404 Guard & URL Intelligence — privacy-safe 404/410 diagnostics, controlled same-site redirects and URL intelligence.
- KOZ Consent Manager — privacy-first visitor consent, optional script control and Google Consent Mode v2 synchronization.
- KOZ Donate Stats & Conversions — local donation-journey analytics and consent-aware conversion events for WordPress.
安装:
- Install and activate the plugin.
- Open KOZ Suite > 404 Guard.
- Check the Settings tab: the log, lightweight responses and address-change redirects are on by default.
- Come back to the 404 log after a few days and fix the most requested addresses.
常见问题:
Does it create redirects automatically?
Only if you choose "Create the 301 redirect automatically" for address changes. By default, redirects for changed addresses are suggested and wait for your approval; nothing else is created automatically.
Does it slow down the site?
Settings and the enabled rules are loaded with the other autoloaded options, so normal page views need no extra query. A 404 hit is one database query. Missing files are answered without rendering the theme.
Why are logged-in administrators not redirected or logged?
So that you can open and fix pages that have rules without being redirected away. Check rules in a private window.
What does the log store?
Status, path (while "Show paths" is on), query parameter names, visitor or bot, page type, the page of this site that linked to it, counters and dates. Never IP addresses, User-Agents, query values or other sites' addresses.
Can I move my redirects from another plugin?
Export them as CSV with the columns source, target, status, type, preserve_query, enabled and import the file on the Redirects tab.
更新日志:
2.2.0
- Fixed: 410 rules for a query key or key=value now also apply to the home page (for example ?pagelayer-template=…); only WordPress system routes are excluded.
- Fixed: addresses in Cyrillic and other non-Latin scripts were cut to dashes (/звіт-на/ became /--/) because percent-encoded characters were stripped. Paths are now decoded, so rules and the log match and show the real address.
- New: continuous 404 log in its own table, grouped by path. One database query per hit, daily cleanup by age (default 90 days) and size (default 2,000 rows). The ten-minute sampled capture window is removed.
- New: "Show paths" (on by default): the log shows the requested path, query parameter names and the page of this site that linked to it. IP addresses, User-Agents, query values and external referrers are still never stored; the JSON export still contains fingerprints only. Turning the option off removes stored paths.
- New: actions in the log: create a redirect (with a suggested target found by slug), add a 410 rule, ignore, delete. Filters: open 404, reached from this site, 410, redirected, visitors or bots, search, sort.
- New: redirects when a published entry changes its address (slug, parent or date): suggested for approval by default, or created automatically, or off.
- New: redirect rules can be edited and turned off, show hits and last hit, support path-prefix rules (moving a whole section) and keeping the query string, and can be imported and exported as CSV. 410 rules can be edited and turned off.
- New: missing static files (images, CSS, JS, fonts, media) get a plain 404 without rendering the theme.
- New: Site Health test for internal links that lead to 404, a KOZ 404 Guard section in Site Health info and a dashboard widget with the top 404 addresses of the last 7 days.
- Changed: the language guard for canonical redirects uses the languages of KOZ Static Translate when it is active; otherwise only two-letter codes (and codes with a region) count, so /faq/ or /app/ are no longer treated as languages.
- Changed: the internal link check no longer reports archives, categories, tags, authors, KOZ Static Translate language routes and addresses handled by a rule as broken, and shows how many 404 hits each link had.
- Changed: settings and a compact index of enabled rules are autoloaded; front-end requests need no extra database query when there are no rules.
- Changed: the admin screen is split into tabs (404 log, Redirects, 410 rules, Settings, Tools) and the main class into request handling, rules, log, address-change watch and Site Health classes.
- Changed: redirect targets follow the permalink trailing-slash setting, avoiding a second canonical redirect.
- Added Ukrainian translations for all new admin strings.
- Removed PayPal from the developer support panel and corrected the BTC and USDT TRC-20 developer wallet addresses (from 2.1.5).
- Removed PayPal from the developer support panel and corrected the BTC and USDT TRC-20 developer wallet addresses.
- Updated KOZ Suite documentation to include all eight current public plugins.
- Updated WordPress compatibility metadata for WordPress 7.1.
- No functional changes.
- Prevents WordPress canonical guessing from dropping a language-like namespace on 404 requests.
- Keeps stale translated routes as real 404 responses unless an explicit KOZ redirect rule exists.
- Preserves same-namespace canonical fixes.
- Separates Cloudflare/system-route 404s from real content misses.
- Classifies legacy ?attachment_id= 404s without storing the attachment ID.
- Shows the privacy-safe source classification in the grouped diagnostics table and export.
- Keeps system routes protected from redirect and 410 rules.
- Rebranded as KOZ 404 Guard & URL Intelligence.
- Added KOZ Suite integration and multilingual runtime administration.
- Preserved legacy settings, redirects, 410 rules and privacy-safe log data.
- Replaced the legacy support footer with the shared KOZ support panel.
- Kept the production safety and privacy contracts unchanged.