Redirect Path – Our Free Google Chrome Extension

Rob Kerry

Since 2005, I’ve used a very handy tool called Web Sniffer for checking HTTP Headers and bad/chained website redirects. A humble redirect can sometimes decide whether a website ranks or not, capturing link authority from non-existant URLs or stopping Google from indexing a site properly. Tools such as Web Sniffer are very much *reactionary* though, something to prove your initial suspicions about how a website behaves.

That’s where Dan Smith, our brand spanking new (and awesome) Web Developer came in handy. One of Dan’s key responsibilities at Ayima, will be ensuring that our SEO Consultants never have to rely on 3rd party tools, plus always have the most accurate and well presented data to hand. So when Joe and Dave suggested we have a Google Chrome extension to replace our need for Web Sniffer, Dan got to work and produced an awesome tool the following day!

We couldn’t keep this one to ourselves, so Ayima is offering it out to SEOs and Web Developers alike, free of charge. Flagging up 301, 302, 404 and 500 HTTP Status Codes, our Redirect Path plug-in brings attention to potential issues that may not otherwise be seen. As well as flagging up redirects and errors, the plugin also displays other HTTP Headers (such as server types, cookies, caching etc) and the server IP Address at the click of a button. All the magic happens on your computer, so it doesn’t “phone home” to anyone (except when auto-updating itself) and is instantaneous.

Over to Dan, for the quick install guide…

UPDATED: We’ve made installation even easier! Simply visit our Chrome Web Store page and click “Add To Chrome”.

You’re all done! Extension installed. You’ll get a new icon next to the top address bar:
Redirect Path - Step 3
If the plugin detects any redirects or errors, it will change the icon like below:
Redirect Path - Step 4
Clicking the icon will show you further details, including the full redirect chain:
Redirect Path - Step 5
Finally, you can click on any of the items in the path to see any additional headers sent along with that request, including the final successful page request:
Redirect Path - Step 6

Thanks Dan!