AI visibility fixes, delivered as a pull request.
BrandViz.AI ships AI visibility fixes as a GitHub pull request your dev team reviews and merges: schema, structured data and content changes on a branch, with a full diff and your CI checks. Nothing reaches main without your review.
7 days free. Cancel anytime. Nothing publishes without you.
- Never writes to main
- Your CI runs on every branch
- Nothing merges without your team
Add Organization schema, HubSpot integration page and pricing FAQ capsule
brandviz-agent/organization-schema-hubspot-3f9a2c → main
Summary
Gemini and ChatGPT describe the company as a "marketing agency" because the Organization schema is missing and no page states the category in its first sentence. This PR adds the schema, a HubSpot integration page answering the 4 tracked queries where competitors are cited instead, and a pricing FAQ capsule. 1 commit, 4 files.
- components/schema/OrganizationSchema.tsx+41 −6
- app/pricing/page.tsx+18 −3
- app/integrations/hubspot/page.tsx+212 −0
- app/sitemap.ts+6 −0
What does the pull request contain?
The finished change, written against your codebase. One commit, one reviewable diff.
Schema blocks as JSON-LD
Organization, FAQPage, BreadcrumbList and WebPage schema, wired into the schema components your site already has rather than pasted as loose script tags.
Content section diffs
New pages in your content directory using your frontmatter, layout and components, plus surgical edits to existing pages where a section or answer capsule was missing.
Metadata and sitemap
Title, description, canonical and Open Graph tags on the page, and a sitemap entry with the correct lastmod, so the change is crawlable the moment it deploys.
A PR description that explains itself
The summary in the PR body is the same summary shown in your BrandViz.AI activity feed, so the reviewer on GitHub and the marketer in the app read one story.
The Engine reads your existing pages first and matches their conventions, so a schema change reuses the component you already export and a new page imports the same layout as its siblings.
Who reviews it, and what does your CI do?
Your own reviewers, under your own rules. CODEOWNERS assigns the reviewer, branch protection enforces required checks, and your CI runs on every push.
- 01
A branch is opened
Named brandviz-agent/ plus a slug for the task. Your main branch is never written to.
- 02
The change lands as one commit
Every file the task touched is staged and flushed together, so the diff is reviewable as a single unit.
- 03
Your checks run, and the Engine reads them
BrandViz.AI polls the check runs on the head commit. If a check it caused to fail comes back red, it reads the annotations and pushes a fix, up to a capped number of cycles.
- 04
Your reviewers are assigned by your rules
The PR is an ordinary PR, so CODEOWNERS, required reviewers and branch protection apply. BrandViz.AI reads the review state back into your activity feed.
- 05
Your team merges
Request changes in the app and the same branch is revised in place. Approve on GitHub and merge when your team is satisfied.
Setup is one step: Integrations, GitHub, approve the BrandViz GitHub App on the repository. The walkthrough lives in the connect your platform docs.
Is it safe to install the BrandViz GitHub App?
Yes. It is installed through GitHub's own consent screen on the repositories you choose. It creates branches and pull requests, and every change goes through your branch protection before it can land.
What BrandViz.AI can do
- Create branches named brandviz-agent/ plus a task slug, and open pull requests from them.
- Create and edit files on those branches, in one commit per task.
- Read your repository so new code matches your conventions, components and imports.
- Read check runs and review state on its own pull requests, and push follow-up commits to fix failures it caused.
What BrandViz.AI can never do
- Push to main or to any branch it did not create.
- Merge a pull request on a plain GitHub connection. Only your team merges, under your branch protection and CODEOWNERS rules. A Lovable connection merges once your build passes, so the change reaches your editor.
- Delete files, branches or pull requests you own. No delete operation is exposed to the Engine.
- Change repository settings, secrets, workflows, collaborators or the GitHub App installation itself.
What happens after you merge?
The change deploys through your normal pipeline, the weekly scan measures it, and the Engine queues the next fix.
Merge deploys through your pipeline
The merged change ships the way every other change on your site ships, on your schedule.
The weekly scan re-runs your queries
On the Growth plan, 150 tracked buying queries are refreshed weekly across ChatGPT, Claude, Gemini and Perplexity, with the competitive benchmark alongside.
The next task is queued from the result
Where the scan shows a gap still open, the Engine builds the next fix and opens the next PR.
What if you use a CMS or a builder instead of GitHub?
Connect it too and pick the destination per task. Technical fixes to GitHub, content pages to the CMS, or everything through one channel.
WordPress
Lands as Draft posts and pages in your WordPress site.
Webflow
Lands as Draft CMS items and staged SEO fields, unpublished until you publish the site.
HubSpot
Lands as Draft blog posts and site pages in HubSpot CMS.
Contentful
Lands as Unpublished entries in your chosen content type.
Lovable
Lands as A pull request on a brandviz-agent/ branch, merged when your build passes so it appears in Lovable.
Frequently asked questions
What does a BrandViz.AI pull request actually contain?
A BrandViz.AI pull request contains the finished change, not a description of it: JSON-LD schema blocks wired into your existing schema components, new content pages in your content directory following your frontmatter and component conventions, surgical diffs to existing pages for metadata and sections, and a sitemap entry, all in one commit on a brandviz-agent branch.
What happens after the PR is merged?
Merging publishes through your normal deploy, and the change flows back into the tracking loop. On the Growth plan BrandViz.AI re-runs your 150 tracked queries every week across ChatGPT, Claude, Gemini and Perplexity, so the next refresh shows whether mention and citation rates moved, and the Engine queues the next fix from that result.
Can we use the CMS integration instead of GitHub?
Yes. BrandViz.AI connects to WordPress, HubSpot, Webflow and Contentful as well as GitHub, and you pick the destination per task. CMS work lands as a draft your team approves in the CMS, with the same review gate. Teams commonly send technical fixes to GitHub and content pages to the CMS, or route everything through one channel.
Does BrandViz.AI ever push to our main branch?
No. Every change lands on its own brandviz-agent/ branch and arrives as a pull request. Your branch protection, required checks and CODEOWNERS rules apply as they do to any other branch.
Does this work with Astro, Next.js, Hugo or our framework?
Yes, and there is nothing framework specific to switch on. Next.js, Astro, Nuxt, SvelteKit, Gatsby, Remix, Hugo, Jekyll and Eleventy all mean the same thing here: the site is code in a repository. BrandViz.AI reads that repository at the start of every job and follows the conventions already in it, your file format, your frontmatter, your metadata declaration, your routing and your sitemap, so the pull request looks like the code around it. The same is true of a Rails, Django or Laravel site, or any other stack with a repository.
Does the GitHub route work with Lovable, v0 or Bolt sites?
Yes. Lovable has its own integration: connect the synced repository and the change appears in your Lovable editor once your build passes. Sites built with v0, Bolt and other builders connect through the GitHub integration, and the builder picks up the merged change on its next sync.
What happens if we disconnect GitHub?
Disconnecting stops BrandViz.AI opening new branches and pull requests. Open pull requests stay in your repository, and you can remove the app under GitHub Settings, Integrations.
Other integrations
How every integration works
Ship your first fix as a pull request.
Start the trial, install the GitHub App on your repository, and review the first pull request where your team already reviews code.
7 days free. Cancel anytime. Nothing publishes without you.