VecPost AI Search for Posts vs Aivec AI Search Schema

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/

VecPost AI Search for Posts replaces WordPress’s default SQL LIKE search with vector-based semantic search. Instead of matching exact words, it understands the meaning of a search query. Example: A user searching “heart workouts” will find your post titled “Best cardiovascular exercises” – even though no words overlap – because the meanings are similar. How It Works When you publish a post, the plugin sends its content to your chosen AI provider (OpenAI or Google Gemini) to generate a vector embedding – a list of numbers that represents the meaning of the text. These numbers are stored in your database. When a user searches, their query is also converted to numbers, and the plugin finds posts whose numbers are closest – meaning most semantically similar. Features Semantic search powered by OpenAI (text-embedding-3-small or text-embedding-3-large) or Google Gemini (gemini-embedding-001) Hybrid re-ranking: combines semantic similarity with keyword matching for best results Gutenberg block and shortcode [vecpost_semantic_search] for easy placement Bulk indexer with progress bar for existing posts WP-CLI support: wp vecpost-semantic-search index, wp vecpost-semantic-search status, wp vecpost-semantic-search search "query" Configurable scoring thresholds via Settings -> VecPost – AI Semantic Search for Posts Automatic re-indexing when you switch embedding models Results cached via WordPress object cache (Redis/Memcached compatible) Third-Party Services This plugin sends post content to external AI APIs to generate embeddings. By using this plugin, you agree to the terms of service and privacy policies of your chosen provider: OpenAI: https://openai.com/policies/privacy-policy | https://openai.com/policies/terms-of-use Google Gemini: https://policies.google.com/privacy | https://ai.google.dev/terms No data is sent without your API key being configured. Data is only transmitted when posts are published or during bulk indexing. Performance Note Semantic search requires loading all embeddings into PHP memory for comparison. This works well for sites with up to approximately 1,500 posts. For larger sites, a dedicated vector database (pgvector, Qdrant, or Pinecone) is recommended.