Paste one full URL per line. Screpy checks up to 50 URLs with GET, follows up to five redirects and keeps each observed step. Blank lines are ignored and repeated normalized URLs are checked once.
Read the first and final code
A direct 200 response appears green. A 301 followed by 200 means the original URL redirects to a successful destination. Expand the row to see the chain. A final 404 or 500 appears red. Check whether a response matches the page's intended purpose before changing it.
Keep unavailable results separate
DNS, connection and timeout failures have no final HTTP code. Gray rows explain the reason. Each URL has eight seconds; the whole batch has 30 seconds. Observed steps remain visible when a check cannot finish. HTTPS-to-HTTP redirects receive a warning. Request duration is not browser page-load speed.
Verify your fixes
Filter errors or redirects, export the visible rows as CSV and check the same URLs after a repair. Use the On-Page SEO Checker for page metadata and the Sitemap Checker for sitemap files. A successful HTTP response alone does not prove indexing, a correct canonical or useful content.
Choose URLs that answer a useful question
Include a page that should work, an old URL that should redirect, and a deleted URL. Paste full addresses such as https://example.com/ and https://example.com/old-page/, using your own site's real paths. The checker reports what those addresses return; it does not discover every URL on your website.
Decide what needs fixing
A 301 indicates a permanent redirect; a 302 indicates a temporary redirect. Check the destination as well as the code: an old product redirecting to an unrelated homepage may need a better replacement. A 403 means access was refused, while a 429 indicates too many requests. A 404 or 410 can be intentional for removed content. A 500 or 503 deserves investigation on a page that should remain available.
Start with broken URLs still used in navigation, internal links or your sitemap. Update those references to the intended final URL and rerun the same list. A 200 response can still contain an error message or an empty page, so inspect questionable content yourself. Results describe one public request at the time of checking; they do not prove that every visitor or crawler receives the same response.