# WP BaseStation — launch copy & competitive positioning
**Prepared 2026-08-25 · competitor claims sourced from their own public pages on that date · verify before publishing**

---

# PART 1 — THE POSITIONING

## The one-sentence difference

**Every other Divi AI plugin helps AI *build*. WP BaseStation is the only one that *checks what it built*.**

That's not a feature list difference — it's a category difference, and it's worth building the whole site around. Here's the argument:

The moment an AI can build forty pages in an afternoon, the bottleneck stops being *making* and starts being *knowing whether any of it is any good*. Divi Love, Novamira, DiviOps and Respira all solve the making. None of them solve the knowing. You ship AI-built pages and find out about the 3.1:1 contrast, the missing H1, the 2 MB hero and the empty meta description when a client's customer does — or when their lawyer does.

WP BaseStation is the only one of the five that will tell you, before you ship, and then fix it with one click and let you undo that fix alone.

**Recommended headline direction** (keep your aviation theme — it's working):

> ### Your Divi site, on autopilot.
> Claude builds your pages. WP BaseStation checks every one before it ships — accessibility, SEO, performance, legal, and whether it still looks like your brand.

**Alternate hero lines, if you want to A/B:**
- "Build it with AI. Ship it with proof."
- "The only Divi AI that audits its own work."
- "Anyone can generate a page. This one tells you if it's any good."

---

# PART 2 — SITE COPY, SECTION BY SECTION

*Paste-ready. Written in the plugin's own voice — direct, specific, honest about limits. That honesty is a differentiator in a market of hype; don't let a copywriter sand it off.*

## Hero

**Headline:** Your Divi site, on autopilot.

**Subhead:** Claude connects straight into Divi 5 — building real pages from your design system, then auditing every one before it ships. 79 tools. Six audits. One click to fix what they find.

**CTA:** Get WP BaseStation free → | See how it works

**Trust line under the CTA:** Free tier, no card. Works with Claude, ChatGPT, Cursor, or any MCP client. Your site, your server — nothing routes through us.

---

## Section: The problem nobody else is solving

**Eyebrow:** THE HONEST PART

**Headline:** AI can build forty pages in an afternoon. Can you review forty pages in an afternoon?

**Body:**
Every AI page builder has the same blind spot: it hands you volume and leaves you the review. And AI-built pages fail in specific, repeatable ways — a heading level skipped, white text over a photo nobody checked, a 3 MB hero, a meta description that never got written, a button that says "Learn More" for the ninth time.

WP BaseStation builds like the others. Then it does the part they don't: it reads every page back the way a reviewer would, names what's wrong in plain English, and offers to fix it — one click, one undo.

---

## Section: Six audits, on every page

**Eyebrow:** FLIGHT CHECKS

**Headline:** Six auditors read your site the way a reviewer would.

| Audit | What it catches |
|---|---|
| **Site QA** | Pages that aren't really Divi 5, broken attribute paths, unknown modules, invented design tokens, anything your client can't edit in the Visual Builder |
| **Accessibility** | WCAG AA contrast with real inheritance, heading order, alt text, link text, iframe titles — plus the Divi-specific defects a generic scanner can't find, like a module link that renders as an unreachable clickable div |
| **Performance** | Oversized and hotlinked images, page weight, module counts, nesting depth — read from stored content and your media library, with no third-party service and no API key |
| **SEO** | Titles, meta descriptions, thin content, slugs, internal links, staleness, noindex, and the Divi fault where a Text module is styled to look like a heading but carries none of a heading's meaning |
| **Legal** | Privacy policy, terms, cookie and consent surfaces — the pages agencies forget until a client asks |
| **Design Guardian** | Dated patterns, auto-rotating sliders, generic CTA copy, type-scale drift away from your own design system |

**Kicker:** Every finding names the exact fix. Eleven kinds of finding fix themselves with one click — and every fix is individually undoable, not a page rollback.

---

## Section: Fix and Undo

**Eyebrow:** ONE CLICK, ONE UNDO

**Headline:** Finding a problem is half a product.

**Body:**
Most audit tools hand you a list and wish you luck. WP BaseStation puts a **Fix** button next to the finding, and an **Undo** button next to the fix.

Compress the oversized images — the original file never moves, every reference is rewritten, and undo restores it byte-identically. Write the missing alt text. Repair the heading order, relabelling each heading to the level it should have been. Fix one page, or hit **Fix all** and clear the same cause across every page it touches.

If a fix can't do anything, it says so. It will never report success for work it didn't do.

---

## Section: It builds too

**Eyebrow:** WHEELS UP

**Headline:** Real Divi modules. Your design system. Not fake HTML.

**Body:**
WP BaseStation writes genuine Divi 5 blocks — sections, rows, columns, modules — that open and edit normally in the Visual Builder. It reads your colors, fonts, spacing and presets first, then builds from *your* tokens instead of hardcoding hexes, so your pages restyle when your brand does.

It builds beyond pages, too: blog posts, WooCommerce shop pages, Theme Builder headers, footers and templates, reusable patterns, and a style-guide page on request.

And when it isn't sure what value to use, it resolves rather than guesses — checking your tokens first, then your site's own established conventions, then a real default, and telling you which of the three it used.

---

## Section: Rescue

**Eyebrow:** BRING IT UP TO DATE

**Headline:** Got an older site? Start there.

**Body:**
Divi 4 shortcodes, classic content, leftovers from deleted plugins, chrome living outside the Theme Builder — the compatibility check classifies every page and produces an ordered fix plan. Then Claude repairs the site page by page, snapshot first, with every step undoable.

---

## Section: Safety

**Eyebrow:** NOTHING CHANGES SILENTLY

**Headline:** You decide what the AI is allowed to touch.

**Body:**
Safety switches are enforced in the write path, not described in a doc — a refused call is refused before anything is touched. Start new pages as drafts. Require confirmation before replacing a published page. Lock the design system so pages can still be built but your brand can't be changed underneath you. Or flip **Read-only** and let it analyse without writing a single byte.

Every design-system write takes a snapshot first. Every action is logged. Every page write keeps a revision.

**Private mode:** on client sites, restrict the entire plugin to the administrators you choose. Everyone else with admin rights keeps editing pages normally — they just never see WP BaseStation. No menu, no dashboard, and optionally no row on the Plugins screen.

---

## Section: Proof

**Eyebrow:** WE TEST OURS

**Headline:** 1,154 integration tests, against your live install.

**Body:**
Not tests against a mock — tests against *your* Divi, on *your* server, in one click. Every check exists because that exact bug shipped during the build. Run it after every plugin update and after any Divi update: a Divi release quietly changing one of its own conventions is exactly the failure this catches, and it's the failure that silently breaks every other tool in this category.

No other Divi AI plugin ships anything like it. Ask them.

---

## Section: For agencies

**Eyebrow:** CLIENT WORK

**Headline:** The report is the deliverable.

**Body:**
Run the audits on a schedule and get a digest that says what was fixed, what regressed and what's new — the sentence you forward to a client. Download a self-contained client report covering every audit. Bind the plugin to your own admin account so the client never sees it. Snapshot before, roll back after, and show the audit trail of who changed what.

---

## Section: Honest limits

**Eyebrow:** WHAT IT CAN'T DO

**Headline:** Every audit tells you what it couldn't see.

**Body:**
Static analysis reads stored content, so it works on drafts and staging and behind auth — and it cannot see anything that only exists in the browser. Slider arrows, gallery lightboxes and portfolio filters are built by JavaScript and are invisible to it. It doesn't measure Core Web Vitals; use PageSpeed Insights for that, and use this to fix the page content that causes them. Text over a background photo is reported as *undecidable*, not guessed at. A clean accessibility result is a floor, not a WCAG conformance claim.

We print that on every report. An audit that overclaims is worse than no audit — you stop checking what it was silent about.

---

## FAQ

**Does my site data go through your servers?**
No. The plugin runs a server on *your* WordPress install, and your AI client connects straight to it. There's no middleman, no third-party image service, no API key to buy.

**Which AI assistants work?**
Any MCP client — Claude (web, desktop, Code), ChatGPT, Cursor, and others. You paste one connector URL.

**Will it wreck a live site?**
Not by default: new pages start as drafts, replacing a published page needs explicit confirmation, every design-system write snapshots first, and every page write keeps a revision. Start on staging, keep backups, and use Read-only mode while you evaluate.

**Do I need to know how Divi 5 stores things?**
No. That's the point. WP BaseStation carries the Divi 5 knowledge — attribute paths, preset resolution, token formats — so your AI doesn't have to guess at it.

**What if Divi changes?**
Run the self-test. 1,154 checks against your live install will tell you within a minute whether a Divi update broke a convention this plugin depends on.

---

# PART 3 — COMPETITIVE COMPARISON

*Sourced from each vendor's own public pages, 2026-08-25. Re-verify before you publish anything comparative — they ship fast, and a stale claim is a liability.*

| | **WP BaseStation** | Divi Love (Divi Connect) | Novamira Pro | DiviOps | Respira |
|---|---|---|---|---|---|
| Builds real Divi 5 modules | ✅ | ✅ | ✅ | ✅ | ✅ |
| MCP tool count | **79** | not published | not published | 74 | not published |
| Design system / tokens | ✅ + resolvers | ✅ | ✅ | ✅ | partial |
| Theme Builder | ✅ | ✅ | ✅ | ✅ | — |
| WooCommerce | ✅ | — | ✅ | — | — |
| Query loops / dynamic binding | ❌ **gap** | — | ✅ | ✅ (SCF) | — |
| Display conditions | ❌ **gap** | — | ✅ | — | — |
| ACF / custom fields | ❌ **gap** | — | ✅ | ✅ | — |
| Ready-made style library | 5 patterns | ✅ **490 styles, 5 looks** | — | — | — |
| **Accessibility audit** | ✅ **WCAG, module-aware** | color readability only | ❌ | ❌ | separate paid product |
| **SEO audit** | ✅ | ❌ | ❌ | ❌ | ❌ |
| **Performance audit** | ✅ | ❌ | ❌ | ❌ | ❌ |
| **Legal / compliance audit** | ✅ | ❌ | ❌ | ❌ | ❌ |
| **Design-taste audit** | ✅ | ❌ | ❌ | ❌ | ❌ |
| **One-click Fix + per-fix Undo** | ✅ **11 fix types** | ❌ | ❌ | ❌ | ❌ |
| **Self-test against live install** | ✅ **1,154 checks** | ❌ | ❌ | ❌ | ❌ |
| **Scheduled audits + digest** | ✅ | ❌ | ❌ | ❌ | ❌ |
| **Client-ready report export** | ✅ | ❌ | ❌ | ❌ | ❌ |
| Divi 4 → 5 migration | ✅ Rescue | ❌ | ❌ | ❌ | edits D4 in place |
| Snapshots / rollback | ✅ | ✅ 20 versions | ❌ | dry-run only | ✅ duplicate-first |
| Operator lock / white-label | ✅ Private mode | audit log | ❌ | ❌ | ❌ |
| Multi-builder | Divi only | Divi only | Divi only | Divi + WP-wide | 8+ builders |
| Open source | ❌ | free skill is | ❌ | ✅ MIT | ❌ |

## The five claims you can make and defend

1. **The only one that audits.** Six audit suites vs zero anywhere else. Divi Love's "colour readability checker" is the closest thing any competitor has, and it's one check against your palette — not an audit of your pages.
2. **The only one that fixes what it finds.** Eleven auto-fixable finding types with per-fix undo. Nobody else has a Fix button at all.
3. **The only one that tests itself against your live Divi.** 1,154 checks, one click. This is your strongest technical moat and the hardest to copy.
4. **The only one built for client work end to end** — scheduled audits, digests, a downloadable client report, and Private mode so the client never sees the tooling.
5. **The only one that migrates Divi 4 → Divi 5 as a guided, page-by-page, snapshot-first project.**

## Claims to AVOID

- ❌ "Most tools" — DiviOps ships 74 against your 79. Too close to lead with.
- ❌ "Best page builder" — Novamira's dynamic-content and conditions work genuinely beats yours today.
- ❌ "Most styles" — Divi Love's 490 styles and five named looks dwarf your 5 patterns.
- ❌ Anything about their pricing or roadmaps. Compare capability only, cite the date, and link their page.

---

# PART 4 — WHAT YOU'RE MISSING (you asked)

**Four real gaps. The first three are the same gap wearing different hats: your builder can't do data-driven pages.**

### 1. Query loops + dynamic content binding — the biggest one
Novamira does this explicitly: enable query loops on loop-capable modules, bind fields per item, wire dynamic content from post, site, ACF and WooCommerce data. DiviOps does it via Secure Custom Fields. You have **zero** tools for it — I checked the manifest.

This matters because it's the difference between building forty *static* pages and building one *template* that renders forty. Any real estate site, job board, directory, or product catalogue needs it. Right now you can't build those, and a prospect who needs one will pick Novamira.

**Recommendation:** highest-priority post-launch feature. `divi_set_query_loop`, `station_bind_dynamic_field`, `divi_list_content_sources`.

### 2. Display conditions
Novamira sets visibility by login status, user role, post type, date, device, or WooCommerce state. You have none. This is table stakes for membership sites and any personalised page, and it's a small, self-contained feature — probably a few days' work.

### 3. ACF / SCF custom fields
Both Novamira and DiviOps integrate with custom field plugins. ACF is on a huge share of professional WordPress sites. Without it you can't build the content-modelled sites agencies actually get paid for.

### 4. The style library — Divi Love's real advantage
This is what their "Design Taste/Styles" announcement is (see Part 5). They ship **490 ready-made styles and five named aesthetic packs**. You ship 5 patterns plus resolvers.

Your resolvers are *architecturally* better — they derive values from the site's own evidence rather than imposing a look. But "490 styles, pick a look" demos beautifully and yours doesn't demo at all. **Don't rebuild their library — you'd lose that race.** Instead make your advantage visible: let WP BaseStation *derive* a named look from a brand the user already has (a logo, a URL, three colours), and show the before/after. Their looks are presets someone else chose; yours would be your client's brand, systematised.

**Smaller gaps worth noting:** no lifetime pricing tier (Divi Love: $199 unlimited — expect price pressure); you're Divi-only where Respira spans 8 builders (I'd keep that focus, but know the objection); and your free tier needs to be generous enough to compete with DiviOps being fully open-source MIT.

---

# PART 5 — WHAT DIVI LOVE'S "DESIGN TASTE / STYLES" ACTUALLY IS

**Short answer: it's a curated style library plus brand-aware theming. It is not an auditor, and it does not judge design quality.**

From their own pages, the feature set is:

- **490 ready-made styles** — a large preset library the AI can apply to modules.
- **Five named aesthetic looks** — Meridian, Foundry, Monolith, Electropop, Jungle. Pick a look and the AI builds in that visual language.
- **Brand-first reading** — the AI reads your colours, fonts and spacing *before* building, and generates a coordinated design system rather than hardcoding values.
- **Automatic restyling** — change your colours and existing pages follow, because everything references tokens by name.
- **Design lock** — the AI must ask before touching colours, fonts, or the Theme Builder. Plus read-only mode.
- **A colour readability checker** — light/dark contrast checked "before release." This is the one place they touch accessibility, and it checks the *palette*, not your pages.
- **History** — 20 versions per page, a separate design history, one-click restore to the pre-AI state.

### How to read it competitively

**What they genuinely beat you on:** library scale (490 vs 5) and the demo appeal of "pick a look, get a site." Also design lock as an explicit, marketed concept — you have the equivalent in `protect_design`, but you barely sell it.

**What it is not:** it's a *generation* feature — it makes new pages look coordinated. It tells you nothing about the site you already have. It won't find the 3.1:1 contrast on the page your junior built last year, the missing H1s, the 2 MB hero, or the thin content. Their contrast checking is a palette-level check before release; yours is a per-page audit with inheritance, gradient and image awareness, that reports *undecidable* rather than guessing.

**The line I'd use:**

> Divi Love gives your AI 490 styles to build with. WP BaseStation gives it your design system to build with — and then checks the result against WCAG, your SEO, your page weight, and your own brand conventions. Styles make new pages look good. Audits tell you whether they *are* good.

### Two things to copy from them, honestly

1. **Name your looks.** Even 5–8 named starting points ("Foundry", "Meridian") give a prospect something to point at. You have patterns and a style-guide builder; package and name them.
2. **Market your design lock.** They lead with "the AI must ask before touching your colours." You have `protect_design` and a whole write-path enforcement layer that's *stronger* — and it's buried in a settings panel. Put it on the homepage.
