01 context
Site + product context
SITE_PROFILE.md, DESIGN.md, product facts, and the page brief tell the agent what to build, where it belongs, and what claims are allowed.
Agent skills for production SEO/GEO pages
Your content plan is ready. Your website repo should be too.
Pagewell gives coding agents the brief-to-merge workflow for shipping SEO pages, free tools, docs, landing pages, and private ABM pages as normal code—without a hosted builder.
bunx skills add ReScienceLab/pagewell --skill pagewell How Pagewell works
A repeatable path from brief to merge.
Use the same agent workflow for one landing page, a free tool, a comparison page, or an entire SEO/GEO cluster.
02 plan
Spec before code
Pagewell asks for route, sections, metadata, schema, links, CTA, and QA requirements before implementation starts.
03 build
Normal website code
The agent edits your Astro, Next.js, Worker, or static site instead of creating a hosted page you have to recreate later.
04 review
SEO/GEO QA
Titles, schema, claims, citations, crawlability, internal links, and discovery files are checked before merge.
What ships
Not mockups. Mergeable page work.
Each Pagewell run turns intent into a route, page structure, copy, metadata, schema, links, QA notes, and discovery updates your team can inspect like any other code change.
| Page type | Output |
|---|---|
| landing page | route, copy, metadata, schema, CTA |
| comparison page | fair positioning, proof, claim QA |
| free tool | working utility UI, SEO shell, WebApplication schema |
| docs/FAQ/glossary | answer-first content, schema, internal links |
| private ABM | noindex page, account brief, shareable route |
Generated page
Landing pages
Campaign pages that match the visitor’s intent and ship with one clear CTA.
Generated page
Comparison pages
Alternatives and vs pages that position honestly and keep claims tied to sources.
Generated page
Docs and tutorials
Task-focused routes with setup steps, examples, and stack-specific guidance.
Generated page
FAQ and glossary
Short, crawlable answers and definitions built for search engines and AI answer surfaces.
Generated page
Free tools
No-signup utilities where the tool does real work before the product CTA appears.
Generated page
Private ABM
Personalized sales pages that stay out of search while following the same design and QA standards.
Bring your own site
Astro here. Your framework in your repo.
Pagewell does not assume a CMS, builder, or frontend stack. Agents read SITE_PROFILE.md, choose the closest adapter, and work inside the conventions that already exist.
adapters/astro.md
adapters/nextjs.md
adapters/cloudflare-worker.md
adapters/static-html.md
adapters/unknown-framework.md
output: routes, components, content, metadata
no runtime, hosted builder, or lock-inDESIGN.md
colors: #000000 #ffffff #0099ff #a6a6a6
typography: Geist + Inter + Geist Mono
components: pill CTAs, dark cards, blue rings
SITE_PROFILE.md
routes, layouts, components, content, metadataBrand guardrails
Put the brand rules where agents can follow them.
DESIGN.md gives agents the visual contract for typography, colors, components, spacing, and interaction states, so generated pages feel like the same site—not a one-off AI export.
Built-in review loop
Fast pages still need gates.
Pagewell makes the boring launch checks explicit before a generated route becomes part of your SEO/GEO system.
QA gate
Search intent
Every page starts with route, primary query or use case, audience, and CTA before code.
QA gate
Schema + metadata
Titles, descriptions, canonicals, Open Graph, and supported JSON-LD are part of the spec.
QA gate
Claim control
Agents only use facts from product docs, briefs, or user-provided proof—not invented stats.
QA gate
Discovery
Internal links, sitemap, robots, and future discovery files stay aligned with generated routes.
FAQ
Short answers for builders.
What is Pagewell?
Pagewell is a framework-agnostic skill pack for coding agents. It turns a brief, product facts, SITE_PROFILE.md, and DESIGN.md into normal website code plus SEO/GEO QA.
Who is Pagewell for?
Pagewell is for developers, founders, and growth teams that want AI-assisted page creation without moving their site into a no-code builder or breaking brand and stack conventions.
How is Pagewell different from an AI landing page builder?
Builders host the page and own the editing surface. Pagewell runs inside your repo, follows your framework, and outputs routes, components, content, schema, and discovery updates you can review and merge.
What can Pagewell generate?
Pagewell supports landing pages, product and use-case pages, alternatives, docs, FAQ and glossary pages, free tools, and private ABM pages.
What files do Pagewell agents need?
Agents need DESIGN.md for visual rules, SITE_PROFILE.md for stack conventions, product facts for truth, and a page brief for audience, intent, route, and CTA.
How does SEO/GEO QA work?
Pagewell prompts agents to check title and description, schema, factual claims, internal links, crawlability, answer-readiness, and sitemap/discovery updates before a page ships.
Install the workflow
Give your agent a page system before the next request.
Start with one homepage, use-case page, comparison, or free tool. Pagewell keeps the brief, design rules, stack conventions, QA gates, and discovery updates in the same repo as the code.
bunx skills add ReScienceLab/pagewell --skill pagewell Installs the Pagewell agent skill via skills.sh.