eeoom GEO is a Generative Engine Optimization plugin for WordPress that helps you analyze and improve important pages for AI search.<\/p>\n\n
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.<\/p>\n\n
The plugin brings together four complementary workflows:<\/p>\n\n
Instead of focusing only on technical markup, eeoom GEO combines analysis and improvement workflows with structured data and entity infrastructure.<\/p>\n\n
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.<\/p>\n\n
Core features include:<\/p>\n\n
eeoom GEO does not automatically rewrite page content.<\/p>\n\n
Improvement tools provide structured insights and questions that can help editors decide what information should be added, clarified or expanded on an existing page.<\/p>\n\n
Source of Trust and EntityPool are optional external services.<\/p>\n\n
They are not contacted until an authorized user explicitly connects or uses the corresponding integration.<\/p>\n\n
Source of Trust analyses and improvement audits are started manually. The plugin does not silently submit pages for analysis in the background.<\/p>\n\n
Full data-use, endpoint and privacy details are provided in the External services section below.<\/p>\n\n
The external services used by eeoom GEO are operated by eeoom.<\/p>\n\n
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.<\/p>\n\n
Each service is used only for the features described below.<\/p>\n\n
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.<\/p>\n\n
The integration is activated only when an authorized WordPress user explicitly enables the corresponding eeoom GEO Suite functionality.<\/p>\n\n
Plugin activation, normal page views and visits by public website users do not initiate a connection to the Source of Trust API.<\/p>\n\n
On the initial connection, the plugin sends:<\/p>\n\n
wordpress<\/code> as optional client-platform metadata<\/li>\n- standard HTTP request metadata<\/li>\n<\/ul>\n\n
The service returns a Suite installation credential and identifiers for the central workspace, site, homepage Page and homepage Monitor.<\/p>\n\n
The credential is stored in the WordPress database and used as a Bearer credential for later authenticated requests.<\/p>\n\n
After the explicit connection, depending on the requested operation, the plugin may send:<\/p>\n\n
\n- the Suite installation credential as a Bearer credential<\/li>\n
- the current public probe URL generated by this WordPress installation<\/li>\n
- workspace, Page, Monitor and AuditRun identifiers<\/li>\n
- published public URLs selected for monitoring<\/li>\n
- the requested audit type<\/li>\n
- lifecycle status when the connected plugin is activated or deactivated<\/li>\n
- standard HTTP request metadata<\/li>\n<\/ul>\n\n
The public probe URL contains an opaque random token and returns only HTTP 204 for the valid token or HTTP 404 otherwise.<\/p>\n\n
It does not expose installation, account, entity, configuration, version or product-status data.<\/p>\n\n
Source of Trust does not currently perform scheduled probes.<\/p>\n\n
The plugin does not send:<\/p>\n\n
\n- draft content<\/li>\n
- private content<\/li>\n
- preview URLs<\/li>\n
- WordPress post body content<\/li>\n
- visitor data<\/li>\n
- passwords or WordPress user credentials<\/li>\n
- personal WordPress user data<\/li>\n<\/ul>\n\n
Analyses and improvement audits are started manually by an authorized WordPress user and may be processed asynchronously.<\/p>\n\n
To perform the requested audit, Source of Trust may retrieve and analyze the publicly accessible response of the selected URL.<\/p>\n\n
The plugin itself does not transmit WordPress post body content.<\/p>\n\n
The plugin may receive an AuditRun ID and poll the Source of Trust API for that specific result.<\/p>\n\n
Depending on the selected audit, Source of Trust may also use external search signals and AI processing to generate analysis or improvement results.<\/p>\n\n
Returned data may include:<\/p>\n\n
\n- central workspace, Page, Monitor and policy data<\/li>\n
- AuditRun status and history<\/li>\n
- optional scores<\/li>\n
- findings and issues<\/li>\n
- recommendations<\/li>\n
- page-improvement results<\/li>\n
- Customer Questions<\/li>\n
- supporting search signals where applicable<\/li>\n<\/ul>\n\n
Service:<\/p>\n\n
\n- Source of Trust: https:\/\/sourceoftrust.com\/<\/li>\n
- Production API: https:\/\/api.sourceoftrust.com\/<\/li>\n
- Terms of Service: https:\/\/sourceoftrust.com\/en\/terms<\/li>\n
- Privacy Policy: https:\/\/sourceoftrust.com\/en\/privacy<\/li>\n<\/ul>\n\n
EntityPool<\/h4>\n\n
EntityPool is an eeoom service for centrally managed entities, relationships and entity graphs.<\/p>\n\n
EntityPool is optional.<\/p>\n\n
The integration is activated only when an authorized WordPress user explicitly enters an EntityPool integration key and connects the WordPress site.<\/p>\n\n
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.<\/p>\n\n
Depending on the requested operation, the plugin may send:<\/p>\n\n
\n- the EntityPool integration key as a Bearer credential<\/li>\n
- the UID of a selected EntityPool entity as part of an entity-specific API request<\/li>\n
- standard HTTP request metadata<\/li>\n<\/ul>\n\n
The plugin does not send WordPress post body content, visitor data, passwords or WordPress user credentials to EntityPool.<\/p>\n\n
EntityPool may return:<\/p>\n\n
\n- graph identifiers<\/li>\n
- graph name<\/li>\n
- graph revision<\/li>\n
- root entity information<\/li>\n
- entity and relationship counts<\/li>\n
- entities available in the connected graph<\/li>\n
- Full Graph JSON-LD representations<\/li>\n
- entity-specific Subgraph JSON-LD representations<\/li>\n
- available saved Representations and their stable IDs<\/li>\n
- Representation name, Primary Entity and semantic revision metadata<\/li>\n
- finished saved Representation JSON-LD projections<\/li>\n<\/ul>\n\n
The plugin contacts EntityPool when required for actions such as:<\/p>\n\n
\n- connecting an EntityPool graph<\/li>\n
- manually checking the connection<\/li>\n
- refreshing the available entity list<\/li>\n
- refreshing an expired editor entity cache<\/li>\n
- refreshing the available Representation list<\/li>\n
- manually revalidating all known local EntityPool caches in one global refresh<\/li>\n
- retrieving graph data that is not yet available locally<\/li>\n
- revalidating the global graph revision<\/li>\n
- refreshing a Full Graph or Subgraph after a semantic graph change<\/li>\n
- conditionally revalidating an expired saved Representation using its own ETag<\/li>\n<\/ul>\n\n
EntityPool graph data is cached locally in WordPress.<\/p>\n\n
Public frontend requests do not contact EntityPool on every page load.<\/p>\n\n
A relevant frontend request can trigger a lightweight graph revalidation when EntityPool graph data is needed and the global validation interval has elapsed.<\/p>\n\n
If the semantic graph revision has not changed, the existing Full Graph and cached Subgraphs remain valid and are not downloaded again.<\/p>\n\n
Saved Representations are cached and revalidated independently.<\/p>\n\n
Their cache validity is determined by the semantic revision and ETag of the specific Representation rather than the global graph revision.<\/p>\n\n
EntityPool graph synchronization does not require WP-Cron, system cron, background workers or external schedulers.<\/p>\n\n
The local Schema & Entity functionality and GEO analysis features continue to work without EntityPool.<\/p>\n\n
Service:<\/p>\n\n
\n- EntityPool: https:\/\/entitypool.com\/<\/li>\n
- Application: https:\/\/entitypool.com\/app\/<\/li>\n
- Terms of Service: https:\/\/entitypool.com\/terms<\/li>\n
- Privacy Policy: https:\/\/entitypool.com\/privacy<\/li>\n
- Imprint: https:\/\/entitypool.com\/imprint<\/li>\n<\/ul>\n\n\n
\n- Install and activate eeoom GEO through the WordPress Plugins screen.<\/li>\n
- Open eeoom GEO in the WordPress admin.<\/li>\n
- Add strategically important pages under AI Search Monitors.<\/li>\n
- Use Analyze page to run available GEO and structured-data analyses.<\/li>\n
- Use Improve page to discover page-specific content improvement opportunities.<\/li>\n
- Open Schema & Entity to configure local entity signals.<\/li>\n
- Optional: Connect an EntityPool graph under Schema & Entity \u2192 EntityPool.<\/li>\n
- Optional: Map posts, pages and public custom post types to their Primary Entity.<\/li>\n
- Optional: Select Custom Graph and choose a saved EntityPool Representation for individual content.<\/li>\n<\/ol>\n\n
A supported schema integration is required for connected EntityPool graph output on the frontend.<\/p>\n\n\n
\nWhat is eeoom GEO?<\/h3><\/dt>\neeoom GEO is a Generative Engine Optimization plugin for WordPress.<\/p>\n\n
It provides tools for analyzing and improving WordPress pages for AI search.<\/p>\n\n
This includes GEO and structured-data analysis, AI-assisted content improvement, Customer Questions, AI Search Monitors, entity optimization, Primary Entity mapping and connected entity graphs.<\/p><\/dd>\n
What does GEO mean?<\/h3><\/dt>\nGEO stands for Generative Engine Optimization.<\/p>\n\n
It focuses on improving the signals that help generative search and answer systems understand websites, entities, relationships, relevance and context.<\/p><\/dd>\n
Can eeoom GEO help me improve my website content?<\/h3><\/dt>\nYes.<\/p>\n\n
eeoom GEO includes page-specific improvement tools that analyze the context of an existing public page and relevant search signals to identify useful content opportunities.<\/p>\n\n
The goal is not to automatically rewrite your content.<\/p>\n\n
Instead, eeoom GEO helps you understand what users may want to know and which information could be added, clarified or expanded on the page.<\/p><\/dd>\n
What is the difference between Analyze page and Improve page?<\/h3><\/dt>\nAnalyze page focuses on evaluating the current state of a page.<\/p>\n\n
Depending on the available audit, it can provide scores, findings, issues and recommendations related to GEO or structured data.<\/p>\n\n
Improve page focuses on actionable opportunities for improving the content of that page.<\/p>\n\n
It can use page context, search signals and AI-assisted analysis to identify useful questions or information that may be worth addressing.<\/p>\n\n
The two workflows are independent.<\/p>\n\n
You do not need to run an Analyze audit before using Improve page.<\/p><\/dd>\n
What are Customer Questions?<\/h3><\/dt>\nCustomer Questions is a page-specific AI-assisted improvement analysis.<\/p>\n\n
It identifies questions potential customers may ask about the topic of a specific page.<\/p>\n\n
The analysis combines the existing page context with relevant search suggestions, filters unrelated signals and groups useful results into customer-oriented questions.<\/p>\n\n
These questions can help editors identify information that may be useful to add, clarify or expand on the page.<\/p><\/dd>\n
Does eeoom GEO automatically generate or rewrite my content?<\/h3><\/dt>\nNo.<\/p>\n\n
eeoom GEO provides analysis and improvement insights.<\/p>\n\n
It does not automatically replace or publish page content.<\/p>\n\n
Editors remain in control of which recommendations or questions are relevant and how the page should be improved.<\/p><\/dd>\n
Are the content improvement ideas generated only by AI?<\/h3><\/dt>\nNo.<\/p>\n\n
Where applicable, eeoom GEO combines the existing page context with external search signals and AI-assisted filtering and structuring.<\/p>\n\n
For example, Customer Questions uses page context together with relevant search suggestions to identify questions that fit the actual topic of the page.<\/p>\n\n
The goal is to provide page-specific improvement insights rather than generic AI-generated topic lists.<\/p><\/dd>\n
What are AI Search Monitors?<\/h3><\/dt>\nAI Search Monitors are selected WordPress URLs that are strategically important for AI search.<\/p>\n\n
Each monitor represents one public page that can be analyzed and improved through the available eeoom GEO workflows.<\/p>\n\n
From a monitored page, authorized users can open the Analyze page area for GEO checks or the Improve page area for content improvement tools.<\/p><\/dd>\n
Are AI Search Monitor analyses automatic?<\/h3><\/dt>\nNo.<\/p>\n\n
Analyses and improvement audits are started manually by an authorized WordPress user.<\/p>\n\n
If the Source of Trust API processes an audit asynchronously, eeoom GEO polls for the result of that specific AuditRun.<\/p><\/dd>\n
Does the plugin send my WordPress content to the checking service?<\/h3><\/dt>\nNo.<\/p>\n\n
Manual analyses send the public URL of the selected published content.<\/p>\n\n
Source of Trust may retrieve the publicly accessible response of that URL in order to perform the requested analysis.<\/p>\n\n
Drafts, private posts, preview URLs, WordPress post body content and personal WordPress user data are not submitted by the plugin.<\/p><\/dd>\n
Do I need EntityPool?<\/h3><\/dt>\nNo.<\/p>\n\n
AI Search Monitors, Analyze page, Improve page, GEO checks and local Schema & Entity functionality work without EntityPool.<\/p>\n\n
EntityPool adds centrally managed entity graphs, Primary Entity mapping, Full Graph and Subgraph integration and connected entity relationships.<\/p>\n\n
It also provides saved Representations that can be selected as explicitly curated Custom Graphs for individual WordPress pages.<\/p><\/dd>\n
What is a Primary Entity?<\/h3><\/dt>\nA Primary Entity is the main real-world entity associated with a WordPress page, post or public custom post type.<\/p>\n\n
For example, a page may primarily represent a person, organization, location, product, service or topic.<\/p>\n\n
eeoom GEO stores the EntityPool UID with the WordPress content while the entity itself remains managed in EntityPool.<\/p><\/dd>\n
What happens on the homepage when EntityPool is connected?<\/h3><\/dt>\nThe homepage uses the complete connected EntityPool graph.<\/p>\n\n
The root entity can be integrated with the website's existing organization entity so that the structured graph contains one connected representation instead of duplicate definitions.<\/p><\/dd>\n
What happens on a mapped page?<\/h3><\/dt>\neeoom GEO retrieves the EntityPool Subgraph associated with the selected Primary Entity.<\/p>\n\n
The entity and its relevant relationships are connected with the structured data of the current page.<\/p><\/dd>\n
What is a Custom Graph?<\/h3><\/dt>\nA Custom Graph is a saved EntityPool Representation selected for a specific WordPress post, page or public custom post type.<\/p>\n\n
The Representation and its finished JSON-LD projection remain managed in EntityPool.<\/p>\n\n
WordPress stores only its stable ID.<\/p>\n\n
If the Representation is unavailable, eeoom GEO does not replace it with a broader Standard Graph.<\/p><\/dd>\n
Does eeoom GEO download EntityPool graph data on every request?<\/h3><\/dt>\nNo.<\/p>\n\n
Graph data is cached locally.<\/p>\n\n
A graph-wide semantic revision is used to determine whether cached Full Graph and Subgraph data is still current.<\/p>\n\n
If nothing has changed, existing cached representations remain valid.<\/p>\n\n
If the graph changes, only the representation currently required is refreshed.<\/p>\n\n
Saved Custom Graph Representations are validated independently.<\/p>\n\n
A change to one saved Representation does not invalidate other Representation payloads.<\/p><\/dd>\n
Does EntityPool synchronization require WP-Cron?<\/h3><\/dt>\nNo.<\/p>\n\n
Graph synchronization is request-driven and does not depend on WP-Cron, system cron, background workers, external schedulers, webhooks or loopback requests.<\/p><\/dd>\n