Title: Aivec AI Search Schema
Author: Aivec LLC
Published: <strong>15 de marzo de  2026</strong>
Last modified: 4 de agosto de  2026

---

Buscar plugins

![](https://ps.w.org/aivec-ai-search-schema/assets/banner-772x250.png?rev=3633689)

![](https://ps.w.org/aivec-ai-search-schema/assets/icon-256x256.png?rev=3633689)

# Aivec AI Search Schema

 Por [Aivec LLC](https://profiles.wordpress.org/aivectai/)

[Descargar](https://downloads.wordpress.org/plugin/aivec-ai-search-schema.1.3.1.zip)

 * [Detalles](https://es-ar.wordpress.org/plugins/aivec-ai-search-schema/#description)
 * [Valoraciones](https://es-ar.wordpress.org/plugins/aivec-ai-search-schema/#reviews)
 * [Desarrollo](https://es-ar.wordpress.org/plugins/aivec-ai-search-schema/#developers)

 [Soporte](https://wordpress.org/support/plugin/aivec-ai-search-schema/)

## Descripción

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 / ジオコーディング

 1. 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制限、クォータ設定を行って
    ください。
 2.  * Google Cloud Console で新規プロジェクトを作成し、**Geocoding API** を有効化（
       他 API は不要）
     * 「認証情報」から API キーを発行し、HTTP リファラーまたは IP 制限を設定
     * 1 日あたりのクォータ上限を設定して不正利用を防止
 3. 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 には出力されません。
 4. 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 秒のレート制御とキャッシュ
    を実装しているため、住所を変更したタイミングのみ再取得してください。
 5. 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 / セットアップ

 1. Upload the plugin folder to `wp-content/plugins/aivec-ai-search-schema`
     プラグ
    イン一式を `wp-content/plugins/aivec-ai-search-schema` に配置
 2. Activate from WordPress admin
     管理画面で有効化
 3. Open **Settings  AI Search Schema** and complete the forms
     **設定  AI Search Schema**
    で各項目（ブランド情報／店舗情報／SNS／APIキー 等）を入力して保存

### FAQ / よくある質問

See [See the FAQ on GitHub:](https://github.com/aivec/ai-search-schema/blob/main/docs/FAQ.md)
for frequently asked questions about:
 よくある質問については [See the FAQ on GitHub:](https://github.com/aivec/ai-search-schema/blob/main/docs/FAQ.md)
をご覧ください：

 * 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](https://github.com/aivec/ai-search-schema/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/

## Capturas

[⌊Schema console — manage brand, site identity, and JSON-LD output from a single
settings screen.⌉⌊Schema console — manage brand, site identity, and JSON-LD output
from a single settings screen.⌉[

Schema console — manage brand, site identity, and JSON-LD output from a single settings
screen.

[⌊Page-type schema controls — override schema type, breadcrumbs, FAQ extraction,
and priority per post type and taxonomy.⌉⌊Page-type schema controls — override schema
type, breadcrumbs, FAQ extraction, and priority per post type and taxonomy.⌉[

Page-type schema controls — override schema type, breadcrumbs, FAQ extraction, and
priority per post type and taxonomy.

[⌊Local details & hours — Google's recommended LocalBusiness properties with a real-
time completeness check.⌉⌊Local details & hours — Google's recommended LocalBusiness
properties with a real-time completeness check.⌉[

Local details & hours — Google’s recommended LocalBusiness properties with a real-
time completeness check.

[⌊AEO/GEO diagnostics — validates Organization, LocalBusiness, WebSite, and WebPage
schema before it ships.⌉⌊AEO/GEO diagnostics — validates Organization, LocalBusiness,
WebSite, and WebPage schema before it ships.⌉[

AEO/GEO diagnostics — validates Organization, LocalBusiness, WebSite, and WebPage
schema before it ships.

[⌊Setup wizard — guided configuration that gets structured data live in about five
minutes.⌉⌊Setup wizard — guided configuration that gets structured data live in 
about five minutes.⌉[

Setup wizard — guided configuration that gets structured data live in about five
minutes.

## Preguntas frecuentes

### Does it support multiple locations?

Current version supports a single LocalBusiness location. Use separate sites or 
custom extensions for multi-store setups.

### How often does geocoding run?

It runs only when you click “Fetch coordinates from address” or when address fields
change. Repeated requests are rate limited (10 seconds).

### What is llms.txt?

llms.txt is a standard for helping AI systems understand your site structure. See
[llmstxt.org](https://llmstxt.org/) for the specification. This plugin auto-generates
the file at yoursite.com/llms.txt.

### Can I use this with other SEO plugins?

Yes! This plugin automatically suppresses conflicting schema output from Yoast SEO,
Rank Math, and All in One SEO.

## Reseñas

No hay reseñas para este plugin.

## Colaboradores y desarrolladores

“Aivec AI Search Schema” es un software de código abierto. Las siguientes personas
han colaborado con este plugin.

Colaboradores

 *   [ Aivec LLC ](https://profiles.wordpress.org/aivectai/)

[Traduce “Aivec AI Search Schema” a tu idioma.](https://translate.wordpress.org/projects/wp-plugins/aivec-ai-search-schema)

### ¿Interesado en el desarrollo?

[Revisa el código](https://plugins.trac.wordpress.org/browser/aivec-ai-search-schema/),
echa un vistazo al [repositorio SVN](https://plugins.svn.wordpress.org/aivec-ai-search-schema/),
o suscríbete al [log de desarrollo](https://plugins.trac.wordpress.org/log/aivec-ai-search-schema/)
por [RSS](https://plugins.trac.wordpress.org/log/aivec-ai-search-schema/?limit=100&mode=stop_on_copy&format=rss).

## Registro de cambios

#### 1.3.1

 * [Fixed] Fixed the setup notice staying visible on sites configured from the settings
   screen instead of the wizard
 * [Fixed] Fixed Japanese labels for business hours, logo selection, store photo
   selection, and prefecture selection
 * [Fixed] Fixed the Japanese validation summary dropping the issue count from “%
   d error” and “%d warning”
 * [Fixed] Fixed several Japanese diagnostic messages reporting the opposite of 
   the actual result
 * [Changed] Included LICENSE.txt in the distributed package
 * [Changed] Fixed the build task order so the packaged files carry the correct 
   version number

#### 1.3.0

 * [Fixed] Fixed a fatal error on Product schema pages when WooCommerce is not active
 * [Fixed] Fixed llms.txt being HTML-escaped, which broke Markdown quotes and apostrophes
 * [Fixed] Fixed llms.txt redirecting to a trailing-slash URL instead of serving
   directly
 * [Security] Blocked PHP object injection when restoring serialized product meta
 * [Changed] Raised the minimum supported WordPress version to 6.5
 * [Changed] Confirmed compatibility with WordPress 7.0
 * [Changed] Added X-Content-Type-Options: nosniff to the llms.txt response
 * [Changed] Consolidated translation templates into a single aivec-ai-search-schema.
   pot

#### 1.2.3

 * Escape output in templates for WP.org compliance

#### 1.2.2

 * Added ZipCloud API endpoint, Terms, and Privacy to External Services
 * Compressed changelog to recent versions only
 * Removed PHPCS ignore comments with proper escaping

#### 1.2.0

 * WP.org compliance: Removed bundled dependencies from distribution
 * WP.org compliance: Prefixed script handles for conflict avoidance
 * WP.org compliance: Updated build configuration for cleaner distribution

#### 1.0.0

 * Initial release with Organization/LocalBusiness JSON-LD
 * Article, FAQ, QAPage, Product schema support
 * BreadcrumbList and ItemList structured data
 * Google Maps geocoding with OpenStreetMap fallback
 * llms.txt generation for AI systems
 * Self-diagnostics and schema conflict suppression

## Meta

 *  Versión **1.3.1**
 *  Última actualización **hace 2 meses**
 *  Instalaciones activas **Menos de 10**
 *  Versión de WordPress ** 6.5 o superior **
 *  Testeado hasta **7.0.7**
 *  Versión de PHP ** 8.0 o superior **
 *  Idioma
 * [English (US)](https://wordpress.org/plugins/aivec-ai-search-schema/)
 * Etiquetas:
 * [ai search](https://es-ar.wordpress.org/plugins/tags/ai-search/)[llms.txt](https://es-ar.wordpress.org/plugins/tags/llms-txt/)
   [local seo](https://es-ar.wordpress.org/plugins/tags/local-seo/)[schema](https://es-ar.wordpress.org/plugins/tags/schema/)
   [structured data](https://es-ar.wordpress.org/plugins/tags/structured-data/)
 *  [Vista avanzada](https://es-ar.wordpress.org/plugins/aivec-ai-search-schema/advanced/)

## Valoraciones

Todavía no se enviaron reseñas.

[Your review](https://wordpress.org/support/plugin/aivec-ai-search-schema/reviews/#new-post)

[Ver todas las reseñas](https://wordpress.org/support/plugin/aivec-ai-search-schema/reviews/)

## Colaboradores

 *   [ Aivec LLC ](https://profiles.wordpress.org/aivectai/)

## Soporte

¿Tenés algo que decir? ¿Necesitás ayuda?

 [Ver el foro de asistencia](https://wordpress.org/support/plugin/aivec-ai-search-schema/)