Integration

Test Cloudflare Pages previews with simulated visitors

Cloudflare Pages builds a preview for every branch. Mimiq sends visitors through it, and through Cloudflare Access when the preview is protected.

5 visitors try to .
First test free with an accountRun it from your coding agent

How do I test Cloudflare Pages preview deployments?

Point the visitors at the preview URL (the hash or branch address on pages.dev) with a task in plain words. The Mimiq preview check GitHub Action runs when the preview is deployed and comments on the pull request. If the preview sits behind Cloudflare Access, give Mimiq a service token as two headers in the app or from your coding agent.

Previews that only the team ever opens

A Pages preview runs your real build with its Functions, redirects and headers, which is where it differs from local. A broken Function shows up as a failed request; a wrong redirect rule as a dead end. Nobody sees them until someone uses the preview like a user.

  • Works on hash and branch preview addresses on pages.dev.
  • Pages Functions that fail show up as failed or 5xx requests.
  • Cloudflare Access: a service token, sent as two headers.
  • One pull request comment with the GitHub Action.

How it works

  1. 01

    Give it a link and a task

    A preview, staging or the live app, and a task in plain words like "Sign up and start using it". No test scripts.

  2. 02

    Visitors use it

    5 visitors by default, each a different visitor profile in its own real browser, with a working inbox for verification emails.

  3. 03

    Read what they hit

    What broke, what the browser recorded (JavaScript errors, failed and slow requests), where each visitor got stuck and why, with a screenshot of every step.

  4. 04

    Fix and rerun

    Run the same visitors on the fixed build, by hand, from your coding agent, or on every preview deploy with the GitHub Action.

Previews behind Cloudflare Access

Create a service token in Cloudflare Zero Trust and add a Service Auth policy for it on the preview's Access application. In Mimiq, open Access and add two headers: CF-Access-Client-Id and CF-Access-Client-Secret with the token's values. From a coding agent, pass the same two headers in access.headers. They are sent only to that site, for that run, and deleted when it ends. This needs paid credits.

If you forget, Mimiq checks the address before charging anything and says that Cloudflare Access is in the way.

GitHub Action

The Action reads the preview URL from the deployment event, so a public preview needs no extra setup. It does not take custom headers yet, so for previews behind Access run the check from the app or your coding agent.

Limits

Visitors are simulated. They find problems fast and on every build; they do not predict how many real people will convert, they are not a deterministic regression suite, and they do not install native mobile apps.

What you get with Mimiq

  1. 01

    Run it by hand, or on every pull request

    Paste a link and a task in the app and watch the visitors work. Or run them on every preview deploy: the GitHub Action comments on the pull request, any other CI can call the MCP endpoint, and your coding agent can run it too.

  2. 02

    Bugs and usability problems in one report

    The browser records errors and failed or slow requests on the step they happened. The visitors say where the wording or the steps confused them, and where they left.

  3. 03

    Visitors that behave like your audience

    Each visitor is a different profile with a reason to be there, matched to who the page is for, described by you, or built from your own customers.

  4. 04

    A prompt to fix each problem

    Every problem comes with a fix to paste into Cursor, Claude Code, Lovable or any coding agent, and one prompt hands over the top problems at once. Then send the same visitors through again.

  5. 05

    Follow every visitor

    See each visitor's whole path, step by step with screenshots, and what it was thinking at every step. Ask any visitor a question.

The browser records relevant JavaScript errors and failed or slow app requests encountered during the run, attached to the step where they occurred. The visitors are simulated: they find problems, they do not predict how many real people will convert.

$0for your first test, with a free account (Google or email, no card). It includes 50 credits, enough for 10 visitors. After that a visitor uses 5 credits, and packs start at $9 for 120 credits.
See a sample report

Questions

Does Cloudflare's bot protection block the visitors?

It can. Any visitor stopped by one is marked as blocked by the site, and if it stops every visitor, the run fails and nothing is charged. A staging or preview address without bot protection works, as long as it is public or you give access.

What does it cost?

5 credits a visitor per run. Your first test is free with a free account: sign in with Google or email and it starts right away, no card. The account includes 50 credits, enough for 10 visitors. After that a visitor uses 5 credits, and then it is a $9 Starter (120 credits that never expire) or monthly plans from $19.

Keep reading

Send visitors and see what breaks first.

Your first test is free: sign in with Google or email and it starts right away. Last checked 2026-11-01.

5 visitors try to .