Fixes the connection test failing with "unexpected response (HTTP 302)" on a fresh install. Recommended for everyone.<\/p>","1.0.0":"
Initial release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3688792,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3688792,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3688792,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3688792,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0","1.0.1"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3688792,"resolution":"1","location":"assets","locale":"","width":1448,"height":1086},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3688792,"resolution":"2","location":"assets","locale":"","width":1448,"height":1086},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3688792,"resolution":"3","location":"assets","locale":"","width":1448,"height":1086},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3688792,"resolution":"4","location":"assets","locale":"","width":1448,"height":1086},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3688792,"resolution":"5","location":"assets","locale":"","width":1448,"height":1086}},"screenshots":{"1":"Turn 404 errors into relevant redirects automatically with real server-side 301\/302 redirects.","2":"Automatically match broken URLs with the closest relevant live pages without creating redirect rules one by one.","3":"Set up no404 in minutes by installing the plugin, adding your API key, and testing the connection.","4":"Protect SEO and paid traffic by redirecting visitors from broken landing pages, search results, and old backlinks.","5":"Built for WooCommerce stores and changing catalogs, including deleted products, renamed URLs, seasonal pages, and migrations."}},"plugin_section":[],"plugin_tags":[932,905,14279,727,186],"plugin_category":[55],"plugin_contributors":[279989],"plugin_business_model":[],"class_list":["post-366487","plugin","type-plugin","status-publish","hentry","plugin_tags-932","plugin_tags-905","plugin_tags-broken-links","plugin_tags-redirect","plugin_tags-seo","plugin_category-seo-and-marketing","plugin_contributors-ropillc","plugin_committers-ropillc"],"banners":{"banner":"https:\/\/ps.w.org\/no404-auto-404-redirect\/assets\/banner-772x250.png?rev=3688792","banner_2x":"https:\/\/ps.w.org\/no404-auto-404-redirect\/assets\/banner-1544x500.png?rev=3688792","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/no404-auto-404-redirect\/assets\/icon-128x128.png?rev=3688792","icon_2x":"https:\/\/ps.w.org\/no404-auto-404-redirect\/assets\/icon-256x256.png?rev=3688792","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/no404-auto-404-redirect\/assets\/screenshot-1.png?rev=3688792","caption":"Turn 404 errors into relevant redirects automatically with real server-side 301\/302 redirects."},{"src":"https:\/\/ps.w.org\/no404-auto-404-redirect\/assets\/screenshot-2.png?rev=3688792","caption":"Automatically match broken URLs with the closest relevant live pages without creating redirect rules one by one."},{"src":"https:\/\/ps.w.org\/no404-auto-404-redirect\/assets\/screenshot-3.png?rev=3688792","caption":"Set up no404 in minutes by installing the plugin, adding your API key, and testing the connection."},{"src":"https:\/\/ps.w.org\/no404-auto-404-redirect\/assets\/screenshot-4.png?rev=3688792","caption":"Protect SEO and paid traffic by redirecting visitors from broken landing pages, search results, and old backlinks."},{"src":"https:\/\/ps.w.org\/no404-auto-404-redirect\/assets\/screenshot-5.png?rev=3688792","caption":"Built for WooCommerce stores and changing catalogs, including deleted products, renamed URLs, seasonal pages, and migrations."}],"raw_content":"\n
When you delete a product, change a permalink or migrate a site, the old URLs keep getting traffic. Visitors land on an empty 404 page, and the traffic and the signals those old links carry go nowhere.<\/p>\n\n
Most redirect plugins ask you to fix this by hand: you write a rule for every broken URL. That does not scale past a few dozen.<\/p>\n\n
no404 works the other way around.<\/strong> It keeps a synchronised index of the URLs your site actually has, and when a request 404s it finds the closest match in that index automatically. You write no rules.<\/p>\n\n If the service is slow or unreachable, the plugin steps aside and your theme's own 404 page renders normally. Requests time out after 1.5 seconds, and after a failure the plugin stops calling out entirely for a short while instead of adding that delay to every 404.<\/p>\n\n The default is deliberately cautious, because 301s may be cached aggressively by browsers and search engines and can be hard to reverse quickly:<\/p>\n\n You can force everything to 301 in the settings, but it is off by default.<\/p>\n\n Results are cached locally for an hour, including \"no match found\". A bot hammering the same dead URL two hundred times a day costs you one lookup, not two hundred. Static files (.css, .js, .png and so on) and admin paths such as \/wp-admin and \/wp-json are never sent to the service at all.<\/p>\n\n Deleted product URLs are the main thing this plugin was built for. It does not interfere with WooCommerce permalink structures.<\/p>\n\n The matching engine runs as a hosted service, so the plugin needs a free no404 account and an API key. The free plan covers 1,000 lookups per month. See the External services section below for exactly what is transmitted.<\/p>\n\n The plugin is written in English and ships with translations for Turkish, German, French, Spanish, Russian, Hindi and Arabic (right-to-left). It follows the language of your WordPress installation, so there is nothing to configure.<\/p>\n\n This plugin relies on the no404 service to work out where a broken URL should be redirected. The matching is done remotely, against an index of your site built from your sitemap, so the plugin cannot perform it on its own.<\/p>\n\n When data is sent<\/strong><\/p>\n\n A request is sent when a visitor hits a 404 page, and only then. Requests are not sent when:<\/p>\n\n What is sent<\/strong><\/p>\n\n What is not sent<\/strong><\/p>\n\n The plugin does not transmit the visitor's IP address, the visitor's user agent, cookies, session data, form contents, or any other personal data.<\/p>\n\n Service provider<\/strong><\/p>\n\n The service is operated by no404, https:\/\/no404.tr<\/p>\n\n The API key is the only value you need to enter. The service address field is already filled in correctly.<\/p>\n\n The API key is used server side only and never appears in your site's HTML.<\/p>\n\n\n Yes. The matching engine is a hosted service, so the plugin needs an API key. There is a free plan that covers 1,000 lookups per month, and local caching means a lookup is not the same as a page view.<\/p><\/dd>\n Nothing breaks. The plugin fails open: if a request times out or errors, no redirect happens and your theme's 404 page is shown as usual. The wait is capped by the timeout you configure, 1.5 seconds by default, and only ever applies to 404 pages. After a failure the plugin pauses outgoing requests for a while so a service outage does not add that delay to every 404 on your site.<\/p><\/dd>\n No. Results are cached for an hour by default, so the same URL costs at most one lookup per hour. Results with no match are cached too. Static files and admin paths are never sent.<\/p><\/dd>\n Add a manual redirect for that URL in your no404 dashboard. Manual redirects always take priority over automatic matches. Note that if the redirect was sent as a 301, browsers may have cached it, which is why speculative matches are sent as 302 by default.<\/p><\/dd>\n No. The plugin hooks into Yes. Each site keeps its own API key, its own settings and its own cache.<\/p><\/dd>\n Redirected responses carry an Yes. Settings \u2192 no404 has an \"Excluded paths\" field. Enter one path prefix per line. Static files and admin paths are excluded automatically.<\/p><\/dd>\n Normal pages are untouched, because the plugin only runs when WordPress has already decided the request is a 404. On a 404, a cached result adds no network wait at all.<\/p><\/dd>\n It follows your WordPress language setting. English is the default, and translations are bundled for Turkish, German, French, Spanish, Russian, Hindi and Arabic. If your language is not among them, the plugin falls back to English rather than showing untranslated placeholders.<\/p><\/dd>\n\n<\/dl>\n\n\nHow it is different<\/h4>\n\n
\n
\/old-url<\/code> \u2192 \/new-url<\/code> written out one at a time. no404 matches against your live catalogue, so a deleted product URL finds its closest surviving equivalent on its own.<\/li>\ntemplate_redirect<\/code>, so Yoast SEO, Rank Math and Redirection get to act first. It is a last resort, not a competitor to your redirect table.<\/li>\n<\/ul>\n\nYour site never waits<\/h4>\n\n
301 or 302?<\/h4>\n\n
\n
Quota friendly by design<\/h4>\n\n
WooCommerce<\/h4>\n\n
Account required<\/h4>\n\n
Languages<\/h4>\n\n
External services<\/h3>\n\n
\n
\n
\/old-product<\/code>. Query strings are stripped before sending.<\/li>\nReferer<\/code> header, when the browser supplies one.<\/li>\n\n
\n
\n
Do I need an account?<\/h3><\/dt>\n
What happens if the no404 service goes down?<\/h3><\/dt>\n
Does every 404 use up part of my quota?<\/h3><\/dt>\n
It redirected someone to the wrong page. How do I fix that?<\/h3><\/dt>\n
Will it conflict with Yoast SEO, Rank Math or Redirection?<\/h3><\/dt>\n
template_redirect<\/code> at a very low priority, so those plugins resolve their own redirect tables first. no404 only acts on 404s that nothing else handled.<\/p><\/dd>\nDoes it work on multisite?<\/h3><\/dt>\n
How can I tell that a redirect came from this plugin?<\/h3><\/dt>\n
X-Redirect-By: no404<\/code> header. Every request is also listed in the 404 Events tab of your no404 dashboard.<\/p><\/dd>\nCan I exclude certain URLs?<\/h3><\/dt>\n
Does the plugin slow down my site?<\/h3><\/dt>\n
What language does the plugin use?<\/h3><\/dt>\n
1.0.1<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n
template_redirect<\/code>.<\/li>\n