DEV Community

Dejun (Alice) Chen
Dejun (Alice) Chen

Posted on

Our trial page returned 200 OK for a day. It was the wrong page.

A page on our site was broken for a day and every monitor we had said it was fine. The URL returned HTTP 200, the page loaded fast, and uptime checks were green. It was serving the wrong page.

What caught it was not an uptime check. It was an SEO check for AI search readiness, run against our own site. Here is what happened and the three cheap checks that would have caught it sooner.

What went wrong

We host a static site on a CDN with a fallback rule: any path that has no file gets the homepage. That is normal for single-page apps and for "pretty" 404s.

Then a deployment went out from a machine that did not have the full build. The new deployment had about 900 files instead of about 14,000. One of the missing files was our free-trial page.

Nothing errored. The deploy succeeded. The trial URL kept returning 200 OK, because the fallback rule served the homepage in its place. Visitors who clicked "Start free trial" landed on an unrelated page in a different language, and left.

How it showed up

I was running a readiness check on our pages: robots.txt rules for AI crawlers, llms.txt, structured data, canonical tags and sitemaps. The landing page passed. The trial URL failed two checks:

"summary": {"PASS": 3, "WARN": 1, "FAIL": 2, "UNMEASURED": 0, "INFO": 0},
"fix_first": [
  "[structured_data_and_canonical] FAIL: canonical points to another host (usethelever.com); answer engines may attribute this page elsewhere.",
  "[structured_data_and_canonical] FAIL: og:url points to another host (usethelever.com); answer engines may attribute this page elsewhere.",
  "[structured_data_and_canonical] WARN: no JSON-LD found in the initial HTML. ..."
]
Enter fullscreen mode Exit fullscreen mode

The trial page lives on a subdomain. Its canonical tag suddenly pointed at the root domain. A page does not change its own canonical host. That only happens when the server is sending you a different document.

From there it took a few minutes: list the deployments, compare file counts, roll back to the last complete one.

Three checks that would have caught it earlier

1. Check the canonical host, not just the status code.
A soft 200 (the fallback page served with status 200) is invisible to uptime monitors. The canonical tag is a cheap fingerprint: if <link rel="canonical"> on /trial does not point to /trial on the same host, you are not looking at the trial page.

2. Check the title of your key pages after every deploy.
One line per page in CI:

curl -s https://example.com/trial | grep -o '<title>[^<]*' | grep -q 'Free Trial' || echo "trial page is wrong"
Enter fullscreen mode Exit fullscreen mode

3. Refuse deploys that shrink a lot.
If the new build has far fewer files than the last one, stop. A 90% drop in file count is never a content change. Most CDNs that support direct uploads let you list the files in a deployment, so this is a simple comparison in your deploy script.

Why an AI-search check found it

AI answer engines cite a specific URL. If that URL's canonical points elsewhere, or the HTML is the wrong document, the page will not be cited for what it is supposed to be about. So a GEO/AI-search readiness check has to look at what the page says it is: canonical, og:url, structured data. Uptime monitoring only looks at whether the page answered.

That difference is why the check caught a bug that uptime monitoring missed.

The tool

The checks above come from a small open-source MCP server I built: GEO & SEO Readiness MCP — Lite. It is one Python file, no dependencies, MIT licensed. You can run it from Claude Desktop or Cursor, or straight from the terminal:

git clone https://github.com/alicexixi85/geo-seo-mcp-pro.git && cd geo-seo-mcp-pro
python3 server.py --check https://your-site.com
Enter fullscreen mode Exit fullscreen mode

It reads the initial HTML only (no JavaScript rendering), and it reports UNMEASURED instead of guessing when a site blocks it. My earlier post covers the five checks in more detail: Is your site invisible to ChatGPT Search? Five checks you can run in a minute.

Disclosure: I built this tool. There is also a paid edition for agencies, but the open-source server is complete on its own.

Have you been bitten by a soft 200 like this? I would like to hear what you check after deploys.

Top comments (0)