SEO content planned from search performance, not from a keyword list
- Client
- Ammpli ↗
- Sector
- Marketing technology
- Engagement
- Fixed project
- Scope to production
- 7w
- Engineers, not 7
- 3
The AI content market filled up with tools that generate volume. Volume is the wrong output. A site does not rank because it published thirty posts; it ranks because it published the few that matched something people actually search for and that the site has a credible claim to answer.
Ammpli was scoped against that: fewer posts, chosen from the site's own search-performance data, competitor positions and search intent, rather than from a keyword list bought by the thousand.
What we did
A fixed project: defined scope, fixed price, fixed date, delivery responsibility on us.
- Scoping, three days. The product decision that shaped everything was deliberate scarcity. Two strategic posts a week, not daily output. That constraint drove the planning model, the pricing and the entire quality bar.
- Factory setup, week one. Environments, CI, the delivery platform, and Search Console ingestion running against real properties before any generation existed.
- Build, weeks two to six. Three certified engineers, shipping weekly. Agents handled the publishing integrations and the content pipeline scaffolding. The engineers owned the opportunity-scoring model, which is the actual intellectual property, and the brief structure that keeps generated writing specific to the business rather than generically competent.
- Hardening and launch, week seven. Publishing reliability, rollback on failed posts, email delivery as a fallback path, and subscription billing.
What made the difference
Grounding the plan in the site's own Search Console data rather than in a generic keyword corpus is the difference between advice and guessing. It also means the recommendations improve as the site accumulates history, which turns a content tool into something with a reason to be kept.
Publishing directly into WordPress and Shopify was the second decision that mattered. Content that arrives as a document is work; content that arrives as a scheduled draft in the CMS is a product.
Where it landed
Two strategic posts a week per site, planned from live search-performance data, published into the customer's existing CMS or delivered by email, from $99 a month.
StackTypeScript · Node · Postgres · Search Console API · WordPress and Shopify APIs
Create 10x more value with technology.
Your roadmap shouldn't be waiting.
30-minute call · No deck · Engagement lead on the call