Your blog should rank — and link back to the catalog.
Most Shopify blogs are a content graveyard: posts drafted by a general-purpose tool, disconnected from the catalog, never read again. Rankow plans pages from buyer demand, writes to a fixed quality floor, publishes through the Admin API, and decides what happens after publish.
See the full engineWhere it breaks
Three failures this page has to fix.
01
The blog does not know the catalog.
A general writing tool mentions products by name but never resolves a link to a real product handle. Readers finish the article and leave.
02
Publishing is a copy-paste job.
Titles, meta descriptions, and covers live in someone's notes. Every post costs an hour of manual cleanup before it is presentable.
03
Nothing is read after publish.
Posts go live and are never looked at again — no position check, no refresh, no rollback when a page slips.
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.
02 · Planning
Plan pages, not keywords.
Keywords become page units by splitting entities and intent, then ordering hubs before supporting articles. The pillar gate keeps thin category pages out of the queue.
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 works04 · Publishing
Ship without breaking the site.
Rankow publishes through the Shopify Admin API or a WordPress webhook, with SEO metafields, JSON-LD, and WebP images delivered from a CDN. Every write is idempotent and snapshotted.
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
Published pages keep getting rewritten until position moves — or get rolled back.
14-day refresh eligibility, 7-day thin-content rule, position 5–20 with CTR under 2%, rollback on a drop over 3 positions.
Source · engine/dfs/feedback/rules.py
Questions
Before you start.
No. You create a custom app in Shopify admin, then enter the store domain plus the Admin API client ID and secret. Rankow requests a 24-hour access token with the client-credentials grant and tests the connection before anything publishes.
No. Drafts wait for your approval. Publishing writes the article body, SEO title and description, JSON-LD, and a WebP cover through the Admin API. Every write is idempotent and snapshotted.
Yes. A post becomes refresh-eligible at 14 days, or 7 days if it is under 3,000 words. One refresh per URL, then a 90-day cooldown. If a page drops more than 3 positions at the 28-day check, the snapshot is restored.
Shopify
Plan one collection. See the page list first.
Connect the store, add competitor domains, and get a ranked list of pages before a single draft is written. The trial runs the same engine.
7 days · 1 site · No credit card