Release notes for 8.7 — 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 8.7 and why it matters.
- Which changes are safe to auto-apply.
- What to spot-check after upgrading.
What's New
The 8.7 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: Dynamic XML & News Sitemaps
Auto-generated index sitemaps split by post type, language and freshness, with per-URL priority, hreflang alternates and a News sitemap for time-sensitive content.
Why this matters for "WBP Omni SEO Pro 8.7 — Release Recap": A single flat sitemap at scale slows discovery and hides freshness signals from crawlers and LLM indexers.
- 1Step 1
SEO Features → Sitemap → Enable index sitemaps
- 2Step 2
Split by CPT, language and updated-in-last-48h
- 3Step 3
Ping IndexNow + Bing + Google on publish
- 4Step 4
Expose the News sitemap only for CPTs you mark as news
"Discovery is a solved problem; the plugins that still ship one flat sitemap just haven't updated the solution."
— WBP Omni SEO Pro
References & further reading
- Google Search Central — Structured data guidelines
- web.dev — Core Web Vitals field data
- Search Engine Journal — AI Overviews coverage
- Wikipedia — Semantic search, entity linking, schema.org
- YouTube: WP Bulk Publishing channel — walkthroughs of the agentic loop
- Reddit — r/SEO, r/bigseo threads on GEO measurement
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.
Best practices worth stealing
- Ship the fix as a diff, not a screenshot — reviewers can approve in seconds.
- Log every applied change with user, timestamp and before/after payload.
- Cap batch sizes at 250 URLs so rollback stays surgical.
- Re-crawl within 24h of any apply so attribution stays clean.
Paired module: Entities & Knowledge Graph Linking
Detects entities in your content, links them to Wikidata/Wikipedia/your Fact Bank and emits sameAs and mentions properties into the schema graph. LLMs cite pages they can disambiguate — entity linking is how you tell them exactly what you mean.
- Enable Entities under Brand Authority
- Review detected entities with confidence scores
- Attach sameAs targets from Wikidata or your Fact Bank
- Publish — sameAs propagates into the page @graph automatically
Is 8.7 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 I still need to submit sitemaps in GSC?
Submit the index sitemap once. WBP keeps children current and pings IndexNow on every change, so GSC re-fetches without manual resubmits.
Do I need to hand-curate every entity?
No — high-confidence entities auto-attach on save; only ambiguous ones enter the review queue. You can also lock brand entities so they never require review.
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.
