Keep your archive AI-fresh — not just published.
If you publish dozens of posts a week, AI search will judge your archive as a whole. PENMAN helps editorial teams refresh, restructure and re-link content so every post stays cited.
Always-fresh editorial archive.
Drafts & diffs — never blind edits.
Rollback + revision history.
Bulk re-analyse, fix what matters, publish what’s safe.
- Re-fetch every week — new posts in, modified posts updated, no manual checks.
- Discover-friendly patterns — freshness, entity coverage, image structure baked in.
- HTML Templates for FAQ blocks, comparisons, key-takeaways — AEO-friendly out of the box.
- Drafts only — no surprise edits to live posts.
The hard part isn’t ideas. It’s proof, prioritization and approvals.
PENMAN makes archive maintenance and AEO/GEO delivery repeatable.
Proof over opinions
Visibility runs create a shared baseline — so editorial meetings stop debating “AI said…” anecdotes.
Explainable recommendations
Compare to AI-selected sources and translate gaps into a clear task list editors understand.
Approval-friendly execution
Draft-first publishing with diffs and rollback makes editorial approvals faster and safer.
Packaged deliverables
Run “AI visibility sprints” with a consistent output format and a repeatable monthly rhythm.
Cross-module consistency
Link Sets and HTML Templates keep output structured and reviewable across desks and verticals.
Voice control (optional)
AI Personas keep a consistent author voice across content and EEAT campaigns — without changing strategy decisions.
A monthly loop your newsroom can actually run.
PENMAN packages archive maintenance into a loop that’s easy to communicate and easy to approve.
Run AI Visibility on priority verticals
Establish a baseline source set for each desk and normalize results into easy tiers (high / medium / low).
Compare against AI-selected sources
Identify why other publications are selected and convert it into explainable recommendations editors can action.
Generate draft-ready updates
Create content improvements, internal linking updates and FAQ/HTML template inserts as drafts — structured and reviewable.
Review diffs → approve → publish explicitly
Editors see exactly what changed. Publishing happens only after explicit approval. Roll back if needed.
Re-run to measure movement
Repeat the loop monthly to sustain momentum and keep visibility improvements measurable.
Editorial wins when progress is visible.
Draft-first changes and diffs reduce back-and-forth and protect production sites.
- Review only what changed (diffs), not entire pages.
- Roll back quickly when a change isn’t worth keeping.
- Standardize deliverables across desks with the same workflow.
HTML Templates (format contract), Link Sets (approved references) and AI Personas (voice layer).
Make AI visibility your next editorial discipline.
Visibility runs → comparisons → recommendations → draft-first WordPress execution with diffs and rollback. Publishing is always explicit.