Free check
What does your landing page send to a phone?
Paste the URL your ads point at. We fetch it the way a paid click arrives — as an iPhone, following every redirect — and show you the page that came back, with the evidence next to each verdict. It takes about three seconds.
Why a status code is not enough
Five of these six answer 200 OK
Each one is a detector running in production right now, not a list of things a checker could in principle look for. The checker above runs the same six against one URL, once.
The page says it is gone
Sev-1
The click lands somewhere else
Sev-1
The page renders broken
Sev-1
Conversions stopped while spend carried on
Sev-1
Fine on your laptop, broken for the click
Sev-2
The page is refusing visitors
Sev-2
What each one is, how it happens, what an uptime monitor reports while it does and what to do about it is on landing page monitoring, which is the page for that half of the job. The most expensive of the six is the soft 404, and the rest of what is free to run against a URL is in the tools index.
The honest limit of a free tool
One check cannot tell you when it broke
INC-2291 answered 200 OK for 213 minutes while three campaigns spent $12,480 into it at $58.59 a minute. A checker run at any point in those 213 minutes would have caught it instantly. The problem was that nobody ran one, because nobody knew to — the page had been fine the day before and no alert exists for a page that is quietly fine until it is not.
That is the whole difference between this page and the product. Detection took 6 minutes; the other 207 were a person asleep. A free tool fixes neither number. What fixes them is something asking the question on a schedule and waking whoever is actually awake.
And the checks that never touch a URL
Half the product does not fetch anything at all. These run on the numbers your systems already report, and none of them can be answered by looking at a page:
A number stopped arriving
Runs every minute.
A cost passed the line you set
Runs every minute.
A target went off pace
Runs every 15 minutes.
Two systems disagree about the same number
Runs every 15 minutes.
What each of those four watches for, and why it is its own check rather than a dashboard threshold, is on PPC monitoring. Any number you can send reaches them — one POST and a token, no OAuth screen.
Common questions
Checking a landing page, answered plainly
How do I check if my landing page is broken?
Fetch it the way a paid click arrives — from a mobile user agent, following redirects — and read the page that comes back rather than the status code. Five of the six ways a landing page breaks still return 200 OK, so a check that stops at the status line reports a dead page as healthy. This checker does the fetch and shows you the status, the URL it landed on, the size of the response and any not-found phrasing it found in the page.
Is this landing page checker free?
Yes, with no account and no card. A single check costs us one fetch. What is not free is continuous monitoring — the same six checks every five minutes with a person paged after two consecutive failures — because that is the part that catches a break at two in the morning.
What does the checker test?
That the click still arrives at the URL you gave us; that the page does not say it is gone; that it came back whole rather than as an empty shell; that a phone is not shown a wall a laptop never sees; and that the page is not refusing visitors with a 401, 403, 429 or 503. It also reports how long the page took to answer. The sixth check — whether conversions stopped while spend continued — cannot be answered by a single fetch, and the result says so.
Why does my page pass here and fail in Google Ads?
Usually because Google saw something a single fetch did not: a check at a different moment, from a different country, or after JavaScript ran. This checker reads the response your server sends, not the page a browser finally paints. It catches the failures that live in the response — which is most of them, and all of the expensive ones.
Do you store the URL I check?
No. We keep one row per check — which of the six checks passed or failed, the status code, the page size and how long it took — so we can publish how often paid landing pages are quietly broken. That row has no URL in it, no hostname and no IP address. We did consider storing a hash of the hostname to avoid counting the same site twice, and decided against it: a hash of a domain name is reversible by anyone with a domain list, so storing one and calling it anonymous would have been worse than being straightforward about it.
Why this page gives away the thing we sell: because the check is not the product. Anyone can fetch a URL. What takes building is asking every five minutes, knowing that two failures in a row is an outage and one is a blip, and having somewhere to send that at midnight in the right timezone. A free checker that is genuinely complete costs us one fetch and buys the only argument that has ever worked here — showing you your own page instead of describing somebody else’s. The alternative was another paragraph about INC-2291, which you can already read on what a dead landing page costs.