Release notes for 3.7 & 3.7.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 3.7 & 3.7.1 and why it matters.
- Which changes are safe to auto-apply.
- What to spot-check after upgrading.
What's New
The 3.7 & 3.7.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: Local SEO & NAP Consistency
Business schema, multi-location LocalBusiness graph, NAP consistency scan across your site, and Google Business Profile / Bing Places sync.
Why this matters for "WBP Omni SEO Pro 3.7 & 3.7.1 — Release Recap": Local rankings collapse when name, address or phone drift by a character across pages — LLMs then refuse to cite you as an authority for the location.
- 1Step 1
Brand Authority → NAP → Add business profile(s)
- 2Step 2
Scan the site for NAP mismatches
- 3Step 3
Auto-fix or open a review queue for edge cases
- 4Step 4
Sync to Google Business Profile and Bing Places
"Local SEO is a data-integrity problem wearing a marketing costume."
— WBP Omni SEO Pro
Tools & resources by category
- Crawlers: Screaming Frog, Sitebulb, WBP Site Scanner
- Schema: Rich Results Test, Schema.org validator, WBP Schema Graph Builder
- AI visibility: Perplexity, ChatGPT search, WBP AI Rank Tracker
- Analytics: GSC, GA4, Microsoft Clarity, WBP per-URL analytics
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.
Auto-apply without rollback points is the single fastest way to lose a month of traffic. Any vendor pitching autonomy without reversibility is asking you to bet the site on their prompt.
Paired module: Presets & Widgets
Reusable presets for meta, schema, sidebar widgets (breadcrumb, related posts, author box) and cornerstone rules — applied by CPT, silo or tag. Presets are how you keep 5,000 posts on-brand without opening 5,000 posts.
- Create a preset per CPT or silo
- Attach schema, widget and meta rules to the preset
- Apply retroactively with a preview
- Version presets so a change is auditable
Is 3.7 & 3.7.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.
How does NAP interact with multi-location sites?
Each location gets its own LocalBusiness node, is scoped to its landing page, and inherits shared Organization data — no duplicate NAP on unrelated pages.
Do presets fight my per-post overrides?
Per-post fields always win; presets only fill fields you left blank, and the UI shows exactly which field came from where.
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.
