Skip to content

WordPress connector

Give Netrix a narrow write path—not the keys to WordPress.

The first-party connector pairs through a short-lived code and authenticates each API request with an HMAC signature, timestamp, and one-use nonce. The site reports its own capabilities and permissions, while deployment history and reversion remain visible inside WordPress.

Request access Explore the platform
01 / EvidenceWordPress connectorSource state remains inspectable
02 / DecisionHuman reviewScope and authority are explicit
03 / OutcomeVerified independentlyApplication and observation remain separate

What the workflow must answer

Keep the operating question attached to the evidence.

01

Purpose-built authentication

No shared administrator account or reusable dashboard password is required for the connector path.

02

SEO field compatibility

The plugin writes supported values through Yoast, Rank Math, or SEOPress metadata when detected.

03

Site-owner control

Permissions, connection state, deployment history, and reversion controls remain available in wp-admin.

Connector contract

Connection, permission, write, and verification are separate claims.

NETRIXREVIEW / SCOPEWordPress connector · authorized action
PROVIDER GATE
  • Identity
  • Capability
  • Permission
PUBLIC STATERead separatelyNo success inferred from a write response
Illustrative flow. Exact provider support and permissions depend on the configured connection and action.

An accountable trail

A useful state says exactly what happened.

  1. 01Observed

    The source evidence is recorded.

  2. 02Interpreted

    The condition is reviewed in context.

  3. 03Decided

    An authorized person chooses the next state.

  4. 04Applied

    A supported destination accepts the action.

  5. 05Verified

    The public result is read independently.

  6. 06Reported

    The claim matches the available evidence.

Product truth

Automation prepares work. Authority stays visible.

  1. 01
    No hidden autopilot

    Netrix does not publish AI drafts or apply SEO changes without an explicit authorized action.

  2. 02
    No optimistic verification

    An accepted write and a confirmed public value remain different states, and an unreadable page stays unknown.

  3. 03
    No invented scope

    Pages describe the product’s current boundary and name external providers or unfinished paths where they matter.

Continue the work

Related Netrix resources

Browse all resources

Integrations

Use each system at the boundary it actually controls.

See how Netrix connects Screaming Frog, WordPress, Cloudflare, Local Viking, Local Brand Manager, Anthropic, and SEO plugins.

Cloudflare edge connector

Change the delivered HTML without pretending the origin changed.

Apply approved SEO overrides through a scoped worker and KV namespace in the customer’s Cloudflare account, then verify the edge response.

Screaming Frog workflow

Keep the depth of the crawl and add an accountable operating layer.

Operationalize Screaming Frog crawl exports as page-level issues, review queues, AI suggestions, reports, and controlled fixes.

See it in your workflow

Bring the evidence, decisions, and outcomes into one trail.

Request access