301 Redirects Validation automated way

[HeenaMadan]

Hi Team,

Is there any way to automate 301 redirects validation? For eg: We have migrated old website(non-aem) to new(AEM). We have written 301 redirects at Dispacther layer. Right now we are checking manually. Does AEM provides any other way to validate all rules automatically?

TIA

[arunpatidar]

Hi,

Since redirect is happening from dispatcher/apache , AEM can't help here.

You can test this using JMeter, where you can configure all the urls and do a test.

If you are looking for validation/test of rules, you can check here as well.

https://technicalseo.com/tools/htaccess/ 

[HeenaMadan]

Thanks @arunpatidar i was looking for any tool if aem provides. We can use jmeter but configuring urls we need to do at our end but yeah thats fine.

So custom solution would be needed for the same only

[Nikita___Garg]

hi @HeenaMadan,

A convenient test script to ensure that the 301s have been properly configured is available at  https://github.com/Adobe-Marketing-Cloud/tools/tree/master/dispatcher/redirectTester

See also the following Community pages: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/provide-301-redirect-in-ae...

Hope this helps.

Thanks,

Nikita Garg

[Avinash_Gupta_]

Hi @HeenaMadan 

I have used screamingfrog tool in past to detect automatically the page redirects. It will show the status code (whether a 301, 302, 303 etc), the status (permanent or temporary) as well.

It's free in lite form, for up to 500 URLs. You have two options to check redirects:-

1. Crawl the Website

2. Upload a list of URLs to check the redirects.

https://www.screamingfrog.co.uk/redirect-checker/ 

Hope this helps.

[Jörg_Hoh · Accepted solution]

What do you want to validiate? That these rules are configured correctly (as in: No typos)? In that it is a one-time check and you can probably generate a test script from the ruleset.

Another usecase could be that you want to avoid any 404s, e.g. because an author renamed a page which was initially there when these dispatcher rules have been created. In this case you could also generate a script based on the ruleset and let it warn if it encounters a 404 instead of the expected 301.