Bolt.new blog: three ways to add one, and which one ranks
Bolt.new blog options compared: prompt Bolt to build one, wire a headless CMS, or run Superblog at yoursite.com/blog with your Bolt site unchanged.
There are three ways to add a Bolt.new blog: prompt Bolt to build blog pages, run Superblog at yoursite.com/blog, or wire a headless CMS through prompts. Bolt has no native CMS, so building it yourself leaves the blog front end, schemas and sitemaps to you. Superblog ships all of it, and your Bolt site stays unchanged.
Three ways to add a blog to a Bolt.new site
All three put a blog on your Bolt.new site. They differ in who publishes, what you maintain, and whether a post needs an update to your Bolt project.
Option 1: Prompt Bolt to build blog pages
Ask Bolt for a blog index and a post template. Posts live in the code or in a table in Bolt Database or your Supabase project.
What it gets right
- One codebase and one design system
- Live in minutes, with no extra tool or bill
- SEO boosting on Bolt Pro and above, per the Bolt pricing page
What it costs you
- Posts in code: each one is a prompt, tokens and an update
- Posts in a table: you also build the admin screen writers use
- Schema, sitemap entries and feeds are prompts you maintain
Option 2: Run Superblog at yoursite.com/blog
Route /blog on your domain to Superblog, or use blog.yoursite.com where /blog is not possible. Your Bolt project keeps every route it has and never republishes for a post.
What it gets right
- Editor, hosting and blog front end in one product
- Schema, sitemaps, IndexNow and llms.txt on every post
- Your team publishes without Bolt access or tokens
What it costs you
- One routing rule to set up once, and /blog depends on your host
- The blog uses Superblog templates matched to your colors and fonts
- A separate subscription, from $49 a month on Pro
Option 3: Wire a headless CMS through prompts
Connect a CMS and prompt Bolt to build pages that fetch and render its posts.
What it gets right
- Writers get a real editor
- Content sits outside your project code
- Posts can go live without an update if the site fetches them on each request
What it costs you
- You still build the blog front end
- You still build schemas, sitemaps and canonical logic
- A CMS plan on top of your Bolt plan
For a step-by-step walkthrough of each route, including what Bolt generates when you prompt for a blog, read our guide to adding a blog to a Bolt.new site.
Where a Bolt.new blog gets stuck
Bolt builds blog pages quickly. These limits show up once you publish posts every week.
No native CMS. As of November 2026, Bolt's help center documents hosting, domains and a database, and no blog editor or CMS. Posts live in your project's code, in a database table, or in an outside CMS you connect.
Every post waits on a republish. Bolt's docs say changes to your project are not applied to the published site until you click Update in the Publish menu. A post stored in code is a prompt and an update, every time.
A bigger project costs more tokens per message. Bolt's token docs say most usage comes from reading and syncing your project files, so larger projects use more tokens per message. Every post you add to the code makes the project larger.
/blog is not a documented route on Bolt hosting. As of November 2026, Bolt's hosting and domain docs describe no rewrite or proxy rule. They also tell you to keep the Cloudflare proxy off for Bolt records, because SSL provisioning fails when it is on. A Cloudflare Worker only runs on proxied records, so it is not a supported way to route /blog here.
Add the blog to your Bolt.new site at yoursite.com/blog
Pick the path that matches where your site is published. Paths 1 and 2 send /blog to Superblog and leave every other route on your site. Path 3 covers sites on Bolt hosting.
Create your blog in Superblog and choose a paid plan. Subdirectory hosting is on every paid plan; trial sites cannot connect a subdirectory. Pro is $49 a month (see pricing). The code below uses yourblog.superblog.click as a placeholder. Your dashboard shows the code with your own address.
Path 1: your site is published through Bolt's Netlify integration
As of November 2026, Bolt can publish a project to Netlify instead of Bolt hosting. Netlify proxies a path to an outside address with a rewrite rule, so /blog works here.
- Create a file named _redirects, with no file extension, in the folder your build copies to its output as-is. In a Vite project that is the public folder.
- Add the two lines below. Put them above any catch-all rule that sends every path to /index.html, because Netlify uses the first rule that matches.
- In the Publish menu, click Update so the file goes out with the site.
- Open yoursite.com/blog. It serves Superblog. Later posts publish without another update.
/blog https://yourblog.superblog.click/ 200!
/blog/* https://yourblog.superblog.click/:splat 200!To move a project that is already on Bolt hosting, disconnect its custom domain, unpublish it, choose Netlify under Domains & Hosting, publish, and add the domain again in Netlify. Bolt's docs say Netlify cannot host a database or a backend, so a project that needs one stays on Bolt hosting.
Path 2: your code is synced to GitHub and deployed on Vercel or Netlify
Bolt syncs your project to a GitHub repository you connect. Bolt's docs say you can publish that code with another service you choose. If you deploy it on Vercel or Netlify, add a rewrite to the repository root and redeploy once.
- On Vercel, add the rewrites below to vercel.json. On Netlify, add the redirects below to netlify.toml. If the repository already has a _redirects file, add the two lines from Path 1 to that file instead, because Netlify reads _redirects before netlify.toml. In every case, put the rules above any catch-all rule that sends every path to /index.html.
- Commit the file to the repository. Bolt checks GitHub every 30 seconds and pulls the change into your project.
- After the deploy, yoursite.com/blog serves Superblog. Later posts publish without another deploy.
{
"rewrites": [
{
"source": "/blog",
"destination": "https://yourblog.superblog.click/"
},
{
"source": "/blog/:path*",
"destination": "https://yourblog.superblog.click/:path*"
}
]
}[[redirects]]
from = "/blog"
to = "https://yourblog.superblog.click/"
status = 200
force = true
[[redirects]]
from = "/blog/*"
to = "https://yourblog.superblog.click/:splat"
status = 200
force = trueSame setup for other stacks: blog for Lovable, blog for v0 and blog for Base44.
Path 3: your site is on Bolt hosting with a custom domain
Use blog.yoursite.com. As of November 2026, Bolt hosting documents no rule that sends /blog elsewhere, and Bolt's docs say to keep the Cloudflare proxy off for Bolt records. A subdomain needs only one DNS record. Connecting blog.yoursite.com also needs a paid Superblog plan.
- In Superblog, connect blog.yoursite.com as your blog domain. The dashboard shows the CNAME record to add.
- If you bought the domain through Bolt, add that CNAME in Bolt under Settings > Cloud > Custom domains > Open domain settings > Add new record. Otherwise, add it where your DNS is managed.
- Your Bolt site stays on yoursite.com and the blog serves from blog.yoursite.com. Nothing in the Bolt project changes.
A subdomain builds authority separately from your main domain. If you want posts at /blog later, switch to Path 1 or Path 2. Our guide to subdomain vs subdirectory explains the difference.
What your Bolt.new blog gets on Superblog
- Blog at yoursite.com/blog: A Netlify or Vercel rewrite sends /blog to Superblog. Your Bolt project serves every other route.
- Automatic blog SEO: JSON-LD schema, XML sitemaps, IndexNow, Open Graph tags and llms.txt on every post. Nothing to prompt.
- 90+ Lighthouse guaranteed: Pre-built static pages on a global CDN. Sub-second load times on every post.
- Built-in lead generation: Email capture forms below posts, in the sidebar, and as pop-ups. No form code in your project.
- Writers publish on their own: Pro is $49 a month with 5 team members and scheduled posts. Nobody opens Bolt to publish.
- Posts cost no tokens: Posts never enter your Bolt project, so it stays the same size. Publishing rebuilds the blog, not your site.
The editor, hosting and SEO layer, mounted at /blog
Keep your site exactly as Bolt built it. Set up the blog in the 7-day free trial, no credit card required, then connect yoursite.com/blog on a paid plan.
Bolt.new blog options side by side
Posts rank when they go out on a steady schedule with schema and sitemaps on every one. The table shows which option keeps that work off your team.
| Aspect | Prompt-built blog | Superblog | Headless CMS |
|---|---|---|---|
| Publish without redeploy | No if posts live in code. Posts in a table skip it, once you build an editor | Yes. Publish from the dashboard | Yes, if the site fetches posts on each request |
| Schemas and sitemaps | You prompt and maintain them | Automatic on every post | You build them into the front end |
| Who writes posts | Whoever works in Bolt | Your team, 5 members on Pro | Writers in the CMS |
| Cost | Bolt tokens per edit | $49 a month on Pro | CMS plan plus Bolt tokens |
Bolt.new blog questions
Does Bolt.new have a built-in blog or CMS?
No. As of November 2026, Bolt's help center documents no CMS. You build blog pages with prompts or connect an outside CMS.
Can I put a blog at yoursite.com/blog on Bolt hosting?
Not with any rule Bolt documents. Publish through the Netlify integration or deploy the GitHub repository yourself to get /blog, or use blog.yoursite.com.
Does Bolt hosting work behind the Cloudflare proxy?
No. Bolt's docs say to keep the Cloudflare proxy off for Bolt records, because SSL provisioning fails when it is on.
Can I connect /blog during the Superblog free trial?
No. Subdirectory hosting is on every paid plan. Use the 7-day free trial, with no credit card required, to set up the blog and write first.
Related guides for Bolt.new builders
Go deeper on the Bolt setup, blog URL structure, and the same setup on other stacks.
How to Add a Blog to a Bolt.new Site
The full walkthrough: what Bolt builds, what it costs in tokens, and the routing config.
Subdomain vs Subdirectory
Why yoursite.com/blog keeps authority on your main domain.
Blog for Lovable
Add a blog at /blog to an app built with Lovable.
Blog for Vercel
Route /blog to Superblog with a vercel.json rewrite.
Ready to add a blog to your Bolt.new site?
Bolt runs the site. Superblog runs the blog, CMS, hosting, speed, and SEO layer.