Cloudflare

Connecting

1. Open SEO → Connections → Cloudflare and press Create the token on Cloudflare. Cloudflare's token page opens with the three permissions Vidrys needs already chosen — edit Workers, edit Workers routes, read your zones — and nothing else. Choose your account and your domain, then Create Token.

2. Paste the token and press Connect. Vidrys checks it, finds your domain, puts its Worker up and routes it on your site's host name and its www (or bare) twin.

3. Optionally, tick Also send AI crawlers' visits to AI logs: the same Worker reports which pages ChatGPT, Claude and the rest read.

Your domain must be on Cloudflare (its nameservers pointing there) and its site's DNS record proxied — the orange cloud — or the Worker never runs. A route another Worker already holds is never taken: Vidrys says which, and you choose.

What it serves

Every fix that changes a page as it's served: titles, meta descriptions, canonicals, removing a noindex, Open Graph tags, image alt text, links and page edits — headings, link words, what's added — on any page, whatever builds it; one title, description and canonical per page; the page language; an HSTS header; a real 404 for a not-found page; the sitemap in robots.txt; your organisation's structured data; hreflang links back. And what only a server can do: a permanent redirect for dead addresses, chains, loops and temporary redirects, http:// to https://, and one host name. On a site built in JavaScript, rendered copies of its pages for crawlers. Each is checked on your live site afterwards; rolling one back takes it away, and the page is what your server sends again.

Rendered copies for crawlers

Google runs a page's JavaScript late and not always; Bing and the AI crawlers — ChatGPT's, Claude's, Perplexity's — mostly don't run it at all. On a site built in JavaScript they can find a page nearly empty. When the site audit finds pages whose content only appears once scripts run, Fixes proposes Rendered copies for crawlers — one fix for the whole site, waiting for you. Approved, the Worker serves those crawlers a ready-rendered copy of each such page: the page as a browser shows it, with your other fixes on it. People get your site exactly as before.

Vidrys renders the pages in its own browser, straight from your server, and renders each copy again after a week. Where most of the site's pages need JavaScript, any page a crawler asks for is rendered; otherwise only the pages the audit found. A page whose server already sends its content keeps no copy, and until a page's copy is ready, crawlers get the page as your server sends it.

Each page rendered counts against your plan's rendered copies a month (Track 200, Grow 1,000, Scale 5,000, Custom 20,000), and so does each weekly refresh. Once the month's are used, new pages wait for the next month, and the copies already made are still served. The Cloudflare card shows how many copies are ready, waiting, not needed or couldn't be rendered (those are tried again a day later), and how many renders this month has used. Rolling the fix back stops the copies at once and deletes them.

A copy holds only what your own page shows people, so it isn't cloaking. Google calls this dynamic rendering and accepts it as a workaround; its long-term advice is pages your server sends complete (server-side rendering), which needs no copy at all.

Previewing a fix

In a fix's review, Preview on your site opens the page with the change on it, for an hour, for whoever has that link — share it with care. It is never cached, and your visitors see the page as it is.

Pausing, and if anything goes wrong

Pause Vidrys's changes on the Cloudflare card stops everything the Worker serves at once; Resume puts it back. If the Worker ever hits an error, it serves the page exactly as your server sent it. Removing the connection takes the Worker and its routes off your site.

What it costs

The Worker runs on your Cloudflare plan: free up to 100,000 requests a day; a busier site needs Cloudflare's Workers Paid plan ($5 a month), which Vidrys doesn't charge for or see.