Build Log · June 29, 2026

ForgeKit Guides: The SEO Shelf

Built a 16-guide SEO content shelf from scratch — full Forge funnel cluster, structured data, sitemap, and three hardening passes before deploy.

Timeline

Start
Ideation + strategy
Anvil check on three distinct SEO plays — landed on Forge funnel as the money wedge
Pass 1
Guides shelf built
lib/guides.ts, /guides index, /guides/[slug] template, GuideCTA, sitemap, robots, nav/footer
Pass 2
Hardening pass 1
OG image verified, JSON-LD fixed to Article+FAQPage @graph, unsourced stats removed, SMS compliance added
Pass 3
Forge cluster + split
lib/guides.ts split into per-product files, 10 new Forge funnel guides added, markdown-link renderer added
Pass 4
Content trust QA
10 claim goblins caught and softened — policy precision, behavioral guarantees, implied stats removed

What shipped

lib/guides/ — split into types.ts, productMeta.ts, forge.ts, hearth.ts, leashline.ts, known.ts, index.ts
/guides index page — card grid with product color-coding and type badges
/guides/[slug] dynamic template — sections, templates, checklists, FAQs, JSON-LD, breadcrumb, canonical URL
GuideCTA component — product-specific CTA block, reusable across all guides
app/sitemap.ts — Next.js native sitemap, auto-extends as guides are added
app/robots.ts — robots.txt pointing to sitemap
Nav + Footer updated with Guides link
JSON-LD: Article + FAQPage @graph (not FAQPage-or-Article toggle)
Inline markdown link renderer — [text](url) in body, bullets, and numbered lists
16 guide pages total, all SSG prerendered — 13 Forge, 1 Hearth, 1 Leashline, 1 Known
Forge funnel cluster: missed call → estimate follow-up → job confirmation → review request → tracking → follow-up calendar