Projects and connected sites with explicit connection state
Keep project identity, validated site URLs, verified connectors, reporting sources, and downstream workflows aligned.
Workflow preview
Keep project identity, site connection, and downstream work aligned
WordPress is the verified production connector. Other downloadable CMS packs remain Limited Beta and noindex.
- 01
Create
Define the project and validated primary site.
- 02
Connect
Authenticate a supported CMS or reporting source.
- 03
Operate
Use the project context across audits, content, measurement, and reports.
The problem
Work loses site context
Audits, keywords, content, and reports become unreliable when they are not tied to the correct project.
Connection state is unclear
Teams need to know which source is authorized, selected, healthy, or disconnected.
Main capabilities
Project management
Create and select the site context used across customer workflows.
Connected-site lifecycle
Review supported connection, status, sync, and disconnect states.
WordPress publishing connection
Use the verified plugin authentication and publishing workflow.
Reporting source selection
Connect and select supported Google properties for project measurement.
How it works
- 1
Create the project
Add the customer-facing name and validated site URL.
- 2
Connect supported sources
Authorize WordPress, GA4, GSC, or GBP through their verified workflows.
- 3
Use one context
Run audits, research, content, and reporting against the selected project.
Operational benefits
Fewer cross-site mistakes
Keep operations anchored to an explicit project and destination.
Visible connection health
Separate connected, action-required, and disconnected states.
Data sources
These are the implemented inputs used by this workflow; availability can depend on a connected service or provider configuration.
Project records
Authenticated project identity, site URL, and related settings.
Verified connectors
WordPress and supported Google OAuth integrations described in the integration directory.
Automation and control
Shared project context
Eligible feature runs reuse the selected project rather than arbitrary public input.
No blanket CMS availability
Non-WordPress packs are not presented as production-ready connections.
Human approval
Authorize each external source
A permitted user completes the relevant plugin or OAuth connection and selects the correct property.
Who it is for
Multi-site owners
Separate work and data by project.
Agencies and teams
Use a consistent site context for authorized customer workflows.
Security and permissions
SSRF-safe site validation
Connected-site URL handling uses the application's validated backend path.
Disconnect controls
Verified connectors provide an explicit way to revoke or remove the connection.
Known limitations
Availability and automation boundaries are stated explicitly so visitors can evaluate the workflow accurately.
Connector readiness differs
Only individually verified integrations should be treated as Available.
Team roles remain Limited Beta
This page does not promise complete multi-client or project-scoped RBAC behavior.
Frequently asked questions
Which CMS is fully available?
WordPress has the verified authentication, status, disconnect, sync, and publishing workflow. Other packs remain Limited Beta.
Can one project connect analytics sources?
Yes. Verified GA4, GSC, and Google Business Profile workflows support their respective property or location selection.