An AI visibility report changes nothing until it is deployed: what happens after the scan

An AI visibility report changes nothing on its own: until the files it recommends are live, generative AI crawlers read exactly what they read the day before. The scan is the easy part. What matters is the path between the diagnosis and the file your domain actually serves, and that path depends entirely on the platform your site is built on. A WordPress site, a Shopify store, a hand-coded site and a Wix site do not follow the same path, and two of them have a ceiling you know about before you start.

Why is a diagnosis worth nothing without deployment?

An AI visibility scan reads a site's homepage and a handful of public files, read-only, and checks 19 signals across 3 axes: visible, citable, agent-ready. The full list is published on the Biencité method page. The report says what is missing: a reading guide for AI, structured data, content cut up for citation, declared usage preferences. None of those signals turns green because you read a report. A signal changes state when the corresponding file is served, at the right address, with the right content, and not before.

The cost of a diagnosis is not the diagnosis. It is the number of weeks that pass between the day you know and the day the file is live. The article "How long before you see an effect on your AI visibility?" goes into this: the clock starts on deployment day, never on scan day. A report sitting in a shared folder does not move the clock forward by a second.

What does the tool produce once a gap is identified?

Once a missing signal is identified, Biencité generates the matching asset: an llms.txt file, structured data in JSON-LD, an article structured for citation, crawler directives, a usage-preferences declaration. Each asset is adapted to the platform declared for the site. Generation runs on Claude or on Mistral, the customer's choice, and only the public information of the scanned site is sent to the model, never account data. The free scan gives you the diagnosis; generation and tracking sit in the paid plans.

One honest caveat belongs here: a generated asset is a starting point you proofread, not a text you publish with your eyes closed. A model writing about your business only knows what your site says publicly. If your site says little about your services, your prices or the area you serve, the generated file will say little too. The quality of what comes out depends on the quality of what is already online.

How does a fix reach a WordPress site?

WordPress runs 40.2% of all websites as of September 16, 2026, according to W3Techs' daily survey. It is also the platform where deployment is the most direct, because WordPress gives you access to the root of the domain. Biencité ships a dedicated WordPress plugin: you install it, paste the endpoint and API key it displays into your Biencité workspace, and every generated asset gets a "Deploy to WordPress" button.

Articles land in your WordPress as drafts. Nothing is published without you, unless you switch on automatic publishing yourself. That default is deliberate: a generated text about your business deserves a read-through before it carries your name. The plugin moves files; it does not make editorial decisions on your behalf.

And a Shopify store?

Shopify powers 5.4% of websites as of September 16, 2026 (W3Techs), and a Shopify store lives two realities at once. First: Shopify locks certain files at the root of the domain. The matching signals are marked impossible on this platform instead of being counted against the store, and they never appear in its action plan. Second: Shopify has opened its own channel to AI. The Shopify Help Center describes "agentic storefronts", active by default for eligible stores and managed in the admin under Sales channels, then Agentic, which make products discoverable in ChatGPT, Google AI Mode, Gemini, Microsoft Copilot and Meta.

The Biencité integration for Shopify works through a private app you create in your admin, with write access to content and products. Generated articles are then published to the store's blog from your workspace, and the action plan asks you to check that the Agentic channel is switched on. What the integration does not do: it does not unlock the root. A Shopify store improves what is reachable on Shopify, and its report says so in plain words.

And a hand-coded site?

A site built on Next, Astro or static pages accepts no plugin, but it allows everything. For those sites, Biencité exposes a secured MCP (Model Context Protocol) server: you connect your account to Claude Code, and the assistant fetches or generates your GEO assets straight into your code repository, in the right format, ready to be reviewed and deployed. The connection is reserved for Pro plans. Nothing goes live without a commit: the developer stays in the loop at every step.

It is the path with the most freedom and the most responsibility. Nobody clicks for you, and nobody checks that the deployment actually happened either, except the next scan. A coded site can reach all 19 signals; someone in the company still has to know how to push a file to production.

And Wix, Webflow or Framer?

Wix accounts for 4.2% of websites and Webflow for 0.8% as of September 16, 2026 (W3Techs). On these platforms there is no plugin and no Claude Code connection: the action plan gives you instructions to paste into the editor's custom-code area and SEO settings, page by page. Files locked at the root stay marked impossible. The article "Shopify, Wix, Webflow, Framer: what your platform actually lets you do for AI" goes signal by signal through what remains reachable on each.

The ceiling is lower, and it is known before you start. That is the only honest way to treat these platforms: you will never receive a recommendation your site cannot apply, and your score will never be dragged down by a file you are not allowed to create.

How do you check that the deployment did anything?

A deployment is verified by running the scan again: the same 19 signals, and the corrected signal must have changed state. A file that is deployed but unreachable, because a cache holds it back, a redirect diverts it or it returns an error, is marked "not measured", not "passed". The report shows how many of the 19 signals were actually verified, which tells you immediately whether the problem lies in the file or in the measurement.

The scan measures eligibility. The outcome is measured differently: through weekly citation tracking across five AI assistants, ChatGPT, Claude, Perplexity, Gemini and Le Chat, on questions your customers actually ask. These are two distinct measurements, and neither promises a citation. Keep a sense of scale too: Ahrefs, in its February 4, 2026 update covering 300,000 keywords between December 2023 and December 2025, found that the click-through rate of the first organic result drops by 58% when an AI Overview is shown. Deploying for AI is about the discovery that now happens inside answers; it adds to Google, it does not replace it.

When is deploying the wrong spend?

Deploying assets for AI is the wrong spend in at least four situations, and an honest report has to name them.

• Your site has nothing to cite. A reading guide pointing to three eighty-word pages changes nothing: write first, deploy second.
• Nobody mentions you outside your own site. Technical eligibility with no external source produces little. A first-year budget may be better spent on a well-kept Google Business Profile, a serious trade directory or a local press article.
• Your platform is locked and the reachable signals are already green. A monthly subscription will not change that; a free scan now and then is enough to keep watch.
• You have a developer and a single site. The method is public and the export exists: you can do the work yourself and only come back for tracking.

In every other case, the question is not whether the scan is any good. It is who in your company will press the button, and how many weeks will pass before they do.