301 redirects checker

[SEO Lady]

Hi guys n gals

I've been doing a fair bit of blogging over the past few months and using 301 redirects on aged URLs on my website to more SEO-friendly when I change the subject (example: 2015-Google-update to Google-alogorithm-update)

Coinciding with this my AHREFs report came on on Saturday and I've got over 430 errors, all "500 Internal Server Error" and they seem to be related to my blog.

I got in touch with the developers who raised a ticket and are logging in tomorrow, but I've just had a thought, would an erroneous 301 redirect create an infinite loop and cause the live message:

There has been a critical error on this website.

Learn more about debugging in WordPress.

Rather than spending an hour potentially chasing my tail I thought I'd pop in here to ask. The last ones I created last Friday are redirecting fine, something has happened and my developer is out of ideas.

Big thanks

Edit: I've messaged my host to roll back the site a week

 

[SEO Lady]

Host update:
It's possible that the issue here is actually that there was a WordPress core update done on the 9th.

 

[ukbf0001]

Before going round changing links etc , what has changed on your site ? any plugins updated, if you use yoast have the permalinks changed in any way. I have had loop errors before that were caused by yoast. The 1 thing I do whenever I have a WP problem - disable all plugins, and then check the error again , and one by one re enable them. I have usually always found the error that way and from there you can sort a fix.
Hope it's fixed soon

 

[SEO Lady]

Before going round changing links etc , what has changed on your site ?

You replied to my update

Host update:
The issue here is actually that there was a WordPress core update done on the 9th.

 

[InternetMarketingPlatinum]

Generally a 301 redirect loop would be an unlikely candidate to cause this. It's actually difficult to get into a loop to be fair. This would be way down the the list of possible causes. Way down. On a sidenote, I would suggest leaving the year out of the URL of such posts to avoid having implement 301s, as the aim should ideally be to minimise the number of these, not build it into your strategy to continue to implement them. Simply leaving the year out of a permalink is the way to go in my opinion.