AI visibility fixes, as unpublished entries in Contentful.
BrandViz.AI installs into one Contentful space and ships AI visibility fixes and content as unpublished entries in the content type you choose. Your own publish workflow puts them live.
7 days free. Cancel anytime. Nothing publishes without you.
- Unpublished entries only
- Scoped to one space and environment
- Field mapping discovered, not guessed
How it works
Ships draftsConnect Contentful
Install the BrandViz app into your space, then connect with the Space ID; or a CMA personal access token.
The Engine builds the fix
Grounded in your visibility report and the pages your site already has.
It lands as a draft
Unpublished entries in your chosen content type.
Your team approves
Contentful, through your own publish workflow.
What ships
What does BrandViz.AI ship to Contentful?
BrandViz.AI ships finished work to Contentful as unpublished entries: posts in your blog content type with the body written as Rich Text or long text according to the discovered mapping, metadata fields filled where your model has them, and the answer-first structure AI engines quote. Each entry waits in your space for an editor to publish.
Unpublished entries
Content targeting the buying queries where competitors are cited instead of you, created in your blog content type and left unpublished for your editors.
Fields filled by mapping
Title, slug, body and the rest of your fields are populated from the mapping discovered at connect, so entries fit your model rather than a generic template.
Metadata where your model has it
SEO title and description fields are filled when your content type defines them, so the front end renders them without a second pass.
Your default locale
Entries are written in the default locale read at connect time, so they appear in your editors’ normal view rather than in a locale nobody checks.
Technical fixes that live in your front end rather than in Contentful, such as Organization schema or sitemap entries in a Next.js or Gatsby codebase, are better carried by the GitHub integration, which opens a pull request against the repository. Many headless teams connect both.
Safety
Is it safe to connect BrandViz.AI to Contentful?
Yes. BrandViz.AI has access only to the space and environment where your team installed the app. It creates unpublished entries and cannot publish, delete or change your content model. Uninstalling the app in Contentful ends access immediately.
What BrandViz.AI can do
- Create unpublished entries in your chosen blog content type.
- Fill fields according to the mapping discovered for that content type.
- Read your content types, field mappings and default locale, and re-run discovery on request.
- Show every shipped entry in your BrandViz.AI activity feed with its summary.
What BrandViz.AI can never do
- Publish anything. Every entry waits for an editor to publish it through your workflow.
- Delete or archive entries or assets. No delete operation is exposed to the Engine.
- Change your content model, environments, roles, webhooks or space settings.
- Reach any other space or environment than the one the app is installed in.
After approval
What happens after an editor publishes?
Publishing closes the loop. On the Growth plan, BrandViz.AI re-runs your 150 tracked buying 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.
Your editor publishes
The entry goes through your Contentful workflow and your front end renders it on its next build or revalidation, the same as any other entry.
The weekly scan re-runs your queries
150 tracked queries are refreshed weekly across four AI engines, with the competitive benchmark alongside, so you see the effect of what you published.
The next entry is queued
Where the scan shows a gap still open, the Engine builds the next fix and creates the next unpublished entry.
Connecting
How does BrandViz.AI connect to Contentful?
BrandViz.AI connects to Contentful through the BrandViz app: install it into your space under Apps, Custom apps, then connect with the Space ID and environment. Access is scoped to that space and there is no token to copy.
- 1
Install the BrandViz app in your space
In Contentful, go to Apps, Custom apps, and install BrandViz. Installation is what grants access; the backend verifies it by minting an app access token for that space.
- 2
Connect with the Space ID and environment
In BrandViz.AI Integrations, choose Contentful and enter the Space ID and the environment (master by default). Or switch to a CMA personal access token if your team prefers.
- 3
Discovery maps your content model
Field mappings for every content type are discovered at connect, the blog content type is auto-detected, and your default locale is read. Switching the blog type applies its mapping immediately.
- 4
Check the body field
The active content type needs a Rich Text or long text body field mapped. If none is found the panel warns you before the Engine writes, so no entry arrives with an empty body.
Re-run discovery from the connection panel whenever your content model changes, without rotating credentials. The walkthrough 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
What access does BrandViz.AI have in Contentful?
One space and one environment: the ones your team installed the BrandViz app into. There is no token to copy, and uninstalling the app ends access. If you use a CMA token instead, it is stored server-side and can be rotated at any time.
Does BrandViz.AI publish entries in Contentful?
No. BrandViz.AI creates entries and leaves them unpublished. Your editors review them in the Contentful web app and publish through whatever workflow you already run, including scheduled publishing or approval tasks. Because most headless front ends render only published entries, nothing appears on your site until that step happens.
How does BrandViz.AI know which fields to fill?
At connect time BrandViz.AI maps every content type in the space and picks the blog type. You can override that choice in the connection panel. The active type needs a Rich Text or long text body field, and the panel warns you if none is mapped.
What about schema and technical fixes in our front end?
Structured data, metadata templates and sitemap entries usually live in the front-end codebase, not in Contentful. BrandViz.AI carries those through the GitHub integration as a pull request against your repository, reviewed by your developers. Content entries go to Contentful, code goes to GitHub, and you pick the destination per task.
Ship your first fix to Contentful.
Connect Contentful, run your first report, and review the first draft where your team already works.
7 days free. Cancel anytime. Nothing publishes without you.