Skip to content
SEO OS
03 / CONNECTED SITES

Control the work centrally.
Keep permission local.

Build a connected-site estate beneath each client project without sharing administrator passwords. Switch the active site across SEO OS, configure its features centrally and push the approved manifest to that site’s connector.

View installation steps →Review permissions
SEO / OSCENTRAL COMMAND
Client AVerified · Content enabled
Client BVerified · Read only
Client CConnection review
03.1
THE CONNECTION MODEL

A narrow connector, not an open back door.

The central SEO OS installation stores every site relationship, the active operating target and its versioned feature manifest. The companion plugin verifies each signed request, applies the central configuration beneath a one-time local trust ceiling and reports the effective state back.

CONTROL SITE

SEO OS

  • Client and project context
  • Content plan and SEO fields
  • Search evidence and reports
  • Signed request creation
HMAC-SHA256→5-minute expiry
one-time nonce
CLIENT SITE

SEO OS Connector

  • Verifies timestamp and signature
  • Blocks repeated requests
  • Checks local permissions
  • Returns only approved results
PERMISSION MODEL

The client site remains in charge.

The managed site authorises the central relationship once. SEO OS then controls the site-specific feature manifest while content, scheduling and media remain capped by the permissions approved locally.

CapabilityDefaultWhat SEO OS can doWhat it cannot do
Site statusEnabled

Read WordPress version, theme, HTTPS state and published-post count.

Cannot access users, passwords or private content.

Sitemap discoveryEnabled

Identify WordPress core, Yoast, Rank Math or AIOSEO sitemap locations.

Cannot change sitemap or SEO-plugin settings.

Central configurationAuthorised locally

Receive feature, identity, content, sitemap and AI-crawler settings from the main site.

Cannot exceed the trust ceiling set by the local administrator.

Content syncOff

Create or update posts associated with a central content-plan item.

Cannot delete posts or edit unrelated content.

Scheduled publicationOff

Schedule a synced post for a future date after readiness checks.

Cannot immediately publish through the connector.

Featured imagesOff

Sideload the approved featured image from the central installation.

Cannot browse or remove the site’s media library.

CONTENT DELIVERY

Plan centrally. Publish on the site that owns the audience.

When content sync is enabled, SEO OS routes the active project’s content item to the currently selected WordPress installation. Site switching is retained in queued work, so background delivery cannot silently move to another destination. Source identifiers prevent accidental duplication and make later updates target the same post.

  1. 01

    Prepare the article

    Complete the copy, metadata, internal link, publication date and featured image inside the project content plan.

  2. 02

    Check readiness

    SEO OS checks word count, unfinished planning notes and image requirements before scheduling.

  3. 03

    Send the signed payload

    The target connector verifies the request, local permission and source identity before writing anything.

  4. 04

    Return the WordPress result

    The remote post ID, edit link and status are stored against the originating project item for audit and reporting.

SETUP

Connect and configure a site in five controlled steps.

1

Install Connector

Upload the companion plugin on the managed WordPress site.

2

Set trust ceilings

Authorise central configuration and only the content actions this site may accept.

3

Add and test

Save the URL and secret beneath the correct project, then verify the signed connection.

4

Configure centrally

Choose the site features, content defaults, sitemap and AI-search policy in SEO OS.

5

Push and switch

Apply the manifest, then use the Active Site selector to carry this context into every tool.

Security boundary

Use HTTPS. Treat the shared secret as a password. Rotate it if exposed, and disconnect the project to remove the saved central secret.

NEXT / REPORTING

Turn connected activity into client proof.

Explore Reporting →