AI Visibility Audit

Config.Json

19
of 100
Grade F · Invisible to AI engines
ChatGPT (GPT-4o)
15
No Wikipedia article, but 47 news mentions — ChatGPT will give fragmented info pulled from articles. Risk of outdated or confused descriptions.
Perplexity
45
47 recent news citations — Perplexity will return current, link-cited info. Strong real-time visibility.
Gemini (Google)
10
No website easily findable. Gemini will struggle to show anything beyond a name match.
Claude.ai
16
No Wikipedia and weak site signals. Claude will be cautious and likely respond with "I don't have specific information on..."
Bing Copilot
10
Limited Bing visibility. Copilot may not surface much beyond basic search results.
How scored: deterministic checks across Wikipedia, Google News RSS, DuckDuckGo, and the business's own website (if found). Each engine score is rule-based using documented citation behavior, not LLM inference. Free forever.

Public signals we found

Website
Could not auto-detect
Wikipedia
No article
Recent news mentions
47 articles (past year)
DuckDuckGo infobox
✗ Not found

How each engine answers 8 standard customer questions

1. Who is Config.Json?
Best · Perplexity
Engines may not confidently identify this business.
Gap
No Wikipedia article — ChatGPT and Claude will hedge.
2. What does Config.Json do? What services do they offer?
Best · Perplexity
Limited info — engines will give generic answers.
Gap
No discoverable website — Gemini struggles.
3. Is Config.Json good? What do customers say about them?
Best · Perplexity
47 news mentions provide some sentiment signal.
Gap
No gap.
4. How much does Config.Json charge?
Best · Perplexity
No pricing data accessible.
Gap
No website to scan pricing from.
5. Where is Config.Json located? What are their hours?
Best · Perplexity
Location not in major AI knowledge bases.
Gap
No GBP / DDG infobox — Gemini and Copilot lack location data.
6. How is Config.Json different from competitors?
Best · Perplexity
Engines will struggle to differentiate this business from competitors.
Gap
Minor gap.
7. Should I trust Config.Json? Are they legitimate?
Best · Perplexity
Weak trust signal stack — AI engines will hedge their answers.
Gap
Add diverse trust signals — website + reviews + press + Wikipedia.
8. What public sources cite or mention Config.Json?
Best · Perplexity
47 news articles
Gap
No gap.

What's holding Config.Json back from AI engines

  • No Wikipedia article — ChatGPT and Claude.ai will struggle to give confident answers about this business.
  • Could not auto-detect a website from the business name — Gemini relies heavily on website data + Google Business Profile.
  • No DuckDuckGo Instant Answer card — indicates weak general web indexing across Bing-derived engines.

5 fixes that will move the score

  1. Create a Wikipedia article (or a Wikidata entry at minimum). This single fix unlocks ChatGPT and Claude.ai dramatically.
  2. Make sure the business has a discoverable website with the business name in the homepage <title>. Multi-domain attempts (e.g. business.com, business.io) all need to point to one canonical site.
  3. Claim and complete a Google Business Profile + verify the address. Gemini and Bing Copilot both pull from this directly.
  4. Add a clear "About" page on the website with founding story, leadership names, address, and founding year. AI engines weight first-party authority pages heavily.

Need help implementing the fixes?

Our $499 website rebuild includes structured data, GBP optimization, content rewrites for AEO, and citation outreach. Live in 5 days.

Build the fixed site for $499 →

Get notified when Config.Json re-audits

We re-run this audit monthly. Get the diff in your inbox so you can track which fixes moved the score.

Audit another business