Search Console shows this URL at 69 impressions, 0 clicks, and position 6.64 over 28 days (pulled 22 Sep 2026). That average is not a Meta AI rank. The only named queries are a Postman site search for Instagram's Business Discovery API — 8 of 69 impressions. Meta documents business_discovery.username() as a lookup of another professional account, not an assistant that names you. Absent from four Google SERPs. Engines blocked. Keep the Google page. Do not invent one.
Updated 22 Sep 2026.
What we tested (22 Sep 2026)
Worked example: this live URL — a Meta AI explainer whose title used the words “business discovery” — plus Search Console, URL Inspection, and four Google SERPs. Not a hypothetical plumber. Not a product-scan dump.
- Google Search Console (28d, pulled 22 Sep 2026): this URL 69 impressions, 0 clicks, CTR 0%, position 6.64. Named queries, both of them:
site.postman.com/meta/instagram "business discovery"— 6 / 0 / 5.83;%site.postman.com/meta/instagram "business discovery"— 2 / 0 / 5.5. Named queries sum to 8 of 69 impressions. The rest are anonymized. Page-level average position is not a H1 rank. - GA4 organic landings (28d, pulled 22 Sep 2026): this path returned no rows. That is 0 organic sessions and 0 key events, matching the 0 clicks. On-site checker traffic is a different report.
- URL Inspection (22 Sep 2026): Crawled — currently not indexed. Verdict NEUTRAL. Google canonical = this URL. User canonical = this URL. Last crawl 27 Jul 2026 (
2026-07-27T19:06:54Z). Robots allowed. Indexing allowed. Page fetch successful. Crawled as mobile. Referring URLs:/glossary/meta-aiand the sitemap. No rich-result types were returned. - Live this URL before rewrite: HTTP 200, self-canonical,
x-matched-path/learn/meta-ai-business-discovery, 164,367 bytes, Vercel HIT. Visible date 12 Apr 2026. No Updated line. No What-we-tested box. Checker link already in the layout. The April body asserted social-proof causes (review counts, a Yelp feed, a WhatsApp catalog) without a dated measurement. Those claims are gone. The numbers are not repeated here, so Google cannot re-snippet them as facts. - DataForSEO Google organic, desktop US, 22 Sep 2026 ($0.002/query): Scope absent on all four.
meta ai business discovery— Facebook for Business #1, ai.meta.com #2, SMK #3, SEO.com #4, Hashmeta #5.how to get recommended by meta ai— about.fb.com #1, Meta’s personal-assistant page #2, Reddit r/FacebookAds #3, Frizerly #4.meta ai recommend my business— Meta AI Business Assistant #1, Meta Help Center #2, WebFX #3.does meta ai recommend local businesses— Facebook small-business news #1, ai.meta.com business page #2, Fast Company #3.
- Answer engines this run: ChatGPT.com and Perplexity returned HTTP 403. Gemini and grok.com returned HTTP 200 HTML shells. No citation list was captured. Record blocked, never invent who named whom.
- Technical gate the same morning: homepage HTTP 200.
/ai-visibility-checkerHTTP 200 without following redirects, canonical = itself. Live sitemap 339<loc>, including this URL and the checker. GSC lastDownloaded the sitemap on 20 Sep 2026 with submitted 339.contents.indexed: 0is reporting lag, not a wipe. No extra sitemap submit.
That gap — 69 impressions, 0 clicks, a Postman query wearing the page’s title words, last crawl 27 Jul, SERP owned by Meta’s own pages — is why the slug stays and the claim changes.
What is Meta AI business discovery?
Three different things share the words. Mixing them is how a page collects impressions and teaches the wrong job.
| Surface | What it actually is | What it is not |
|---|---|---|
| Meta AI assistant | The chat product on Facebook, Instagram, WhatsApp, and meta.ai. Consumer page: ai.meta.com/meta-ai/assistant. | Not the Instagram Graph API. Not a Search Console position. |
| Meta AI Business Assistant | A tool the owner asks, documented at facebook.com/business/ai/business-assistant. Occupies #1 for meta ai recommend my business (22 Sep 2026). | Not proof that Meta AI named your business to a customer. |
| Instagram Business Discovery | A Graph API method. Meta for Developers: business_discovery.username(<USERNAME>) “returns data about another Instagram Business or Creator IG User.” You call it as a professional account and pass the target username. Docs: IG User Business Discovery. | Not an answer engine. Not “get recommended.” |
The April title on this URL was “Meta AI and Business Discovery.” Google’s named queries for the page are a site:postman.com search for that API. Postman hosts public Meta Instagram collections. A developer looking up the endpoint and a marketer hoping to be named in a chat are not the same searcher.
Common misconception
“Position 6.64 means we almost rank for Meta AI business discovery.”
No. Average position blends every query that showed the URL, including anonymized ones. The only queries Google was willing to name are the Postman string and its percent-encoded twin, at 5.83 and 5.5, totaling 8 impressions. DataForSEO showed this URL absent from the top results for meta ai business discovery the same morning. Do not write “we rank #7 for Meta AI.”
A second misconception: “Meta AI Business Assistant means Meta recommends my business.” The #1 result for meta ai recommend my business is Meta’s page for an assistant the owner uses. That is a product for the business, not a citation in a customer’s chat. We did not open Meta AI and ask it to name a business this morning. Engines we can reach were blocked. Do not convert a help-center URL into a recommendation win.
A third: the Reddit result at #3 for how to get recommended by meta ai is r/FacebookAds telling advertisers not to apply Meta’s in-product ad recommendations. That is an ads-UI argument. It is not a study of who Meta AI names.
Why is this URL showing up for a Postman query?
Because the title contained the API’s name.
site.postman.com/meta/instagram "business discovery" is not a buying prompt. It is someone (or Google’s query clustering) associating this Learn URL with documentation of the Instagram collection on Postman. Six impressions at position 5.83, plus two more on the encoded twin. Zero clicks. A click on that query would have been a developer who wanted the Graph API reference, not a local operator who wanted to be recommended.
That is still useful. It tells you the page’s extractable phrase was “business discovery,” and Google filed it next to the API docs, not next to Hashmeta or Frizerly. Those publishers occupy the H1 SERP. We do not.
Do not “fix” this by minting /learn/instagram-business-discovery-api. That slug would cannibalize the only query this URL has actually been shown for, and it would still not be an AI-recommendation article. Upgrade in place. Say what the API is, then say what we did not measure.
How is the Instagram Business Discovery API different from Meta AI?
The API returns fields about an account you already named.
Meta’s reference (fetched 22 Sep 2026): perform the request on the Instagram professional account making the query, and identify the target with username. The method is business_discovery.username(<USERNAME>). It is a read of public professional-account data — biography, media, counts — for an app that already knows who to look up. It does not decide who to recommend. It does not read your Facebook reviews. It does not consult a Yelp feed. If your integration needs another account’s public Instagram fields, use the docs. If your question is “will a customer’s Meta AI chat name us,” this endpoint does not answer it.
Meta AI is the other direction. A person asks a question. The product may or may not name a business. We have no dated panel of those answers from this run. ChatGPT.com and Perplexity were 403. Gemini and grok.com were HTML shells. Recording blocked is the honest log. Inventing a catalog-completeness cause would be the April failure mode.
Google Search is the third direction, and it is the one we can measure. This URL is crawled and not indexed. Last crawl 27 Jul 2026. Canonical is itself, so this is not a homepage-canonical bug. Complementary rule: an AI answer, if it ever cites the open web, still needs a page Google can index and snippet. A Graph API method does not replace that. A Facebook Page checklist does not replace that either.
Does Meta AI recommend local businesses?
We did not measure that on 22 Sep 2026.
What we measured is who occupies the Google SERP for the question:
- Meta’s own domains (facebook.com/business, ai.meta.com, about.fb.com, meta.com help) hold #1 or #2 on every query we paid to check.
- Independent explainers (SMK, SEO.com, Hashmeta, Frizerly, WebFX, Fast Company) fill the rest of the top five.
- Scope is absent.
- The consumer assistant URL sits at #2 for
how to get recommended by meta ai. That page is “your personal AI assistant,” not a local-pack study.
So the operator question “does Meta AI recommend local businesses?” currently retrieves Meta talking about Meta AI, plus agencies explaining Meta’s tools. It does not retrieve a citation ledger. Do not publish a percentage of local businesses named in Meta AI. We do not have one. Scope’s checker measures ChatGPT, Claude, Gemini, and Perplexity. It does not run Meta AI. Saying the product tracks “social AI recommendations” was an overclaim. Deleted.
What you can still do, labeled as hygiene rather than a cause:
- Keep the Facebook Page’s category, address, hours, phone, and website filled, because those fields are what a human and a Knowledge Panel reader can verify. That is not a tested Meta AI ranking factor from this run.
- Do not buy a review-count target from an old blog post on this URL. We removed one. We are not replacing it with a new invented threshold.
- If you sell on Instagram via the Graph API, read Business Discovery as an API. If you want to be named in answers, that is a different project: an indexed page, plus whatever off-site pages the engines you can actually query already cite. See how to get cited in AI search. Do not rewrite that URL from here.
What should you not copy from the old version of this page?
The old body was a settings tour. It told operators to complete every Facebook field, turn on reviews, post two or three times a week, switch Instagram to a professional account, and fill a WhatsApp catalog. Some of those are ordinary profile hygiene. None of them were tied to a query, a crawl, or an engine answer.
It also implied Scope’s monitoring covered Meta AI the way it covers other assistants. It does not. The AI visibility checker is the indexable lead magnet for the engines the product runs. The Scope MCP server reads that visibility for an agent. Neither is a Meta AI probe. Neither replaces Search Console for this URL.
Compare pages have the same honesty problem if they blur “assistant for the owner” and “assistant that names the owner.” See Scope vs Profound. Profound publishes MCP content. That row is about agent access to a visibility product, not about Meta’s Graph API.
Worked example: this URL, 22 Sep 2026
Not a hypothetical restaurant.
| Check | Result 22 Sep 2026 |
|---|---|
| Learn URL HTTP | 200, self-canonical, matched path correct, 164,367 bytes, Vercel HIT |
| Visible date before rewrite | 12 Apr 2026, no Updated line, unsourced social-proof causes |
| GSC 28d | 69 impressions, 0 clicks, CTR 0%, pos 6.64 |
| Named GSC queries | 2 queries, 8 of 69 impressions. Both are site.postman.com/meta/instagram "business discovery" (one percent-encoded) |
| GA4 organic on this path | no rows — 0 sessions, 0 key events |
| Inspect | Crawled — currently not indexed; last crawl 27 Jul 2026; canonical = self; referrers = glossary + sitemap |
meta ai business discovery | Absent (Facebook #1, ai.meta.com #2, SMK #3, SEO.com #4, Hashmeta #5) |
how to get recommended by meta ai | Absent (about.fb.com #1, personal assistant #2, Reddit ads thread #3, Frizerly #4) |
meta ai recommend my business | Absent (Business Assistant #1, Meta Help #2, WebFX #3) |
does meta ai recommend local businesses | Absent (Facebook news #1, ai.meta.com #2, Fast Company #3) |
| ChatGPT.com / Perplexity | HTTP 403 — blocked |
| Gemini / grok.com | 200 HTML shells — blocked, not an omit |
| Claim we will not make | A Meta AI citation rate, a review-count threshold, “position 6.64 is #7,” or “Scope measures Meta AI” |
If the April settings tour were enough, this URL would not sit on 69 impressions and 0 clicks while Meta’s own domains own the H1. The honest work is to separate the API from the assistant, then measure Google in Search Console and the engines you can actually query. See GEO vs SEO.
Sitemap live this morning: 339 <loc>, including this URL. Homepage HTTP 200. Checker HTTP 200 without following redirects, canonical = itself. Existing-URL upgrades are allowed under that gate. We did not mint a cannibal slug. We did not extra-submit the sitemap — last download was 20 Sep 2026 and the submitted count already matches live 339.
30-minute operator checklist
Do this for one money URL. Do not start a Meta AI ranking project from a Postman query.
- Write three labels on a card: Meta AI assistant, Meta AI Business Assistant (a tool you ask), Instagram Business Discovery (a username lookup). If a sentence uses “recommend” for more than one of them, split the sentence.
- Open Search Console → this URL → queries. If a named query contains
site.postman.comor the API phrase in quotes, do not report the page’s average position as a Meta AI rank. Ours: 69 / 0 / 6.64, and 8 of those impressions are that Postman string. - Search Google for
meta ai business discovery,how to get recommended by meta ai,meta ai recommend my business, anddoes meta ai recommend local businesses. Write whether your URL is in the top 10. Ours: absent / absent / absent / absent (22 Sep 2026). - Open Meta’s Business Discovery reference. Confirm the method takes a username you already know. If your task is “be named when someone asks,” close the API tab.
- Open the #1 result for
meta ai recommend my business. If it is Meta’s Business Assistant, you are reading a tool for the owner. Do not screenshot it as proof you were recommended. - URL Inspection: write the coverage state and last crawl. Ours: crawled — not indexed, 27 Jul 2026. Canonical must be this URL, not the homepage. It is.
- Profile hygiene (category, NAP, hours, website) is fine as a 10-minute pass. Write “not measured as a Meta AI cause” next to it. Do not add a review-count target.
- Run two engines you can actually reach. Record mentioned / omitted / confused / blocked. A 200 HTML shell is blocked. This morning ChatGPT.com and Perplexity were 403; Gemini and grok.com were shells. Do not fill the blank with a guessed citation.
- Measure ChatGPT, Claude, Gemini, and Perplexity on the AI visibility checker. That board is not Meta AI. Agents can read it via the Scope MCP server. Keep Google SEO. Do not mint
/learn/how-to-get-recommended-by-meta-ai.
Key takeaways
- “Business discovery” on this URL was colliding with Instagram’s Graph API method
business_discovery.username(), not with a Meta AI citation study. - Search Console, 22 Sep 2026: 69 impressions, 0 clicks, position 6.64. Named queries are only the Postman site search and its encoded twin — 8 of 69 impressions. Page-level position is not a H1 rank.
- GA4 organic: no rows. Inspect: crawled — currently not indexed, last crawl 27 Jul 2026, canonical = self, referrers = glossary and the sitemap.
- Absent from four Google SERPs. Meta’s own domains hold the top slots. Hashmeta, SEO.com, Frizerly, and WebFX explain the product. We do not.
- Meta AI Business Assistant is a tool the owner asks. The personal assistant page is a consumer product. The Reddit hit is an ads-UI argument. None of those is a local-recommendation rate.
- ChatGPT.com / Perplexity 403; Gemini / grok.com HTML shells. Blocked ≠ omitted. Scope does not measure Meta AI. Do not invent a citation list.
- Keep Google indexing. Delete unsourced social-proof causes. Do not mint a cannibal slug. Do not extra-submit a sitemap Google already downloaded at 339 URLs.
References
- Google Search Console page report for
https://scope.online/learn/meta-ai-business-discovery, pulled 22 Sep 2026: 28d 69 impressions / 0 clicks / pos 6.64. Named queries:site.postman.com/meta/instagram "business discovery"6/0/5.83;%site.postman.com/meta/instagram "business discovery"2/0/5.5. - GA4 organic landings, Markifact account 520476298, 22 Sep 2026:
/learn/meta-ai-business-discovery— no rows. - Google URL Inspection, 22 Sep 2026: coverageState
Crawled - currently not indexed; verdict NEUTRAL; lastCrawlTime2026-07-27T19:06:54Z; googleCanonical = userCanonical = this URL; robotsTxtState ALLOWED; indexingState INDEXING_ALLOWED; pageFetchState SUCCESSFUL; crawledAs MOBILE; referringUrls =/glossary/meta-aiandsitemap.xml. - Live fetches, 22 Sep 2026: this URL HTTP 200, 164,367 bytes, self-canonical, Vercel HIT, visible date 12 Apr 2026 before rewrite. Homepage 200.
/ai-visibility-checker200 without following redirects, canonical = itself. Live sitemap 339<loc>. GSC sitemap lastDownloaded2026-09-20T21:24:45Z, submitted 339, contents.indexed reported 0 (lag). - Meta for Developers, IG User Business Discovery, fetched 22 Sep 2026:
business_discovery.username(<USERNAME>)returns data about another Instagram Business or Creator account. The request runs on the professional account making the query. - DataForSEO Google organic live/regular, desktop US, 22 Sep 2026, $0.002/query.
meta ai business discovery: Facebook for Business #1, AI at Meta #2, SMK #3, SEO.com #4, Hashmeta #5.how to get recommended by meta ai: about.fb.com #1, personal assistant #2, r/FacebookAds #3, Frizerly #4.meta ai recommend my business: Business Assistant #1, Meta Help #2, WebFX #3. Scope absent on all four. - ChatGPT.com / Perplexity HTTP 403; Gemini / grok.com HTTP 200 HTML shells, 22 Sep 2026.
- GEO vs SEO; how to get cited in AI search; AEO audit; glossary: Meta AI.
Q: Is position 6.64 a rank for Meta AI business discovery? A: No. On 22 Sep 2026 the page average was 6.64 across 69 impressions and 0 clicks. The only named queries were a Postman site search for Instagram’s Business Discovery API (8 impressions). DataForSEO showed this URL absent from that H1 SERP. Do not write “we rank #7.”
Q: What is Instagram Business Discovery?
A: A Graph API method. Meta’s docs say business_discovery.username(<USERNAME>) returns data about another Instagram Business or Creator account, requested by a professional account that already knows the username. It is not Meta AI, and it is not a recommendation.
Q: Does Meta AI Business Assistant mean Meta recommended my business?
A: No. That product is a tool the owner asks. It was the #1 Google result for meta ai recommend my business on 22 Sep 2026. A help-center URL is not a citation in a customer’s chat. We did not run that chat.
Q: Does Scope measure Meta AI recommendations? A: No. The AI visibility checker and the Scope MCP server cover the engines the product runs — ChatGPT, Claude, Gemini, and Perplexity. They do not probe Meta AI. Search Console is the measurement for this URL.
Q: Why is the page crawled but not indexed? A: Inspection on 22 Sep 2026 said crawled — currently not indexed, last crawl 27 Jul 2026, canonical equal to itself, robots allowed. That is a Google decision on this URL, not a homepage-canonical bug. Upgrading the page is the move. A new slug would not fix the last crawl.
Q: Should I add a review-count target so Meta AI names me? A: Not from this page. The previous version asserted social-proof causes without a dated test. Those lines are deleted. Profile completeness is hygiene. It is not a measured Meta AI factor from this run.
Q: ChatGPT.com returned 403. Did ChatGPT omit us? A: Record blocked. This morning ChatGPT.com and Perplexity returned 403. Gemini and grok.com returned HTTP 200 HTML shells. That is not an omit, and it is not a Meta AI answer either.
Q: Should we publish a separate API guide? A: No. This slug already collected the API query. A second URL would cannibalize it. Explain the method here, point developers at Meta’s reference, and keep the recommendation question honest: unmeasured on 22 Sep 2026.