The SEO redirect module was first created by us in 2012 when we “converted” a client website from PHP to DNN. Because the existing website ranked quite well in google we needed a way to add mapping for redirects from the old pages to the new ones.
Over the years we have add more functionality to the module and its interface and we now use it on most of our websites.
404 and 301
For SEO, it’s useful to redirect renamed or moved pages or files to their new location.
Although DNN has built in functionality for renamed pages, it does not for all other situations.
The SEO redirect allows you to see the incoming 404’s and add a redirect them to a new location if needed.
Redirect URL's that would otherwise generate a 404
-The module logs what URLs generate a “Page not Found” on the 404 page.
- An admin can see a list of 404s and add redirect (301) rules to another location.
- This is possible for DNN pages and static files.
- The mappings are stored in an XML file in the portal Folder.
This allows you to prepare a redirect list when moving a website from another system to DNN.
Force 404 on URL's with an existing top-level page
DNN does not generate 404 errors for URL's below an existing page.
For example: if /Banana does exist, there will not be a 404 error for /Banana/Green, even when that page does not exist.
This feature, introduced in version 2.4 of this module, will allow you to force that 404 by checking the page on the edit-page for Force-404.
There's a download link on the right of this on desktop and at the bottom of this page on mobile devices.
Please download the manual for this module here.
Issues & suggestions
If you find any issues or suggestions please log them on Github
This module is open source. We've published the source code on GitHub.