CreatorDB · The Rebuild
A ground-up rebuild of creatordb.app — static HTML on the Cloudflare edge, AI-generated creator profiles, market-targeted SEO money pages, and a measurement layer that actually moves the needle.
Why we rebuilt · the core motivation
This wasn't a cosmetic refresh. More and more buyers now ask ChatGPT, Claude, Perplexity, or Gemini questions like "best creator analytics platform" or "Asia influencer marketing agency" — and the AI gives them a shortlist. When we tested those exact prompts, our old site never came up. The reason: AI tools only read pages they can understand instantly, and our WordPress site needed heavy scripts to even show its text — so the AIs saw a blank page. The rebuild fixes that. Every page is now fully readable the moment it loads.
<h1>, <h2>, alt text, schema.org JSON-LDGoogle Lighthouse + Core Web Vitals · mobile
Measured on a live niche page. For context, most SaaS marketing sites score 35-65 on performance and 80 on SEO — we're well above that on every metric Google measures.
Public profile pages · honest before vs after
Honest Claude-graded indexability score on each side. Caveat: no one can guarantee Google indexes any page — these scores reflect what's controllable about the page itself, not Google's domain-trust signals.
| Crawlable HTML (no JS dep) | ✗ Headings JS-rendered |
| Semantic structure | ✗ Divi div-soup |
| Schema.org coverage | ✗ Yoast generic only |
| Unique content per page | ✗ Same template everywhere · no bio · no FAQ · no news |
| URL structure | ~ Plugin paths, IDs |
| LCP / CLS / TBT | ✗ ~5s / ~0.2 / heavy |
| Canonical / hreflang | ~ Yoast canonical only |
| Internal-link graph | ~ Menu only |
| Mobile-first responsive | ~ Divi mobile, heavy |
| Alt text on all images | ✗ Inconsistent |
| Third-party trackers | ✗ 12+ blocking scripts |
| LLM-citation friendliness | ✗ 0/3 prompts cited |
| Crawlable HTML (no JS dep) | ✓ 100% static |
| Semantic structure | ✓ Real h1/h2/h3 + landmarks |
| Schema.org coverage | ✓ 6 types per page |
| Unique content per page | ✓ Per-creator bio + FAQs + news + sponsors |
| URL structure | ✓ /creatorstats/<slug>/ |
| LCP / CLS / TBT | ✓ 2.6s / 0 / 0ms |
| Canonical / hreflang | ✓ Canonical + hreflang where bilingual |
| Internal-link graph | ✓ Niche + country + similar-creator |
| Mobile-first responsive | ✓ Lighthouse 92/92 |
| Alt text on all images | ✓ Descriptive on every img |
| Third-party trackers | ✓ Zero blocking scripts |
| LLM-citation friendliness | ✓ Static HTML + llms.txt + JSON-LD Person |
Cutover without loss
A rebuild can quietly destroy years of SEO if URLs change or if a paywall blocks search engines. We avoided both.
All 14 market and vertical landing pages live at the exact same URLs as before. Google sees no broken links, no redirects, no ranking reset. The pages look modern, but the addresses didn't move.
/taiwan-influencer-marketing/
/japan-influencer-marketing/
/thailand-…/
/singapore-…/
/dubai-…/
/london-…/
/new-york-…/
/b2b-…/
+ 6 more
The 5-view paywall only kicks in for human visitors. Google, Bing, ChatGPT, Claude, and Perplexity get a free pass — they index the full content, so the paywall protects revenue without costing us SEO or AI visibility.
Cost per page · all Claude models
Real per-page math: ~10.5K input tokens (data sheet, web context, prompts) + ~7.5K output tokens (bio, FAQs, news, sponsors, niche framing). Plus 2 web search calls per page where supported.
Numbers assume no prompt caching. Caching cuts input cost ~10× on repeat calls — meaningful at scale. Web search billed at $10 / 1K queries (Sonnet & Opus only).
Realistic rollout · slow and observed
A couple hundred indexed pages would be a huge win on its own. The plan is to not add anything new for a while, measure what we have, and only scale once we have evidence Google is actually indexing and ranking the work.
Submit sitemap to Google Search Console + Bing Webmaster. Then do nothing for 30-45 days — first-batch indexing takes time on a fresh domain footprint.
Add only high-intent creators we have data for. Submit a few dozen URLs per week. Trigger only if >40% of the original 275 are indexed and at least a handful are surfacing on long-tail queries.
Only if there's evidence the existing 400-ish pages are bringing organic traffic. Anything bigger than 1,000-1,500 total is a separate conversation — we're not chasing volume.
Why so conservative. Programmatic SEO at our domain age is unproven — Google may decide it doesn't want most of these in the index regardless of quality. Better to learn that lesson with 275 pages than 10,000. A couple hundred well-indexed pages outranks a thousand un-indexed ones, every time.
Before we go live
Open question: who owns the final read for each side?
Open question: do we run a 1-2 day security pass before the cutover?