Directory-in-a-Vertical
Ship a niche aggregator site with programmatic SEO pages, bilingual content, and a supplier inbox, from a standing start, in one to four weeks.
How it works
The core idea is crossing a taxonomy (product categories, service types, or supplier classifications) with a geography dimension (states, cities, or regions) to produce hundreds of indexable pages from a single data model. Each page is a legitimate, unique destination. Buyers searching for "timber suppliers in Selangor" or "hardware wholesalers in Penang" land on a page that was built for that query, not a generic search results page.
Content is generated in both English and Bahasa Malaysia from the start. Bilingual structure is not a bolt-on. It is in the data model, the URL schema, and the Astro component templates before a single page renders. This matters for Malaysian buyers and for Google's regional signals.
Supplier intake happens through AgentMail, an agent-managed inbox that parses incoming supplier requests, validates them against the taxonomy, and routes them into the directory without manual work. The RFQ flow (buyer contacts supplier through the directory) also runs through AgentMail so neither party needs to share personal contact details publicly.
The entire site deploys to Cloudflare Workers Static Assets on every build. No Vercel bill, no Node.js server to maintain. Static files served from the edge with sub-50ms TTFB globally.
What you get
- ✓Astro site codebase with pSEO page templates (category index, category × state, supplier profile)
- ✓Taxonomy data model: category tree, state and city list, supplier schema
- ✓Bilingual EN and MS content in Astro content collections
- ✓AgentMail RFQ inbox configuration and email routing rules
- ✓Cloudflare Workers Static Assets deployment configuration with wrangler.toml
- ✓sitemap.xml and robots.txt generated on build
- ✓Schema.org LocalBusiness markup on supplier profile pages
- ✓Supplier self-submission intake form (optional, Production tier and above)
- ✓Admin dashboard for reviewing and approving supplier submissions (Agentic OS tier)
- ✓Monthly pSEO expansion: 50 new category × geography pages per month (Agentic OS retainer)
Three tiers
Core site with up to 200 pSEO pages, one category dimension, seeded supplier data, Cloudflare deploy. Good for validating demand before committing to a fuller build.
Full taxonomy, multiple category dimensions, supplier self-submission, AgentMail RFQ, bilingual EN and MS. Ongoing retainer covers monthly pSEO expansion and supplier intake management.
Everything in Production, plus automated supplier onboarding, admin approval dashboard, AI-assisted content refresh, and monthly analytics reporting. Built to run with minimal manual intervention.
ttkbuildingmaterials.com
A Malaysia building materials directory built using this exact pattern. 530 pages indexed on first deploy. 41 suppliers seeded across 22 product categories and 13 states. Bilingual EN and MS throughout. Hosted on Cloudflare Workers Static Assets. Shipped from first commit to live production in under 4 hours.
ttkbuildingmaterials.com →What happens each week
Define the category tree, geography dimensions, supplier schema, and URL structure. Agree on bilingual content priorities and AgentMail routing rules. Deliver a written scope document for sign-off.
Build the Astro site with all page templates. Seed initial supplier data. Configure Cloudflare Workers Static Assets deploy. First live preview shared.
Generate the full category x geography page matrix. Add bilingual content throughout. Configure sitemap.xml, robots.txt, and Schema.org markup.
Configure AgentMail RFQ inbox. Build supplier self-submission form. Set up admin approval workflow. Launch to production domain.
Any issues found during the shake-out period are fixed as part of the engagement. No extra charges.
Blueprint A questions
Minimum viable is around 20 to 30 suppliers across at least 5 categories. The pSEO pages index on day one regardless of supplier count. The supplier density fills in over time via the AgentMail intake flow.
Yes. The Production and Agentic OS tiers include a featured-listing flag in the supplier schema. The display treatment (highlighted card, first position) is configurable.
The pattern is industry-agnostic. The taxonomy, page templates, and AgentMail routing all take a configuration file as input. I have applied it to materials, services, and professional directories.
Positively, in Malaysia. Google indexes both language variants as separate URLs. Each language version targets a distinct search query set. You effectively double the indexable surface from a single data set.
Nothing. The account is yours. Workers Static Assets has a generous free tier. You keep everything. The retainer covers ongoing pSEO expansion and supplier management, not hosting.