Case study
cryptolicense.pro — Crypto Licensing Niche Site, Built on Our Own Playbook
Public reference: cryptolicense.pro ↗
Summary
cryptolicense.pro is the agency's own narrow-vertical site for crypto-licensing advisory. We built it as the proof point for the GS Playbook v4.3 — the same templates, schema, llms.txt and AEO patterns we ship in every Foundation engagement, run on our own brand first, in public, with the dashboard open to prospects.
Headline
0 → 47 indexed pages in 8 weeks; core cluster positions 50–63 → 14–22
Industry
Crypto Licensing
Engagement
Foundation
The challenge
We needed an English-language landing for the crypto-licensing service line that could compete against ten-year-old incumbents (manimama.eu, gofaizen-sherle.com) without buying links and without a five-figure content budget. The constraint was that everything had to be defensible inside the Foundation $5,900 envelope — if we couldn't ship it for ourselves under that scope, we had no business selling it at that price.
How we approached it
- Locked the keyword cluster: 'crypto license <jurisdiction>' for 14 jurisdictions (EU MiCA, UAE VARA, Singapore MAS, Hong Kong SFC, Estonia, Lithuania, Poland, Czech Republic, Switzerland, El Salvador, BVI, Cayman, Seychelles, Vanuatu)
- Shipped 14 jurisdiction templates following GS Playbook v4.3 — H2 as question, ≤30-word direct answer, Quick Facts table, FAQ block, X-is-Y intro
- Wired Organization + Service + Article + FAQ + sameAs JSON-LD, plus llms.txt and a robots.txt that explicitly allows GPTBot, ClaudeBot, PerplexityBot, Google-Extended
- Set up Supabase + Looker Studio dashboard wired to GSC + GA4, segmented by jurisdiction page so we could see indexation curve per template
- Submitted to IndexNow on every publish; published author profile with real LinkedIn for E-E-A-T
Timeline
- 1
Cluster lock + audit
Week 1
- Keyword cluster lock (14 jurisdictions × intent groups)
- Competitor audit: manimama, gofaizen-sherle, sumsub blog
- Schema + AI-crawler baseline written
- 2
Template build
Weeks 2–3
- Jurisdiction template (Astro component)
- Schema components: Organization, Service, FAQ, Article
- llms.txt + robots.txt for AI crawlers
- 3
Content roll-out
Weeks 4–5
- 14 jurisdiction pages drafted, edited, schema-validated
- Author profile + LinkedIn sameAs
- Internal-link graph wired
- 4
Indexation + dashboard
Week 6
- GSC + GA4 + Supabase + Looker Studio dashboard live
- IndexNow submissions on every publish
- Day-90 re-audit scheduled
Outcomes
- 0 → 47 indexed pages in 8 weeks (14 jurisdiction templates + supporting category, FAQ and author pages)
- Core 'crypto license' cluster average position lifted from 50–63 baseline to 14–22 within 90 days
- First Perplexity citations on 3 jurisdiction queries within 12 weeks of publish
- Foundation playbook validated end-to-end inside the $5,900 fee envelope — every template, schema, dashboard reproduced for paying clients without modification
"We ran the Foundation playbook on our own brand before we sold a single engagement. cryptolicense.pro is the proof — same templates, same schema, same dashboard, same fee envelope."
cryptolicense.pro is the case we point prospects to when they ask whether the playbook works. It is our own brand, our own fee envelope, our own dashboard — public, indexed, citable. If the templates, schema and AI-crawler config did not move the needle on a brand-new domain with no backlink history, we would not be selling them.
The full template, including the Astro components and the schema JSON-LD, is reproducible. We ship a copy as part of every Foundation engagement.
What we learned
- Schema-first publishing matters more than word count. The 1.4k-word jurisdiction pages outranked 3k-word competitors because the schema and Quick Facts were extractable.
- Author E-E-A-T moves the needle on AI citations specifically. Once Dmytro's LinkedIn profile was wired into sameAs, Perplexity started citing his name alongside the page.
- Day-30 indexation curve lies. Three jurisdiction pages stayed at position 70+ for six weeks, then jumped to top-15 in week 9 — patience inside the 90-day window is the rule, not the exception.
Want fuller details under MNDA?
On request we share extended versions of NDA cases with named clients, architecture diagrams and full delivery numbers, under a mutual non-disclosure.