Meta AI doesn't mention your brand? Six things to check, in order
A diagnostic checklist for brands that are missing from Meta AI answers: availability, Meta's crawlers, firewall rules, prompt type, cited sources, and accuracy. What each check tells you and how to run it.
A brand that shows up in ChatGPT and Perplexity but not in Meta AI usually assumes it has a content problem. Sometimes it does. But the cause can also sit earlier in the chain, where writing new pages won't touch it.
Here's the order we check things in. Each step rules something out before you spend money on the next.
1. Is Meta AI even answering in your market?
Start with the boring one. Meta's help center says the Meta AI app and website "are not yet available everywhere", and that some features may not be available in your area. It also says the assistant runs inside Facebook, Instagram, Messenger and WhatsApp (Meta Help Center).
So before you diagnose anything, confirm that the version of Meta AI your buyers use exists in their country and language, and that your tracking runs from there. A test run from a US office says little about what a buyer in Spain sees on WhatsApp.
2. Can Meta's citation crawler reach you?
Meta documents its crawlers, and one of them is directly tied to citations. Meta says Meta-WebIndexer "navigates the web to improve Meta AI search result quality" and that allowing it in robots.txt "helps us cite and link to your content in Meta AI's responses" (Meta web crawlers).
Open your robots.txt and look for these user agents:
| User agent | Meta's stated purpose |
|---|---|
meta-webindexer | Meta AI search results and citations |
meta-externalagent | Training models, or improving products by indexing content |
meta-externalfetcher | Fetching a link at a user's request (may bypass robots.txt) |
facebookexternalhit | Link previews for shared URLs |
If you blocked the whole family to opt out of training, you also asked not to be cited. You can allow meta-webindexer and handle meta-externalagent separately. Just know that Meta's description of ExternalAgent includes indexing for products, not only training, so blocking it may have side effects. Decide it on purpose.
3. Is something else blocking it?
Robots.txt is a request. Your firewall is the actual door. Bot-management products and WAF rules can challenge or block anything that looks automated, and a crawler that gets a 403 or a challenge page never sees your content, whatever robots.txt says.
You can't see this from robots.txt. You need logs. We use Promptwatch's Agent Analytics, which records Meta-WebIndexer, Meta-ExternalAgent and Meta-ExternalFetcher from your CDN or server, checks each request against Meta's published IP ranges, and flags errors with an explanation. The question to answer is simple: did Meta-WebIndexer fetch the pages that should be cited, and did it get a 200?
Promptwatch's own data shows why this is worth checking now. Its Meta-WebIndexer report found the crawler went from about 2 percent of tracked AI crawler requests in mid-July 2026 to nearly 38 percent on August 9. If your firewall rules were going to trip over it, they've had plenty of chances.
4. Is the question one Meta AI searches for?
Not every answer comes from the web. Meta's developer docs for its model API say the model decides whether to search, and skips searching when it can answer from training data, with simple factual questions as the example (Meta search grounding). That's the API, not the consumer app, so take it as a hint rather than proof.
The practical takeaway is to look at which of your tracked prompts produce cited sources at all. If your missing prompts are ones where Meta AI answers without citing anything, you're competing with what the model already believes, which is a slower fight than winning a citation. Prioritize the prompts where Meta AI does cite pages, because those are pages you can replace.
5. Whose pages does it cite instead?
When Meta AI names a competitor and cites a source, that source is your target. It might be the competitor's own comparison page, a review site, a listicle, or a social post.
This is where per-answer records matter. Promptwatch stores every Meta AI answer with the brands named, their order, and each cited URL and its position. Its citation views then group those by page and domain, and the "My channels" filter separates your own social profiles from everyone else's. If Meta AI keeps citing one third-party roundup that leaves you out, that's a pitch, not a blog post.
6. When it does mention you, is it right?
Run a few brand prompts: "is [brand] legit", "what does [brand] cost", "[brand] vs [rival]". You're looking for wrong prices, discontinued products and old positioning. They're worth catching on an engine people use inside the same apps where they message your support team.
Fixes here are usually about making the correct fact easy to find on a page Meta can crawl, then checking the answer again in a couple of weeks.
A note on clicks
We haven't covered traffic, because it's the least settled part. Promptwatch's visitor analytics attributes AI-referred visits and conversions for engines like ChatGPT, Perplexity, Gemini, Claude and Copilot, but its published referrer list doesn't name Meta AI. So treat Meta AI click attribution as an open question. Look at what your own analytics records for visits from Meta's apps, and don't build a forecast on it yet.
Where to run this
You can do checks 1 and 2 by hand in an afternoon. Checks 3 to 6 need daily answers and real logs. We run them in Promptwatch: Meta AI is on every paid plan through the real interface, and the Meta crawler logs come with Professional and every agency plan.
If you'd rather we run the checklist for you, write to hello@visiblyrank.com.