eeoom GEO – AI Search Optimization

Description

eeoom GEO is a Generative Engine Optimization plugin for WordPress that helps you analyze and improve important pages for AI search.

It combines GEO analysis, AI-assisted content improvement, structured data optimization and entity-based signals to help search and AI systems better understand your website, its content and the real-world entities behind it.

The plugin brings together four complementary workflows:

• Analyze important WordPress pages with GEO and structured-data checks.
• Improve existing page content with AI-assisted insights based on page context and relevant search signals.
• Optimize machine-readable organization and entity signals.
• Connect WordPress content with centrally managed real-world entities and relationships through the optional EntityPool integration.

Instead of focusing only on technical markup, eeoom GEO combines analysis and improvement workflows with structured data and entity infrastructure.

This makes it possible to identify issues, understand what information may be useful to users and strengthen the signals that help AI systems interpret a page correctly.

Core features include:

• AI Search Monitors for strategically important published public URLs.
• Page-specific GEO and structured-data analysis with centrally stored status, scores, findings and recommendations.
• AI-assisted page improvement tools for discovering relevant content opportunities.
• Customer Questions analysis for identifying questions potential customers may ask about the topic of a specific page.
• Improvement results based on page context and relevant search signals rather than generic AI-generated content ideas.
• Separate Analyze page and Improve page workflows for each monitored page.
• Server-controlled audit availability with clear Recheck timing.
• Local Organization schema enhancements such as sameAs, address, areaServed and knowsAbout.
• Optional EntityPool Full Graph, entity-specific Subgraph and saved Representation integration.
• Primary Entity mapping for posts, pages and public custom post types.
• Integration into supported JSON-LD output, including Yoast SEO graphs.
• Persistent EntityPool caching with revision- and ETag-based revalidation.
• Capability and nonce checks for administrative actions.

eeoom GEO does not automatically rewrite page content.

Improvement tools provide structured insights and questions that can help editors decide what information should be added, clarified or expanded on an existing page.

Source of Trust and EntityPool are optional external services.

They are not contacted until an authorized user explicitly connects or uses the corresponding integration.

Source of Trust analyses and improvement audits are started manually. The plugin does not silently submit pages for analysis in the background.

Full data-use, endpoint and privacy details are provided in the External services section below.

External services

The external services used by eeoom GEO are operated by eeoom.

They provide server-side GEO analysis, AI-assisted page improvement and centrally managed entity graph functionality that cannot be performed entirely inside the WordPress plugin.

Each service is used only for the features described below.

Source of Trust API

Source of Trust is an eeoom service used for the shared Suite installation identity, centrally managed monitored pages and manually initiated GEO, structured-data and page-improvement analyses.

The integration is activated only when an authorized WordPress user explicitly enables the corresponding eeoom GEO Suite functionality.

Plugin activation, normal page views and visits by public website users do not initiate a connection to the Source of Trust API.

On the initial connection, the plugin sends:

• the public WordPress home URL
• wordpress as optional client-platform metadata
• standard HTTP request metadata

The service returns a Suite installation credential and identifiers for the central workspace, site, homepage Page and homepage Monitor.

The credential is stored in the WordPress database and used as a Bearer credential for later authenticated requests.

After the explicit connection, depending on the requested operation, the plugin may send:

• the Suite installation credential as a Bearer credential
• the current public probe URL generated by this WordPress installation
• workspace, Page, Monitor and AuditRun identifiers
• published public URLs selected for monitoring
• the requested audit type
• lifecycle status when the connected plugin is activated or deactivated
• standard HTTP request metadata

The public probe URL contains an opaque random token and returns only HTTP 204 for the valid token or HTTP 404 otherwise.

It does not expose installation, account, entity, configuration, version or product-status data.

Source of Trust does not currently perform scheduled probes.

The plugin does not send:

• draft content
• private content
• preview URLs
• WordPress post body content
• visitor data
• passwords or WordPress user credentials
• personal WordPress user data

Analyses and improvement audits are started manually by an authorized WordPress user and may be processed asynchronously.

To perform the requested audit, Source of Trust may retrieve and analyze the publicly accessible response of the selected URL.

The plugin itself does not transmit WordPress post body content.

The plugin may receive an AuditRun ID and poll the Source of Trust API for that specific result.

Depending on the selected audit, Source of Trust may also use external search signals and AI processing to generate analysis or improvement results.

Returned data may include:

• central workspace, Page, Monitor and policy data
• AuditRun status and history
• optional scores
• findings and issues
• recommendations
• page-improvement results
• Customer Questions
• supporting search signals where applicable

Service:

• Source of Trust: https://sourceoftrust.com/
• Production API: https://api.sourceoftrust.com/
• Terms of Service: https://sourceoftrust.com/en/terms
• Privacy Policy: https://sourceoftrust.com/en/privacy

EntityPool

EntityPool is an eeoom service for centrally managed entities, relationships and entity graphs.

EntityPool is optional.

The integration is activated only when an authorized WordPress user explicitly enters an EntityPool integration key and connects the WordPress site.

The integration key is sent to EntityPool as a Bearer credential and stored in the WordPress database so the site can access the graph associated with that key.

Depending on the requested operation, the plugin may send:

• the EntityPool integration key as a Bearer credential
• the UID of a selected EntityPool entity as part of an entity-specific API request
• standard HTTP request metadata

The plugin does not send WordPress post body content, visitor data, passwords or WordPress user credentials to EntityPool.

EntityPool may return:

• graph identifiers
• graph name
• graph revision
• root entity information
• entity and relationship counts
• entities available in the connected graph
• Full Graph JSON-LD representations
• entity-specific Subgraph JSON-LD representations
• available saved Representations and their stable IDs
• Representation name, Primary Entity and semantic revision metadata
• finished saved Representation JSON-LD projections

The plugin contacts EntityPool when required for actions such as:

• connecting an EntityPool graph
• manually checking the connection
• refreshing the available entity list
• refreshing an expired editor entity cache
• refreshing the available Representation list
• manually revalidating all known local EntityPool caches in one global refresh
• retrieving graph data that is not yet available locally
• revalidating the global graph revision
• refreshing a Full Graph or Subgraph after a semantic graph change
• conditionally revalidating an expired saved Representation using its own ETag

EntityPool graph data is cached locally in WordPress.

Public frontend requests do not contact EntityPool on every page load.

A relevant frontend request can trigger a lightweight graph revalidation when EntityPool graph data is needed and the global validation interval has elapsed.

If the semantic graph revision has not changed, the existing Full Graph and cached Subgraphs remain valid and are not downloaded again.

Saved Representations are cached and revalidated independently.

Their cache validity is determined by the semantic revision and ETag of the specific Representation rather than the global graph revision.

EntityPool graph synchronization does not require WP-Cron, system cron, background workers or external schedulers.

The local Schema & Entity functionality and GEO analysis features continue to work without EntityPool.

Service:

• EntityPool: https://entitypool.com/
• Application: https://entitypool.com/app/
• Terms of Service: https://entitypool.com/terms
• Privacy Policy: https://entitypool.com/privacy
• Imprint: https://entitypool.com/imprint

Technical details

Version	1.9.0
Last updated	September 29, 2026
Active installs	10+
Rating	★★★★★ 5/5 (2 reviews)
Requires WordPress	6.2 or higher
Requires PHP	7.4 or higher
Author	eeoom
Tags	ai-search, entity-seo, generative-engine-optimization, geo, structured-data