建站实录：.si 域名从注册到上线的 24 小时
fusi.si's actual build timeline — not a tutorial but a timestamped log of real steps and pitfalls.
Phase 1: domain & direction
Register the domain, confirm via WHOIS, then lock the site direction. We pivoted from a for-sale page to an AI review content site — the pivot reshaped the whole structure.
Phase 2: build & deploy
- 首页 + 目录 + 内容页 + 合规页
- 命令行一键推，拿到 pages.dev 预览地址
- 注册商改 NS，Pages 挂自定义域名
Phase 3: SEO & content
Inject Open Graph / JSON-LD / hreflang in bulk, generate sitemap & robots, add the EU-mandated cookie consent, then keep publishing content.
Phase 4: troubleshoot
Two typical post-launch issues: the domain still showing the old page (DNS cache) and search engines needing an explicit submit. Solved by forcing authoritative IPs and submitting the sitemap.
Reusable lessons
- 顺序不能反，绑定依赖 NS 生效
- 配置 / 解析 / 缓存，定位对症下药
- SEO 与合规是门票，原创内容才是过审关键
The timeline
- Step 1：注册域名，等 WHOIS 落地确认注册成功（原本显示「注册中」）。
- Step 2：确定方向（此处从「出售页」改为「评测内容站」），搭好首页/目录/内容页/合规页。
- Step 3：部署到 Pages 拿到预览地址，再把域名 NS 改到 Cloudflare，绑定自定义域名。
- Step 4：批量注入 SEO、生成 sitemap/robots、配 Cookie 同意与隐私政策。
- Step 5：持续扩充内容并排查上线后问题（DNS 缓存、搜索引擎收录）。
Wrong turns
- Set direction first：中途从出售页改评测站，等于重做结构，一开始就该想清楚。
- Binding order：区域 pending 时绑自定义域名导致记录没写全，后来删掉重加才解决。
- Cache illusion：以为上线了，其实是本地 DNS 缓存，浪费了排查时间。
What I'd do differently
- Content before chrome：确认有 10+ 篇内容再设计站点结构。
- Wait for active：等区域 active 再加自定义域名。
- Use a generator：内容多时模板化生成，保证一致且省时。
Cost & time
The only cost was the domain; hosting was free. Roughly an hour from registration to a live site, excluding content creation. For a content site, the real cost is time, not money.
Real case: the key trade-off behind this log
The pivotal decision: starting as a domain for-sale page, then pivoting to an AI tool review content site. It meant rebuilding the structure — but it is what gave the site a sustainable content engine instead of a one-off sale.
- If redone：先写满 10+ 篇内容再设计站点结构，能省掉一次大改。
- Time ledger：域名到上线约 1 小时，SEO 与合规基建约 1 小时，之后每天的边际成本就是写内容本身。