Control Where Your Visitors go on Your Website.

One thing that will happen is that people visiting your website will accidently trigger a 404 page not found error. Whether this is done by accidentally misspelling a word, or some nefarious hacker trying to hunt down different pages to break, having control over what happens to those users can make a difference to your over site look, feel and your users experience.

Using custom 404 pages can be helpful in a multitude of manners. These pages can be set to go to a search page, any form of potential landing page to increase your sales numbers, or just a simple FAQ page to give help to your users.

Used in conjunction with a security plugin such as WordFence, can limit the number of attempts a hacker can process (or how fast) so that you can help to eliminate additional site load times and control such issues as IP address banning.

Why Use Custom 404 Pages

With 100,000+ active installations the 404page plugin is the most used plugin to create a customized 404 error page in WordPress.

Bringing visitors to your website takes time and effort. Every visitor is important. The default 404 error page of most themes do not provide any information on what to find on your site. A first time visitor, who does not know you, is left in a dead end and leaves your website. Set up a helpful custom 404 error page to keep him on your site.

This handy plugin allows you to easily create your own 404 error page without any effort and it works with almost every theme.

404page – your smart custom 404 error page

Version: 11.2.6
Author: Peter Raschendorfer
Last Updated: 08/01/2020
Requires: 4.0+ or higher
Compatible up to: 5.5.3
Average 5-Star Rating: 5.0
Active Installs: 100,000+
11.2.6 Latest Point Release

11.2.6 (2020-08-23)

• Plugin Foundation updated to PPF06

11.2.5 (2020-08-22)

• minor UI adjustments

11.2.4 (2020-08-16)

• bug fix for Flamingo (see topic) plus potentially other plugins (thanks to garfiedo for supporting me to find the reason)

11.2.3 (2020-07-05)

• fix for Polylang (see topic)

11.2.2 (2020-03-28)

• changes to the notification for hopefully better compatibility
• Plugin Foundation swtiched to PPF04

11.2.1 (2020-01-04)

• if W3 Total Cache is installed and caching is active URLs that result in an 404 error are automatically excluded from caching

11.2.0 (2020-01-01)

• if WP Super Cache is installed and caching is active URLs that result in an 404 error are automatically excluded from caching

11.1.4 (2019-12-29)

• urgent bug fix for PPF03

11.1.3 (2019-12-29)

• Plugin Foundation updated to PPF03, no functional changes

11.1.2 (2019-11-19)

• exclude 404 page from XML sitemap generated by Jetpack

11.1.1 (2019-11-16)

• from now on it is not only detected if Yoast SEO Plugin is active, but also if the sitemap feature is activated

11.1.0 (2019-11-10)

• now uses Plugin Foundation PPF02 for plugin compatibility
• introduces two new functions for developers pp_404_get_page_id() and pp_404_get_all_page_ids()

11.0.5 (2019-10-22)

• bugfix for Yoast SEO XML Sitemap (see topic)
• added a note to settings page if Yoast SEO is active

11.0.4 (2019-10-06)

• bugfix for WPML

11.0.3 (2019-09-01)

• bugfix for REST API call (see here)

11.0.2 (2019-08-30)

• two bugs fixed (see here and here)

11.0.1 (2019-08-13)

• fix for PHP 7.1 – __construct() access level in subclass – this is an PHP error that was fixed in PHP 7.2, but I’ve changed my code to also work with PHP 7.1

11.0.0 (2019-08-13)

• mostly rewritten based on my own newly created Plugin Foundation

10.5 (2019-04-01)

• some more security improvements

10.4 (2019-03-31)

• security vulnerability in AJAX call fixed (thanks to Julio Potier for pointing me to this)

10.3 (2019-02-21)

• fix for compatibility with iThemes Sync (ticket)

10.2 (2019-02-19)

• just another small change to prevent from potential problems with version 10

10.1 (2019-02-14)

• error fixed (ticket)

10 (2019-02-14)

• workaround for WordPress Permalink bug #46000
• code improvement
• performance tuning

9 (2019-01-24)

• Gutenberg note added

8 (2019-01-11)

• fixed compatibility issue with latest WPML version
• code improvement
• UI improvements

7 (2018-07-16)

• corrected wrong image path
• added video links to admin page
• code improvements

6 (2018-06-18)

• exclude 404 page from XML sitemap generated by Yoast SEO
• further UI-improvements

5 (2018-03-05)

• show an indicator if the currently edited page is a 404 error page
• minor code- & UI-improvements

4 (2018-03-05)

• bugfix for bbPress (see topic)

3.3 (2017-11-16)

• support for right-to-left-languages added
• faulty display in WP 4.9 fixed

3.2 (2017-10-05)

• new feature to send an HTTP 410 error for deleted objects

3.1 (2017-07-24)

• bugfix for Polylang (see topic)
• bugfix for CLI (see topic)
• add debug class to body tag
• also add body classes for Customizr theme
• do not add error404 class if already exists
• further redesign admin interface

3.0 (2017-07-05)

• new feature to force 404 error after loading page
• new feature to disable URL autocorrection guessing
• finally removed Polylang stuff disabled in 2.4
• redesigned admin interface
• code improvement

2.5 (2017-05-19)

• hide 404 page from search results on front end (if WPML is active, all languages are hidden)
• do not fire a 404 in Compatibility Mode if the DW Question & Answer plugin by DesignWall is active and a question has no answers

2.4 (2017-03-08)

• ensure that all core files are loaded properly (see topic)
• Polylang plugin does no longer require Compatibility Mode (see topic)
• hide all translations if WPML is installed and “Hide 404 page” is active (thanks to the WPML guys for pointing me at this)
• post status fix (see topic)
• Enfold theme issue fix (thanks to the guys at Kriesi.at for supporting me)

2.3 (2016-11-21)

• a few minor bugfixes solve some problems with page templates in certain combinations