ຄຳອະທິບາຍ
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
wordpressas 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
ການຕິດຕັ້ງ
- Install and activate eeoom GEO through the WordPress Plugins screen.
- Open eeoom GEO in the WordPress admin.
- Add strategically important pages under AI Search Monitors.
- Use Analyze page to run available GEO and structured-data analyses.
- Use Improve page to discover page-specific content improvement opportunities.
- Open Schema & Entity to configure local entity signals.
- Optional: Connect an EntityPool graph under Schema & Entity EntityPool.
- Optional: Map posts, pages and public custom post types to their Primary Entity.
- Optional: Select Custom Graph and choose a saved EntityPool Representation for individual content.
A supported schema integration is required for connected EntityPool graph output on the frontend.
ຄຳຖາມທີ່ພົບເລື້ອຍ
-
What is eeoom GEO?
-
eeoom GEO is a Generative Engine Optimization plugin for WordPress.
It provides tools for analyzing and improving WordPress pages for AI search.
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.
-
What does GEO mean?
-
GEO stands for Generative Engine Optimization.
It focuses on improving the signals that help generative search and answer systems understand websites, entities, relationships, relevance and context.
-
Can eeoom GEO help me improve my website content?
-
Yes.
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.
The goal is not to automatically rewrite your content.
Instead, eeoom GEO helps you understand what users may want to know and which information could be added, clarified or expanded on the page.
-
What is the difference between Analyze page and Improve page?
-
Analyze page focuses on evaluating the current state of a page.
Depending on the available audit, it can provide scores, findings, issues and recommendations related to GEO or structured data.
Improve page focuses on actionable opportunities for improving the content of that page.
It can use page context, search signals and AI-assisted analysis to identify useful questions or information that may be worth addressing.
The two workflows are independent.
You do not need to run an Analyze audit before using Improve page.
-
What are Customer Questions?
-
Customer Questions is a page-specific AI-assisted improvement analysis.
It identifies questions potential customers may ask about the topic of a specific page.
The analysis combines the existing page context with relevant search suggestions, filters unrelated signals and groups useful results into customer-oriented questions.
These questions can help editors identify information that may be useful to add, clarify or expand on the page.
-
Does eeoom GEO automatically generate or rewrite my content?
-
No.
eeoom GEO provides analysis and improvement insights.
It does not automatically replace or publish page content.
Editors remain in control of which recommendations or questions are relevant and how the page should be improved.
-
Are the content improvement ideas generated only by AI?
-
No.
Where applicable, eeoom GEO combines the existing page context with external search signals and AI-assisted filtering and structuring.
For example, Customer Questions uses page context together with relevant search suggestions to identify questions that fit the actual topic of the page.
The goal is to provide page-specific improvement insights rather than generic AI-generated topic lists.
-
What are AI Search Monitors?
-
AI Search Monitors are selected WordPress URLs that are strategically important for AI search.
Each monitor represents one public page that can be analyzed and improved through the available eeoom GEO workflows.
From a monitored page, authorized users can open the Analyze page area for GEO checks or the Improve page area for content improvement tools.
-
Are AI Search Monitor analyses automatic?
-
No.
Analyses and improvement audits are started manually by an authorized WordPress user.
If the Source of Trust API processes an audit asynchronously, eeoom GEO polls for the result of that specific AuditRun.
-
Does the plugin send my WordPress content to the checking service?
-
No.
Manual analyses send the public URL of the selected published content.
Source of Trust may retrieve the publicly accessible response of that URL in order to perform the requested analysis.
Drafts, private posts, preview URLs, WordPress post body content and personal WordPress user data are not submitted by the plugin.
-
Do I need EntityPool?
-
No.
AI Search Monitors, Analyze page, Improve page, GEO checks and local Schema & Entity functionality work without EntityPool.
EntityPool adds centrally managed entity graphs, Primary Entity mapping, Full Graph and Subgraph integration and connected entity relationships.
It also provides saved Representations that can be selected as explicitly curated Custom Graphs for individual WordPress pages.
-
What is a Primary Entity?
-
A Primary Entity is the main real-world entity associated with a WordPress page, post or public custom post type.
For example, a page may primarily represent a person, organization, location, product, service or topic.
eeoom GEO stores the EntityPool UID with the WordPress content while the entity itself remains managed in EntityPool.
-
What happens on the homepage when EntityPool is connected?
-
The homepage uses the complete connected EntityPool graph.
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.
-
What happens on a mapped page?
-
eeoom GEO retrieves the EntityPool Subgraph associated with the selected Primary Entity.
The entity and its relevant relationships are connected with the structured data of the current page.
-
What is a Custom Graph?
-
A Custom Graph is a saved EntityPool Representation selected for a specific WordPress post, page or public custom post type.
The Representation and its finished JSON-LD projection remain managed in EntityPool.
WordPress stores only its stable ID.
If the Representation is unavailable, eeoom GEO does not replace it with a broader Standard Graph.
-
Does eeoom GEO download EntityPool graph data on every request?
-
No.
Graph data is cached locally.
A graph-wide semantic revision is used to determine whether cached Full Graph and Subgraph data is still current.
If nothing has changed, existing cached representations remain valid.
If the graph changes, only the representation currently required is refreshed.
Saved Custom Graph Representations are validated independently.
A change to one saved Representation does not invalidate other Representation payloads.
-
Does EntityPool synchronization require WP-Cron?
-
No.
Graph synchronization is request-driven and does not depend on WP-Cron, system cron, background workers, external schedulers, webhooks or loopback requests.
-
Existing cached graph data is retained during temporary network and service failures.
The plugin does not remove a good cached representation simply because a remote request fails.
-
Which structured data integrations are supported?
-
The current schema graph integration supports Yoast SEO.
When active, eeoom GEO merges its entity layer directly into the existing JSON-LD graph.
AI Search Monitors, GEO analysis, page-improvement tools, EntityPool administration, entity caching and Primary Entity mapping are eeoom GEO features and are not dependent on the schema integration.
-
Does eeoom GEO create a second JSON-LD graph?
-
With the currently supported schema integration, no.
Connected EntityPool data is merged into the existing graph so entities and relationships can be represented without creating competing duplicate definitions.
-
Do I need to clear my website cache after GEO or entity changes?
-
If your website uses full-page caching, CDN caching or server-side HTML caching, previously generated pages may continue to contain an older JSON-LD representation.
Clear or purge the relevant page cache when immediate publication of schema changes is required.
ການຣີວິວ
ຜູ້ຮ່ວມພັດທະນາ ແລະ ຜູ້ພັດທະນາ
“eeoom GEO – AI Search Optimization” ແມ່ນຊອຟແວໂອເພັນຊອດ (Open Source). ບຸກຄົນຕໍ່ໄປນີ້ໄດ້ມີສ່ວນຮ່ວມໃນການພັດທະນາປລັກອິນນີ້.
ຜູ້ຮ່ວມພັດທະນາ
ແປ “eeoom GEO – AI Search Optimization” ເປັນພາສາຂອງເຈົ້າ.
ສົນໃຈຮ່ວມພັດທະນາບໍ່?
ເບິ່ງລະຫັດ, ກວດເບິ່ງ ຄັງເກັບ SVN, ຫຼື ຕິດຕາມ ບັນທຶກການພັດທະນາ ຜ່ານ RSS.
ບັນທຶກການປ່ຽນແປງ
1.9.0
- Adds Customer Questions as the first page-specific AI Suggestions experience.
- Adds consistent Analyze page and Improve page entry points across monitor cards and the WordPress dashboard.
- Reuses the existing Suite activation, Page and Monitor flow for both analysis and improvement features.
- Allows users to open page improvements without running a score audit first or automatically starting a Suggestions audit.
- Adds a clearer dashboard empty state while preserving existing score and running-audit displays.
- Removes ambiguous global timestamps and generic View details actions from overview surfaces.
1.8.0
- Adds the new AI Search Health dashboard widget for quick homepage health checks and score visibility.
- Adds a one-click first health check flow directly from the WordPress dashboard.
- Adds detailed Structured Data audit results with scores, findings, recommendations and affected entities.
- Adds support for multiple independent audits running in parallel with live status updates and automatic result refresh.
- Restores running audit states after reloads, navigation and returning to the browser tab.
- Adds a compact activation prompt for starting the first homepage health check.
- Improves score visualization with proportional, color-coded score rings.
- Improves the Check Center for independently updating audits and detailed audit results.
- Improves the AI Search Monitors overview with a visual Add Page card when additional pages can be monitored.
- Refines access control for WordPress administrators, eeoom GEO plugin admins and editors.
1.7.4
- Fixed production API endpoint configuration.
- Improved documentation of the optional EEOOM GEO Suite connection and external service communication.
- Improved WordPress coding standards compliance.
- Added the technical installation availability endpoint for future Suite connectivity checks.
- Added audit-specific server policies with a five-minute Recheck interval for Structured Data checks.
- Improved cooldown handling with clear Recheck availability and server-provided timing feedback.
- Redesigned AI Search Monitors with page cards, score and status states, clearer slot usage and an Add Page dialog.
- Restructured the Check Center with a score overview and focused audit detail sections.
- Simplified the initial AI Search Monitors connection experience and supporting privacy information.
1.7.3
- Improved WordPress compatibility and coding-standard compliance.
- Added a technical installation availability endpoint for future Suite connectivity checks.
- No changes to monitoring behavior or automatic checks.
1.7.2
- Replaced the legacy local monitor and run storage with the central Source of Trust audit service.
- Added suite-wide installation identity and centrally managed sites, pages, monitors and audit history.
- Added account-wide Free monitoring for up to five Pages, including the required homepage slot.
- Added a 30-day reserved-slot period for archived Free monitors and direct reactivation with preserved history.
- Added the generic structured-data audit flow backed by central AuditRuns.
1.7.1
- Added a global manual EntityPool data refresh in the WordPress administration.
- Added immediate revalidation of the EntityPool connection, entity list and Representation list.
- Added global refresh of the Full Graph and all indexed Subgraphs and Custom Graph Representations.
- Preserved usable stale graph and Representation payloads when remote refreshes fail temporarily.
- Fixed loading of the EntityPool graph refresh service for protected WordPress admin requests.
1.7.0
- Added Standard Graph and Custom Graph modes for posts, pages and public custom post types.
- Added selection and manual refresh of saved EntityPool Representations in the WordPress editor.
- Added persistent graph-bound caching for finished Representation JSON-LD payloads.
- Added per-Representation semantic revision and ETag validation with 304 support.
- Added independent 24-hour revalidation, request locks and retry suppression per Representation.
- Added fail-closed Custom Graph behavior without fallback to Full Graph or Subgraph.
- Added homepage validation requiring the Representation Primary Entity to match the verified graph root.
- Added WebPage mainEntity integration for Custom Graphs while preserving Standard Graph semantics.
- Improved the shared EntityPool and Yoast merge with local document-context normalization.
- Added recursive JSON-LD ID reference rewriting and deterministic WebPage, WebSite and BreadcrumbList deduplication.
- Preserved EntityPool resolver IDs as deduplicated sameAs links when real-world entities merge with local IDs.
1.6.0
- Redesigned the eeoom GEO administration.
- Introduced AI Search Monitors for strategically important URLs.
- Improved GEO check workflows and stored result handling.
- Expanded Schema & Entity tools for entity-focused GEO optimization.
- Added EntityPool graph integration.
- Added graph-specific EntityPool connection support.
- Added EntityPool graph metadata and connection validation.
- Added Primary Entity mapping for posts, pages and public custom post types.
- Added manual EntityPool entity refresh in the WordPress editor.
- Added persistent EntityPool Full Graph and Subgraph caching.
- Added revision- and ETag-based graph validation.
- Added request-driven graph revalidation without cron or background workers.
- Added stale-cache fallback for temporary EntityPool failures.
- Added direct EntityPool integration into supported JSON-LD output.
- Added Root Entity integration with the existing website organization.
- Added Primary Entity references for mapped content.
- Improved capability-based access control and integration security.
1.5.0
- New layout.
1.2.0
- Improved URL Checks with a cleaner REST API based workflow and server-to-server Source of Trust API communication.
- Improved persistent check status handling and stored check results per URL/page.
- Improved the Structured Data Check report and URL Checks overview UI.
- Added Plugin Admins with direct eeoom GEO capability assignment for selected users.
- Prevented plugin administrators from accidentally removing their own access.
- Improved the Settings page structure and responsive layout.
1.1.0
- Redesigned the Schema Enhancements settings page for a clearer GEO workflow.
- Improved the admin interface for managing Organization schema and entity signals.
- Updated the plugin display name to eeoom GEO.
- Improved plugin description and readme wording for AI search visibility.
1.0.0
- Initial public release.
- Added Organization schema enhancements for supported schema output.
- Added sameAs, hasMap, PostalAddress, areaServed and knowsAbout fields.
- Added parentOrganization and subOrganization fields.
- Added manual Source of Trust page checks.
- Added asynchronous Source of Trust API checks with job ID polling.