AI visibility fixes, delivered into your Lovable project.
BrandViz.AI connects to the GitHub repository Lovable keeps in sync and ships AI visibility fixes and pages as pull requests, merged when your build passes so they appear in Lovable. You review and publish there.
7 days free. Cancel anytime. Nothing publishes without you.
- Pull request first, merged only on a passing build
- Publishing stays in Lovable
- Disconnect any time
How it works
Ships draftsConnect Lovable
Turn on GitHub sync in Lovable, then install the BrandViz GitHub App on that repository.
The Engine builds the fix
Grounded in your visibility report and the pages your site already has.
It lands as a draft
A pull request on a brandviz-agent/ branch, merged when your build passes so it appears in Lovable.
Your team approves
Lovable’s editor, where you review and publish as usual.
What does BrandViz.AI ship to a Lovable project?
BrandViz.AI ships the same work to a Lovable project that it ships to any code repository: schema and metadata, new pages built from your existing components, section-level content edits, and technical fixes to how AI crawlers read the site. Each arrives as one change with a summary in your activity feed.
Schema and metadata
Organization, product, FAQ and article structured data, plus titles and descriptions, written into the pages and layouts your project already has.
New pages and content
Pages for the buying queries where competitors are cited instead of you, written in your voice and built from your project’s own components so they look like the rest of the site.
One pull request per job
A brandviz-agent/ branch, one flushed commit, and a description that matches the summary in the app. Your repository’s own build checks run on it.
The files Lovable owns, untouched
Lockfiles, vite.config, tsconfig, generated UI components and Supabase files are never edited, because editing them from outside is what breaks a project’s two-way sync.
Built with another AI app builder such as v0 or Bolt? Their repositories connect through the GitHub integration with the same pull-request flow; you merge the pull requests yourself.
Is it safe to connect BrandViz.AI to a Lovable project?
Yes. BrandViz.AI can open branches and pull requests on the synced repository, and nothing else. A merged change lands in Lovable’s editor, and publishing from there is still what puts it in front of a visitor. If the build fails, the pull request is left open for you.
What BrandViz.AI can do
- Open a branch and a pull request on the synced repository.
- Fix build failures its own change caused, and re-run the checks.
- Merge the pull request once your build passes, when merge-on-green is on.
- Read the repository so new pages use the components and styles the project already has.
What BrandViz.AI can never do
- Publish your site. That happens in Lovable, by you.
- Push content directly to the branch Lovable syncs. Every change goes through a pull request; the only direct push is the empty sync-nudge commit you can trigger from a job card.
- Edit the files Lovable owns and round-trips, or delete files and branches.
- Merge a change whose build failed or could not be confirmed. That pull request is left open, and the job card says why and offers Merge now if you want it anyway.
What happens after a pull request merges?
Lovable picks the change up on its next sync and it appears in your project as unpublished changes: a new version in the history, visible in the preview, with a dot on the Publish button. The job card in BrandViz.AI names the version, lists the pages it changed, and links to your Lovable project. On the Growth plan, BrandViz.AI re-runs your 150 tracked queries every week, so the next refresh shows what the change did.
The change appears in Lovable
Merged on a green build, synced by Lovable, visible in your preview as unpublished changes. If it has not appeared after a minute, the job card’s Nudge sync pushes a commit that makes Lovable pull again. No preview exists inside Lovable before the merge, which is why the merge is done for you.
You review in the preview and publish
The same review you give your own edits, then Publish, then Publish changes, from Lovable the way you always do. There is no approval step inside Lovable: publishing is the approval.
The weekly scan re-runs your queries
150 tracked queries refreshed weekly across four AI engines, with the competitive benchmark alongside, so you see the effect and the next fix follows from it.
How does BrandViz.AI connect to Lovable?
Lovable has no API of its own, so the repository is the integration. Turn on GitHub sync in your Lovable project, connect that repository from the Lovable card in BrandViz.AI Integrations, and confirm the target branch is the one Lovable syncs. Three steps, no tokens to copy.
- 01
Turn on GitHub sync in Lovable
In your project, open GitHub, Connect to GitHub at the top right, and authorise Lovable. It creates a repository in your account or organisation and keeps it in two-way sync. Available on every Lovable plan. Until this is on there is no repository for BrandViz.AI to connect to.
- 02
Connect that repository from the Lovable card
In BrandViz.AI, open Integrations, choose Lovable and press Connect GitHub. Approve the BrandViz GitHub App on the synced repository. If BrandViz is already installed on your GitHub account, use Find my installations and pick it.
- 03
Confirm the target branch
Every change is a pull request against this branch, and Lovable syncs one branch, normally main. The panel shows which branch is set and lets you change it.
- 04
Merge automatically when checks pass is turned on
Connecting through the Lovable card enables this by default, because on a synced repository an unmerged pull request is a dead end nobody can see in Lovable. You can turn it off under the connection details. GitHub will email you about the pull requests and checks this creates; those are ours, and nothing needs doing in GitHub itself.
The step-by-step walkthrough, including what to do when GitHub skips the approval screen, lives in the connect your platform docs.
Before you ask
How soon does the first draft arrive?
Connect once, and the first drafts follow from your first report. Each one waits for your approval.
What does it cost?
Included in the Growth plan: 150 tracked queries refreshed weekly, plus the Engine building and shipping fixes. Seven days free to start.
What if a draft is wrong?
Decline it, or request changes in the app and the same item is revised in place. Nothing publishes until you approve.
Frequently asked questions
Why does BrandViz.AI merge the pull request instead of leaving it for me?
On a Lovable project an open pull request is invisible to you: until it merges, nothing changes in your editor. So the Lovable card merges once your build passes. The change then appears in Lovable as unpublished changes for you to check in the preview, and publishing remains yours.
The job says it merged, but I cannot see the change in Lovable. What now?
Open your project’s history: the job card names the version to look for, and the preview shows it as unpublished changes. If it is not there, press Nudge sync on the job card. Lovable pulls when GitHub notifies it of a push and does not retry a missed notification, so the nudge pushes a small commit that makes it pull again. If the job says the pull request was left open instead, the card says why and Merge now sends it to Lovable.
Which branch should the target be?
The branch Lovable syncs, which is main unless you switched it. This is the step that catches people out: a pull request opened against any other branch can merge perfectly and never reach Lovable. The connection panel shows the target branch and lets you change it at any time.
Will it break my project’s sync with Lovable?
No. Editing the files Lovable owns from outside is what breaks two-way sync, so BrandViz.AI refuses to write to them: lockfiles, vite.config, tsconfig, generated UI components under src/components/ui and anything under supabase. Everything else is ordinary application code and syncs the way your own commits do.
What if I use v0, Bolt or another builder?
Their repositories connect through the GitHub integration with the same pull-request flow, and steps one and three above apply to them too. You merge the pull requests yourself; merge-on-green is only turned on for repositories connected through the Lovable card.
Other integrations
How every integration works
Ship your first fix to Lovable.
Connect Lovable, run your first report, and review the first draft where your team already works.
7 days free. Cancel anytime. Nothing publishes without you.