Context
Connect the operating context
Signed WordPress metadata sync and Google Search Console access bring the page, its SEO state, and its performance evidence into one tenant-scoped view.
An operating system for WordPress SEO work, not another disconnected audit.
Content Signal holds the context around a page, turns evidence into accountable work, and keeps supported changes inside a review-first process.
Ready for review24 7 need review
Clicks at risk3.8k 18.4% vs prior period
Approved this week11 6 verified
Page and evidenceIssueImpactStatus
/wordpress-seo-guideClicks down 31%
CTR decline+18Open/enterprise-content-auditMissing metadata
Title gap+13Open/publisher-archiveNoindex detected
Robots review+9OpenOne connected loop
Bring evidence, decisions, and execution into the same operational view.
The product keeps each stage bounded: integrations provide defined metadata and metrics, teams decide what to act on, and supported writes require human approval before WordPress changes.
Evidence
Find work worth doing
Audits, traffic-loss checks, and opportunity detection expose affected URLs with the evidence needed to decide whether a task deserves attention.
Backlog
Run one accountable backlog
Impact, effort, owner, due date, status, comments, and source records stay attached as work moves from triage to completion.
Safety
Apply supported changes carefully
Bounded SEO operations use a visible preview, dry run, explicit confirmation, signed worker execution, and recorded result or restoration state.
Designed with boundaries
Useful automation without hidden publishing.
Evidence stays visible. Recommendations retain their audit, synced content, or Search Console source instead of presenting an unexplained score.
Permissions stay scoped. Organizations, sites, members, credentials, and operation records are separated by tenant and role.
Writes stay controlled. The product does not auto-publish content; supported SEO metadata operations are deliberately constrained and review-first.
Common questions
What the platform does and doesn’t do.
Straight answers about the free audit, the optional platform connection, and the review-first controls around every supported change.
Does Content Signal replace Yoast or Rank Math?
No. Content Signal is an operations layer, not an SEO plugin replacement. It reads supported Yoast and Rank Math metadata fields and writes back only through the same preview, dry run, and confirmation process described above.
Does the free WordPress audit require an account or send data anywhere?
No. The local content health audit runs entirely inside WordPress with no account, API key, or external request. Nothing leaves the site until an administrator explicitly connects the optional platform.
Does the audit or sync ever modify posts or SEO metadata on its own?
No. The local audit is read-only. Connected platform writes stay inside the same preview, dry run, explicit confirmation, and rollback path used for every supported operation.
What does the plugin actually sync to the platform?
Bounded post and page metadata: URL, title, status, author, word count, link counts, supported SEO fields, and the latest audit's active findings. Post bodies, the full link graph, and ignored findings never leave WordPress.
Who can see and approve a proposed change?
Every organization, site, member, and operation record is scoped by tenant and role, and a supported SEO change only reaches WordPress after a person explicitly confirms it.
What happens if I deactivate or delete the plugin?
Deactivating removes recurring and queued sync jobs. Deleting also removes the local audit results, sync log, and stored connection token. Disconnect from the settings page first if you also need to invalidate the connection on the platform side.
See the operating view
Use one real WordPress site to test the workflow end to end.
Start a scoped trial, or request a guided walkthrough that follows the work your team actually needs to manage.