Aivec AI Search Schema vs AI Search for WooCommerce – Semantic Search

AI-focused structured data (JSON-LD) for LocalBusiness, breadcrumbs, FAQ extraction, and llms.txt. Overview / 概要 WordPress plugin for generating structured data optimized for AI-powered search engines, including Local SEO, breadcrumbs, and FAQ extraction. Optimizes your site for AI-powered answer engines (sometimes called AEO: Answer Engine Optimization). Configure everything in Settings → AI Search Schema and the plugin will emit JSON-LD tailored to your organization or storefront. AI検索最適化・ローカルSEO対応のWordPressプラグインです。設定 → AI Search Schema で会社情報・LocalBusiness 情報・SNS・ジオコーディングなどを入力すると、検索エンジン向けの JSON-LD を一括生成できます。 Why Structured Data Matters Now / 今、構造化データが重要な理由 The Age of Answer Engines / 回答エンジンの時代 Search is evolving from “10 blue links” to AI-powered answer engines (Google SGE, Bing Copilot, ChatGPT with browsing). These systems don’t just index pages—they understand them. Structured data (JSON-LD) is the language that helps AI comprehend your content. 検索は「10本の青いリンク」から、AIによる回答エンジン（Google SGE、Bing Copilot、ChatGPTのブラウジング機能）へと進化しています。これらのシステムはページを単にインデックスするだけでなく、「理解」します。構造化データ（JSON-LD）は、AIがあなたのコンテンツを正しく理解するための言語です。 Why AI Search Optimization Matters / AI検索最適化が重要な理由 AI citations: When AI assistants answer questions, they cite sources. Proper schema increases the chance of being cited. AI引用: AIアシスタントが質問に回答する際、出典を引用します。適切なスキーマは引用される可能性を高めます。 Rich results: Google displays enhanced search results (stars, prices, FAQs, breadcrumbs) for sites with valid schema. リッチリザルト: Googleは有効なスキーマを持つサイトに対し、拡張検索結果（星評価、価格、FAQ、パンくず）を表示します。 Local SEO/MEO: LocalBusiness schema directly powers Google Maps and local pack rankings. ローカルSEO/MEO: LocalBusinessスキーマはGoogleマップとローカルパックの順位に直接影響します。 Voice search: Structured data helps voice assistants provide accurate answers from your site. 音声検索: 構造化データは音声アシスタントがあなたのサイトから正確な回答を提供することを助けます。 Features / 機能 Organization / LocalBusiness JSON-LD – address, geo, price range, payment methods, reservations, storefront imagery, areaServed, branchOf などを 1 つの @graph に統合 Organization / LocalBusiness スキーマ：住所・緯度経度・価格帯・支払方法・予約可否・店舗画像・商圏情報を1つのJSON-LDに集約 Article / FAQ / QAPage / Product – per-post metabox lets editors switch schema types, auto injects FAQPage mainEntity, and WooCommerce products map to Product schema with offers/brand/rating/images 投稿メタボックス切替 / WooCommerce連携：Article / FAQPage / QAPage / Product を選択可能。WooCommerce商品はブランド・価格・在庫・ギャラリー画像付き Product スキーマに自動変換 BreadcrumbList & ItemList – structured breadcrumbs plus archive ItemList, with optional frontend breadcrumbs template Structured Breadcrumbs：パンくず / アーカイブ ItemList を JSON-LD で出力し、テンプレートでも表示可能 SearchAction & Site metadata – WebSite includes SearchAction, supported languages, and SearchAction URLs SearchAction 対応：サイト内検索を SearchAction で明示し、対応言語タグを JSON-LD に反映 Automatic geocoding – Google Maps Geocoding API + OpenStreetMap fallback, rate limiting and caching ジオコーディング：Google Maps Geocoding API＋OSMフォールバック、レート制御・キャッシュ機能付き Self-diagnostics – Validator checks required Google Rich Results properties (WebSite/Organization/LocalBusiness/Article/Product) and shows admin notices when fields are missing 自己診断：Google推奨プロパティを自動検証し、不足項目を管理画面で警告 Multilingual admin – 全 UI と翻訳リソースを英語ベースで整備し、日本語翻訳を同梱 多言語UI：英語ベースの翻訳ファイル＆日本語翻訳を標準同梱 llms.txt Generation – Auto-generate llms.txt to help AI systems understand your site structure. Editable in the settings. llms.txt生成：AI検索エンジンがサイト構造を理解しやすいllms.txtを自動生成。設定画面で編集可能 Geocoding / ジオコーディング Obtain a Google Maps Geocoding API key (limit it to “Geocoding API” only) and add referrer/IP restrictions plus daily quotas. Google Geocoding APIキー を取得し、API制限（Geocoding のみ）、HTTPリファラー／IP制限、クォータ設定を行ってください。 Google Cloud Console で新規プロジェクトを作成し、Geocoding API を有効化（他 API は不要） 「認証情報」から API キーを発行し、HTTP リファラーまたは IP 制限を設定 1 日あたりのクォータ上限を設定して不正利用を防止 Enter the key in Settings → AI Search Schema. The key is saved only in WordPress options and never rendered in HTML/JS. キーは WordPress のオプションにのみ保存され、HTML/JS には出力されません。 Click Fetch coordinates to geocode the current address. Requests are rate-limited (10 seconds) and cached. Re-fetching is required only when address fields change. 住所から緯度・経度を取得 ボタンで geocode が発火します。10 秒のレート制御とキャッシュを実装しているため、住所を変更したタイミングのみ再取得してください。 When the key is empty the plugin falls back to OpenStreetMap (Nominatim) for development use. Production sites should keep a Google API key configured. キー未設定時は開発用フォールバックとして OpenStreetMap (Nominatim) を使用します。本番では Google API キーの設定を推奨します。 Security / セキュリティ This plugin follows WordPress security best practices: 本プラグインはWordPressのセキュリティベストプラクティスに従っています： All settings require administrator privileges / 全設定に管理者権限が必要 User inputs are sanitized and validated / ユーザー入力はサニタイズ・検証済み API keys are stored securely (never exposed in HTML) / APIキーは安全に保存（HTMLに露出しない） Installation / セットアップ Upload the plugin folder to wp-content/plugins/aivec-ai-search-schema プラグイン一式を wp-content/plugins/aivec-ai-search-schema に配置 Activate from WordPress admin 管理画面で有効化 Open Settings → AI Search Schema and complete the forms 設定 → AI Search Schema で各項目（ブランド情報／店舗情報／SNS／APIキー 等）を入力して保存 FAQ / よくある質問 See See the FAQ on GitHub: for frequently asked questions about: よくある質問については See the FAQ on GitHub: をご覧ください： Schema conflicts with other plugins / 他プラグインとのスキーマ衝突 LocalBusiness schema setup / LocalBusinessスキーマの設定 Troubleshooting common issues / よくある問題のトラブルシューティング License / ライセンス GPLv2 or later Support Policy Free version support: Bug reports only. What We Support Bug reports with clear reproduction steps Issues causing PHP errors or broken schema output What We Do NOT Support Usage questions (“How do I…?”) SEO/AEO strategy consulting Feature requests Customization requests Response Policy Best effort – no guaranteed response time Issues without reproduction steps will be closed Bug reports: GitHub Issues only We do not provide support via WordPress.org forums. WP.orgフォーラムでのサポートは行っておりません。 Required Information for Bug Reports WordPress version, PHP version, plugin version Theme name and active plugins (especially SEO plugins) Steps to reproduce (mandatory) Expected vs actual behavior Error logs (if available) External Services This plugin can connect to external services only when you use specific features. Google Maps Geocoding API (optional) Used to convert the address you enter into latitude/longitude when you click “Fetch coordinates”. API endpoint: https://maps.googleapis.com/maps/api/geocode/json Data sent: the address fields you entered, your site locale, and your site URL in the User-Agent header. Service provided by Google. Terms: https://cloud.google.com/maps-platform/terms | Privacy: https://policies.google.com/privacy OpenStreetMap Nominatim (optional fallback) Used only when no Google Maps API key is configured and you click “Fetch coordinates”. API endpoint: https://nominatim.openstreetmap.org/search Data sent: the address fields you entered, the admin email (if available), and your site URL in the User-Agent header. Service provided by OpenStreetMap (Nominatim). Usage policy: https://operations.osmfoundation.org/policies/nominatim/ | Privacy: https://osmfoundation.org/wiki/Privacy_Policy ZipCloud (optional, Japan only) Used to auto-fill address fields from a Japanese postal code when you enter a 7-digit zip code in the admin settings. API endpoint: https://zipcloud.ibsnet.co.jp/api/search Data sent: the postal code you entered (e.g., “1000001”). Timing: only when you type a valid 7-digit Japanese postal code in the settings page. Service provided by ZipCloud. Terms: https://zipcloud.ibsnet.co.jp/rule/api | Privacy: https://ibsnet.co.jp/privacy-policy/

Queryra is an AI search plugin for WooCommerce and WordPress — a semantic search engine that understands what customers mean, not just what they type. Your customer types “present for my girlfriend”. Your WooCommerce store returns: 0 results. You sell gift boxes, perfumes, skincare sets — exactly what she’d love. But default WooCommerce search can’t connect “present for girlfriend” to “Gift Box”. Your customer leaves. Sale lost. This happens every day. 👉 Try AI Search live → WooCommerce demo store — 220+ products across 10 brands. Search naturally and see the difference. What is AI Search for WooCommerce? AI Search replaces WooCommerce’s default product search with semantic search that understands meaning. Your products stay the same. Your store stays the same. Search just works. Trusted compatibility: Oxygen Builder, Breakdance, Meta Box, TranslatePress, Weglot, MemberPress, B2BKing, and more. Default WooCommerce search → 0 results: ❌ “my skin looks tired” ❌ “gift for mom who loves candles” ❌ “looking older than my age” Same store with AI Search → products found: ✅ “my skin looks tired” → Night creams, recovery oils, eye patches ✅ “gift for mom who loves candles” → Scented candles, home fragrance sets ✅ “looking older than my age” → Anti-aging serums, firming creams Beyond Semantic Search AI Search goes further than vector search alone. A natural language query like “wireless headphones under $80, not Beats” applies the price filter AND excludes the brand automatically. No other WooCommerce AI search plugin does this. AI Search works as an AI product search engine for WooCommerce — handling intent-aware queries, ChatGPT-style natural language, and B2B wholesale bulk search. Powered by vector embeddings and LLM intent parsing. AI Search Compatible Plugins Queryra has confirmed integrations and tested compatibility with leading WordPress plugins: Page Builders: * Oxygen Builder — full Oxygen 4.x and 6.0 support, automatic content extraction * Breakdance — native Breakdance content indexing Custom Fields: * Meta Box — text and group fields indexed automatically * ACF (Free + Pro) — text, textarea, WYSIWYG, repeaters, groups Multilingual: * TranslatePress — single unified semantic index across all languages * Weglot — multilingual semantic search Membership & Affiliate: * MemberPress — semantic search across member-only content; MemberPress continues to gate the content itself at render time * Easy Affiliate Pro — affiliate product search with custom fields B2B: * B2BKing — semantic AI search in bulk order forms (new in 1.4.1) More integrations and developer docs → queryra.com/docs AI Search for Page Builders & Custom Fields Page builder content used to be invisible to WordPress search. Queryra fixes this — AI search now reads everything your visitors see: Elementor AI search — indexes content stored in _elementor_data, including text widgets, headings, and product descriptions built with Elementor Beaver Builder & Breakdance — full content extraction from saved layouts Oxygen Builder — both legacy shortcode mode and modern JSON v2 supported Gutenberg / WPBakery / Divi — native support (content already in post_content) AI Search for Custom Fields & Taxonomies Most product data lives in custom fields, not the post content. Queryra reads it automatically: ACF (Free + Pro) — text, textarea, WYSIWYG, repeaters, and groups indexed without configuration Meta Box — text fields and group fields via the official registry Custom taxonomies — book_genre, material, property_type, or any public custom taxonomy is sent to the AI search index, keyed by slug Pods, JetEngine, Bricks Builder — supported via developer filter queryra_indexable_meta_content Smart filtering automatically excludes CSS values, hex colors, URLs, and dates from the semantic search index — keeping AI relevance high. Make Your Store Discoverable by AI AI Search doesn’t just help your customers — it helps AI assistants find your store. Queryra automatically generates structured data and AI-readable files so ChatGPT, Perplexity, Google AI Overviews, and Claude can recommend your products. Dynamic /llms.txt and /llms-full.txt for AI crawlers JSON-LD structured data on search pages X-Search-Engine header for AI attribution Want extra visibility? Partner Program — qualifying sites can apply for Queryra at no cost. See Partner Program details. Site promotion — your site gets featured on queryra.com and promoted across AI search platforms WordPress 7.0 Connectors API & Abilities API Queryra is a native WordPress 7.0 AI search connector. After activation, Queryra appears in Settings → Connectors alongside OpenAI, Anthropic, and Google — giving site owners a unified place to manage AI search configuration. Connectors API — Queryra registers as an AI search connector. Manage your Queryra API key from the standard WordPress 7.0 Connectors screen. Abilities API — Queryra exposes queryra/semantic-search as a discoverable ability. AI agents, chatbots, and assistants running on WordPress 7.0 can call Queryra natively for semantic product search. Backward compatible — Queryra works on WordPress 5.8+. Connector and ability features activate automatically on WordPress 7.0 and newer. Queryra is one of the early AI semantic search plugins to register as a WordPress 7.0 connector — making API key management consistent with other AI providers in Settings → Connectors. AI Search Setup in 5 Minutes ✅ Free demo — no credit card required ✅ No OpenAI account needed ✅ WooCommerce AI search ready in 5 minutes Start your free demo → Install and activate Follow the Setup Wizard Get your free API key at queryra.com/signup One-click WooCommerce product import Done — AI search now understands your customers No coding. No configuration headaches. WooCommerce AI Search Setup Guide → WooCommerce Product Search Features Natural Language Search – Customers type like they think, AI search finds what they need WooCommerce Product Search – Indexes titles, descriptions, SKUs, categories, tags, and attributes Semantic Search Ranking – AI ranks results by meaning, not alphabetical order Boost Controls – Promote products you want to sell more of Live Product Search – Instant AJAX-powered suggestions as customers type Auto-Sync – New WooCommerce products indexed automatically on publish Smart Context Detection – AI search activates on WooCommerce shop pages automatically Search Analytics – See what customers search for, including zero-result queries Page Builder Support – Indexes content from Elementor, Beaver Builder, Breakdance, Oxygen automatically Custom Field Indexing – Reads ACF and Meta Box custom fields out of the box WooCommerce Product Search Works With Any Store Beauty & Skincare – “my skin looks tired” finds night creams Fashion – “something for a summer wedding” finds dresses Electronics – “good laptop for video editing” finds the right specs Home & Garden – “cozy living room” finds rugs, lamps, pillows Food & Beverage – “healthy snacks for kids” finds the right products Semantic Search for WordPress Content Queryra’s semantic search also works with regular WordPress content — posts, pages, and custom post types. Well-suited for knowledge bases, blogs, and FAQ sections. AI Search for B2B and Wholesale Stores AI Search includes native B2BKing integration starting from version 1.4.1. The bulk order form’s keyword search is replaced with semantic AI product search — your B2B buyers find products by intent, not just exact SKUs or names. Wholesale-specific use cases supported: “warm jackets for winter — bulk order” “shirts in cotton, breathable, wholesale pricing” “keychains and accessories — high quantity” B2B visibility rules (group restrictions, per-product permissions, category-level access) are fully respected. Works for B2BKing, B2BWoo, and manual B2B WooCommerce setups. Why Replace Default WooCommerce Search? Default WooCommerce product search matches exact words. If your product is “Velora Overnight Recovery Oil” and someone types “my skin looks tired”, they get nothing. AI search fixes that — customers find products even with vague or natural language queries. Why Queryra vs Other WooCommerce Product Search Plugins? No OpenAI Account Required — Queryra includes its own search backend, so you don’t need to create a separate OpenAI account or manage external API keys. Indexed on YOUR WooCommerce Store — Queryra learns from YOUR products, descriptions, and categories — not generic global data. Intent-Aware AI Search — Most semantic search plugins only match meaning. Queryra goes further: “wireless headphones under $80, not Beats” applies the price filter AND excludes the brand. Vector-only plugins ignore both. Why vector search isn’t enough → Privacy Queryra is built with privacy in mind. This section explains exactly what data leaves your WordPress site, what stays local, and how you stay in control as the store owner. What Queryra sends to the API Content indexing (posts, pages, products): For every published item of the post types you enable (default: posts and pages; optionally products), Queryra sends: Title, content, excerpt (HTML stripped) Post type, permalink, featured image URL Categories and tags (names only) For WooCommerce products: price, stock quantity, SKU, brand, short description, product attributes (e.g. Color, Size) Featured/sticky flag (used to boost ranking of highlighted content) That’s it. This is the same data your site already shows publicly on the frontend — Queryra does not read private posts, drafts, or protected content. Search queries: When a visitor types in your search box, only the query text is sent to the API. The API returns matching post IDs, which WordPress then renders normally from your own database. Anonymous usage analytics: On plugin lifecycle events (activation, deactivation, setup milestones and error reports), Queryra sends: a randomly generated instance UUID (stored locally, no link to any user), WordPress version, PHP version, plugin version, WooCommerce active flag, whether AI search is switched on, which content types you enabled for indexing, and counts of posts, pages, products and public custom post types. This helps us prioritize compatibility fixes. You can disable this entirely by adding the following line to your wp-config.php: define('QUERYRA_DISABLE_ANALYTICS', true); Site profile (optional, user-declared): When the setup wizard opens you may optionally answer what kind of site you run and what you expect from search. Your answer is sent to Queryra once and is not stored on your site; only a small flag stays locally so the question is not asked twice. Skipping sends no answer — only the fact that you skipped, so we can tell a decline apart from never having seen the question. You can answer or update it at any time in Settings → Site Profile. Deactivation feedback (optional): If you choose to submit the feedback form when deactivating, your selected reason and comments are sent to Queryra together with your site URL, the plugin version and — only if you enter one — your email address for a reply. Skipping the form sends no feedback content; the deactivation event records only whether the form was submitted, skipped, or never shown. What Queryra NEVER sends No visitor IP addresses No user agents or browser fingerprints No cookies or session identifiers No customer accounts, emails, or order data No browsing history or behavior tracking No personally identifiable information (PII) about searchers or customers No private, draft, password-protected or unpublished content Your control as a store owner Choose which post types are indexed (Settings → Queryra) Disable AI search anytime — WordPress falls back to native search Deactivate the plugin to stop all data transmission Delete indexed records from the Queryra dashboard Security Queryra is publicly tracked by independent security and quality services: WPScan vulnerability database PluginTests static analysis and smoke tests Source code on GitHub No third-party frontend scripts: Queryra loads only its own minimal stylesheet on public pages. No external JavaScript, no tracking pixels, no third-party CDN requests on the frontend. Responsible disclosure: Found a security issue? Email contact@queryra.com. We will investigate on a best-effort basis and credit reporters in the changelog. Full privacy policy: queryra.com/privacy Additional Information Support AI Search Documentation FAQ WooCommerce Product Search Setup Email: support@queryra.com Links WooCommerce AI Search Live Demo Partner Program WooCommerce Search & AI Product Discovery Blog GitHub