Content that matches the product, not a keyword list.
SaaS content usually splits in two: docs that convert nobody and blog posts that mention the product once. Rankow plans from demand signals, writes against what the product actually does, and reads the result before deciding what to write next.
See the full engineWhere it breaks
Three failures this page has to fix.
01
Keyword lists outrank product knowledge.
The plan is a list sorted by volume, so pages are written about terms the product cannot answer better than anyone else.
02
Thin posts with a demo button.
Eight hundred words, one product mention, a CTA. There is no comparison, no numbers, nothing a reader could not get from the first three results.
03
No owner after publish.
The team moves to the next launch. Nobody checks whether the page indexed, ranked, or earned a click.
What runs
The same loop, on your site.
These are sections of the engine documented on the product page — not a separate product for your segment.
01 · Discovery
Start from evidence, not a competitor list.
Competitors are one input, not the starting point. Rankow certifies seeds from two demand signals — competitor organic rankings, and your own Search Console queries with impressions but no top-three position — then expands them with keyword ideas, suggestions, and related terms. Four sources merge into one source-tagged pool.
How this layer works03 · Writing
A draft that has to earn its slot.
Writing starts from a brief that fixes the entity, intent, outline, sources, and FAQ. The 3,000-word floor is enforced before the quality check runs.
How this layer works05 · Feedback
Let Search Console close the loop.
At 28 days, each page is checked against Search Console: index status, impressions, position, and clicks. The result decides the next action.
How this layer worksWhat you get
Results, with the rule behind them.
Every claim below comes from the same rulebook the engine runs on. None of it is a ranking promise.
A 12,000-keyword candidate pool becomes this month's page list.
120 page units per cycle: hubs first, supporting pages after, pillars gated.
Source · engine/dfs/planning/plan.py
Every draft clears 3,000 words and an information-gain check before it can publish.
Length is a floor, not a finish line. A draft below the floor or without a gain signal is blocked.
Source · engine/dfs/writing/gate.py
Day 28: Search Console tells you what happened to each page.
Index status, average position, impressions, and CTR are read per URL, not per account.
Source · Google Search Console
Questions
Before you start.
The page plan is rebuilt each cycle from competitor coverage and your own Search Console queries. Published pages are re-read at 28 days and re-checked against the refresh rule at 14 days.
No. Rankow plans and writes demand-facing pages. Docs stay with your product team; those pages can be linked from the cluster so the article sends readers to the source of truth.
Yes, through the publish contract: your app receives the HTML body, SEO fields, and structured data, then renders them. Shopify is the fully managed path in production today; other channels take publish-ready drafts or payloads.
SaaS
Plan the pages your product should own.
Connect Search Console and a few competitor domains. The first output is a page list, not a batch of posts.
7 days · 1 site · No credit card