Testing URL Redirections

Follow

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.

  Note

Your Agility CMS instance must have the Content Fetch API enabled, as well as a production domain set in your configuration in order to test URL Redirections.

How to Test URL Redirections

  1. Login to your Agility CMS instance

  2. Navigate to Settings > URL Redirections

    mceclip0.png

  3. Click the Test button. If you have not selected ANY items in the grid, this will test ALL redirects. Optionally, you may select one or many specific redirects to only test the selected items.

    mceclip2.png

  4. Click Test Now to begin the test.

    mceclip6.png

  5.  Depending on how many items you have, this may take some time. Redirects are tested 100 at a time.

    mceclip7.png

  6. Upon completion, you'll get a summary of the results.

    mceclip8.png

  7. The URL Redirections grid now shows the latest test result and when the test was the last run.

    mceclip3.png

Reviewing Results

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.

Review a Single Item

You can review the details of a failed test by clicking on the item and referring to the failed test description.

mceclip0.png

Reviewing Multiple Items

You can Export the list of URL Redirections. This will include the test result, as well as its failed test description.

mceclip1.png

Examining Result Messages

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.

Example Messages

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.

2 out of 2 found this helpful

Comments

0 comments

Please sign in to leave a comment.