Dashboard
AI Labs Audit
Last audit: 05/15/2026 12:39 PMGlobal diagnostic
Your AI visibility score at a glance.
AI presence
How AI engines cite your brand — when, why, against whom.
Qualite des mentions
No data — run a new audit
Brand Safety
Performance by AI engine
Which model cites you best: ChatGPT, Sonar, Claude, others.
Score without Internet
What AIs know about you by defaultScore with Internet
What AIs find when searching| AI Model | Score | Sentiment | Position | Mention Rate |
|---|---|---|---|---|
|
Gpt 5 Mini:Online
WEB
|
6.7/10 |
6.8
|
#1.5 |
92.9%
|
|
Gpt 5 Mini
NATIF
|
6.1/10 |
5.7
|
#1.7 |
87.1%
|
|
Sonar
WEB
|
6.2/10 |
6.5
|
#1.7 |
87.1%
|
|
Claude Haiku 4.5
NATIF
|
3.4/10 |
2.5
|
#2.7 |
85.7%
|
|
Grok 4.1 Fast:Online
WEB
|
6.6/10 |
6.4
|
#1.6 |
84.3%
|
|
Gemini 2.0 Flash 001:Online
WEB
|
5.6/10 |
5.3
|
#2.3 |
80.0%
|
|
Grok 4.1 Fast
NATIF
|
5.4/10 |
5.3
|
#1.6 |
78.6%
|
|
Gemini 2.0 Flash
NATIF
|
5.0/10 |
4.2
|
#2.0 |
77.1%
|
|
Claude Haiku 4.5:Online
NATIF + WEB
|
4.3/10 |
4.3
|
#1.7 |
60.0%
|
S1 — Visibility & Awareness
4/4 categories testedS2 — Authority & Trust (E-E-A-T)
5/5 categories testedS3 — Sentiment & Perception
3/3 categories testedS4 — Competitive Positioning
5/5 categories testedS5 — Search Intent
8/8 categories testedS6 — Customer Journey & Recommendation
5/5 categories testedGEO technical audit
Is your site crawlable, citable, optimised for AI?
SSR / AI Crawlability
Entity Health Check
Citation Readiness
Source Authority
AI Perception
- GPTBot
- OAI-SearchBot
- ChatGPT-User
- ClaudeBot
- Claude-SearchBot
- Claude-Web
- anthropic-ai
- PerplexityBot
- Perplexity-User
- Google-Extended
- GoogleOther
- Applebot-Extended
- meta-externalagent
- Meta-ExternalAgent
- Bytespider
- CCBot
- Bingbot
- Amazonbot
- cohere-ai
- Verify that robots.txt is accessible at /robots.txt (HTTP 200)
- Verify no global block User-agent: * / Disallow: /
- Verify GPTBot is NOT in a Disallow directive
- Verify ClaudeBot is NOT in a Disallow directive
- Verify Claude-SearchBot is allowed
- Verify OAI-SearchBot is allowed
- Verify PerplexityBot is allowed
- Verify Google-Extended is allowed
- Verify Applebot-Extended is not blocked
- Ensure public content directories (/blog/, /services/, /about/) are accessible
Run an AI Labs Audit before/after changes. Check server logs for AI bot requests within 2-4 weeks. Test manually with curl -A "GPTBot" https://yoursite.com/.
- Verify /sitemap.xml returns HTTP 200
- Verify sitemap is referenced in robots.txt via Sitemap: https://yoursite.com/sitemap.xml
- Verify the XML is valid (no parsing errors)
- Verify <lastmod> tags are present on each URL
- Verify <lastmod> dates match actual update dates
- Verify there are no error URLs (404, 500) in the sitemap
Check Google Search Console for sitemap indexation status. Monitor server logs for AI bot sitemap access.
- Create a /llms.txt file at the site root
- Add an H1 title with the company name
- Add a summary blockquote (2-3 sentences describing the business)
- List key pages with URL and short description (home, services, about, pricing, FAQ, blog)
- Use valid Markdown format
- Test accessibility with curl https://yoursite.com/llms.txt
- Optional: also create a /llms-full.txt file with full content
Monitor server logs for llms.txt file access. Note: direct impact is not yet proven, it's an AI readiness signal.
- Verify the site is accessible via HTTPS
- Verify the SSL certificate is valid and not expired
- Verify HTTP → HTTPS redirect is in place (301 permanent, NOT 302)
- Verify no mixed content (HTTP resources on HTTPS pages)
- Verify all internal URLs use HTTPS
Immediate test via browser or curl -I https://yoursite.com. Certificate must be valid.
nginx- Test site access with GPTBot user-agent: curl -A "GPTBot/1.0" → should return 200
- Test with ClaudeBot: curl -A "ClaudeBot/1.0" → should return 200
- Test with PerplexityBot: curl -A "PerplexityBot" → should return 200
- If Cloudflare: verify "Bot Fight Mode" is not in aggressive mode
- If Cloudflare: verify AI Crawl Control has desired AI crawlers set to "Allow"
- Check custom WAF rules: no rule should generically block user-agents containing "bot"
- Verify no CAPTCHA challenge is returned to AI bots
- Verify WAF rules and AI Crawl Control settings do not contradict each other
Re-run curl tests after changes. Monitor Cloudflare analytics for AI bot requests: they should show as "Allowed".
- Add Organization JSON-LD script on homepage (name, url, logo, description, contactPoint, sameAs)
- Add WebSite JSON-LD script on homepage
- Add Article or BlogPosting JSON-LD script on each blog article
- Add FAQPage JSON-LD script on pages with FAQs
- Add BreadcrumbList JSON-LD script for breadcrumb navigation
- Add Person JSON-LD script on author/team pages
- For service/product pages: add Product or Service with Offer
- Validate each schema with Google Rich Results Test
- Verify JSON-LD is server-side rendered (SSR), not injected via client JavaScript
Validate via Google tools. Run an AI Labs Audit and compare the Structured Data score.
- Verify og:title is present on all pages (unique per page)
- Verify og:description is present (complementary to title)
- Verify og:image with a quality image (1200x630px recommended)
- Verify og:image:alt with descriptive text
- Verify og:url points to the canonical URL
- Verify og:type is present (website for home, article for articles)
- For articles: add article:published_time and article:modified_time
- Also add Twitter Card tags (twitter:card, twitter:title, twitter:description, twitter:image)
- Test rendering with Facebook Sharing Debugger and LinkedIn Post Inspector
Test sharing a URL on LinkedIn/Facebook/Twitter and verify the preview is correct and complete.
- Verify each page has a <link rel="canonical" href="..."> tag
- Verify canonical is self-referential (points to the same page)
- Verify consistency between canonical, og:url and actual URL
- Verify canonicals don't point to 404s or redirects
- Verify pages with UTM parameters have a canonical to the clean version
- Verify protocol consistency (all HTTPS)
Crawl the site with Screaming Frog or similar tool and check the "Canonical" column for inconsistencies.
- Add "dateModified" to all Article/BlogPosting JSON-LD scripts
- Add "datePublished" if missing
- Verify dateModified is more recent than datePublished
- Display the update date visibly on the page ("Updated on...")
- Update the corresponding <lastmod> in sitemap.xml
- Set up a regular update process (at least quarterly)
Validate JSON-LD with Rich Results Test. Run AI Labs Audit and verify the check turns green.
- Each page has a unique <title>
- Length between 30 and 60 characters
- Contains the main keyword or page topic
- No generic title ("Home", "Page", domain name alone)
- Consistent with the page H1
- No duplication with other site pages
- Includes brand name (at end of title, after separator)
Crawl the site and extract all titles. Verify uniqueness and length. Track CTR evolution in Google Search Console.
- Each page has a meta description
- Length between 120 and 160 characters
- Informative and descriptive content (not hollow marketing)
- Unique per page
- Contains a direct answer or actionable summary
- Includes an implicit call to action when relevant
Crawl the site to check coverage. Track CTR in Google Search Console.
- Identify the 5-10 most frequent customer/prospect questions
- Write direct, factual answers in 2-4 sentences each
- Integrate the FAQ section on key pages (services, pricing, home)
- Use <h2> or <h3> tags for each question
- Implement FAQPage schema in JSON-LD with question/answer pairs
- Validate schema via Rich Results Test
- Write questions in natural conversational language
Validate FAQPage schema. Test questions in ChatGPT, Claude and Perplexity to see if the site appears in responses.
- Each page has a single H1 describing the main topic
- H2s structure the main sections
- H3s detail the subsections
- No level skipping (no H1 → H4 directly)
- Headings are descriptive and self-explanatory
- No headings used for styling purposes
- Each H2 section is relatively self-contained (extractable alone by an LLM)
Use an SEO audit tool (Screaming Frog, Semrush) to validate heading structure.
- Check word count of main content on each page (excluding nav, footer)
- Pages under 2000 words should be enriched or consolidated
- No "under construction" or placeholder pages
- Service pages should have at least 500 words of substantial content
- Include data, concrete examples, and use cases
- Avoid generic or duplicated content from other sources
Count words on key pages. Run audit again to verify the check turns green.
- Create a Blog or News section on the site
- Publish a first in-depth article on your domain of expertise
- Each article must have: named author, visible publication date, Article/BlogPosting schema, 800+ words, images with alt text
- Set a publication rhythm (minimum 1 article/month)
- Cover customer questions (guide, comparison, how-to formats)
- Set up internal links between articles and service pages
- Ensure articles are indexed in the sitemap
Track organic traffic to the blog section. Regularly test covered topics in ChatGPT/Claude/Perplexity to see if the site is cited.
- Convert key stats into <blockquote> with source
- Add a <dl> 'Key terms' with 5-10 definitions
- Replace ranking <ul> with numbered <ol>
- Wrap key figures in <aside class='stat'> or <div class='callout'>
- Add at least 1 comparative <table> (>=2 data rows)
Score 0-100 based on count of 5 sub-types on homepage. Pass if score >= 30. See Citation-Readiness card in dashboard.
- Identify key questions your clients ask
- Reformulate long paragraphs into 'implicit question + 40-50-word answer' blocks
- Place a standalone answer at the start of each h2/h3 section
- Avoid paragraphs >100 words without syntactic break
Automatic check: ratio of 40-50-word paragraphs over total. Pass if >=30%.
- Identify 30 key terms in your domain (competitor analysis)
- Check density (>=0.5%) of each term on homepage and key pages
- Enrich content to fill underdensified terms
- Align glossary / FAQ with these 30 terms
Automatic check: average density of top-30 co-occurring terms vs target. Pass if average >=0.5%.
- Page is accessible from main navigation or footer
- Contains company history (founding date, founders)
- Contains verifiable legal information (registration number, address, legal form)
- Describes mission, values, positioning
- Mentions certifications, labels, partnerships
- Contains at least 400 words of substantial content
- Organization schema implemented with the same information
- Team or office photos (proof of real existence)
Ask ChatGPT, Claude and Perplexity "What is [company name]?" and verify if returned information matches the About page.
- Each content author has a biography on the site
- Bio contains: full name, position, expertise area, career summary
- Mentions certifications, degrees, or years of experience
- Professional photo
- Link to LinkedIn profile
- Person schema implemented (name, jobTitle, description, sameAs, worksFor)
- Blog articles display author name and bio
- No content published under "Admin" or "The team" without attribution
Verify Person schema is valid. Test "[expert name] + [field]" in AI to see if expertise is recognized.
- Social media links present on the site (footer or contact page)
- All links are functional (no 404s or deleted profiles)
- Profiles are active (last publication < 3 months)
- Brand name is consistent between site and all profiles
- Organization schema with sameAs property listing all profiles
- Minimum 2 active networks (LinkedIn is most important for B2B)
- Profiles link back to the website
Check consistency of Google Knowledge Panel for the brand. Validate Organization schema.
- Identify your registration number for your country (SIREN/SIRET, Company Number, KVK, IDE, BCE, etc.)
- Add it to your Legal Notice / Impressum / Terms page
- For France: add SIREN, SIRET, RCS and registration city
- For UK: add Company Number (8 characters) and place of registration (Companies House)
- For Germany/Austria: add Handelsregisternummer (HRA/HRB + number) in the Impressum
- For Switzerland: add IDE number (CHE-xxx.xxx.xxx)
- Ensure the number is in plain text (not in an image)
Check that the registration number is visible as text in the legal notices. The automated audit detects it via scraping.
- Add a contact email in the footer or contact page (mailto: format preferred)
- Add a phone number (tel: format preferred)
- Ensure these are in plain text, not only behind a contact form
- Ideally: add Schema.org ContactPoint markup
Check for mailto: and/or tel: links on the site. The automated audit detects them.
- Add the full name of the director/manager in the legal notices
- Specify their role (CEO, Manager, Director of Publication)
- Ideally: add Schema.org Person markup with sameAs to LinkedIn
- If applicable: mention director qualifications or certifications
Check that the director name appears in the legal notices or impressum. The automated audit detects it.
- Choose a unique canonical form of the name (e.g., "CITEL")
- Audit the site (header, footer, og:site_name, Schema Organization) to remove variants
- Align Schema.org Organization.name with canonical form
- Check consistency on LinkedIn, Wikipedia, third-party profiles
Automatic check: variant detection on homepage + key pages. Pass if <=2 variants.
- Check for absence of <meta name="robots" content="noai"> in <head>
- Check for absence of X-Robots-Tag: noai HTTP header
- If present, remove it to allow AI indexation
The automated audit detects the noai meta tag and X-Robots-Tag header.
- Add a <link rel="alternate" type="application/rss+xml"> in <head>
- Ensure the feed is accessible (HTTP 200, valid XML)
- Include at least the 10 most recent modified articles/pages
- Verify each item has a <pubDate> or <updated> date
The AEO section of the dashboard automatically detects RSS or Atom feeds.
- Implement AQA Basic markup on your FAQ pages (dates + sources)
- Add dateCreated and dateModified on each question
- Add a citation (source URL) on each answer
- Declare conformanceLevel in the Article block
- Validate with the AQA validator: github.com/sarsator/aqa-specification
The AEO section of the dashboard automatically detects AQA presence and level (Basic/Standard/Full).
- Verify dateModified is present in Schema.org JSON-LD
- Update key pages at least every 90 days
- Add current statistics (current year) in content
- Maintain a blog with regular publications
The Citation Readiness v2 module automatically evaluates content freshness.
- Check dateModified on key pages via Schema Article/WebPage
- Update key content (stats, sources, dates) every <90 days
- Display the last-update date visibly (page footer)
- Add a changelog/revision history on important pages
Automatic check: HTTP last-modified header + Schema dateModified. Pass if <=90 days on homepage.
Page freshness 100 — click to expand
Action plan
What you can do now, by priority.
Respond professionally to negative reviews on Google, forums and review sites.
Verify all sameAs links in Schema.org point to valid and active pages.
LLMs (AI Overviews, Perplexity, Claude) prioritize blockquotes, <dl> definition lists, data tables and callouts (class="callout", "tldr", "stat") for verbatim attributed citation. A page without any of these blocks is rarely quoted directly. Add 2-3 clear stat callouts + 1-2 structured definitions on your key pages.
LLMs identify entities through cross-page textual consistency. Using more than 2 variants of the name (e.g. "CITEL", "Citel SA", "Group VTS") muddies entity resolution. Pick ONE canonical name and use it everywhere, with variants only in sameAs tags and legal mentions.
Le SIREN/SIRET n'est pas visible. Les IA associent la transparence légale à la fiabilité.
For each H2/H3, the first sentence must be a complete standalone 40-50 word answer that can be extracted and cited as-is. Avoid "It depends…" or sentences that refer to prior context. Preferred format for AI Overviews and Perplexity direct citation.
Beyond SEO, multimodal LLMs read alt-texts to interpret images. Describe visual content and brand link, not just keywords.
Create and distribute content highlighting strengths, customer testimonials, case studies and concrete results.
If the brand is notable enough, create a Wikipedia page with verifiable sources. Otherwise, enrich the Wikidata entry.
Use audit source tracing to identify URLs that generate negative sentiment in AI responses.
When ChatGPT/Claude/Gemini/Perplexity give contradictory facts about your brand (50 vs 200 employees, 2015 vs 2018, Paris vs Lyon HQ), it signals training-source confusion. Identify the wrong sources and update them.
LLMs prioritize sources that produce their own data. Publish 1-2 studies/surveys/benchmarks per year with explicit attribution ('Our research shows', 'According to our data'). +30-40% AI visibility boost (Princeton GEO).
Actions deprioritized by the GEO engine. Click to activate.