"Introduction to Content Architecture", the eBook for designing effective and scalable digital experiences. Download
Agility CMS makes it easy to test all of your URL redirections so you can identify when they aren't working and take action to fix them or remove them.
In this tutorial, you will learn step by step how to test the URL redirections in your Agility CMS Instance.
Step One: Click "Settings"
Step Two: Click "URL Redirections"
Step Three: Select Redirections you wish to test, and click "Test"
Step Four: Click "Test Now"
Depending on how many items you have, this may take some time. Redirects are tested 100 at a time.
Upon completion, you'll get a summary of the results.
The URL Redirections grid now shows the latest test result and when the test was the last run.
While the grid view will quickly show you which tests have passed or failed, you'll likely want to get more detail as to why particular tests have failed.
You can review the details of a failed test by clicking on the item and referring to the failed test description.
You can Export the list of URL Redirections. This will include the test result, as well as its failed test description.
Test results will only succeed if the appropriate 301/302 responses are returned from the Origin URL and the Destination URL results in a 200 response.
The redirection is working properly
This means that your Origin URL successfully returned the expected 301/302 result and the Destination URL resulted in a successful response.
The status code returned 404, expected was 301
This means that the Origin URL returned a 404 as opposed to the expected 301 (a 301 response will normally return the Destination URL). If you get this result, contact your developer to investigate.
An error occurred while accessing origin URL <url>
This means that the Origin URL encountered a server error and did not return the expected 301/302 result. If you get this result, contact your developer to investigate.
The destination url is <some url>, expected <destination url>
This means that the Origin URL did respond with a redirect, however, the Destination URL it ended on was not the expected destination.