skip to content

← work — the registryBLT-03built & shipped

SEOflare

SEO app for the ShopWired platform — through review, onto the store

Audit, generate, gate, deploy: an SEO app for a hosted ecommerce platform whose first production-scale install turned a firewall into the architecture.

sector
storefront SEO SaaS · live on the ShopWired app store
period
2026 · live
role
built and shipped — builder credit

seoflare.app

readouts — measured, sourced

04 on the record · every one names its source

readout

1,647 / 1,752

pages lost to a CDN firewall in thirty seconds — the incident


read from — crawl evidence rows

readout

1,752 / 1,752

evidence rows on the paced crawl, zero 403s


read from — crawl evidence rows

readout

13.6 min

full crawl, from a 31.9-minute baseline


read from — run timings

readout

~450

tests across eight packages


read from — repository

the file — read in order

01

the problem

  • The first big store: 1,752 resources. The guided run ticked fast, then hung. A first HTTP/2 crawl lost 1,647 of its 1,752 pages to the platform's CDN firewall in about thirty seconds. The two-minute crawl time was a wall.

02

the engineering

  • A pacer that spaces request starts globally, trips a circuit breaker into cooldown at permanently half rate on 403 or 429, and defers blocked pages for one retry pass instead of finalising them — tested end to end through an injected virtual clock. Raw HTML stripped after the evidence insert (700 MB → about 400 MB peak), embeddings chunked, a heartbeat every 25 pages, a reaper for silent runs.

  • Generated metadata passes two gates or doesn't ship: deterministic validators first (SERP pixel width with real font metrics, keyword position, sibling distinctiveness via vector search), then claim-grounding. Deployment is a ten-step pipeline with per-row real-HTTP write verification and a post-deploy storefront re-crawl as live proof.

03

the proof

  • The paced full crawl: 1,752 of 1,752 evidence rows, zero 403s, zero restarts, 13.6 minutes against a 31.9-minute baseline. First full audit on that store: 12,790 open findings, counted once.

  • Around 450 tests across eight packages. Live on the platform's app store.

provenance

surfaces touched
crawler and pacer · audit engine · metadata gates · deploy pipeline · app-store install flow
numbers read from
crawl evidence rows · run timings · repository
stack
Turborepo · Fastify · BullMQ · Supabase + pgvector · Redis · OAuth2 install flow
tags
saas · crawling · vector search · deploy pipeline

builder credit — engineered and shipped; ownership sits with the product. every readout above is measured from the repository or the platform that runs it.

the registry

the same hands

The person who diagnosed this file is the person who ships the fix. Two plain sentences beat a brief.