CAPABILITIES

WordPress operations, governed by capability.

GES organizes agent access around explicit classes of work—so reading content, publishing a page and administering a site do not share the same authority boundary.

See how it works

View plans

CAPABILITY LANGUAGE

READ

Inspect supported native state without changing it.

PREVIEW

Generate the exact proposed mutation against current state.

WRITE

Apply only within the permitted native operation.

REVIEW

Require explicit human authorization when the operation demands it.

VERIFY

Read resulting WordPress state back after execution.

CAPABILITY FAMILIES

Six surfaces. One governance model.

The specific operation can change, but the operating principle stays consistent: inspect native state, constrain authority, preview meaningful writes and verify the resulting WordPress state.

01 / CONTENT

Create and maintain content.

Work with supported posts, pages and structured content while preserving WordPress as the editable source of truth.

Read and query content
Exact text, title and excerpt changes
Create, draft and publish supported content
Section and block-level editing
Revision-aware recovery and verification

02 / DESIGN

Operate native WordPress layout.

Work with supported Gutenberg and Site Editor resources without turning page content into a custom-code island.

Gutenberg block structure
Columns, groups and layout composition
Block settings and attributes
Templates and template parts
Global styles and supported navigation

03 / MEDIA

Use media with context.

Find and manage supported media operations with the same permission, review and read-back discipline.

Media discovery
Supported import and upload workflows
Image placement
Featured images
Image metadata

04 / SEO & DISCOVERY

Improve how content is discovered.

Support source-backed and machine-readable improvements without separating discovery work from the content it changes.

Supported SEO metadata
Internal-link workflows
Official-source citations
Content and discovery audits
AI-era discovery workflows

05 / ADMINISTRATION

Put stronger gates around stronger authority.

Higher-risk site administration belongs behind higher permissions and explicit reviewed operations.

Supported users and roles
WordPress settings
Theme and software operations
Privacy administration
Connection-aware permission boundaries

06 / ADVANCED

Extend governance to specialized workflows.

Where a supported adapter exists, the same execution model can govern more specialized WordPress operations.

WooCommerce workflows
Multisite administration
Migration and import operations
Privacy workflows
Adapter-specific operations

AVAILABILITY & AUTHORITY

A capability can exist without being available to every connection.

Actual access depends on the connected account, plan, connection permissions, WordPress capabilities, the target resource and the native adapter available for that operation. GES fails closed when a required gate is missing.

01 / PLAN

Product-level availability.

The plan determines which classes of governed operations are available to the account.

02 / CONNECTION

Connection-level authority.

Each connection limits what that agent or integration is allowed to request on the site.

03 / WORDPRESS

Native capability checks remain.

WordPress user roles and capability checks still participate in the authorization boundary.

04 / RESOURCE STATE

Live state must still match.

The target resource, current state and supported adapter must satisfy the operation before Apply can proceed.

Explore security

START WITH THE RIGHT BOUNDARY

Connect one site. Grant only the authority the work requires.

Start with core governed operations and expand capability as your workflow and plan require.

Start free

View plans