wpos.ai —
rebuild spec & run.
Everything the audit found, turned into a build plan: what’s on the site today, what has to change, what has to be added, and the order to do it in. Grounded in the real pages, not a wishlist.
01 · What’s on the site today
The grounded inventory.
The content rewrite landed cleanly and the technical hygiene is good. The gaps are structure, positioning, and evidence — not plumbing.
Home page — sections that exist
Hero (new copy ✓), 3-step “how it works” ✓, a stats section still titled “From First Prompt to Live WordPress Website in 30 Minutes*”, feature blocks (Connect apps / Figma / Image Gen), Transparent Pricing, Community (YouTube embeds), Book a Call, FAQ (new ✓), final CTA.
Pages that exist
- home · what-is-wpos · cases · connectors · pricing (new model ✓)
- wpos-vs-10web · manifesto · beta
- company (stale, WPCursor-era) · blog (20 SEO posts) · legal
Technical SEO — healthy
- 1 h1, canonical, 8 OG/Twitter tags
- Rich JSON-LD: FAQPage, SoftwareApplication, Organization, AggregateRating, Review, BreadcrumbList, WebSite+SearchAction
- robots.txt → wp-sitemap.xml (5 sub-sitemaps, populated)
How the site is edited
- Page copy = Gutenberg block attributes → needs the WPOS agent or a WP app-password (MCP key is 401 on page edits)
- Shared widget templates → editable via MCP key, revisioned + rollback
02 · What needs to change
Fix what’s already there.
These are edits to existing content — no new pages. Most are content-only (safe via the WPOS agent), and each fixes a specific audit finding.
03 · What needs to be added
The structure that isn’t there.
The docs prove ~20 capabilities; the site markets ~5, and every feature page is a 404. Adding them sells the product properly and builds the SEO/AEO/GEO surface in one move — each page is a capability sold + a real search intent targeted.
Feature & use-case pages Add
Conversion & evidence Add
/pilot (or /start)
A real landing page for the pilot motion & “Start free” — instead of every CTA dumping into the paywall. Where “comment pilot” and the CRM outreach send people.
Hero demo film
The money-demo video above the fold (brand PDF → live site). Show-don’t-tell — currently the only video is buried in a Community block.
Surface the 50-page showcase
The exjsx showcase as visual proof on-page, not just a text link. Cross-link exjsx.dev ⇆ wpos.ai both ways.
UTMs on every outbound link
Currently zero — 66% of traffic reads as “Direct.” Tag everything so posts and pages get attributed.
AEO / GEO Add
/llms.txt
Currently 404 on wpos.ai — the core file AI answer engines read to understand & cite you. Ironic: the product advertises serving it automatically. Publish one listing the new pages.
Per-page schema
Extend the strong home-page JSON-LD (FAQPage, SoftwareApplication) to the new feature/use-case pages so each is independently answer-engine legible.
04 · The end-to-end run
Sequence: measure, then message,
then structure, then evidence.
Instrument first so every later change is measurable. Fix the message before building pages onto a confusing one. Structure before evidence. And hold anything that promises “free” until the app can honor it.
You can’t tune what you can’t see. Turn the funnel visible before touching content.
UTMs on every outbound link across the site and all comment links.
content · fixes the 66%-Direct blind spot
Define ~6 PostHog conversion events on wpos.ai: hero_cta_click, pricing_view, signup_start, paywall_hit, pilot_submit.
PostHog MCP (read) + a dev to add the capture calls
Everything in §02. Safe, no new pages, mostly one WPOS-agent pass.
Headline + title/meta off the jargon → plain benefit line + “not just an AI builder.”
WPOS agent (page copy) or WP app-password
Real proof numbers into the stats section (57 / 50,000 / 42s / 99.1%).
WPOS agent — targeted at the “30 Minutes” section
Source PDF ends here — Phase 1 is cut off mid-list and Phases 2+ are in a follow-up document.