Cogny Cloud · WordPress

The content audit, running every Monday on its own.

Cogny reads WordPress + Search Console + GA4 through MCPs, finds posts losing rank, and creates a ticket per structural fix — metadata, internal links, redirects. Approve in tickets — Cogny ships through the WordPress MCP.

❯ book a Cloud demo see how it replaces the manual flow →

❯

cogny --replaces

FLOW

Same outcome. Two very different processes.

How you do it today

Quarterly content audits in spreadsheets.
Manual cross-checks between WordPress, GSC, GA4.
Decide "refresh, kill, or double down" by feel.
Hand the doc to whoever has WordPress access.
Wait. Forget. Audit again next quarter.

How Cogny Cloud does it

Cogny connects to WordPress + Search Console + GA4 via MCP — one-time.
Pulls post + ranking + traffic reports on a schedule.
Finds insights: posts losing rank, decay velocity, internal-linking gaps.
Creates a ticket per proposed structural fix — metadata, internal links, redirects.
You approve in tickets.
Cogny ships the approved structural change through the WordPress MCP.
Re-checks rankings 2 weeks later — learns which fix actually moves your domain.

❯

cogny --tickets

read + write

Cogny creates tickets AND executes the approved ones through the MCP. Each insight becomes one ticket — here are the kinds Cogny creates from WordPress:

Refresh-meta ticketUpdate meta-description or schema on a decaying post.

Internal-link ticketAdd internal links from related posts to a target page.

Redirect ticketConsolidate cannibalizing posts with a 301.

ExecutionCogny can update metadata, tags, internal links and redirects through the WordPress REST API after approval. Theme/code changes flow through Cogny Code as PRs. Cogny does not write or rewrite post content.

LearnsCogny watches which structural fixes actually recover rankings and tunes its proposals to your domain — so over time you only see the fixes that have a track record on your site.

❯

cogny --reads

DATA

The reports Cogny pulls on schedule for WordPress insights

WordPressPosts, Pages, Tags

Search ConsoleQuery + page data

GA4Engagement + conversions

Cogny CodeTheme/code PRs to your repo

❯

cogny --book

DEMO

Tell us your use case. Then book a 15-min Cloud demo.

❯

cogny --faq

ASK

The questions we usually get on the demo call

Does Cogny replace WordPress?

No. Cogny connects to WordPress and adds an AI analyst on top — you keep using WordPress for everything you do today.

Does Cogny make changes automatically?

No — Cogny creates a ticket for every proposed action, you approve in tickets, then Cogny executes the approved ticket through the WordPress MCP. Nothing ships without you signing off.

Does Cogny write copy or creative?

No. Cogny does not write ad copy, email bodies, post content, image creative or rewrite existing copy. Cogny’s execution is limited to structural changes — segments, tags, metadata, internal links, redirects, scheduling assets you’ve already drafted, status changes (pause/resume/archive), and code-level PRs via Cogny Code.

Does Cogny actually get smarter over time?

Yes. Every approval and rejection is a signal. Cogny tracks the outcome of each executed ticket (did the deal close, did the ranking recover, did the segment lift revenue) and tunes its proposals to your business — so noisy or irrelevant tickets fall off and the high-signal ones become the default.

❯