Release notes for 9.1 — this recap covers the meaningful changes for site owners running WordPress SEO in production. We rewrote it as a plain-language checklist rather than a wall of tickets.
- What's new in 9.1 and why it matters.
- Which changes are safe to auto-apply.
- What to spot-check after upgrading.
What's New
The 9.1 cycle focused on stability, schema fidelity, and clearer signals for AI-search surfaces. Nothing here forces a re-architecture — the goal was cleaner defaults and fewer manual overrides.
Safe to Auto-Apply
Rendering fixes, security hardening, and schema output corrections all fall into the safe bucket. If you use WBP Omni SEO Pro's Apply loop, these move without human review.
- Schema output normalization for edge cases.
- Rendering fixes on paginated archives.
- Backwards-compatible filter deprecations.
Post-Upgrade Checks
After the release lands, run a fresh audit and spot-check the highest-traffic templates. The Explain step will tell you why anything changed.
Inside WBP Omni SEO Pro: Social Media & Open Graph Manager
Per-URL Open Graph and Twitter Card overrides, auto-generated share images from a template, and per-network preview validators.
Why this matters for "WBP Omni SEO Pro 9.1 — Release Recap": Social previews are the second first impression — a broken OG image kills click-through more than a bad title.
- 1Step 1
Set brand defaults for OG and Twitter
- 2Step 2
Override per-post in the Editor sidebar with live preview
- 3Step 3
Auto-generate share images from a template + post data
- 4Step 4
Validate against Facebook, LinkedIn and X debuggers from the panel
"The share card is the ad you never wrote — treat it that way."
— WBP Omni SEO Pro
Manual vs. audit-tool vs. agentic
| Trait | Manual | Audit tool | Agentic (WBP) |
|---|---|---|---|
| Output | Spreadsheet | PDF report | Approvable diffs |
| Reversibility | Manual DB fix | None | One-click rollback |
| Speed to fix | Days | Weeks | Minutes |
| Scale | ≤ 200 URLs | Any (read-only) | Any (write + rollback) |
Stats snapshot
Case study — from audit fatigue to shipped fixes
A DTC brand with 4,200 URLs replaced its quarterly PDF audit with weekly per-silo agentic runs. After 60 days, orphan pages dropped from 812 to 14, FAQ-eligible URLs grew 6×, and AI citations tracked in Social Media & Open Graph Manager rose 41% month-over-month.
Paired module: GEO — Generative Engine Optimisation
Optimisation for how ChatGPT, Gemini, Claude, Perplexity and Google AI Overviews retrieve and cite your content — llms.txt, extractability, factual density and citation-worthy formatting. AI answer engines route intent before the SERP does; being invisible to them is being invisible to the top of the funnel.
- Enable GEO mode in SEO Features
- Publish llms.txt with cited pages and license terms
- Audit posts for extractability (short facts, clear headings, TL;DR)
- Track citations in the AI Rank Tracker weekly
Is 9.1 a required upgrade?
Yes for security-relevant releases; otherwise recommended within one to two cycles so your snippets and schema stay in step with what AI surfaces expect.
Will it break my existing overrides?
No — we treat published overrides as user intent and never overwrite them on upgrade. Deprecations always ship a compatibility layer for at least two minor versions.
Do the auto-generated share images count as duplicate media?
Each image is generated per post with a unique title, author and hero — they share a template, not the file, and are cached at the edge.
Is GEO just SEO with new labels?
It shares the discovery layer, but the ranking function is different — LLMs weight extractability, factual density and entity clarity far more than backlinks.
Ship this workflow inside WordPress
WBP Omni SEO Pro turns every playbook on this blog into an approvable, reversible diff.
Get WBP Omni SEO ProAffiliate — this link goes to the official WBP Omni SEO Pro product page.
