From 820cba2012cb204dcd75abc436df2f2fb781879a Mon Sep 17 00:00:00 2001
From: Chris Taylor <forgetso86@gmail.com>
Date: Tue, 20 Oct 2026 14:54:29 +0100
Subject: [PATCH] Cloudflare Worker: explain why you add the script, in its own
 section

Ported from #115, which is otherwise superseded by #116 and #118.

Main had this as a trailing sentence on the "What you get" section, which
put the answer to "why am I editing my own HTML?" somewhere nobody would
look for it. #115 made it a section of its own, framed for the reader rather
than as a note about what changed, and pointed out that Lambda@Edge works
the same way. That is better on all three counts, so take it.

Its clearer heading for the install step comes too: "Add the Protect script
to your pages" rather than "Add the snippet". The troubleshooting anchor
that aims at it follows.

Not taken: #115 describes the install as one script tag. There are two --
the config block and the bundle -- and the paragraph under the snippet
depends on both, so main's wording stays.

astro build passes, 417 pages. Re-walked every cloudflare-worker# anchor
used anywhere in the site after the heading rename: all resolve.

Co-Authored-By: George Oastler <goastler@users.noreply.github.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---
 src/content/docs/en/protect-edge/cloudflare-worker.mdx | 6 ++++--
 src/content/docs/en/protect-edge/troubleshooting.mdx   | 2 +-
 2 files changed, 5 insertions(+), 3 deletions(-)

diff --git a/src/content/docs/en/protect-edge/cloudflare-worker.mdx b/src/content/docs/en/protect-edge/cloudflare-worker.mdx
index 5364090205136..72ea4e1a5ee52 100644
--- a/src/content/docs/en/protect-edge/cloudflare-worker.mdx
+++ b/src/content/docs/en/protect-edge/cloudflare-worker.mdx
@@ -36,7 +36,9 @@ Versioned tarballs are at `https://packages.prosopo.io/cloud/Prosopo-Cloudflare-
 
 Part 2 (client-side) is hosted by us. You add two `<script>` tags to your pages, the second pointing at `https://js.protect.prosopo.io/protect.bundle.js`. Nothing to download or bundle yourself. We publish new versions to that URL; your pages pick them up on their next reload without a redeploy from you.
 
-The worker never edits your pages, so you control where and when the bundle loads and the worker's response path stays a straight pass-through.
+## Why the worker doesn't add the script for you
+
+The worker never changes the pages your origin sends back. You add the Protect script to your own HTML, so you decide which pages load it, where it sits in the page and when it loads. The [Lambda@Edge integration](/protect-edge/lambda-edge) works the same way.
 
 ## Prerequisites
 
@@ -191,7 +193,7 @@ Worker verified? Move to Part 2.
 
 **This part is mandatory.** Without the bundle no session cookie is ever set, and the worker returns 401 `no-session` on every protected path in perpetuity. The worker does not add it for you.
 
-### 2a. Add the snippet
+### 2a. Add the Protect script to your pages
 
 Add this snippet to the `<head>` of every HTML page your site serves, as early as you can. A shared header template is the usual spot:
 
diff --git a/src/content/docs/en/protect-edge/troubleshooting.mdx b/src/content/docs/en/protect-edge/troubleshooting.mdx
index 4d27f5bf10a65..84da3c1800105 100644
--- a/src/content/docs/en/protect-edge/troubleshooting.mdx
+++ b/src/content/docs/en/protect-edge/troubleshooting.mdx
@@ -77,7 +77,7 @@ Common block sources:
 2. Filter for `protect.bundle.js`. If it's not there, the `<script>` tag isn't reaching your HTML. Check your header or footer template.
 3. Filter for `/api/protect/init`. It should be a `POST` to `https://protect.<your-domain>` returning 200 with `Set-Cookie: prosopo_session=…`.
 
-   - If it's going to `https://js.protect.prosopo.io/api/protect/init` instead and getting a 405, your snippet is missing the `window.prosopo_config` block. Add it above the `<script src=…>` line. See [the CF Worker install step](/protect-edge/cloudflare-worker#2a-add-the-snippet).
+   - If it's going to `https://js.protect.prosopo.io/api/protect/init` instead and getting a 405, your snippet is missing the `window.prosopo_config` block. Add it above the `<script src=…>` line. See [the CF Worker install step](/protect-edge/cloudflare-worker#2a-add-the-protect-script-to-your-pages).
    - If it's going to the right hostname but returning `4xx`, check the Portal settings and DNS.
 4. Filter for cookies. The `prosopo_session` cookie should be set with `Domain=.<your-domain>` after the init call.