01Raw HTML lacks page content
SEO Boost is unavailable or still switched off
Without a custom domain, the setting is unavailable. With one connected, it still needs to be enabled before crawlers receive its prepared HTML.
SEO fixes for Bolt sites
Turn Bolt’s SEO signals into fixes you can review and keep.
Bolt can build with different frameworks, host on bolt.host or Netlify, and optionally prerender pages with SEO Boost. BulkAudits inspects the actual stack, deployment, and custom domain before it changes a line of code.
Free URL audit. No code changes until you approve a pull request.
BulkAudits repair preview
bolt-site · fix-metadata → main
Raw HTML lacks page contentFOUND
Mixed production originsFIXABLE
One title across every routeFIXABLE
Build and rendered-page verification required before PR
Current Bolt architecture
We build against today’s product—not an old SEO myth.
Bolt supports branches and GitHub sync; SEO Boost is opt-in and custom-domain-only.
Bolt’s SEO Boost prepares HTML for crawlers, but it is disabled by default and only appears on projects with a connected custom domain. Projects also vary by framework and hosting provider, so the safe fix depends on the repository—not the Bolt badge.
Source: Bolt SEO Boost documentationLive URL + source code
The Bolt-specific failure points we test
The same visual project can expose very different HTML depending on its framework, host, visibility, and domain settings.
02Mixed production origins
bolt.host or Netlify URLs leak into metadata
A move between Bolt hosting, Netlify, and a custom domain can leave old origins inside canonical tags, social URLs, or sitemap entries.
03One title across every route
Vite routes share one index.html title
On React + Vite projects, route changes may happen entirely in the browser while crawlers and link-preview bots keep seeing the same global metadata.
04Branch drift while a fix is open
External changes race with builder updates
Bolt checks GitHub frequently, but near-simultaneous edits can still collide. A PR needs current-main checks and an automatic rebase strategy.
What the pull request changes
A small, stack-native patch with proof attached.
No free-form model gets permission to wander through your repository.
01
Detect the framework before selecting a transform
We use the native head API for a supported stack and refuse the change when detection confidence is too low.
02
Normalize the chosen production domain
Metadata, sitemap URLs, and social previews are rebuilt around the primary custom domain and checked against live HTTP responses.
03
Keep the PR current while Bolt keeps building
BulkAudits watches upstream changes, reruns build and page verification, and updates its branch without force-pushing.
Repository handoff
Bolt supports GitHub branches and pull-request workflows. BulkAudits proposes a dedicated fix branch so main stays protected while you review the preview.
New builder commitmain
Regression detected
A Bolt update restored the old bolt.host canonical. Production-domain fix prepared.
Repair branch ready
Build passed · failed check resolved · no healthy page regressed
The fix that stays fixed
Your builder keeps generating. The watcher keeps checking.
BulkAudits remembers the exact finding and code node behind a merged repair. A fast static scan checks it after each push; a full audit confirms the live site on schedule.
Exact-node regression scans
Automatic repair branches
GitHub Check Run on the commit
Full live-site re-verification
Bolt SEO questions
Clear limits before repository access
Does Bolt SEO Boost solve every SEO issue?+
No. It improves the HTML delivered to crawlers, but it does not guarantee unique page copy, correct canonicals, valid sitemap URLs, structured data, accessible images, or protection against later regressions.
Does BulkAudits require Bolt hosting?+
No. The audit starts from the public URL and the fix engine works from the connected GitHub repository. Bolt-hosted and supported externally hosted projects can both be checked.
Can BulkAudits fix any framework Bolt generates?+
No. We currently make code changes only for supported React + Vite, TanStack Start, and Next.js App Router repositories. Unsupported stacks still receive an audit, but no guessed code changes.
Will you publish my Bolt project automatically?+
No. We open a pull request and you control the merge. Hosting and publishing remain in your existing Bolt or deployment workflow.
Other supported builders
The repair path changes with the stack.
Start with the public evidence