🧠 Food for thought

Implications, context, and why it matters.

Comet’s Android debut lacks usage metrics to gauge traction

•  While Perplexity calls Comet “AI-native”, the company has not given Android-specific user numbers in its launch coverage 1.
•  The browser launched on desktop in July with a waitlist. It opened to everyone in October and arrived on Android soon after. The short timeline invites questions about maturity and reliability at scale 1.
•  Perplexity plans to ship an ad blocker. That clashes with its goal to collect data for personalized ads (personalized ad targeting typically relies on tracking user behavior, which ad blockers aim to limit). The mixed signals could erode user trust 2.

Publishers should optimize for AI crawlers as answer engines reshape discovery

•  Browsers like Comet push discovery toward AI answers over classic search results. Creators could lose visibility if they block or limit PerplexityBot (the company’s web crawler, automated software that indexes webpages) 3.
•  Publishers can manage Perplexity’s access with robots.txt (a standard website file that tells crawlers what they can access) 4. Changes take up to 24 hours to apply. These rules work independently from other bots’ settings.
•  Blocking PerplexityBot may cut traffic from AI search results 3. A better move is Answer Engine Optimization (AEO), which means structuring content so AI systems can summarize it accurately. Publishers will need to trust platforms’ citation practices.