Rankow
Case studies

Four sites running the same loop.

One SaaS site, one Shopify store, two B2B manufacturers. Different catalogs and buyers — the same planning, quality gate, and post-publish decisions.

In production

What each site runs.

RankowB2B SaaS

SEO content engine — our own product site

Site
rankow.com
Stack
Next.js + Strapi
  • Topic discovery and page planning before any draft is written
  • Long-form drafts through the 3,000-word and information-gain gate
  • Publish to Strapi, then the 28-day Search Console read
KailashwayE-commerce

Shopify store for handcrafted Himalayan jewelry

Site
kailashway.com
Stack
Shopify Admin API
  • Content clusters planned around mala beads, red string, and crystal jewelry
  • Internal links resolved against real product and article handles
  • Refresh queue for posts that already rank but sit below the click threshold
FIRMFGB2B manufacturing

Precision CNC machining and rapid prototyping

Site
firmfg.com
Stack
Independent site
  • Page units planned by process, material, and buyer intent
  • Specification-led articles that carry numbers, tolerances, and sourcing detail
  • Existing pages refreshed instead of duplicated
LianyuhongB2B manufacturing

Rigid and multilayer PCB manufacturing

Site
lyhcircuits.com
Stack
Independent site
  • Technical topics ordered hub-first so cluster pages have somewhere to link
  • Comparison and specification content aimed at sourcing-stage queries
  • Post-publish read-back to decide refresh, optimize, or hold

First 90 days

The first 90 days, modeled.

A new domain does not produce a curve on day one. Indexation lands first, impressions follow around week three, position moves after the first refresh round, and clicks arrive last.

Modeled — not a customer result

12,400

Impressions / week · Day90

Day14Day30Day45Day60Day75Day9012,400

Search Console impressions

8 new articles published per month, roughly 2 per week

4 refreshes per month on pages past the 14-day gate

Search Console connected from day 0; read at 28 days

No backlinks, no paid distribution, no existing domain authority

Every site is different. These numbers describe the shape of a normal ramp on a new domain, not a promise for yours.

Measurement

A case is a record, not a claim.

Every site is read back from Search Console at 28 days. Traffic and ranking figures stay unpublished until they can be verified against a dated export.

Read at 28 days

Index status, position, impressions, and click-through per page.

Decide, don't guess

Refresh at 14 days or later; optimize pages sitting at position 5–20 with under 2% CTR; hold everything else.

Reversible

Every publish keeps a snapshot. A drop of more than 3 positions can be reversed.

What we don't publish

No traffic multipliers, no ranking guarantees, no logos of sites that cannot be linked. If a number is not in an export, it is not on this page.

Next step

Run the same loop on your site.

Start with one content section. Discovery, planning, writing, publishing, and the 28-day read come as one cycle.

7 days · 1 site · No credit card

Case studies: four sites running the same loop · Rankow