Aivec LLC

AI-focused structured data (JSON-LD) for LocalBusiness, breadcrumbs, FAQ extraction, and llms.txt.
<h3>Overview / 概要</h3>
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 を一括生成できます。
<h3>Why Structured Data Matters Now / 今、構造化データが重要な理由</h3>
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検索最適化が重要な理由
<ul>
<li>AI citations: When AI assistants answer questions, they cite sources. Proper schema increases the chance of being cited. 
AI引用: AIアシスタントが質問に回答する際、出典を引用します。適切なスキーマは引用される可能性を高めます。</li>
<li>Rich results: Google displays enhanced search results (stars, prices, FAQs, breadcrumbs) for sites with valid schema. 
リッチリザルト: Googleは有効なスキーマを持つサイトに対し、拡張検索結果（星評価、価格、FAQ、パンくず）を表示します。</li>
<li>Local SEO/MEO: LocalBusiness schema directly powers Google Maps and local pack rankings. 
ローカルSEO/MEO: LocalBusinessスキーマはGoogleマップとローカルパックの順位に直接影響します。</li>
<li>Voice search: Structured data helps voice assistants provide accurate answers from your site. 
音声検索: 構造化データは音声アシスタントがあなたのサイトから正確な回答を提供することを助けます。</li>
</ul>
<h3>Features / 機能</h3>
<ul>
<li>Organization / LocalBusiness JSON-LD – address, geo, price range, payment methods, reservations, storefront imagery, <code>areaServed</code>, <code>branchOf</code> などを 1 つの @graph に統合 
Organization / LocalBusiness スキーマ：住所・緯度経度・価格帯・支払方法・予約可否・店舗画像・商圏情報を1つのJSON-LDに集約</li>
<li>Article / FAQ / QAPage / Product – per-post metabox lets editors switch schema types, auto injects FAQPage <code>mainEntity</code>, and WooCommerce products map to Product schema with offers/brand/rating/images 
投稿メタボックス切替 / WooCommerce連携：Article / FAQPage / QAPage / Product を選択可能。WooCommerce商品はブランド・価格・在庫・ギャラリー画像付き Product スキーマに自動変換</li>
<li>BreadcrumbList & ItemList – structured breadcrumbs plus archive ItemList, with optional frontend breadcrumbs template 
Structured Breadcrumbs：パンくず / アーカイブ ItemList を JSON-LD で出力し、テンプレートでも表示可能</li>
<li>SearchAction & Site metadata – <code>WebSite</code> includes SearchAction, supported languages, and SearchAction URLs 
SearchAction 対応：サイト内検索を SearchAction で明示し、対応言語タグを JSON-LD に反映</li>
<li>Automatic geocoding – Google Maps Geocoding API + OpenStreetMap fallback, rate limiting and caching 
ジオコーディング：Google Maps Geocoding API＋OSMフォールバック、レート制御・キャッシュ機能付き</li>
<li>Self-diagnostics – Validator checks required Google Rich Results properties (WebSite/Organization/LocalBusiness/Article/Product) and shows admin notices when fields are missing 
自己診断：Google推奨プロパティを自動検証し、不足項目を管理画面で警告</li>
<li>Multilingual admin – 全 UI と翻訳リソースを英語ベースで整備し、日本語翻訳を同梱 
多言語UI：英語ベースの翻訳ファイル＆日本語翻訳を標準同梱</li>
<li>llms.txt Generation – Auto-generate llms.txt to help AI systems understand your site structure. Editable in the settings. 
llms.txt生成：AI検索エンジンがサイト構造を理解しやすいllms.txtを自動生成。設定画面で編集可能</li>
</ul>
<h3>Geocoding / ジオコーディング</h3>
<ol>
<li>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制限、クォータ設定を行ってください。
<ul>
<li>Google Cloud Console で新規プロジェクトを作成し、Geocoding API を有効化（他 API は不要）</li>
<li>「認証情報」から API キーを発行し、HTTP リファラーまたは IP 制限を設定</li>
<li>1 日あたりのクォータ上限を設定して不正利用を防止</li>
</ul>
</li>
<li>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 には出力されません。</li>
<li>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 秒のレート制御とキャッシュを実装しているため、住所を変更したタイミングのみ再取得してください。</li>
<li>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 キーの設定を推奨します。</li>
</ol>
<h3>Security / セキュリティ</h3>
This plugin follows WordPress security best practices: 
本プラグインはWordPressのセキュリティベストプラクティスに従っています：
<ul>
<li>All settings require administrator privileges / 全設定に管理者権限が必要</li>
<li>User inputs are sanitized and validated / ユーザー入力はサニタイズ・検証済み</li>
<li>API keys are stored securely (never exposed in HTML) / APIキーは安全に保存（HTMLに露出しない）</li>
</ul>
<h3>Installation / セットアップ</h3>
<ol>
<li>Upload the plugin folder to <code>wp-content/plugins/aivec-ai-search-schema</code> 
プラグイン一式を <code>wp-content/plugins/aivec-ai-search-schema</code> に配置</li>
<li>Activate from WordPress admin 
管理画面で有効化</li>
<li>Open Settings → AI Search Schema and complete the forms 
設定 → AI Search Schema で各項目（ブランド情報／店舗情報／SNS／APIキー 等）を入力して保存</li>
</ol>
<h3>FAQ / よくある質問</h3>
See <a href="https://github.com/aivec/ai-search-schema/blob/main/docs/FAQ.md" rel="nofollow ugc">See the FAQ on GitHub:</a> for frequently asked questions about: 
よくある質問については <a href="https://github.com/aivec/ai-search-schema/blob/main/docs/FAQ.md" rel="nofollow ugc">See the FAQ on GitHub:</a> をご覧ください：
<ul>
<li>Schema conflicts with other plugins / 他プラグインとのスキーマ衝突</li>
<li>LocalBusiness schema setup / LocalBusinessスキーマの設定</li>
<li>Troubleshooting common issues / よくある問題のトラブルシューティング</li>
</ul>
<h3>License / ライセンス</h3>
GPLv2 or later
<h3>Support Policy</h3>
Free version support: Bug reports only.
<h4>What We Support</h4>
<ul>
<li>Bug reports with clear reproduction steps</li>
<li>Issues causing PHP errors or broken schema output</li>
</ul>
<h4>What We Do NOT Support</h4>
<ul>
<li>Usage questions (“How do I…?”)</li>
<li>SEO/AEO strategy consulting</li>
<li>Feature requests</li>
<li>Customization requests</li>
</ul>
<h4>Response Policy</h4>
<ul>
<li>Best effort – no guaranteed response time</li>
<li>Issues without reproduction steps will be closed</li>
<li>Bug reports: <a href="https://github.com/aivec/ai-search-schema/issues" rel="nofollow ugc">GitHub Issues</a> only</li>
<li>We do not provide support via WordPress.org forums.</li>
<li>WP.orgフォーラムでのサポートは行っておりません。</li>
</ul>
<h4>Required Information for Bug Reports</h4>
<ul>
<li>WordPress version, PHP version, plugin version</li>
<li>Theme name and active plugins (especially SEO plugins)</li>
<li>Steps to reproduce (mandatory)</li>
<li>Expected vs actual behavior</li>
<li>Error logs (if available)</li>
</ul>
<h3>External Services</h3>
This plugin can connect to external services only when you use specific features.
<h4>Google Maps Geocoding API (optional)</h4>
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
<h4>OpenStreetMap Nominatim (optional fallback)</h4>
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
<h4>ZipCloud (optional, Japan only)</h4>
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/

Aivec AI Search Schema

AI-focused structured data (JSON-LD) for LocalBusiness, breadcrumbs, FAQ extraction, and llms.txt.

Abhay Patel

Use natural language prompts to filter posts of any post type via AI.
<h3>Use Cases</h3>
Users can enter natural language prompts across any post type including products, posts, custom post types, and more.
<ul>
<li>
Product Specific Filters:
<ul>
<li>Get products published in May and are in stock</li>
<li>Get New arrivals in the Accessories category</li>
<li>Get products on sale in the electronics category</li>
<li>Get products with a sale price less than 30</li>
</ul>
</li>
<li>
Media-Based Filters:
<ul>
<li>Get posts without featured images</li>
<li>Get only products with gallery images</li>
</ul>
</li>
<li>
Logical Conditions (AND/OR):
<ul>
<li>Get Products in stock and published after Jan 1, 2024</li>
<li>Get products from last 7 days that are out of stock</li>
</ul>
</li>
</ul>
<h3>External Services</h3>
This plugin connects to an API provided by Cohere (https://cohere.com) to perform AI-powered filtering of WordPress posts and custom post types. It sends the prompt entered by the admin to Cohere’s <code>/v2/chat</code> endpoint. The API responds with a set of WP_Query arguments based on understanding of the prompt.
<h3>Details of the API integration</h3>
<ul>
<li>
What the service is: 
The plugin integrates with the Cohere Chat API (https://cohere.com), a third-party AI service that specializes in natural language understanding and generation.
</li>
<li>
What it is used for: 
The API is used to analyze admin-entered prompts and return relevant WP_Query arguments. These are used by the plugin to filter posts or custom post types intelligently, enabling semantic searching in the WordPress admin area.
</li>
<li>
What Data is Sent:
<ul>
<li>The prompt entered by the WordPress admin is sent to the Cohere API. No personal user or customer data is collected or transmitted.</li>
</ul>
</li>
<li>
Why the data is sent: 
The data is sent so that the Cohere API can understand the context of the content and the user’s intent behind the prompt. This allows it to return accurate WP_Query arguments to filter posts, instead of relying on simple keyword-based filters.
</li>
<li>
When Data is Sent: 
Only when the admin enters a prompt in the plugin interface and initiates the filter action
</li>
<li>
How Data is Sent: 
Data is sent via a secure <code>wp_remote_post()</code> request to <code>https://api.cohere.com/v2/chat</code>
</li>
<li>
Terms and Privacy:
<ul>
<li><a href="https://cohere.com/terms-of-use" rel="nofollow ugc">Cohere Terms of Use</a></li>
<li><a href="https://cohere.com/privacy" rel="nofollow ugc">Cohere Privacy Policy</a></li>
</ul>
</li>
</ul>
This API connection is essential for the plugin’s AI features to function. If you choose not to use the AI filtering functionality, the rest of the plugin remains functional.

Aivec AI Search Schema vs AI Post Filter with Cohere