How to Appear in Perplexity and Google AI Overviews: What Is Known
Appearing in Perplexity and Google AI Overviews means having your pages used as sources in AI-written answers to shopping questions. How sources are chosen is not public, so no store can promise a citation. This guide separates what is documented from what is not.
- What is documented
- What is not public
- Practical steps
- A measurement routine
Appearing in Perplexity and Google AI Overviews means having your store’s pages used as sources, or your brand named, in the AI-written answers those two products show for shopping questions. Perplexity is an answer engine that searches the web and writes a response with numbered source links. AI Overviews are AI-generated summaries that Google shows at the top of some search results, with links to pages that support them.
The honest starting point is that the selection of sources is not public. No store can promise a citation, and the advice online ranges from careful to invented. This guide separates what the platforms document from what is guesswork, then covers the practical work that improves your chances without claiming to control the outcome.
I include no statistics here. Where a point is my judgment rather than a documented fact, I say so. Both products change often, so check the current documentation from Google and Perplexity before you act on any detail.
I check crawler access, product data and the pages AI answers could draw on, then hand over a prioritised fix list.
Talk to an AI SEO ConsultantHow the Two Products Work
The two products are different in the way that matters for a store. One is a search engine feature you may already rank in. The other is a separate answer engine with its own crawler.
| Perplexity | Google AI Overviews | |
|---|---|---|
| What it is | An answer engine that searches the web and writes a response with source links. | A Google Search feature that summarises an answer and links to supporting pages. |
| How it finds pages | Its own crawler, PerplexityBot, plus live retrieval when you ask a question. | Googlebot and the Google Search index. |
| Requirement stated by the company | Allow its crawler so pages can be surfaced and linked. | Page must be indexed and eligible to show with a snippet. No other requirement is documented. |
| What you control | Crawler access, page content, markup and what other sites say about you. | Indexing, snippet controls, page content, markup and feeds. |
| Where traffic shows up | Referral traffic from perplexity.ai in your analytics. | Counted within Search Console’s web search results, not reported separately. |
Check each company’s documentation for the current crawler names and rules before you edit anything. They change.
What Is Known and What Is Not
Most disagreement about this topic comes from treating guesses as facts. This is how I separate them.
- Google says a page needs to be indexed and eligible to show with a snippet to be a supporting link in its AI features.
- Google says no special markup or AI-specific file is required.
- Perplexity documents a crawler name and says to allow it in robots.txt.
- Both products show source links, so pages can earn visits.
- Answers can differ between runs and between users.
- Exactly how either product chooses its sources.
- Whether any single tactic raises your chance, and by how much.
- How often your pages are used.
- How much traffic any one appearance will send.
- Whether today’s behaviour will hold next quarter.
Everything after this section is built on the left-hand column plus careful judgment about the right-hand one. Where I suggest an action, I am saying it improves your pages for shoppers and for search generally, not that it forces an appearance.
Start With Access
A page cannot be used if the crawler cannot fetch it. Check robots.txt first, then the layers in front of the store, such as a content delivery network or a firewall with bot protection. Those can block crawlers that robots.txt allows, and the store owner often does not know.
- robots.txt does not disallow Googlebot or PerplexityBot from product, category and guide pages.
- A firewall, CDN or security plugin does not return errors to those crawlers.
- Key content is in the delivered HTML, not only added later by scripts.
- Important pages return a 200 status and are not blocked by noindex.
- The pages you want used are linked from your navigation and sitemap.
On platforms without server log access, such as Shopify, you can still test with a fetch tool and check Search Console crawl statistics for Googlebot. For AI crawlers, a CDN’s bot reports, if you have them, are the closest substitute.
Make Pages That Can Answer a Question
Shoppers ask AI products questions like which backpack suits a long commute, or what the difference is between two kettles. A page can only help if it states the answer plainly. That is a judgment about usefulness, not a documented ranking rule.
| Page | What to state plainly | Why it helps |
|---|---|---|
| Product page | Specifications, materials, sizing, price, availability, shipping and returns | These are the facts an answer needs and a shopper checks |
| Category page | What the range is for, how items differ, how to choose | Gives context a product list cannot |
| Buying guide | The question as a heading, a direct answer below it, then detail | Easy to read for people and for systems that extract answers |
| Comparison page | Honest differences, including who each option is not for | Answers the “which one” question with a reason |
| Policy pages | Delivery, returns and warranty terms | Shoppers and answer systems both look for them |
Keep facts consistent across the site, your product feed and any outside listings. If the price or availability in an answer does not match your page, the shopper loses trust in both. For related detail, see the guides on product page SEO and collection page SEO.
Structured Data and Feeds
Product structured data states the name, price, availability and reviews in a form machines can read. Google’s documentation for its AI features says no special schema is needed, so do not treat markup as an entry ticket. It remains worth getting right for rich results and for keeping your data consistent.
The rule is that markup must match what the visible page says. If a price or an availability value differs from the page, remove the mismatch instead of adding more markup. For Google, a Merchant Center feed that is accurate and current is a separate data source for shopping surfaces, and it should agree with your pages. My guide on product schema for AI search covers which properties matter.
Reviews and Mentions Elsewhere
For shopping questions, answer products often draw on pages that are not your own, such as reviews, roundups, forum threads and publisher guides. I cannot tell you how much weight any of them gets, but it makes sense to be accurately described on the pages that people and systems are likely to read.
Practical steps follow from that. Collect genuine reviews on your own site and on the review platforms your customers use. Make sure retailers and reviewers who write about your products have correct facts. Where a reviewer is wrong, ask for a correction. Do not pay for fake reviews or invent mentions, since that risks your reputation and breaks platform rules. The guide on digital PR for ecommerce covers earning coverage properly.
How to Measure Without Fooling Yourself
Because answers vary, a single check proves little. Build a fixed list of prompts that match how your customers ask, run it on a schedule, and record which sources are named each time. Treat the result as a sample, not a ranking.
- 1Write the prompt list Use real customer questions from support, reviews and search queriesAvoid prompts that only mention your brand name
- 2Run it on a schedule Same prompts, same cadence, dated recordsOne-off checks mislead because answers change
- 3Record sources and mentions Note which sites are cited and whether you appearScreenshots help, but record text too
- 4Check analytics for referrals Look for perplexity.ai as a source and review Search Console for web searchVolumes may be small, so avoid over-reading them
The guide to tracking AI search traffic covers the setup in analytics, Search Console and server logs.
What I Would Avoid
- Fixing access, indexing and page quality first.
- Stating facts clearly on pages that matter commercially.
- Keeping markup and feeds consistent with the page.
- Tracking with a fixed prompt list over months.
- Anyone promising a citation or a placement.
- Treating llms.txt or special markup as required.
- Stuffing pages with question lists written for machines.
- Fake reviews or invented mentions.
Frequently Asked Questions
Can I pay to be cited by Perplexity or shown in AI Overviews?
Not to my knowledge. Citations and supporting links are not something a store can buy through these answers. Be cautious of anyone who promises a citation or a placement, because the selection of sources is not under a store’s control.
Do I need special schema or an llms.txt file?
Google’s documentation says no special markup or AI-specific file is required to appear in its AI features. Product structured data is still worth getting right for other reasons, and an llms.txt file is optional at best. Neither replaces crawlable, useful pages.
Should I block PerplexityBot or Google’s AI features?
That is a business decision. Blocking a crawler can keep your pages out of that product’s answers. Google lets you limit snippets with page-level controls, which can also limit what appears in its AI features. Decide on what you want shoppers to see, then test the effect.
How do I know if Perplexity sends me traffic?
Look for perplexity.ai as a referral source in your analytics. Volumes can be small, so also record the answers directly by running a fixed set of prompts and noting which sites are cited.
How long does it take to appear?
No one can tell you. Pages need to be crawled and indexed, and answers change between runs. Treat any single appearance as a sample, check on a regular schedule, and judge the work over months.
Checklist: Perplexity and AI Overviews for a Store
- Googlebot and PerplexityBot can fetch product, category and guide pages.
- No firewall or CDN setting blocks those crawlers.
- Important pages are indexable, return 200 and carry the key facts in HTML.
- Product pages state specifications, price, availability, shipping and returns plainly.
- Structured data and the product feed match the visible page.
- Genuine reviews exist on your site and on platforms your customers use.
- Outside pages that describe your products have correct facts.
- A fixed prompt list is run on a schedule and recorded.
For the broader plan, the guide on ecommerce AI search visibility sets out the full process, and the guide on getting products cited in ChatGPT covers the same ideas for another assistant.
Book a call and we will go through your crawler access, product data and the prompts that matter, then agree on what to fix first.
Book a Call
I work on how online stores show up in search and in AI answers. This guide keeps to what is documented, labels judgment as judgment, and makes no promise about citations.
More SEO guides
Ecommerce AI Search Visibility
Get your store named in ChatGPT, Google AI Mode and Perplexity answers. Nine steps, real 2026 data, and the AI visibility myths to skip.
Abdullah Mahmud
How to Get Your Products Cited in ChatGPT (2026 Guide)
Get your products cited in ChatGPT: crawler access, clean product data, reviews and third-party mentions. A practical 2026 guide for online stores
Abdullah Mahmud
How to Track AI Search Traffic
Learn how to track AI search traffic from ChatGPT, Perplexity, Gemini and Google AI Overviews using GA4, Search Console, Bing and server logs.
Abdullah Mahmud
Want to know where your store stands in AI answers?
Get your crawler access, product data and key pages checked, with a fix list that does not promise the unpromisable.
I’m an awarded SEO expert and seo consultant with 11+ years of experience. I have generated over $100M in tracked organic revenue by SEO for my clients like you 👉 See Case Study