PHII Labs

Service

AI search visibility: SEO, AEO and GEO

More buyers now ask ChatGPT and Perplexity before they search Google, and a brand missing from the cited sources is absent from that answer

We shape how ChatGPT, Perplexity, Gemini and AI Overviews read your brand, measure it with fixed prompt sets, and never promise inclusion

Capabilities

What we build

  • 01

    AI-visibility audit across ChatGPT, Perplexity, Gemini, AI Overviews

  • 02

    Entity and structured-data engineering

  • 03

    Answer-first content architecture (AEO)

  • 04

    Original-data assets that earn citations

  • 05

    llms.txt and AI-crawler policy

  • 06

    Monthly citation tracking against a fixed prompt set

Proof

Systems we shipped

FAQ

Can you audit whether my brand is cited by ChatGPT, Gemini, Perplexity and Google AI Overviews?

Yes. We run a fixed set of buyer prompts across each engine, record which domains are cited and in what position, and compare your brand with named competitors. The audit ends with a prioritized fix list

How do you measure AI-search visibility without promising inclusion?

We rerun the same prompt set monthly and report the citation table: methods and measured results. No engine offers guaranteed inclusion, so any vendor promising it is selling something they do not control

What structured data should I use for AI search?

Organization, Person, BlogPosting, FAQPage and BreadcrumbList, consistent with what is visible on the page. Schema clarifies who you are and what you offer; it does not guarantee a citation on its own

Does Google use llms.txt?

Google states that AI Overviews need no special files and does not use llms.txt today. Publishing one is a cheap experiment for other engines, not a ranking lever

How do I allow AI search crawlers in robots.txt?

A permissive allow rule for all user agents already covers GPTBot, ClaudeBot and PerplexityBot. Explicit per-bot rules are only needed if your robots.txt blocks crawlers by default

Start with a free audit

A 30-minute call: we map one workflow and show where automation pays back first