acePublic attention
30-day English Wikipedia pageviews, normalized across the measured set
AI company impact profile
Loading company evidence…
Loading company impact history and evidence.
AI company impact profile
Loading company impact history and evidence.
AI company impact profile
An AI-native answer engine operating in the search and publishing ecosystem.
Rank #8 · Emerging observable footprint
Stable attention
Data effective Aug 31, 2026, 12:00 AM UTC · recomputed Sep 1, 2026, 2:14 PM UTC
How to read 31
The score normalizes public attention, official developer activity, evidence-backed gains, evidence-backed problems, and source breadth across the measured company set.
It does not mean: that Perplexity is the “best,” safest, most valuable, or most responsible company. Documented problems contribute to visible footprint rather than being hidden as a negative subtraction.
Read the complete methodology →Normalized components
30-day English Wikipedia pageviews, normalized across the measured set
stars and public repositories in the company’s official GitHub organization
independent stored sources attached to company-linked gain readings
independent stored sources attached to company-linked problem readings
unique independent sources in the published Truvace record
Observed history
Fixed 0–100 scale
Lines connect observed snapshots only. Gaps do not mean a score stayed unchanged. Diamond markers indicate a methodology-version transition.
| Effective date | Perplexity |
|---|---|
| Jul 18, 2026 | 20 · visible-impact-v1 |
| Jul 19, 2026 | 23 · visible-impact-v2 · method changed |
| Jul 20, 2026 | 24 · visible-impact-v2 |
| Jul 21, 2026 | 24 · visible-impact-v2 |
| Jul 22, 2026 | 24 · visible-impact-v2 |
| Jul 23, 2026 | 24 · visible-impact-v2 |
| Jul 24, 2026 | 33 · visible-impact-v2 |
| Jul 25, 2026 | 33 · visible-impact-v2 |
| Jul 26, 2026 | 33 · visible-impact-v2 |
| Jul 27, 2026 | 34 · visible-impact-v2 |
| Jul 28, 2026 | 34 · visible-impact-v2 |
| Jul 29, 2026 | 34 · visible-impact-v2 |
| Jul 30, 2026 | 46 · visible-impact-v2 |
| Jul 31, 2026 | 34 · visible-impact-v2 |
| Aug 1, 2026 | 33 · visible-impact-v2 |
| Aug 2, 2026 | 33 · visible-impact-v2 |
| Aug 3, 2026 | 34 · visible-impact-v2 |
| Aug 4, 2026 | 33 · visible-impact-v2 |
| Aug 5, 2026 | 45 · visible-impact-v2 |
| Aug 6, 2026 | 14 · visible-impact-v2 |
| Aug 7, 2026 | 32 · visible-impact-v2 |
| Aug 8, 2026 | 32 · visible-impact-v2 |
| Aug 9, 2026 | 32 · visible-impact-v2 |
| Aug 10, 2026 | 32 · visible-impact-v2 |
| Aug 11, 2026 | 31 · visible-impact-v2 |
| Aug 12, 2026 | 31 · visible-impact-v2 |
| Aug 13, 2026 | 31 · visible-impact-v2 |
| Aug 14, 2026 | 31 · visible-impact-v2 |
| Aug 15, 2026 | 43 · visible-impact-v2 |
| Aug 16, 2026 | 57 · visible-impact-v2 |
| Aug 17, 2026 | 43 · visible-impact-v2 |
| Aug 18, 2026 | 30 · visible-impact-v2 |
| Aug 19, 2026 | 30 · visible-impact-v2 |
| Aug 20, 2026 | 30 · visible-impact-v2 |
| Aug 21, 2026 | 30 · visible-impact-v2 |
| Aug 22, 2026 | 30 · visible-impact-v2 |
| Aug 23, 2026 | 30 · visible-impact-v2 |
| Aug 24, 2026 | 43 · visible-impact-v2 |
| Aug 25, 2026 | 30 · visible-impact-v2 |
| Aug 26, 2026 | 31 · visible-impact-v2 |
| Aug 27, 2026 | 31 · visible-impact-v2 |
| Aug 28, 2026 | 31 · visible-impact-v2 |
| Aug 29, 2026 | 31 · visible-impact-v2 |
| Aug 30, 2026 | 31 · visible-impact-v2 |
| Aug 31, 2026 | 31 · visible-impact-v2 |
No interpolation
| Effective | Score | Rank | Gain | Problem | Method |
|---|---|---|---|---|---|
| Aug 31, 2026, 12:00 AM UTC | 31 (0) | #8 (0) | 0 | 38 | visible-impact-v2 |
| Aug 30, 2026, 12:00 AM UTC | 31 (0) | #8 (0) | 0 | 38 | visible-impact-v2 |
| Aug 29, 2026, 12:00 AM UTC | 31 (0) | #8 (0) | 0 | 38 | visible-impact-v2 |
| Aug 28, 2026, 12:00 AM UTC | 31 (0) | #8 (0) | 0 | 38 | visible-impact-v2 |
| Aug 27, 2026, 12:00 AM UTC | 31 (0) | #8 (0) | 0 | 38 | visible-impact-v2 |
| Aug 26, 2026, 12:00 AM UTC | 31 (+1) | #8 (0) | 0 | 38 | visible-impact-v2 |
| Aug 25, 2026, 12:00 AM UTC | 30 (-13) | #8 (0) | 0 | 38 | visible-impact-v2 |
| Aug 24, 2026, 12:00 AM UTC | 43 (+13) | #8 (0) | 0 | 38 | visible-impact-v2 |
| Aug 23, 2026, 12:00 AM UTC | 30 (0) | #8 (0) | 0 | 38 | visible-impact-v2 |
| Aug 22, 2026, 12:00 AM UTC | 30 (0) | #8 (0) | 0 | 38 | visible-impact-v2 |
| Aug 21, 2026, 12:00 AM UTC | 30 (0) | #8 (0) | 0 | 39 | visible-impact-v2 |
| Aug 20, 2026, 12:00 AM UTC | 30 (0) | #8 (0) | 0 | 39 | visible-impact-v2 |
Evidence profile
Query volume, retention, and publisher-licensing coverage are mostly private.
Linked to the record
Claims are sorted by their existing Sourced Index impact score. Each card links to its Truvace record and original sources; company marketing is not treated as independent proof.
0 gain · 4 problem · 0 high-evidence
On July 14 2026, Germany's media regulator ruled that Google's AI Overviews and Perplexity AI must comply with the country's media laws, after a court held Google accountable for inaccuracies in AI-produced content and defined AI summaries as proprietary material.
Jul 25, 2026
On July 14, 2026, Germany's media regulator said Google's AI Overviews and Perplexity AI are subject to German media laws. The announcement followed a German court ruling that held Google liable for inaccurate information generated by its AI Overviews feature.
Jul 25, 2026
As of the July 14 2026 report, Germany's media regulator decided that AI-generated content from Google and Perplexity AI falls under national media laws, and a German court ruled Google directly liable for misinformation from its AI Overview feature.
Jul 25, 2026
On 2026-07-14, Germany's media regulator determined that Google's AI Overviews and Perplexity AI fall under national media law obligations. The report identifies the two AI search products as subject to compliance requirements in Germany.
Jul 25, 2026
Recorded changes