Permanent redirect
HTTP 301 to the 200 endpoint
/endpoint.php?case=redirect301Open test link ↗Use deterministic local status endpoints to diagnose URL checking separately from affiliate classification.
All redirects stay within this subdomain.
HTTP 301 to the 200 endpoint
/endpoint.php?case=redirect301Open test link ↗HTTP 302 to the 200 endpoint
/endpoint.php?case=redirect302Open test link ↗302 → 301 → 200
/endpoint.php?case=chainOpen test link ↗Two local URLs redirect to each other
/endpoint.php?case=loopaOpen test link ↗Status codes are set by PHP on the server, so they are repeatable when deployed correctly.
A known-good HTTP 200 response
/endpoint.php?case=okOpen test link ↗A deliberately simulated HTTP 403
/endpoint.php?case=forbiddenOpen test link ↗A deliberately simulated HTTP 404
/endpoint.php?case=missingOpen test link ↗A deliberately simulated HTTP 410
/endpoint.php?case=goneOpen test link ↗A deliberately simulated HTTP 429
/endpoint.php?case=throttledOpen test link ↗A deliberately simulated HTTP 500
/endpoint.php?case=errorOpen test link ↗A deliberately simulated HTTP 503
/endpoint.php?case=unavailableOpen test link ↗Included in sitemap.xml, but disallowed in robots.txt. A robots-respecting crawler should not request its contents. It may record a coverage warning instead.
View disallowed source page ↗This link can appear in the affiliate scan despite the other examples being internal.
https://www.amazon.com/dp/B0DEMO0012?tag=snapdemo-20Open test link ↗