Astro, Vercel, Markdown: A Substack Alternative for SEO Control

This review examines a custom Astro, Vercel, and Markdown stack designed to replace Substack for newsletter publishing. We analyze its technical features, including SEO control and custom rendering, based on the founder's detailed account.

TL;DR

Best for: Developers and content creators who require granular SEO control, custom UI, and a git-based workflow for their newsletter and blog content. This stack is ideal for those already comfortable with modern web development tools like Astro and Vercel. Skip if: You prioritize a fully managed, low-code content platform, lack web development expertise, or need integrated email sending capabilities out-of-the-box. The technical overhead is significant compared to platforms like Substack. Bottom line: The custom Astro, Vercel, and Markdown stack offers superior control over content delivery and presentation, making it a strong choice for technical teams prioritizing SEO and bespoke user experiences over platform simplicity.

METHODOLOGY

This is a v0 review of the custom newsletter stack implemented by the team behind getbeton.ai. Our analysis draws exclusively on the founder's published claims and technical details in their dev.to blog post, "How we run our newsletter on our own Astro stack instead of Substack," accessed on 2026-05-22. This review covers the architectural choices, specific technical features implemented for SEO and UI, and the stated motivations for moving away from Substack. What is not covered in this v0 review includes independent performance benchmarks, long-term workflow efficiency, the actual email sending mechanism, or edge cases related to content management and scaling. Independent benchmarks and a deeper dive into the full content-to-inbox pipeline are pending. Update cadence: This review will be re-tested when claims diverge from observed behavior or when significant new technical details are published.

WHAT IT DOES

The custom stack developed by the getbeton.ai team replaces a traditional newsletter platform with a self-hosted, git-managed content system. It leverages Astro for static site generation, Vercel for deployment, and plain Markdown files for content storage. The primary motivation for this shift was to regain SEO control.

Git-driven lastmod

Unlike platforms that report build time as the lastmod date in sitemaps, this custom setup extracts the true last modification date from the file's git history. This ensures Google receives accurate signals about content freshness, preventing the misleading impression that every page changes with every deployment. This is a critical detail for indexation accuracy.

Raw markdown twins

Each blog post published on getbeton.ai/blog/<slug> also has a corresponding raw markdown file available at getbeton.ai/blog/<slug>.md. This feature allows LLMs or automated scripts to access the clean source content directly, bypassing HTML scraping. This forward-thinking design anticipates future content consumption patterns by AI agents and programmatic tools.

Structured data from frontmatter

The system uses Astro's content collections to process Markdown files. Frontmatter fields for title, description, TL;DR, and FAQ are not just for display; they are compiled directly into JSON-LD structured data. This automates the generation of rich snippets for search engines, ensuring correct structured data without manual coding and improving search visibility.

Custom UI elements

Owning the renderer enables bespoke UI features. The team implemented