Generate SEO pages as code

Why generate pages as code

A one person company still needs durable pages: product pages, use-case pages, docs, FAQs, glossary definitions, alternatives, campaign landing pages, and sometimes free tools. The hard part is not only writing copy. Each page has to fit the site’s framework, metadata conventions, design system, product facts, internal links, and discovery files.

Pagewell is built for that repo-native job. It gives a coding agent the instructions and QA gates needed to make page work reviewable as code instead of exporting a one-off hosted page.

How Pagewell fits

Pagewell starts from three inputs:

1. PAGEWELL.md for product facts, claim rules, route taxonomy, site implementation details, page patterns, and QA rules.
2. DESIGN.md for the visual identity contract.
3. A page brief that defines the route, page type, primary intent, audience, CTA, and constraints.

From there, the agent selects the right playbook, writes a page architecture, implements the route in the current stack, and runs QA for metadata, schema, claims, crawlability, design consistency, and internal links.

A practical workflow

RequestHunt finds repeated market language
→ Pagewell turns validated intent into a page brief and route
→ Hal can run deeper implementation loops when the change is larger
→ Markshare can publish standalone markdown artifacts when a full site route is unnecessary

This keeps the ReScience Lab workflow tight: discover demand, turn it into useful pages, build with agent loops, and publish the right artifact.

What to generate first

Start with pages that have a real search, support, conversion, or product-discovery intent. Good first Pagewell pages include:

• a product page for a concrete tool
• a use-case page for a specific workflow
• a docs page with exact commands
• a FAQ page answering one searched question
• a glossary page for a term the audience uses
• a free tool that gives value before signup

Avoid thin variants that only swap a keyword. Pagewell should make fewer, stronger routes that are specific to the product and site.

What QA should catch

Before merging a generated page, check that it has a unique title and description, one H1, canonical URL, supported schema, factual product claims, useful internal links, and correct indexability. If the page could describe any SaaS after changing the product name, it needs another pass.