Skip to content

Cloudflare edge connector

Change the HTML Cloudflare delivers without changing the CMS.

Netrix creates a worker, route, and site-specific KV map in the customer's Cloudflare account. Supported fixes rewrite the response on its way through the edge. When the route is removed, the untouched origin takes over again.

Request access Explore the platform
ControlSystemHumanClient
Collect evidence✓——
Review meaning—✓✓
Approve action—✓✓
Verify output✓✓—
Permissions depend on the person's account role, ownership of the site, the connected provider, and the change being requested.

What to look for

Get the answer without losing sight of where it came from.

01

Runs in the customer's account

The API token, worker, route, and KV namespace belong to the customer—not Netrix.

02

Leaves the origin alone

Edge fixes do not edit CMS content and stop appearing when the route or worker is removed.

03

Checks that the worker served it

Netrix looks for both the expected value and the worker's response marker before crediting the edge change.

What happens after you connect it

A working connection does not give every person—or every feature—permission to make changes.

NETRIXREVIEW / SCOPECloudflare edge connector · authorized action
PROVIDER GATE
  • Identity
  • Capability
  • Permission
PUBLIC STATERead separatelyNo success inferred from a write response
This is a simplified example. Available actions and permissions depend on the provider, the connected account, and the change being requested.

From finding to follow-up

See where the work stands—and what still needs to happen.

  1. 01Found

    Netrix records the page and the issue it found.

  2. 02Reviewed

    Someone checks the finding in context.

  3. 03Approved

    The right person chooses what should change.

  4. 04Applied

    A supported connection accepts the change.

  5. 05Checked

    Netrix reads the public page again.

  6. 06Shared

    The report summarizes the audit and fixes currently marked applied.

A few things worth knowing

Netrix can prepare the work. Your team still makes the call.

  1. 01
    Nothing publishes itself

    AI drafts and supported SEO changes wait for an authorized person to act.

  2. 02
    A write is not proof

    Netrix records when a provider accepts a change, then checks the public page separately. If it cannot read the page, the result stays unknown.

  3. 03
    Limits belong in the open

    When a feature depends on another provider or stops short of a complete workflow, the page should say so.

Keep exploring

More on this part of the work

Browse all resources

Integrations

Connect the tools that collect the data and make the changes.

Connect Netrix with Screaming Frog, WordPress, Cloudflare, Local Viking, Local Brand Manager, Anthropic, and WordPress SEO plugins.

WordPress connector

Connect the site without handing over an administrator login.

Pair a WordPress site with Netrix, send supported SEO fixes through signed requests, and keep a local change history.

Screaming Frog workflow

Keep Screaming Frog for the crawl. Use Netrix for what happens next.

Turn Screaming Frog exports into page-level issues, review queues, draft fixes, reports, and supported site changes.

See how it fits your team

Bring the crawl, the review, and the follow-up together.

Request access