A buyer opens an assistant and types something like "best place to buy oud perfume online in Saudi Arabia". Four stores get named. Yours is not one of them, and nobody can tell you why. In practice the reason is almost always in the list below, and almost always nearer the top than anyone expects.
1. The crawler is blocked
This is the five-minute check and it is the single most common cause. Bot-protection products, aggressive firewall rules and a robots.txt copied from a template all block AI crawlers by default or by accident. A store that answers 403 or 429 to GPTBot cannot be quoted no matter how good its catalogue is.
2. The product only exists after JavaScript runs
Price loaded by an API call, variants injected by a plugin, the description opened by a tab script: view the page with JavaScript disabled and whatever disappears is invisible to a large part of the retrieval pipeline. On WooCommerce this is usually a theme or plugin decision, not a platform limit, and it is fixable.
3. The page shows the facts but never states them
A product page communicates size through a dropdown, availability through a green badge, and shipping through an icon row. A person reads all of that instantly. A retrieval system reads the text. If the page never contains a sentence saying the product is a 100ml eau de parfum that ships within Saudi Arabia in two days, that sentence cannot be quoted.
Facts a product page should state in words
- What the product is, in a full sentence, not just a title.
- Who it is for and what problem it solves.
- Size, volume, material or specification, written out.
- Price and currency in text, not only in a rendered widget.
- Availability, shipping destinations and typical delivery time.
- Returns, in one sentence, on the product page itself.
4. There is no Product structured data
Product schema with price, currency, availability and a real identifier is the machine-readable version of the previous section. It is not a ranking trick; it is the difference between a system inferring your price from a string and reading it from a field. WooCommerce emits some of this by default and most themes then break it.
5. The store is too slow to be included
Retrieval runs under a deadline while a user watches a cursor blink. A store that takes four seconds to return its HTML is not slow in the SEO sense — it is absent, because the answer was assembled before it replied. This is one of the few places where time to first byte is a hard pass/fail rather than a score.
6. Nothing off your site describes you
A model naming four stores in a category is repeating what the web says about that category. If the only place your store is described is your own homepage, there is no consensus to repeat. Directory listings, marketplace profiles, press, and a clear About page in both languages are the raw material for a mention.
7. You are invisible in the language your buyer asks in
A store in the Gulf whose buyers ask in Arabic but whose entire site is English is answering a question nobody asked it. Machine-translated Arabic is not a fix either — it produces text that reads as filler and is treated accordingly. Arabic content written as Arabic, with correct RTL interfaces, is still the least contested ground in this market.
Sources
Related services
Related work
Read next
- AI SearchHow to build a site an AI assistant can actually citeWhat makes a web page citable by an AI assistant?
- WooCommerceThe product page, rewritten for a buyer who is asking an assistantHow should a product page be written so an AI assistant can recommend it?
- AI SearchWhat AI visibility means, and what it does notWhat is the difference between an AI mention, an AI citation and a search ranking?
- AI SearchArabic is the least contested ground in AI answersDoes publishing in Arabic change whether an AI assistant names my business?
- PerformanceCloudflare in front of WordPress: what it fixes, hides and createsWhat does putting Cloudflare in front of WordPress actually change?
- PerformanceSpeed is not a score. It is the part of the funnel nobody instrumentsHow do I justify spending money on site performance?
