Blog Templates That Rank on Google
Posts as text files, pages as plain HTML, Article schema and llms.txt written for you, and a CI gate that refuses to ship below Lighthouse 100. The dedicated blog template is a free update to owners; the blog itself is in the box today, and in the free Starter.
Written for Readers, Built for Crawlers
A blog has two audiences and most templates serve neither well. Readers get a page that paints late because a web font and a framework bundle load first. Crawlers get HTML that only exists after JavaScript runs, thin metadata, and no structured data at all.
Amrify renders every post to HTML at build time. The reader gets text on screen in the first paint. Google, and now ChatGPT and the other answer engines, get Article schema, a sitemap, an RSS feed and an llms.txt file describing the site, all generated from the same frontmatter you already wrote.
Text In, HTML Out
No hydration step and no client bundle. A 3,000-word post is a single HTML file plus its images, served from a global network.
Article Schema From Frontmatter
Title, description, dates, author and Open Graph image become JSON-LD and meta tags automatically. Nothing to fill in twice.
Typed Posts
Zod schemas validate every post's frontmatter during the build. Forget the publish date and the build tells you, not your readers.
Tags, Categories, Authors
Archive pages for each tag and category, plus author pages for multi-writer blogs where E-E-A-T matters.
RSS and llms.txt
A feed for readers who subscribe and an llms.txt for AI crawlers that summarize, both regenerated on each build.
Reading Time on Every Post
Computed at build from the word count and shown on the post, so a reader knows whether it is a two-minute or a twenty-minute read.
What Your Blog Site Costs
No subscription and no per-site fee for a blog company, or for the ten client sites after it.
Amrify Pro
Dedicated blog template comes later as a free update; the blog system itself ships at launch
- Article, FAQPage and BreadcrumbList schema, sitemap, RSS and llms.txt generated on build
- Tags, categories, author pages, reading time and per-post Open Graph images
- CLAUDE.md, AGENTS.md and four Claude Code skills for drafting and publishing with an agent
- Run as many blogs as you like on one license, one seat per purchase
- Free updates for life, including every niche template that follows
Yours for Good
Buy once, build for yourself or clients. A blog site is one of them.
Leave It Alone
Plain HTML needs no weekly updates. Your blog site stays that way.
Lifetime Updates Included
New features land in the same repo, free. The blog template arrives as a free update.
Reserve the Founding Price
Your blog site starts with a spot on the founding list. The first 5,000 members receive the ten launch trade templates, with the blog template arriving as a free update for $249 instead of $399 the day checkout opens.
- Email: amrifyllc@gmail.com
Contact Form
Keep the $150 Discount
You will hear back by email within one business day.
Two things help: the blog this site is for and what you want it to do. Anything else is optional.
See the founding offer or the docs whenever you like.
A blog template earns its keep on the days you are not thinking about it: the morning a post goes viral on a phone network you have never heard of, the week Google re-crawls your archive, the afternoon an answer engine decides whether to cite you. Amrify’s blog is built for those days first and for the writing experience second, and that order is deliberate.
Be clear about what is on offer. A blog-specific template, with its own homepage layout and design choices for publishers, is not among the ten launch templates; it ships to owners as a free update. The blog system underneath, the one every Amrify site already uses, is ready now. So is the free Starter, which for a single-author blog may be all you need.
What a Crawler Sees on a Post
Google’s Core Web Vitals measure the reader’s experience: how quickly the main content paints, how fast the page responds to a tap, whether anything jumps around while loading. A blog running on a JavaScript framework pays for the framework on every post, even the ones that are nothing but text. The bundle downloads, parses and hydrates before the page is truly interactive, and Interaction to Next Paint records the wait.
Amrify posts do none of that. A post compiles to one HTML file. There is no bundle because there is no framework to ship; the free Starter has no JavaScript framework at all, and Amrify Pro loads a SolidJS island only where a widget needs one. The main content is in the first bytes the browser receives.
Crawl budget follows. Google crawls a limited number of pages per visit, and it crawls faster sites more deeply. For a blog that publishes weekly, a fast archive means new posts are found and indexed sooner, and old posts get re-evaluated more often when you update them.
The newer audience is the answer engine. ChatGPT, Perplexity and Google’s AI answers read structured data and, increasingly, an llms.txt file at the root of a site. Amrify generates both from your frontmatter. If you want to see what one looks like for your current blog, the free llms.txt generator and schema generator produce them in a browser with no account.
What Publishing Looks Like Day to Day
A post is a text file with a frontmatter block: title, description, date, tags, an author, an optional cover image. Write it in whatever editor you like, save it, and the build does the rest.
The Zod schema checks every field. A missing date or a malformed tag fails the build with a message pointing at the file, which is a better place to catch it than a live page with an empty byline. Tags and categories become archive pages on the next build without any configuration. Author pages carry a bio and a list of that writer’s posts, which is what Google’s E-E-A-T guidance is looking for on a multi-writer site.
Every post gets its own Open Graph image generated at build, an Article JSON-LD block, a canonical URL, a place in the sitemap and an entry in the RSS feed. Reading time is computed from the word count and displayed on the post.
Images are the part that usually breaks a fast blog, and Astro’s image pipeline handles them: you reference the original file, and the build writes resized WebP or AVIF variants with a responsive srcset. A photo-heavy post stays under the Lighthouse 100 gate without you touching an image editor.
Starter or Pro for a Blog
For a single blog with one or two writers, the free Amrify Starter covers it: home, blog with tags, about, contact, RSS, sitemap, llms.txt, JSON-LD, generated OG images, and the same Lighthouse 100 CI gate as Pro. Personal or commercial, one blog or twenty, the Starter license costs nothing; the only thing it forbids is reselling it as a template. Its public repo opens at launch.
Amrify Pro is the right purchase if the blog is part of a bigger operation. It adds categories and author pages, the serverless lead engine for a newsletter or sponsorship form that lands in your inbox and on your phone, the sticky call bar and other conversion widgets, the ten trade templates, and a monorepo that runs several blogs from one codebase with shared components. You pay once: $249 if you are among the first 5,000 founding members, $399 afterward, and that covers every blog you run plus updates for life. Because checkout has not opened, the founding price is held by a free account. Delivery is private GitHub repo access for one seat.
Run any of the live showcase sites through the free website grader before deciding. It is Google’s own Lighthouse test and takes about thirty seconds.
Frequently Asked Questions
Can I migrate my existing blog?
Yes. Posts are text files with a frontmatter block, so anything already in that shape (Hugo, Jekyll, Eleventy, Gatsby) copies straight into the collection with the field names adjusted. From WordPress, export to plain text first. The schema validates every post at build time, so a missing date or title fails on your machine rather than going live broken.
Does the blog template support categories and tags?
Yes. Set them in a post’s frontmatter and the build generates the archive pages. The free Starter ships tags; the Pro blog adds categories and author pages on top.
How does the blog handle images?
Astro’s image pipeline resizes each image at build time, converts it to WebP or AVIF, and writes the responsive srcset. You reference the original file; the build does the rest.
Can I monetize my blog?
Yes. The pages are plain HTML, so any ad network or affiliate link works the way it does on any site. With no framework to hydrate, an ad script is usually the only JavaScript on the page.
Coming from WordPress? The WordPress comparison covers the redirect map that keeps your rankings through the move. Evaluating a React framework instead? Read Amrify vs Next.js.
Hold a founding spot above, or ask a question about your archive before you migrate it. Monetizing through product recommendations is covered on the affiliate marketing page; selling what you teach is on the course creator page.
Start a Blog That Actually Ranks
Pay $249 once at the founding price, then publish on a blog whose every build has to pass Lighthouse 100 in CI. The launch set is ten trade templates; a blog-specific layout follows as a free update. Prefer to start at zero? The free Starter already includes the blog.