Skip to main content

Search discovery and readable product data

A store needs to be found before its pages can be read. Those are different problems: search discovery depends on public access and search indexes; reading depends on the content actually served on the page. Neither guarantees a ranking, an assistant citation, a recommendation or a sale.

An assistant may also use existing knowledge or open a URL the user supplies. Do not assume every answer begins with the same search engine.

Which search systems matter?​

SurfaceWhat is verifiedWhat is not established
Google AI Overviews / AI ModeGoogle requires an indexed page eligible for a Search snippet.Eligibility does not guarantee inclusion.
Gemini API with Google Search groundingThis enabled tool uses Google Search.This is not a claim about every Gemini product or mode.
Microsoft search / Copilot-related discoveryBing Webmaster Tools reports citations across Microsoft Copilot and Bing AI experiences.A citation report is not a fixed ranking or an exclusive-provider contract.
ChatGPT searchOpenAI documents OAI-SearchBot for search discovery, separately from training and user-triggered fetches.Specific external providers and their proportions are not verified here.
ClaudeAnthropic documents a web-search tool.A permanent, exclusive Claude → Brave dependency is not verified here.
PerplexitySearch and direct page fetching are separate capabilities.Its exact index/provider mix is not verified here.

Sources: Google AI search eligibility, Gemini grounding, Bing AI performance, OpenAI crawlers, Anthropic web search.

What Clione can prepare and check​

These tools require administrator enablement and the relevant store connection. A feature being documented does not mean your store has connected it.

  • Google: with your Search Console connection and permission for the property, submit configured sitemaps and read URL Inspection results. A submission receipt is not proof of indexing. Clione does not use Google's restricted Indexing API to submit ordinary product pages.
  • Bing: send IndexNow notifications only where a store-hosted key verifies the URL scope. A key below an app-proxy directory cannot verify unrelated product paths. Your connected Bing Webmaster account is an independent route; no merchant connection is borrowed from another store.
  • Brave: show a manual list and a link to the configured submission form. Clione does not automate that form or promise acceptance. Presence checks need an authorized Search API connection or operator configuration.
  • Sitemap health: check declared sitemaps, a bounded sample of enriched URLs, publication dates and page responses. An incomplete sample is labelled, never presented as a check of the whole catalogue. The platform or agency owns fixes.
  • Access checks: compare robots.txt rules and raw responses using configured user-agent headers. These do not execute JavaScript or prove access from a vendor's real network. Google-Extended is a usage-control token, not a fetcher.

Shopify: connect Bing before setting up IndexNow​

Warning: a Shopify app-proxy key does not verify product or collection URLs outside that proxy directory. Uploading the file as a theme asset is not a root-scoped key either. Do not enter one of those URLs as proof for your whole catalogue. Use your own connected Bing Webmaster account while root hosting is unavailable; IndexNow setup does not block that route.

  1. In your own Bing Webmaster account, add this storefront and complete ownership verification. Use the storefront domain connected to Clione, not another store.
  2. Open Settings → API Access → API Key. Accept Microsoft's terms if prompted, then generate or retrieve your key. This key can access your account's verified sites: only share it with services you trust, never in screenshots or support messages.
  3. In Clione, open Settings → Integrations → Indexing. Enter Your Bing Webmaster API key and the exact Verified site URL in Bing Webmaster, then save.
  4. Enable Bing and publication notifications in Notification settings. Administrator enablement is also required. Publish approved content and check the notification log; a receipt means received, not indexed. Provider quota or authorization failures remain visible for retry or reconnection.

For optional IndexNow, use the per-store root-file setup only when your operator already controls the storefront’s edge. Prepare, install the exact file and verify it in Clione before opting in. No edge means IndexNow stays disabled; connected Bing Webmaster remains available. A directory key cannot prove the whole catalogue.

Sources: Microsoft's API setup and IndexNow ownership and key scope.

Read the results without overinterpreting them​

Indexed / observed means supporting evidence was returned for the checked URL or domain. Not indexed requires an explicit supported inspection result. Not measured covers missing permissions, unavailable providers, exhausted budgets, incomplete checks and URLs not observed in a bounded search result. Not finding a URL in that result does not prove it is absent from the index.

Index presence, canonical/indexability and crawler-access findings stay outside the product-data readiness score. They are actionable warnings, not zero content scores or a measurement of “AI visibility”. The proposed scoring revision remains inactive until approved.

What your SEO team still owns​

Your store or agency owns search strategy, editorial content, links, canonical policy, indexing choices, theme/router changes and WAF rules. Clione does not rewrite a platform's sitemap or robots.txt, simulate browser visits to influence an index, or guarantee that notifying a search engine changes its decisions.

Serve approved facts as readable text, specifications and FAQs alongside appropriate structured data. A browser-injected script alone is not proof an assistant received those facts. See product-data delivery and verify the served page for your store.

Optional per-store root-file setup: prepare an existing-edge file, prove it and opt in before IndexNow notifications.