## TL;DR

The fix shipped on the Reader backend; the original reporter later confirmed the exact same link now returns the full page as Markdown. If you hit empty output on a page the browser clearly renders, retry it, since the extraction-side fix applies to the hosted endpoint.

## Steps

1. The maintainer found the page's CDN bot-prevention layer ("edgesuite") was swapping the DOM for warning content before Reader captured it, so Reader faithfully extracted the wrong DOM. The fix shipped on the Reader backend; the original reporter later confirmed the exact same link now returns the full page as Markdown. If you hit empty output on a page the browser clearly renders, retry it, since the extraction-side fix applies to the hosted endpoint.

2. Take the question above and check if it matches what you're seeing. If it does, work through the verified fix step by step. Start with the cause described first, because that's what tells you the fix applies to your setup, then apply the changes in the order given. Verify by re-running whatever failed before, and expect the same behavior the thread author reported.

## When to use

You are seeing this: Jina AI Reader returns empty Markdown content for an ordinary page (the Government of Canada gender-based violence glossary), even though the page is simple HTML with no obvious anti-scraping protection. Use this skill when you run into "Jina Reader returns empty content for a normal page (bot-prevention DOM swap)".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.