Fix 404 Pages

The Fix 404 pages is different that designating a 404 error page for your site. This feature lets you know what people have tried to navigate to directly but resulted in an error page. Either a search engine has an older link still in its index that people are clicking on or a visitor has a bookmark that is out of date. In both cases you want to make their experience of being taken to the correct location as quick and seamless as possible.

How to fix urls marked as 404 errors

  1. Using your admin panel, navigate to Manage > Configuration > Search and Metadata section > URL Redirects > Fix 404 pages tab.
    Location of the Fix 404 pages tab location
  2. Review the table which will list any known page pathways visitors have tried to access. Evaluate the pathway and decide what alternative page might better serve your visitors, if appropriate. In some cases, you may decide the path isn't relevant and that's okay too; there's an option for that.
  3. Under the Operations column, you can either choose to:
    • Add redirect, or;
    • Ignore (select using the downward arrow on the right side of the button)
  4. Add redirect
    1. Click the Add redirect button.
    2. The system will take you to the Add URL redirect page where it will have already filled the Path field for you.
    3. Provide your To field information.
    4. Click Save to finish.
  5. Ignore
    1. Click on the downward arrow option of the Add redirect button to access the Ignore option.
    2. This will take you to the Settings page. It's recommended to leave all settings as they are; the system will add your pathway down near the bottom of the page in a section under Pages to ignore. Confirm your page has been listed.
    3. Click the Save configuration button to finish.
Built-in Protections

You may see a high count for a path labeled '/wp-login.php'. In Drupal, this would normally be appended to the end of your site's domain name to access the login screen like you do with '/login'. At SiteFarm, we use the Campus CAS system for security reasons. What you're seeing is a person or bot's failed effort to log into your site because we've implemented our login process to safeguard your site and content. You can safely ignore this entry.