WordPress
Destination: ships drafts
Draft posts and pages directly on your WordPress site.
- Lands as:
- Draft posts and pages in your WordPress site.
- Approve in:
- wp-admin, when your team presses Publish.
Connect once. Every fix lands where your team already works.
BrandViz.AI ships fixes into your CMS or repository as drafts, staged entries or pull requests, and reads AI crawler logs from your hosting. Connecting takes a minute. You review every change before it goes live.
7 days free. Cancel anytime. Nothing publishes without you.
- Drafts and pull requests, never published pages
- Cannot delete your content
- Disconnect any time
Integrations
Where the Engine ships, and what it reads.
- Ships drafts
WordPress
Draft posts and pages in your WordPress site.
- Ships drafts
Webflow
Draft CMS items and staged SEO fields, unpublished until you publish the site.
- Ships drafts
HubSpot
Draft blog posts and site pages in HubSpot CMS.
- Ships drafts
Contentful
Unpublished entries in your chosen content type.
- Ships drafts
Lovable
A pull request on a brandviz-agent/ branch, merged when your build passes so it appears in Lovable.
- Ships drafts
GitHub
A pull request on a brandviz-agent/ branch, never a push to main.
- Read-only
Vercel
The AI traffic dashboard in BrandViz.AI.
- Read-only
Cloudflare
The AI traffic dashboard in BrandViz.AI.
Which platforms does BrandViz.AI integrate with?
BrandViz.AI ships to WordPress, Webflow, HubSpot, Contentful, Lovable and GitHub, and reads AI crawler logs from Vercel and Cloudflare. Each has its own page with the connection step, the access held, where output lands and where your team approves it.
Webflow
Destination: ships drafts
Draft items in your Webflow CMS collections.
- Lands as:
- Draft CMS items and staged SEO fields, unpublished until you publish the site.
- Approve in:
- Webflow, when your team publishes the site.
HubSpot
Destination: ships drafts
Draft blog posts and site pages in HubSpot CMS.
- Lands as:
- Draft blog posts and site pages in HubSpot CMS.
- Approve in:
- The HubSpot content editor, when your team publishes.
Contentful
Destination: ships drafts
Draft entries in your Contentful space.
- Lands as:
- Unpublished entries in your chosen content type.
- Approve in:
- Contentful, through your own publish workflow.
Lovable
Destination: ships drafts
Pull requests on the GitHub repository Lovable keeps in sync.
- Lands as:
- A pull request on a brandviz-agent/ branch, merged when your build passes so it appears in Lovable.
- Approve in:
- Lovable’s editor, where you review and publish as usual.
GitHub
Destination: ships drafts
Open pull requests against your site’s code repository.
For a site your developers built rather than one made in a website builder: Next.js, Astro, or any other repository.
- Lands as:
- A pull request on a brandviz-agent/ branch, never a push to main.
- Approve in:
- GitHub code review, under your branch protection and CODEOWNERS.
Vercel
Source: reads crawler logs
Stream request logs to see which AI crawlers fetch which pages.
- Shows as:
- The AI traffic dashboard in BrandViz.AI.
- Approve in:
- Nothing to approve: BrandViz.AI never writes to Vercel.
Cloudflare
Source: reads crawler logs
Read hourly AI crawler analytics for your zone.
- Shows as:
- The AI traffic dashboard in BrandViz.AI.
- Approve in:
- Nothing to approve: BrandViz.AI never writes to Cloudflare.
Using something else?
Tell us what it is
Shopify and Framer are in beta: contact us for access. For anything else, we will tell you within a day whether we can set it up for you, and you still get every fix as a brief meanwhile.
How does BrandViz.AI keep every integration safe?
Six rules, the same on every platform: a person approves every change, access is the narrowest that does the job, credentials never leave the server, the Engine cannot delete your content, you can disconnect without losing delivered work, and read-only viewers cannot change a connection. The table states the access held on each platform. Under it, pick your platform for a brief written for the person who has to sign it off.
A person approves every change
The Engine delivers drafts and pull requests. It never publishes. Your team approves where they already work: wp-admin, the HubSpot editor, Webflow, Contentful, the Lovable editor or GitHub code review.
The narrowest access that does the job
Each connection asks for the smallest grant its platform offers for drafting, and nothing for publishing or account settings. The table below states the exact access held on every platform, and each brief explains why.
Credentials stay server-side
Tokens and passwords are stored in your brand’s credentials on the server and never returned to the browser. Where a platform offers app-identity or OAuth connect, there is no token to copy at all.
It cannot delete your content
The Engine creates and edits. It cannot delete your posts, pages, entries, files or branches. The only removals it makes are inside a page it is already editing, staged for your review like any other change.
Disconnect any time, and keep your work
Disconnecting removes BrandViz.AI’s access from Integrations. Drafts, entries and open pull requests already delivered stay where they are, because they belong to your site.
Read-only viewers stay read-only
Client-portal stakeholders without edit rights see connection state, and none of the controls that change it.
| Platform | Connect via | Access held | Output lands as | You approve in |
|---|---|---|---|---|
| WordPress | Authorise BrandViz in wp-admin, or connect with an application password. | Edit posts, edit pages, upload media. | Draft posts and pages in your WordPress site. | wp-admin, when your team presses Publish. |
| Webflow | A Site API token for CMS content, plus a Webflow OAuth consent for pages and design. | Sites, CMS, Pages and Components, read and write. | Draft CMS items and staged SEO fields, unpublished until you publish the site. | Webflow, when your team publishes the site. |
| HubSpot | A Private App access token you create in your portal, content scope only. | CMS content: draft blog posts and site pages, read your theme. | Draft blog posts and site pages in HubSpot CMS. | The HubSpot content editor, when your team publishes. |
| Contentful | Install the BrandViz app into your space, then connect with the Space ID; or a CMA personal access token. | One space and one environment. | Unpublished entries in your chosen content type. | Contentful, through your own publish workflow. |
| Lovable | Turn on GitHub sync in Lovable, then install the BrandViz GitHub App on that repository. | Create branches and pull requests on the synced repository. | A pull request on a brandviz-agent/ branch, merged when your build passes so it appears in Lovable. | Lovable’s editor, where you review and publish as usual. |
| GitHub | Install the BrandViz GitHub App on the repository. No tokens to copy. | Create branches and pull requests on the connected repository. | A pull request on a brandviz-agent/ branch, never a push to main. | GitHub code review, under your branch protection and CODEOWNERS. |
| Vercel | One click: the Vercel consent flow opens, you approve, BrandViz configures the rest. | Request logs, read-only. Requires a Vercel Pro or Enterprise plan. | The AI traffic dashboard in BrandViz.AI. | Nothing to approve: BrandViz.AI never writes to Vercel. |
| Cloudflare | One click: the Cloudflare consent flow opens, you approve, BrandViz configures the rest. | Zone analytics, read-only. Works on every Cloudflare plan, including Free. | The AI traffic dashboard in BrandViz.AI. | Nothing to approve: BrandViz.AI never writes to Cloudflare. |
Last verified: September 2026, against the connection panels in the BrandViz.AI app.
Need something to send your engineering team? Every platform page carries a brief for that platform, covering access, what is written and what is reversible, that copies as an email.
What if your platform is not listed?
If your site runs on a platform BrandViz.AI does not connect to, the Engine still does the work. You receive the finished content and the technical fix as a brief in your activity feed: the exact copy, the JSON-LD block, the metadata, and step-by-step instructions for where each piece goes in your CMS. If your site lives in a GitHub repository, the GitHub integration covers it directly.
That includes sites built with v0, Bolt or another AI app builder, which sync to a GitHub repository, and any custom stack with a repo. See how the GitHub integration works. Direct Shopify and Framer connections are in beta, on request. Not sure what your site runs on? The free website tech checker reads any URL and says which of these integrations apply. For the buyer's view of which GEO platforms ship to which CMS, read our guide to GEO platform CMS integrations.
On a platform we do not list yet?
Tell us what you run. We answer within a day on whether we can set it up for you, and most requests become the next integration we build.
- 1.
The Engine builds the fix as usual
Diagnosis, schema, metadata and content are produced exactly as they would be for a connected platform. Nothing is skipped because the destination is manual.
- 2.
You receive a complete brief
Every piece is paste-ready: the JSON-LD block, the title and description, the page copy with its headings, and the location in your CMS where each one goes.
- 3.
You apply it in your CMS
Your team pastes and publishes in the tool it already uses. The approval gate is the same as everywhere else: a person, in your platform, presses Publish.
- 4.
The weekly scan checks the result
On the Growth plan your tracked queries are refreshed weekly across ChatGPT, Claude, Gemini and Perplexity, so you see what the change did and the next brief follows from that.
Frequently asked questions
Which platforms does BrandViz.AI integrate with?
BrandViz.AI ships fixes and content to WordPress, Webflow, HubSpot, Contentful, Lovable and GitHub, as drafts in a CMS or as pull requests on a repository. It reads AI crawler logs from Vercel and Cloudflare without writing to either. Sites built with v0, Bolt or another AI app builder connect through their GitHub repository, and platforms not listed receive the same fixes as briefs to apply by hand.
Does anything publish automatically?
No. Every integration delivers a draft, an unpublished entry, a staged change or a pull request, and a person on your team publishes it. On a Lovable project the change appears in your Lovable editor, and goes live only when you press Publish in Lovable. Vercel and Cloudflare are read-only sources, so there is nothing to publish from them at all.
Can we connect more than one integration?
Yes. Connect what your site uses and pick the destination per task. A marketing site on Webflow or WordPress usually pairs its CMS with Cloudflare for crawler logs. A code-based site pairs GitHub with a headless CMS, and Vercel. Everything lands in one activity feed.
What if our CMS is not on the list?
The Engine still does the work. You receive the finished content and the fix as a brief in your activity feed, or as a Google Doc: the copy, the schema, the metadata and where each piece goes. If your site lives in a GitHub repository, the GitHub integration covers it directly.
How do we connect a platform?
From Integrations, choose the platform and follow one step. Most are a consent screen; the rest take one token you create in the platform. The free tech checker at brandviz.ai/tools/tech-check tells you which apply to your site.
The full diagnose, build and ship cycle is described on the platform page, and the connection walkthroughs live in the connect your platform docs.
Connect once. Ship the first fix this week.
Start the trial, connect the platform your site runs on, and review the first draft where your team already works.
7 days free. Cancel anytime. Nothing publishes without you.