A year is long enough for the story to be clear. Here is what shipped in 2019, what worked, and where we're taking WBP Omni SEO Pro next.
- The biggest 2019 releases.
- What our users adopted the fastest.
- Roadmap themes for the year ahead.
The 2019 Story
2019 was the year AI-search moved from experiment to default channel. Our release cadence tracked that — cleaner schema, better entity naming, and the first agentic loops.
What Users Adopted Fastest
The Explain step is the surprise winner. Turning a red flag into a plain-language sentence is what makes teams actually fix things.
- Explain → Fix → Approve as the default loop.
- Silo repair for legacy WordPress sites.
- JSON-LD linter with entity graph awareness.
Where We're Going Next
Deeper integrations, more model-specific citation coverage, and a first-party dataset for AI-surface benchmarks.
Inside WBP Omni SEO Pro: Tag Manager & Taxonomy Guard
Merges near-duplicate tags, enforces a controlled vocabulary, prevents thin tag-archive pages and rewrites internal links when tags are merged.
Why this matters for "2019 — WBP Omni SEO Year in Review": Uncontrolled tagging creates thousands of thin archive pages that dilute topical authority and confuse the LLM entity graph.
- 1Step 1
Analytics → Taxonomy Guard → Run duplicate scan
- 2Step 2
Review suggested merges with post counts and overlap %
- 3Step 3
Merge with automatic redirect + internal-link rewrite
- 4Step 4
Set a minimum-post threshold before a tag archive is indexable
"Tags are a UX tool that accidentally became an SEO problem — the fix is a vocabulary, not deletion."
— WBP Omni SEO Pro
Benchmarks to hit
| Metric | Target (p75) | Where WBP helps |
|---|---|---|
| LCP | < 2.5s | Preload hints, image optimiser |
| INP | < 200ms | Script deferral, third-party audit |
| CLS | < 0.1 | Reserved slots for hero and ads |
| Indexed / crawled | > 85% | Sitemap + canonical + orphan repair |
Pick one silo, fix its schema and internal linking first, and measure before touching anything else. A tight win on one silo beats a scattered pass across the whole site.
Glossary — plain-English definitions
Optimising a site so LLMs cite it in ChatGPT, Gemini, Claude and Perplexity answers.
Structuring content so answer engines and voice assistants can lift a single, correct answer.
Winning inclusion inside Google's AI Overviews block above the classic results.
Paired module: Keyword Cannibalization Detector
Finds pages competing for the same query cluster using GSC and embeddings, and suggests merge, canonical or refocus actions. Cannibalization is invisible to most audits and is the #1 hidden ceiling on organic growth after you cross a few hundred posts.
- Analytics → Cannibalization → Run cluster scan
- Review overlapping URLs with impressions and CTR side-by-side
- Choose merge (301), canonical or refocus per cluster
- Track ranking movement on the affected cluster for 30 days
Will your pricing change?
We do not change pricing on active licenses without notice. Any structural changes will always grandfather existing customers.
Is there a public roadmap?
Yes — the roadmap lives inside the Insights dashboard, and we publish quarterly recaps here.
Can I noindex thin tag archives without breaking navigation?
Yes — Taxonomy Guard keeps the archive reachable for users but noindexes and removes it from sitemaps until it crosses the post threshold you set.
Is a merge always the right call?
No — merge when intent is identical, canonical when one page is clearly stronger, refocus when the pages serve different intents that just happen to share a query.
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.
