Directory page template for crawlable listings
Scale a directory of listings — places, tools, people, companies — so each entry earns a dedicated page and the hub earns the category query.
- Sanity / CMS
- Airtable
- GitHub
- Vercel
- Notion
Build a directory of 120 marketing AI tools.
- Pulled the listings120 tools from the category database
- Generated pages120 listing pages from the template
- Enriched thin pages34 pages flagged for a non-boilerplate block
- Shipped the directoryHub + 120 pages, all crawlable
The hub ranks for "marketing ai tools" and each listing ranks for the tool name. Thirty-four pages needed a non-boilerplate block — a fact or a take the hub did not have — and got one. The directory is the category asset now, not a listicle.
A directory page template scales the highest-ROI programmatic play: a hub that ranks for the category query and a dedicated page per listing that ranks for the entity. The template fixes the listing shape — what the entity is, the facts that matter, and how it relates to the category — so the directory grows without a page per entry hand-authored.
What is a directory page template?
A reusable page shape for a directory of listings, where the hub targets the category query and each listing page targets the entity query. The template fixes the shape so the directory scales with the listings, not with the writing.
Build the directory
- Hub that targets the category query
- One page per listing that targets the entity
- Internal linking so the directory is crawlable
Scale without boilerplate
- Generate pages from the listings data
- Add a non-boilerplate block per page — a fact, a take, a comparison
- Hand-tune the high-traffic listings
How do directory pages differ from listicles?
A listicle is one page that ranks a set of items; a directory is a hub plus a page per item. The directory wins the entity queries the listicle cannot — "X company", "Y place" — because each listing has its own URL and its own depth.
What makes a crawlable directory?
A hub that links to every listing, listings that link back to the hub and to adjacent listings, and consistent URL shapes. Internal linking is what makes the directory crawlable; the schema makes it machine-readable.
What content does a listings directory need per page?
The entity name, the facts that matter for the category, a description that is not boilerplate, and a FAQ. Boilerplate is the trap — the page has to add something the listing alone does not, or it adds nothing the hub does not already have.
How the directory page template fits your stack
The agent reads your listings from a sheet, database, or API, generates a page per listing using the template, and flags thin pages for enrichment. It pairs with the integration and persona page patterns and the schema markup draft template.
- Sanity / CMS
- Airtable
- GitHub
- Vercel
- Notion
Who uses this directory page template
- SEO teams
- Win the entity queries a listicle cannot.
- Content leads
- Scale a directory without boilerplate.
- Founders
- Build the category asset competitors have to catch.
How to run this directory page template in Metaflow
List the listings
From a sheet, database, or API.
Generate the pages
Agent fills the template per listing.
Enrich the thin pages
Add a non-boilerplate block per page.
Ship and verify
Export to CMS and confirm the directory is crawlable.
What you provide
- Listings data
- Category structure
- Per-listing facts
What you get back
- Hub page
- One page per listing
- Internal link map
- ItemList schema on the hub
Why use this directory page template?
Wins the entity queries a listicle cannot
Scales with the listings, not the writing
Flags thin pages for enrichment instead of shipping boilerplate
Pairs with the schema template for machine-readable markup
Directory page template FAQs
What is a directory page?
A hub that ranks for the category query plus a page per listing that ranks for the entity. The directory wins the entity queries a listicle cannot, because each listing has its own URL and its own depth.
How do you scale a directory without boilerplate?
Fix the page shape once, generate from the listings data, and add a non-boilerplate block per page — a fact, a take, a comparison. The template makes the long tail cheap; the enrichment makes it rank.
What is the difference between a directory and a listicle?
A listicle is one page that ranks a set of items; a directory is a hub plus a page per item. The directory wins the entity queries the listicle cannot, because each listing has its own URL.
Does a directory need internal linking?
Yes — the hub links to every listing, listings link back and to adjacent listings. Internal linking is what makes the directory crawlable; without it, the hub and the listings are separate pages instead of a directory.
Similar programmatic SEO templates
Key takeaways
- A directory wins entity queries a listicle cannot
- Scale with the listings, not the writing
- Add a non-boilerplate block per page or it adds nothing