The HTTP Header & Redirect Checker for SEO
Redirect Path Extension
Redirect Path flags up 301, 302, 404 and 500 HTTP Status Codes as well as client side redirects like Meta and Javascript redirects, bringing potential issues that may not otherwise be seen to your attention immediately.
As well as flagging up redirects and errors, the plugin also displays other HTTP Headers (such as server types and caching headers) 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.
The redirect path logo is from the \"Iconic\" icon set, which can be found here: http://somerandomdude.com/work/iconic/
Please note, by using this extension you agree to our End User Licence Agreement: https://www.ayima.com/browser-extensions-eula
CHANGELOG:
3.0: Updated the extension to support Googles Manifest V3 roll out, no other major changes
2.1.0: Added a '+' to icon when multiple redirects are detected
2.0.0.6: Major rewrite - a lot of logic has been changed under the hood allowing us to display Meta and Javascript redirects for the first time.
1.0.1 Added an explanation when a 307 Redirect is reported due to chrome caching a HSTS based http > https redirect.
Read more
As well as flagging up redirects and errors, the plugin also displays other HTTP Headers (such as server types and caching headers) 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.
The redirect path logo is from the \"Iconic\" icon set, which can be found here: http://somerandomdude.com/work/iconic/
Please note, by using this extension you agree to our End User Licence Agreement: https://www.ayima.com/browser-extensions-eula
CHANGELOG:
3.0: Updated the extension to support Googles Manifest V3 roll out, no other major changes
2.1.0: Added a '+' to icon when multiple redirects are detected
2.0.0.6: Major rewrite - a lot of logic has been changed under the hood allowing us to display Meta and Javascript redirects for the first time.
1.0.1 Added an explanation when a 307 Redirect is reported due to chrome caching a HSTS based http > https redirect.
Source Manifest.json
{"update_url": "https://clients2.google.com/service/update2/crx", "name": "Redirect Path", "version": "3.0", "version_name" : "3", "manifest_version": 3, "minimum_chrome_version" : "102", "description": "The HTTP Header & Redirect Checker for SEO", "icons": { \t"16": "assets/images/rpath16.png", \t\t"48": "assets/images/rpath48.png", \t\t"128": "assets/images/rpath128.png" \t}, "action": { \t\t\t\t\t\t"default_icon": "assets/images/rpath19_off.png",\t \t\t\t\t\t"default_popup" : "popup.html",\t \t\t\t\t\t"default_title" : "Click here to see your Redirect Path."\t \t\t\t\t}, "background": { "service_worker": "background.js"}, "content_scripts": [ { "matches": [""], "js": ["metaRefreshDetect.js"], "run_at": "document_start" } ], "permissions": [ "webRequest", "webNavigation", "clipboardWrite", "storage" ], "host_permissions": [ "https://*/*", "http://*/*" ]}
Read more