Unclassified

55 — SEO Strategy

Status: CANONICAL · Commercial OS
Owner: PMM hat
Last verified: 2026-07-21

Purpose

How IntegrateWise wins search — with a stage-honest strategy: we cannot outrank incumbents on head terms today, so we own the terms we're creating, dominate the long-tail pain queries our ICP actually types, and build authority through the founder's narrative engine.

Target audience: PMM, content writers, site builders.

1. Strategy: Three Rings

Ring 1 — Category terms (own them from day one). Nobody ranks for our vocabulary yet because we're coining it: workspace for human and AI collaborative work · human AI collaborative work · shared workbench · AI twin for work · governed AI memory · approval-gated AI · adaptive spine. Every category page, manifesto, and essay reinforces these. Winning searches that don't exist yet is cheap; when the category conversation starts (and giants will start it — 07 §3), we're the definitional result. Track pickup monthly; this ring is the launch's true north (51 §4).

Ring 2 — Pain queries (the ICP's actual searches). High-intent long-tail where incumbents write generic listicles and we write the definitive answer from lived pain:

Cluster	Example queries	Asset
The morning ritual	"too many tools customer success," "CSM spends hours gathering data," "reduce QBR prep time"	CS pillar essay + LP-3 (54)
Churn signals	"detect churn signals early," "churn surprised us," "customer health score didn't work"	Wound-story essays; signal-evidence explainers
AI trust	"AI hallucinations at work," "can I trust AI with customer data," "AI forgot context," "govern AI memory"	Demotion essays; governance explainers; LP-2
Comparison intent	"Gainsight alternatives," "copilot vs [category]," "AI for account management"	/vs pages (54 LP-5) — category-compared, never brand-attacked
Stack-specific	"HubSpot account 360," "connect HubSpot Zendesk Stripe one view"	Connector/solution pages; marketplace listings (49)

Ring 3 — Authority (E-E-A-T through the founder). Search engines increasingly reward demonstrated experience; our founder is the experience: MuleSoft architect + CSM bylines on every essay, the $8M story as the About backbone, design-partner numbers with methodology notes. Founder-led content (57) is the authority engine; the site is where it accrues.

2. Site Mechanics

Technical hygiene as table stakes: static-fast (<1s p75 — also a brand claim 52 §4) · clean semantic structure · schema markup (Organization, Product, FAQ on security/pricing pages) · every essay has one target query cluster, stated in the doc's frontmatter before writing (no query, no essay — prevents content drift) · internal linking follows the hub model: essays → pillar pages → product pages (mirrors the Commercial OS's own cross-linking).

Content cadence (realistic for founder + PMM hat): 1 essay/week (56 owns the calendar) · each essay shipped natively to LinkedIn + newsletter, canonical on site · quarterly: refresh top-10 performing pages; prune or merge sub-100-visit pages.

3. What We Don't Do (stage discipline)

No paid search until LTV evidence (50 §3) · no programmatic SEO farms (a thousand thin connector pages would rank briefly and poison the brand's evidence-first posture) · no guest-post link buying · no chasing head terms ("AI workspace" solo is a bonfire of effort pre-authority — we get it via Ring 1 as the category grows).

KPIs: Ring 1 — category-term impressions + our rank (target: #1 on exact category phrase by launch+90) · Ring 2 — non-brand organic visits/mo (500 by launch+90, 2,500 by mid-2027) and organic → CTA conversion ≥ 3% · Ring 3 — branded search volume trend; essay-attributed pipeline in 73 Marketing Metrics.