Agility CMS documentationAgility CMS documentation
OverviewEditorsDevelopersOwners & AdminsTraining GuideApps
Sign inLet's Chat
Editors
Introduction to Pages in Agility CMS: Building and Managing SitemapsManaging PagesMaster URL Redirections in Agility CMS: A Complete Editor's GuideTesting URL RedirectionsManaging SEO for EditorsPublish Multiple PagesRestore a Previous Page VersionInitialize a Page in Another LocaleAdd or Remove a ComponentComponents with Content that is shared across your siteMulti Locale handling with Sitemaps and PagesSocial Sharing Images

Pages

Testing URL Redirections

Running a Test

Testing URL Redirections in Agility is easy! Let’s look at how we can test them, identify when they’re not working, and take action to fix or remove them. 

1. Click Pages, and then URL Redirections in the bottom-left

2. Select the Redirection(s) you’d like to test 

3. From the Selection Drop-down, click Test 

4. Confirm your choice in the pop-out tab and click Test one more time 

Depending on how many URL’s you’re testing, this might take a few minutes as they’re tested 100 at a time. 

Once finished, you’ll be given a summary of the results 

Reviewing Results

While you’ll be shown an overview of which tests have passed or failed, you’ll likely want a close look at why a particular test has failed.  

Review a Single Item

You can quickly review a single item by clicking on it and referring to the test details. 

Reviewing Multiple Items

Select Export to download a list of URL Redirections that will include the test results and each test's details. 

Example Results 

  • “The Redirection is working properly” - Successfully returned the expected result and the redirection is working. 
  • “The status code returned 404, expected was 301” - The Origin URL returned a 404, if you get this result, you should contact a Developer to investigate. 
  • “An error occurred while accessing origin URL ” - The Origin URL encountered a server error and did not return the expected 301/302 result. Contact a Developer to Investigate. 
  • “The Destination URL is , expected destination ” - The Origin URL did respond with a redirect, however, the Destination URL it ended on was not the expected destination. 

Further Reading 

  • URL Redirections
  • Managing Pages

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"

Home Select an Image

Step Two: Click "URL Redirections"

Settings Select an Image

Step Three: Select Redirections you wish to test, and click "Test"

URL Redirections Select an Image

Step Four: Click "Test Now"

Test URL Redirections Flyout Select an Image

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

Select an Image

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

Select an Image

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

Select an Image

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.

Select an Image

Reviewing Multiple Items

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

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.

← Previous
Master URL Redirections in Agility CMS: A Complete Editor's Guide
Next →
Managing SEO for Editors
On this page
Running a TestReviewing Results
Agility CMS documentationAgility CMS documentation

Documentation for the CMS built for editors, developers, and AI agents.

Docs
  • Overview
  • Editors
  • Developers
  • Owners & Admins
  • Training Guide
  • Changelog
Resources
  • Get Support
  • MCP Server
  • System Status
  • llms.txt
Agility
  • agilitycms.com
  • Start Free Trial
  • Sign in
  • Blog
© 2026 Agility Inc. All rights reserved.
Privacy PolicyTerms of Service