Rankow
Product

Every layer of the engine, on the record.

Six capabilities, one loop. Each section explains what goes in, what comes out, and what stops a bad run before it reaches your site.

01 · Discovery

Start from competitors, not guesses.

Rankow reads twelve competitor domains before it asks you for a seed keyword. The output is a candidate pool with counts, sources, and a documented cutoff.

  • Twelve competitor domains per project, set at onboarding.
  • Seed keywords are optional; competitor coverage can start the pool.
  • The candidate pool is capped at 12,000 keywords and truncated by volume.
  • Every keyword keeps its source, so the plan can be traced back.

Input

Competitor domains + optional seeds

Output

Ranked 12,000-keyword candidate pool

Sample run · discovery

Source set

12 competitor domains

Pool built
competitor-01.com2,140 kw
competitor-02.com1,880 kw
competitor-03.com1,620 kw
competitor-04.com1,410 kw

+ 8 more

Candidate pool

12,000

KeywordVolIntent
cast iron care12,100info
best cast iron skillet22,200comm
ceramic vs cast iron9,900info
seasoning a skillet6,600info
Source-tagged12,000 candidates

Interface sample · illustrative data

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.

  • Entity × intent is split so pages do not compete with each other.
  • Hub pages are planned before supporting articles.
  • Pillar gate: more than 50k monthly volume or keyword difficulty above 40.
  • Intent quotas per cycle keep informational and commercial pages balanced.
  • The default cycle plans 120 page units.

Input

12,000 candidates + hub rules

Output

120 page units with priority

Sample run · planning

Page units

Cycle 04 · 120 planned

Pillar gate on
HUBCeramic cookware74,000Pass
HUBCast iron care58,000Pass
SPOKESeasoning a skillet18,000Queued
SPOKEEnamel vs ceramic9,900Queued
SPOKERust removal8,100Queued
Pillar gate> 50k volume or KD > 40
Hub-first ordering8 hubs · 112 spokes

Interface sample · illustrative data

03 · 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.

  • Brief-driven: entity, intent, outline, sources, and FAQ are fixed first.
  • 3,000 words is the hard floor, checked before anything else.
  • Information gain: a comparison table, spec numbers, a verifiable source, or craft detail.
  • FAQ is built from People Also Ask questions found in the SERP.
  • No more than five images per article. A failed check gets one retry.

Input

Page brief + brand rules

Output

A checked draft, or a blocked run

Sample run · writing

Brief

Draft 03 · cast iron care

Gate passed
Entity cast iron skillet · Intent informational · Outline seasoning / rust / restoration
3,000-word floor3,000+ words
Information gaincomparison table
Verifiable source2 citations
Images4 of 5 max
FAQ from PAA3 questions
Word count3,000 / 3,000

Marker at the 3,000-word floor

One retry on failureBlocked until pass

Interface sample · illustrative data

04 · Publishing

Ship without breaking the site.

Rankow publishes through the Shopify Admin API with SEO metafields, JSON-LD, and WebP images delivered from a CDN. Every write is idempotent and snapshotted.

  • Automatic publishing is live for Shopify today.
  • SEO title, meta description, and JSON-LD are written with the article.
  • Images are converted to WebP and served from a CDN.
  • Publish writes are idempotent and snapshotted before they run.
  • Existing URLs are never changed.

Input

Approved draft

Output

Live article + stored snapshot

Sample run · publishing

Publish receipt

Shopify · live

Success
StatusPublished
Handle/blogs/news/cast-iron-care
SEO titleSet
Meta descriptionSet
Structured dataArticle
ImageWebP · 240 KB
Snapshotsnap_04_0314
Previous version stored before this write
URL unchangedIdempotent write

Interface sample · illustrative data

05 · 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.

  • A 28-day read per published page.
  • Index rate is tracked by cycle; below 70% throttles the queue.
  • Titles and descriptions are retuned for pages sitting in positions 4–30.
  • Day-14 and day-28 data are compared before any edit.
  • A drop of more than three positions triggers a rollback check.

Input

Search Console, 28 days

Output

Keep / refresh / retitle / roll back

Sample run · Search Console

Feedback

Recheck rules · day 0 → 28

GSC
Day 0Day 14Day 28
cast iron carepos 5–20Retitled
ceramic vs cast ironimp ≥ 100Refreshed
seasoning a skilletdrop > 3Rolled back
Index rate 57%28-day window

Interface sample · illustrative data

06 · Guardrails

Guardrails before growth.

The engine can stop itself. Budget gates, offline drills, monthly caches, cost ledgers, snapshots, and site isolation keep a bad cycle from becoming a bad month.

  • A budget gate runs before any paid data call.
  • Offline drills replay fixtures before a live run.
  • Responses are cached monthly so reruns do not re-bill.
  • Every run writes a cost ledger line by line.
  • Snapshots make published changes reversible; sites stay isolated.

Input

Cycle plan + budget

Output

Run receipt, or a hard stop

Sample run · guardrails

Run budget

78% of cycle budget

Within limit
Data calls78 / 100
Budget gateArmed
Offline drillPassed
Monthly cacheWarm
Cost ledgerWritten
SnapshotStored
Site isolationOn
Budget · drill · ledger · rollback
Hard stop at 100%No partial run

Interface sample · illustrative data

Platform note

Shopify today. Drafts and structured data everywhere else.

Automatic publishing is live for Shopify today. For other platforms, Rankow produces publish-ready drafts and structured data for your team to ship. We do not claim integrations that are not built.

Product tour

Open the layer your content program is missing.

Most teams start with planning or the quality gate. Tell us which decision is currently made on intuition, and we will show the layer that replaces it.

Reply within 48 hours · No slide deck