Click Below to Get the Code

Browse, clone, and build from real-world templates powered by Harper.
Blog
GitHub Logo

Improving SEO via Pre-Rendering

Discover how Harper’s new pre-rendering template boosts website SEO and performance. Learn how edge delivery, orchestration, and Puppeteer rendering enable lightning-fast static pages and seamless scalability for modern React applications.
Blog

Improving SEO via Pre-Rendering

Austin Akers
Head of Developer Relations
at Harper
November 4, 2025
Austin Akers
Head of Developer Relations
at Harper
November 4, 2025
Austin Akers
Head of Developer Relations
at Harper
November 4, 2025
November 4, 2025
Discover how Harper’s new pre-rendering template boosts website SEO and performance. Learn how edge delivery, orchestration, and Puppeteer rendering enable lightning-fast static pages and seamless scalability for modern React applications.
Austin Akers
Head of Developer Relations

In this conversation, Austin and Marianne discuss a pre-rendered demo built on the Harper platform, focusing on its architecture, rendering process, and the challenges faced during development. Marianne explains how the demo improves SEO by serving pre-rendered content quickly and efficiently, and they delve into the technical aspects of the system, including the use of Puppeteer for rendering and the orchestration of jobs across nodes. The conversation highlights the importance of performance optimization and addresses edge cases encountered during development.

• The demo is a static pre-rendered template aimed at improving SEO.

• Using a headless browser allows for faster content delivery.

• The system architecture includes a delivery cluster and render service.

• Performance testing showed the ability to handle 2,000 pages per minute.

• Challenges included job orchestration and ensuring atomicity in the database.

• Edge cases were addressed to prevent race conditions in job processing.

• The use of Puppeteer allows for flexible rendering options.

• The orchestrator node plays a crucial role in job management.

• Future improvements will be based on community feedback.

• The demo is currently in use with several customers, pending permission for public display.

In this conversation, Austin and Marianne discuss a pre-rendered demo built on the Harper platform, focusing on its architecture, rendering process, and the challenges faced during development. Marianne explains how the demo improves SEO by serving pre-rendered content quickly and efficiently, and they delve into the technical aspects of the system, including the use of Puppeteer for rendering and the orchestration of jobs across nodes. The conversation highlights the importance of performance optimization and addresses edge cases encountered during development.

• The demo is a static pre-rendered template aimed at improving SEO.

• Using a headless browser allows for faster content delivery.

• The system architecture includes a delivery cluster and render service.

• Performance testing showed the ability to handle 2,000 pages per minute.

• Challenges included job orchestration and ensuring atomicity in the database.

• Edge cases were addressed to prevent race conditions in job processing.

• The use of Puppeteer allows for flexible rendering options.

• The orchestrator node plays a crucial role in job management.

• Future improvements will be based on community feedback.

• The demo is currently in use with several customers, pending permission for public display.

Discover how Harper’s new pre-rendering template boosts website SEO and performance. Learn how edge delivery, orchestration, and Puppeteer rendering enable lightning-fast static pages and seamless scalability for modern React applications.

Download

White arrow pointing right
Discover how Harper’s new pre-rendering template boosts website SEO and performance. Learn how edge delivery, orchestration, and Puppeteer rendering enable lightning-fast static pages and seamless scalability for modern React applications.

Download

White arrow pointing right
Discover how Harper’s new pre-rendering template boosts website SEO and performance. Learn how edge delivery, orchestration, and Puppeteer rendering enable lightning-fast static pages and seamless scalability for modern React applications.

Download

White arrow pointing right

Explore Recent Resources

Blog
GitHub Logo

Agentic Engineering Needs an Opinion: Why Scale Starts with Architecture

AI coding works in a sandbox because the environment is trivially narrow. Real systems have history, constraints, and blast radius. Coding agents make sound decisions only when the architecture is explicit and shared. Opinion isn't a constraint on agentic engineering, it's what makes it possible at scale.
Select*
Blog
AI coding works in a sandbox because the environment is trivially narrow. Real systems have history, constraints, and blast radius. Coding agents make sound decisions only when the architecture is explicit and shared. Opinion isn't a constraint on agentic engineering, it's what makes it possible at scale.
A smiling man with a beard and salt-and-pepper hair stands outdoors with arms crossed, wearing a white button-down shirt.
Stephen Goldberg
CEO & Co-Founder
Blog

Agentic Engineering Needs an Opinion: Why Scale Starts with Architecture

AI coding works in a sandbox because the environment is trivially narrow. Real systems have history, constraints, and blast radius. Coding agents make sound decisions only when the architecture is explicit and shared. Opinion isn't a constraint on agentic engineering, it's what makes it possible at scale.
Stephen Goldberg
Jun 2026
Blog

Agentic Engineering Needs an Opinion: Why Scale Starts with Architecture

AI coding works in a sandbox because the environment is trivially narrow. Real systems have history, constraints, and blast radius. Coding agents make sound decisions only when the architecture is explicit and shared. Opinion isn't a constraint on agentic engineering, it's what makes it possible at scale.
Stephen Goldberg
Blog

Agentic Engineering Needs an Opinion: Why Scale Starts with Architecture

AI coding works in a sandbox because the environment is trivially narrow. Real systems have history, constraints, and blast radius. Coding agents make sound decisions only when the architecture is explicit and shared. Opinion isn't a constraint on agentic engineering, it's what makes it possible at scale.
Stephen Goldberg
Blog
GitHub Logo

Building a Cozy Sandbox Game on Harper

A nature-restoration game with six biomes, 150 animals, and a real food web — built with a single Harper component as the entire backend. One YAML file wires the database, API, content seeder, and static host. The same binary ships offline on itch.io.
Shell
Blog
A nature-restoration game with six biomes, 150 animals, and a real food web — built with a single Harper component as the entire backend. One YAML file wires the database, API, content seeder, and static host. The same binary ships offline on itch.io.
Person with long wavy brown hair wearing a bright pink shirt with a teal trim, smiling outdoors in soft sunlight with blurred trees in the background.
Bailey Dunning
Forward Deployed Engineer
Blog

Building a Cozy Sandbox Game on Harper

A nature-restoration game with six biomes, 150 animals, and a real food web — built with a single Harper component as the entire backend. One YAML file wires the database, API, content seeder, and static host. The same binary ships offline on itch.io.
Bailey Dunning
Jun 2026
Blog

Building a Cozy Sandbox Game on Harper

A nature-restoration game with six biomes, 150 animals, and a real food web — built with a single Harper component as the entire backend. One YAML file wires the database, API, content seeder, and static host. The same binary ships offline on itch.io.
Bailey Dunning
Blog

Building a Cozy Sandbox Game on Harper

A nature-restoration game with six biomes, 150 animals, and a real food web — built with a single Harper component as the entire backend. One YAML file wires the database, API, content seeder, and static host. The same binary ships offline on itch.io.
Bailey Dunning
Blog
GitHub Logo

Your Website was Built for Humans. AI Needs Something Cleaner.

The web spent a decade optimizing for browsers. JavaScript-heavy rendering, dynamic CMS templates, and client-side hydration made pages beautiful and machines blind. AI answer engines retrieve, parse, and cite content directly. If your best content is trapped behind a render cycle, a cleaner source wins.
A.I.
Blog
The web spent a decade optimizing for browsers. JavaScript-heavy rendering, dynamic CMS templates, and client-side hydration made pages beautiful and machines blind. AI answer engines retrieve, parse, and cite content directly. If your best content is trapped behind a render cycle, a cleaner source wins.
Person with short dark hair and moustache, wearing a colorful plaid shirt, smiling outdoors in a forested mountain landscape.
Aleks Haugom
Senior Manager of GTM
Blog

Your Website was Built for Humans. AI Needs Something Cleaner.

The web spent a decade optimizing for browsers. JavaScript-heavy rendering, dynamic CMS templates, and client-side hydration made pages beautiful and machines blind. AI answer engines retrieve, parse, and cite content directly. If your best content is trapped behind a render cycle, a cleaner source wins.
Aleks Haugom
Jun 2026
Blog

Your Website was Built for Humans. AI Needs Something Cleaner.

The web spent a decade optimizing for browsers. JavaScript-heavy rendering, dynamic CMS templates, and client-side hydration made pages beautiful and machines blind. AI answer engines retrieve, parse, and cite content directly. If your best content is trapped behind a render cycle, a cleaner source wins.
Aleks Haugom
Blog

Your Website was Built for Humans. AI Needs Something Cleaner.

The web spent a decade optimizing for browsers. JavaScript-heavy rendering, dynamic CMS templates, and client-side hydration made pages beautiful and machines blind. AI answer engines retrieve, parse, and cite content directly. If your best content is trapped behind a render cycle, a cleaner source wins.
Aleks Haugom