WordPress connector

Connect the site without handing over an administrator login.

The Netrix connector pairs with a short-lived code. It signs each API request, checks its age, and rejects a reused nonce. WordPress reports what the connector can do and keeps a local history with reversion controls.

Request access Explore the platform

01 / FindingWordPress connectorKeep the source close to the issue

02 / ReviewA person checks itSee who owns the call and what it covers

03 / Follow-upCheck the live resultA provider response and a public read-back are separate facts

What to look for

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

Pair without sharing a password

The connector does not require a shared administrator account or reusable dashboard password.

Use the site's SEO plugin

When detected, supported values go through Yoast, Rank Math, or SEOPress metadata.

Keep control in WordPress

The site owner can review permissions, connection status, change history, and reversions in wp-admin.

What happens after you connect it

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

NETRIXREVIEW / SCOPEWordPress 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.

01Found
Netrix records the page and the issue it found.
02Reviewed
Someone checks the finding in context.
03Approved
The right person chooses what should change.
04Applied
A supported connection accepts the change.
05Checked
Netrix reads the public page again.
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.

01
Nothing publishes itself
AI drafts and supported SEO changes wait for an authorized person to act.
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.
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.