Custom Post Types unlock programmatic SEO in WordPress. Register them wrong and you kill your own crawl budget.
- Always set has_archive + rewrite for SEO CPTs.
- Register matching taxonomies.
- Verify sitemap inclusion after registration.
One client had 6,000 CPT entries invisible to Google — has_archive was false. Flipping it + regenerating sitemap indexed 5,700 in 3 weeks.
- public: true
- has_archive: true
- rewrite: with_front false
- show_in_rest: true
- menu_icon set
- Sitemap inclusion verified
Inside WBP Omni SEO Pro: Guided Onboarding & Wizards
A first-run wizard that connects GSC, imports competing plugins, recommends starter modules and configures presets based on site type.
Why this matters for "WordPress Custom Post Types — Full 2026 Guide with SEO": Most SEO plugins ship with a config screen — WBP ships with a coach.
- 1Step 1
Onboarding → Answer 6 questions about the site
- 2Step 2
Approve the recommended module set
- 3Step 3
Import from RankMath/Yoast/AIO if detected
- 4Step 4
Land on a dashboard already populated with your data
"The first ten minutes of a plugin decide whether it earns the next ten months."
— 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
AI search killed classic SEO.
AI Overviews cite the same URLs that rank in the top 10 — classic SEO is the qualification round.
More schema = more rich results.
Conflicting schema silently disqualifies you — one clean @graph beats three overlapping emitters.
Programmatic pages get penalised.
Thin programmatic pages get penalised — templated pages with unique data and internal links rank fine.
Quick pre-publish checklist
- Primary entity named in the first 100 words
- Every H2 maps to a real user question
- Schema validated in Rich Results Test
- At least 3 inbound internal links from related pillars
- Canonical set explicitly, not inferred
- FAQ present when 3+ questions are genuinely answered
Paired module: SEO Error Monitor
A rolling scan of indexability, canonical drift, meta length, duplicate H1s, image weight, mixed content and schema validity — with severity and one-click fixes. Errors are cheap to introduce (a theme update, a plugin conflict) and expensive to find without a monitor watching every publish.
- Enable Error Monitor in SEO Features
- Set severity thresholds per environment
- Route P1 issues to Slack/Email via the reports channel
- Approve suggested fixes in bulk or per-URL
CPT UI or code?
Code for production. CPT UI for prototyping.
Do CPTs affect performance?
Only if you register 20+ or use bad meta queries.
Can I re-run onboarding later?
Yes — Onboarding is a persistent module you can rerun after site changes, and each run keeps a history.
Will the monitor false-alarm on staging?
Environment awareness is built in — staging URLs and noindex pages are excluded by default and severity is downgraded accordingly.
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.
