Informational
The server received the request and is still processing it. These are uncommon in a normal landing-page redirect report.
Landing Page QA
Know where every
click goes.
Break down landing-page parameters, understand what each value contains, and check whether redirects preserve the information your campaign needs.
Inspect a landing page URL
Nothing is saved. Reset the test whenever you’re ready to check another URL.
◇ One click checks the URL structure and follows its redirect path. Nothing is saved.
URL ANALYSIS
URL structure
PASS
Parameters
Decoded values found in the submitted URL.
Nested destination
A landing URL was found inside another parameter.
Live redirect check
Follows HTTP redirects without saving the URL or loading the landing page in your browser.
This check contacts each server in the redirect chain. TagCheck requests headers only where supported and does not store the submitted URL.
What does the 3-digit response code mean? View guide
Successful
200 means the page responded successfully. 206 means the server returned the requested partial response.
Redirect
301 and 308 are permanent redirects. 302 and 307 are temporary redirects. TagCheck follows these to the next URL.
Request or access problem
400 is a bad request, 401 requires authentication, 403 denies access, and 404 means the page was not found.
Server problem
The destination server could not complete the request. Common examples are 500, 502, and 503.
About 401: the destination may be valid but protected by a sign-in. TagCheck cannot confirm the page content without that authenticated access.