Measure → Explain → Execute Draft-first, always
A simple workflow to become a preferred AI source.
PENMAN runs a repeatable loop: measure AI visibility, compare against AI-selected sources, then ship improvements safely as WordPress drafts with diffs and rollback.
Existing pages or RTM/new posts.
Tasks, outlines, drafts, link routes, logs.
Nothing publishes automatically.
Screenshot: pipeline overview — see runs, modules, and what’s ready for review.
Two ways teams use PENMAN
Pick the workflow that matches your reality: improve what already exists, or publish fast when the moment matters.
Optimize existing WordPress pages
Import your site context, measure AI source selection, then turn gaps into scoped draft updates.
- 1AI Visibility shows inclusion tiers + source set for your intents.
- 2AI Competition compares against sources AI already prefers.
- 3Tasks/outline become a draft update you can review.
- 4Publish explicitly, then re-run visibility to verify movement.
RTM / new posts (move fast, stay controlled)
Turn a timely topic into a structured outline and a reviewable WordPress draft — then verify.
- 1Select a news/tag opportunity and define the intent.
- 2Generate an outline that matches how AI answers your topic.
- 3Draft content + structure, staged safely in WordPress.
- 4Publish explicitly, then verify with a follow-up run.
Diagram Scroll to reveal steps
The PENMAN loop (4 steps)
A vertical, repeatable flow: measure what AI uses, explain the gap, draft improvements, then verify.
Run a visibility check for a topic/intent set. Get sources and inclusion signals you can act on.
Compare your page against sources AI already prefers. Convert gaps into explainable recommendations.
Turn recommendations into a structured outline and a draft you can review — optimized for AI retrieval and clarity.
Review diffs, publish explicitly, then re-run to verify changes in AI preference signals over time.
PENMAN produces concrete outputs you can assign, review, and ship — without auto-publishing.
Recommendation backlog, outlines, WordPress drafts, link routes, and operation logs.
Structured representations (entities + intent modeling) help make content clearer for retrieval and attribution contexts.
Draft-first changes, explicit approval, diffs, revision history, and rollback — every time.
Benefit: see exactly where AI-preferred sources cover what you don’t — then turn it into a draft plan.
Benefit: review diffs and ship with confidence — publishing is explicit, rollback is ready.
Recommended next steps (6-step timeline)
A simple cadence to stay visible as AI outputs evolve — without overhauling your site every week.
Choose priority topics and the pages that should become sources.
Capture sources, tiers, and inclusion signals.
Use AI Competition to explain what’s missing or unclear.
Turn gaps into a scoped plan and structure.
Review diffs, approve explicitly, and keep rollback ready.
Measure movement over time and iterate in small batches.
Start with Mode 1 on your most important pages. Ship one batch of draft-safe improvements, then verify.
FAQ
Clear answers about safety, comparisons, and how to run the workflow.
No. PENMAN is draft-first. You review diffs and publish explicitly. Rollback and revision history are part of the flow.
It means the sources AI already uses for your topic and intents. PENMAN helps you compare coverage and clarity against that set.
The goal is not copying. It’s closing clarity gaps: structure, definitions, intent coverage, and trust context that help AI retrieval.
Sources come from the visibility runs for your intents/topics. The comparison set is grounded in what AI already prefers in that context.
A backlog of recommendations/tasks, structured outlines, WordPress drafts, internal linking routes, and operation logs.
Many teams start by improving a small set of key pages first. The fastest path is a single draft batch + re-run verification.
Measure AI visibility → ship draft-safe improvements.
Start free, pick a topic/intent set, and get a clear action backlog. Publish only what you approve.