<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Lucien Varlet</title>
  <id>https://aivisibilityfrance.com/en/field-log/feed.xml</id>
  <link href="https://aivisibilityfrance.com/en/field-log/feed.xml" rel="self"/>
  <link href="https://aivisibilityfrance.com/en/field-log/" rel="alternate"/>
  <updated>2026-05-26T00:00:00Z</updated>
  <entry>
    <title>Unknown and Misdescribed Need Different Fixes</title>
    <id>https://aivisibilityfrance.com/en/field-log/unknown-vs-misdescribed-ai/</id>
    <link href="https://aivisibilityfrance.com/en/field-log/unknown-vs-misdescribed-ai/" rel="alternate"/>
    <published>2026-05-26T00:00:00Z</published>
    <updated>2026-05-26T00:00:00Z</updated>
    <summary>How to separate AI systems that ignore a business from AI answers that know it wrongly, then choose the right correction path.</summary>
  </entry>
  <entry>
    <title>Seasonal Businesses Must Time Their AI Audit</title>
    <id>https://aivisibilityfrance.com/en/field-log/seasonal-ai-visibility-audit/</id>
    <link href="https://aivisibilityfrance.com/en/field-log/seasonal-ai-visibility-audit/" rel="alternate"/>
    <published>2026-05-12T00:00:00Z</published>
    <updated>2026-05-12T00:00:00Z</updated>
    <summary>Why seasonal French businesses should time an AI visibility audit around buyer prompts, demand windows and cited source freshness.</summary>
  </entry>
  <entry>
    <title>A Wrong Description Is an AI Visibility Failure</title>
    <id>https://aivisibilityfrance.com/en/field-log/wrong-ai-description-visibility/</id>
    <link href="https://aivisibilityfrance.com/en/field-log/wrong-ai-description-visibility/" rel="alternate"/>
    <published>2026-05-07T00:00:00Z</published>
    <updated>2026-05-07T00:00:00Z</updated>
    <summary>Why erreur description entreprise IA is not a minor wording issue, and how French SMBs can score accuracy separately from presence.</summary>
  </entry>
  <entry>
    <title>A Competitor Jump Starts With Their Cited Sources</title>
    <id>https://aivisibilityfrance.com/en/field-log/competitor-ai-cited-sources/</id>
    <link href="https://aivisibilityfrance.com/en/field-log/competitor-ai-cited-sources/" rel="alternate"/>
    <published>2026-04-28T00:00:00Z</published>
    <updated>2026-04-28T00:00:00Z</updated>
    <summary>How to investigate a competitor suddenly visible in AI answers by reading cited sources, not guessing from rankings or one prompt.</summary>
  </entry>
  <entry>
    <title>Mentions Mean Little Without Competitor Citation Share</title>
    <id>https://aivisibilityfrance.com/en/field-log/ai-citation-share-competitors/</id>
    <link href="https://aivisibilityfrance.com/en/field-log/ai-citation-share-competitors/" rel="alternate"/>
    <published>2026-04-23T00:00:00Z</published>
    <updated>2026-04-23T00:00:00Z</updated>
    <summary>How part de citations IA helps French SMBs measure AI visibility against named competitors instead of trusting occasional mentions.</summary>
  </entry>
  <entry>
    <title>French and English Prompts Often Give Different Verdicts</title>
    <id>https://aivisibilityfrance.com/en/field-log/french-english-ai-prompt-tests/</id>
    <link href="https://aivisibilityfrance.com/en/field-log/french-english-ai-prompt-tests/" rel="alternate"/>
    <published>2026-04-09T00:00:00Z</published>
    <updated>2026-04-09T00:00:00Z</updated>
    <summary>Why test IA français anglais matters for French SMBs measuring AI visibility across customer prompts, engines, sources and languages.</summary>
  </entry>
  <entry>
    <title>A First AI Baseline Must Be Repeatable</title>
    <id>https://aivisibilityfrance.com/en/field-log/first-ai-visibility-baseline/</id>
    <link href="https://aivisibilityfrance.com/en/field-log/first-ai-visibility-baseline/" rel="alternate"/>
    <published>2026-04-03T00:00:00Z</published>
    <updated>2026-04-03T00:00:00Z</updated>
    <summary>How to run an AI visibility audit that becomes a monthly baseline, not a one-time diagnostic screenshot.</summary>
  </entry>
  <entry>
    <title>Hallucinated Business Facts Need a Correction Ledger</title>
    <id>https://aivisibilityfrance.com/en/field-log/correct-ai-business-errors/</id>
    <link href="https://aivisibilityfrance.com/en/field-log/correct-ai-business-errors/" rel="alternate"/>
    <published>2026-04-01T00:00:00Z</published>
    <updated>2026-04-01T00:00:00Z</updated>
    <summary>How to correct AI business errors with a tracked correction ledger: trace the false fact, strengthen better sources and retest the same prompts.</summary>
  </entry>
  <entry>
    <title>The Cited Source Matters More Than the Mention</title>
    <id>https://aivisibilityfrance.com/en/field-log/track-ai-cited-sources/</id>
    <link href="https://aivisibilityfrance.com/en/field-log/track-ai-cited-sources/" rel="alternate"/>
    <published>2026-03-18T00:00:00Z</published>
    <updated>2026-03-18T00:00:00Z</updated>
    <summary>How to log AI-cited sources so a French SMB can see which page feeds an AI answer, not just whether the business is named.</summary>
  </entry>
  <entry>
    <title>Generative Share of Voice Beats Keyword Rank</title>
    <id>https://aivisibilityfrance.com/en/field-log/generative-share-of-voice-ai/</id>
    <link href="https://aivisibilityfrance.com/en/field-log/generative-share-of-voice-ai/" rel="alternate"/>
    <published>2026-03-13T00:00:00Z</published>
    <updated>2026-03-13T00:00:00Z</updated>
    <summary>How to measure generative AI share of voice when answer engines name competitors differently from ordinary keyword rankings.</summary>
  </entry>
  <entry>
    <title>Different AI Engines Need Separate Visibility Ledgers</title>
    <id>https://aivisibilityfrance.com/en/field-log/compare-ai-engines-ledgers/</id>
    <link href="https://aivisibilityfrance.com/en/field-log/compare-ai-engines-ledgers/" rel="alternate"/>
    <published>2026-03-04T00:00:00Z</published>
    <updated>2026-03-04T00:00:00Z</updated>
    <summary>How to compare ChatGPT, Perplexity, Copilot and Google AI Overviews with separate AI visibility ledgers before trusting a score.</summary>
  </entry>
  <entry>
    <title>AI Visibility Can Drop Without a Site Change</title>
    <id>https://aivisibilityfrance.com/en/field-log/ai-visibility-drop-no-site-change/</id>
    <link href="https://aivisibilityfrance.com/en/field-log/ai-visibility-drop-no-site-change/" rel="alternate"/>
    <published>2026-03-04T00:00:00Z</published>
    <updated>2026-03-04T00:00:00Z</updated>
    <summary>Why AI visibility can fall without a website edit, and how French SMBs can monitor source shifts, model shifts and answer-pattern changes.</summary>
  </entry>
  <entry>
    <title>Multi-Location Visibility Needs Per-Location Prompts</title>
    <id>https://aivisibilityfrance.com/en/field-log/multi-location-ai-visibility-prompts/</id>
    <link href="https://aivisibilityfrance.com/en/field-log/multi-location-ai-visibility-prompts/" rel="alternate"/>
    <published>2026-02-20T00:00:00Z</published>
    <updated>2026-02-20T00:00:00Z</updated>
    <summary>How to test multi-location AI visibility with city, service and language prompts instead of trusting one national AI answer.</summary>
  </entry>
  <entry>
    <title>One ChatGPT Answer Is Not a Visibility Measurement</title>
    <id>https://aivisibilityfrance.com/en/field-log/measure-chatgpt-answers-business/</id>
    <link href="https://aivisibilityfrance.com/en/field-log/measure-chatgpt-answers-business/" rel="alternate"/>
    <published>2026-02-12T00:00:00Z</published>
    <updated>2026-02-12T00:00:00Z</updated>
    <summary>Why measuring ChatGPT answers for a business requires repeated runs, engine samples and a ledger, not one flattering screenshot.</summary>
  </entry>
  <entry>
    <title>Customer Prompts Reveal AI Visibility Better Than Service Menus</title>
    <id>https://aivisibilityfrance.com/en/field-log/customer-prompts-ai-visibility-test/</id>
    <link href="https://aivisibilityfrance.com/en/field-log/customer-prompts-ai-visibility-test/" rel="alternate"/>
    <published>2026-01-29T00:00:00Z</published>
    <updated>2026-01-29T00:00:00Z</updated>
    <summary>How to test business AI visibility by building prompt sets from real buyer wording instead of internal service-menu terms.</summary>
  </entry>
</feed>