Google sees an empty page
Some generated apps still ship client-rendered shells that search crawlers cannot reliably read.
Built for AI-generated sites
We find what is broken. Then send the fix.
Your Lovable, Bolt, Replit, v0, or Base44 site can look perfect and still be invisible to Google. BulkAudits opens a verified pull request that fixes it—and watches every push so it stays fixed.
BulkAudits opened pull request #12
bulkaudits/fix-metadata → main
Fixed 9 issues stopping people from finding and sharing your site
Every change passed your build and was checked on a rendered preview.
Unique Google titles1 of 1212 of 12
LinkedIn previewBlankReady
Pages in sitemap012 verified
Build passes 0 regressions You control merge
Looks finished. Is not finished.
The defects your AI builder does not show you
A beautiful page can still be unreadable to crawlers, invisible in search, and broken everywhere it gets shared.
Shared links look broken
LinkedIn, X, Slack, and WhatsApp find no preview image or useful page description.
Every prompt can undo the fix
Generated components are rewritten constantly, silently dropping metadata you already added.
Builder-aware repairs
The same symptom needs a different fix in every stack.
We detect what your builder actually generated, use its native metadata system, and refuse unsupported code instead of guessing.
Lovable
TanStack Start or React + Vite
Prompt-by-prompt metadata regressions
See exact repair pathBolt
Framework and host detected first
SEO Boost, domain, and route gaps
See exact repair pathReplit
Static or server deployment
Source, build, and live output drift
See exact repair pathv0
Next.js App Router
metadataBase and dynamic route gaps
See exact repair pathBase44
GitHub sync through main
Builder, repo, and publish state drift
See exact repair pathFrom URL to merged fix
No reports to decipher. No developer to hire.
The audit is the diagnosis. The pull request is the product.
01
Paste your live URL
We check what Google and social crawlers actually receive. No account required.
02
Connect one GitHub repository
BulkAudits detects the framework and prepares only fixes it can verify safely.
03
Review, preview, and merge
See the before-and-after result. Your site changes only when you approve the PR.
04
Every future push stays protected
If your builder reintroduces a defect, the watcher catches and repairs it again.
Not another score
37checks
with evidence
with evidence
Every finding is graded by whether software can fix it safely—not by which Lighthouse tab it belongs to.
A · deterministicB · review copyC · advisory
Indexability & rendering
10Raw HTML, crawler responses, robots, sitemap URLs, canonicals, domain leakage, soft 404s, and redirects.
Can Google receive the real page?
Metadata & sharing
9Unique titles, descriptions, Open Graph, Twitter cards, preview images, headings, and document language.
Does every route explain itself?
Structured data & AI
5JSON-LD validity, page types, entity signals, llms.txt, semantic landmarks, and extractable content.
Can machines understand the page?
Performance & Core Web Vitals
9LCP, CLS, INP, image sizing, lazy loading, fonts, imports, unused code, and render blockers.
Does the generated code stay fast?
Accessibility
4Image alternatives, colour contrast, form labels, and accessible names for interactive controls.
Can every visitor use it?
Push detecteda18d9f2
Lovable removed the pricing page description
Previously fixed 6 days ago · repair prepared in 12 seconds
Repair PR is ready
Build passed · description restored · no other page changed
The reason you keep it connected
Your site changes every prompt. Your fixes should survive every prompt.
BulkAudits remembers exactly what was fixed, watches the same code after every push, and catches regressions before they cost you traffic.
Fast checks on every commit
Full weekly site audit
Automatic repair pull requests
One-click revert for every fix
Your first pull request
Grouped by intent. Small enough to trust.
We never dump twenty unrelated changes into one diff. Fixes arrive in reviewable clusters, and anything requiring generated copy stays draft.
Crawlabilityrobots.txt, verified sitemap, canonicals
Metadataroute titles, descriptions, social cards
Imagesdimensions, loading, format, preview asset
Bundleimports, dead components, render blockers
Accessibilitylabels, names, decorative image handling
BulkAudits: fix 9 metadata issuesREADY
ResultBeforeAfter
Unique page titles1 / 1212 / 12
Valid sitemap URLs012
Working social cards012
+ src/components/SEO.tsx
~ src/pages/Pricing.tsx
+ public/sitemap.xml
Build passes9/9 resolved0 regressions
Trust is the feature
AI writes words. Deterministic transforms change code.
The model never roams freely through your repository. It can suggest title copy; typed transforms place it at an exact, verified node.
Exact code changes
Framework-aware AST transforms, scoped to the node that failed.
Proof before PR
Build, typecheck, re-render, and regression checks must all pass.
You own the merge
No direct writes to your live branch. No force pushes. Revert anytime.
Questions, answered
Before you connect your repo
Will BulkAudits change my site automatically?+
No. We only open a pull request. You see every changed file and your site changes only after you click merge.
Do I need to understand the code?+
No. Every issue and fix is explained in plain language, with a before-and-after preview and an instant revert path.
What happens when Lovable rewrites my code later?+
The push watcher checks every new commit. If a previously fixed issue returns, BulkAudits prepares a new repair pull request.
Which site builders are supported?+
The first release supports React + Vite, TanStack Start, and Next.js App Router—the common foundations behind Lovable, Bolt, and v0 projects.
Start with the evidence