Brightstep Tech Inc. v0.1.0
Check redirects, chains, loops
Save this plugin to Following and return to review observed changes. Follow up to 10 plugins free.
From the marketplace listing
Redirect Checker: 301 & Status follows every redirect of a URL, hop by hop, and shows what really happens: each status code (301, 302, 307, 308), redirect chains and loops, 302s that should be permanent 301s, http→https and www/non-www problems, the final status (200, 404, 410), canonical tags that point elsewhere, and meta-refresh or JavaScript redirects. Paste one URL, a list, or your whole migration redirect map (old URL → new URL, as CSV, a Shopify redirect export or .htaccess lines) and every row gets a pass or fail against its expected target, up to 200 rows at a time with continuation for longer maps. Results come as a table with a CSV export, and ChatGPT can then write the corrected .htaccess, nginx, Netlify, Vercel or Shopify rules. Requests are made from a server in Frankfurt (EU) with an honest user agent; sites that block automated checkers are labelled as such, not reported as broken. Only public websites can be checked.
Language: English · Automatically detected from descriptions.
Oct 27, 2026 · 1 saved observations
Metadata · Oct 27, 2026 · 00:59 UTC · Compared with Oct 24, 2026 · 13:44 UTC
Package or technical metadata updated
Observed in package metadata. These changes alone do not establish a new customer-facing feature.
Oct 24, 2026 · 13:44 UTC
Not present
Oct 27, 2026 · 00:59 UTC
false
From the developer’s listing and package; capabilities are not independently tested. Package observed Nov 3, 2026.
Review scenarios; not an exhaustive list.
This plugin does not sell products or process payments.
Terms may have changed since this observation.
Check these URLs for redirect chains, loops and 302s that should be 301s
--- name: get-started description: Use this when the user asks "what status code does <url> return", "is this a 301 or 302", "redirect checker <url>", "check these for redirect chains", "check every row of our redirect map lands on the right page", or about a Search Console "redirect error". The tools make a live HTTP request and return each hop's exact status code and Location header, the final URL and the chain length. Do not use for general redirect theory such as "301 vs 308 for SEO". --- Typical requests: "what status code does https://example.com/old return", "is this a 301 or 302: example.com/promo", "redirect checker http://example.com", "we moved to https, check these for redirect chains", "here is our redirect map, check every row lands on the right page". Each one needs a live request that answers with real status codes, not documented behaviour. 1. Ask only for what is missing: the URL(s), or the redirect map (old URL → expected new URL). Paths like `/old-page` need the site address: pass it as `siteUrl`. 2. One URL or a list without expected targets: call `check_redirects`. A map with expected targets (pasted CSV, an attached CSV file, a Shopify redirect export, `.htaccess` "Redirect 301" lines): call `check_redirect_map` with `csv` exactly as given, `rows`, or the attached `file`. 3. Lead with what to fix: failing rows first (wrong target, loop, 404/410 final page, blocked or unreachable), then warnings (chains, 302/307 that should be 301, http→https or www in separate hops, canonical pointing elsewhere, meta-refresh or JavaScript redirects). Quote the status chain, e.g. `301 → 302 → 200`. 4. A 403, 429 or no answer on the last page usually means the site blocks automated checkers. Say so; the redirects before it are real. Never call such a row broken. 5. If the result has `next.startRow`, call the tool again with the same input and that `startRow` until every row is checked, then summarise all parts together. 6. Offer to write the fix: one direct 301 per old URL to its final target, in the user's server format (.htaccess, nginx, Netlify `_redirects`, `vercel.json`, Shopify CSV). Ask which one if unknown. Do not write rules for sites the user does not control. 7. Localhost, intranet and private addresses, and pages behind a login, cannot be checked. Results reflect a request from Frankfurt (EU) without cookies; country, device or login redirects may differ.
Initial release: follow every redirect hop for up to 200 URLs or redirect-map rows per call; status codes, chains, loops, temporary redirects, http→https and www checks, final status, canonical, meta-refresh and JavaScript redirects, pass/fail against expected targets, CSV export.
Declared in the saved package. Remote tools may change independently.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 3, 2026.
plugin_asdk_app_6ac3d518b0808191bf36cba9c9202afd
Download plugin data (JSON)