Documentation

Requirements

• WordPress 6.0 or newer
• WooCommerce 7.0 or newer
• PHP 8.1 or newer
• Pretty permalinks enabled for feed, sitemap, llms.txt, and AI Catalog endpoints

Install Emargy GEO

1. Download the latest emargy-geo.zip from your Emargy account.
2. In WordPress, open Plugins → Add New Plugin → Upload Plugin.
3. Select the ZIP, choose Install Now, then activate the plugin.
4. Open Emargy GEO → Getting Started.

Activate your license

1. Open Emargy GEO → License.
2. Paste the key from your purchase email or account dashboard.
3. Select Activate License.

An active license provides product updates, support, and licensed admin tools. Public schema, feeds, llms.txt, AI Catalog, and sitemap output remains available if a license later expires, so configured discovery output is not abruptly removed.

Recommended first run

1. Open Emargy GEO → Compatibility and confirm the detected SEO mode.
2. Open Merchant Readiness and run a full audit.
3. Return to the Dashboard to review products ready, products needing fixes, and top issue counts.
4. Correct missing images, brand, GTIN/MPN, descriptions, categories, shipping, and policy signals.
5. Open Merchant Feed, run feed validation, and generate the static files.
6. Open AI Catalog and review the llms.txt and catalog previews.

What “ready” means

A ready product has passed the plugin’s configured Merchant and discovery checks. Readiness improves data quality; it does not guarantee approval, ranking, rich results, inclusion in an AI answer, or Merchant Center performance.

Choose who owns overlapping SEO output

Open Emargy GEO → Compatibility to see the active mode and every affected output.

• Standalone — Emargy GEO can provide essential titles, descriptions, robots rules, canonicals, social tags, generic schema, and sitemaps.
• Compatibility — when Yoast SEO, Rank Math, AIOSEO, or SEOPress is detected, overlapping generic output is deferred.
• Manual — choose individual ownership overrides when an advanced setup needs them.

Commerce features remain available

Product schema, Merchant Feed, Merchant Readiness, feed validation, Product Visibility, AI Catalog, llms.txt, and ecommerce tracking remain part of Emargy GEO’s commerce layer in Compatibility Mode.

After changing modes, clear page and CDN caches and validate a representative product page for duplicate metadata or structured data.

What the audit checks

The audit evaluates published products and sellable variations for price, availability, image dimensions, brand, SKU, GTIN or MPN, description length, product category, shipping configuration, return policy, and Google Product Category mapping.

Full and delta audits

• Full audit rebuilds stored results for the entire catalog.
• Delta audit focuses on products changed since the previous audit, reducing work on large stores.
• Clear cache removes stored audit results when you need a clean run.

Using the results

Start with error-level issues that can prevent complete feed items, then fix warnings that weaken identification and product quality. Open affected products individually or use the Bulk Fix tools for suitable catalog-wide changes.

Available formats

Emargy GEO publishes Google Merchant-compatible XML and TSV feeds. Copy the URL shown under Emargy GEO → Merchant Feed into the scheduled-fetch configuration in Google Merchant Center.

Validate before syncing

Feed Validation checks sellable items and variations for common quality problems such as missing identifiers, missing brands, invalid images, absent Google categories, and noindex conflicts.

Background generation

Static feed files are generated in batches under the WordPress uploads directory. Product changes schedule a debounced rebuild. The Merchant Feed screen shows generation state, processed items, last completion time, file sizes, validation totals, and manual controls.

If token protection is enabled, use the protected URL displayed by the plugin and treat the token as a credential.

WooCommerce Product schema

Emargy GEO can publish Product and Breadcrumb JSON-LD using WooCommerce data including offers, availability, variations, brand, SKU, GTIN, MPN, ratings, shipping, and return-policy information when available.

Standalone SEO output

Standalone Mode can also provide Organization, WebSite, and Article schema plus essential metadata. Compatibility Mode defers generic overlapping output while keeping the commerce layer active.

Sitemaps

The plugin provides focused product, product-image, category, Merchant discovery, and AI discovery sitemap coverage. Products marked noindex by supported SEO plugins are excluded where appropriate.

Use Google’s Rich Results Test and inspect the rendered source of representative products after configuration changes.

AI-readable discovery files

Open Emargy GEO → AI Catalog to preview the store’s /llms.txt and /ai-catalog endpoints.

• llms.txt presents a readable store profile, policies, categories, and structured product details.
• AI Catalog exposes structured product data, identifiers, offers, variations, ratings, language, and catalog context.

Content rules

Unpublished and noindex products are excluded. Output is scoped by active language for supported multilingual stores, and bidirectional control characters are cleaned to protect Arabic and Hebrew content integrity.

Optional AI suggestions

OpenAI or Anthropic can be configured for assisted summaries and catalog improvements. API credentials are encrypted at rest. Review generated content before publishing it.

Visibility while editing a product

The GEO Visibility panel in the WooCommerce product editor summarizes Merchant readiness, AI visibility, schema status, identifiers, feed inclusion, indexing, and a search snippet preview.

GEO / AI product data

The product data panel includes an AI summary, Google Product Category override, and custom feed labels. Use overrides only when the global category mapping is not specific enough.

Bulk Fix and Category Suggestions

Bulk Fix supports preview-and-confirm workflows for selected catalog changes. Category Suggestions can propose Google taxonomy mappings, optionally with an AI provider. Always inspect the preview before confirming a bulk operation.

Ecommerce tracking

Configure a GA4 Measurement ID or Google Tag Manager container under Emargy GEO → Settings. Emargy GEO can publish WooCommerce ecommerce dataLayer events for product views, cart actions, checkout, and purchases.

Consent Mode v2

Consent defaults and updates can be configured for stores that use Google Consent Mode. Tracking remains disabled when the master tracking switch is off.

Tracking Debug

Use Emargy GEO → Tracking Debug to verify configuration and inspect expected event behavior. Also confirm events in GTM Preview and GA4 DebugView before relying on production reports.

WPML and Polylang

Emargy GEO detects WPML and Polylang, resolves the current language and translated product URLs, and scopes cached Merchant Feed, AI Catalog, llms.txt, and sitemap output by language.

Arabic and RTL safety

Schema, feed, and AI text passes through cleanup that preserves readable Unicode while removing hidden bidirectional control characters that can corrupt machine-readable output.

Verification checklist

• Open each language-specific feed and AI endpoint.
• Confirm translated names, descriptions, currency, and permalinks.
• Validate Arabic product schema independently.
• Clear caches after changing language URL rules.

Static output instead of expensive requests

Feed and AI Catalog files are written under wp-content/uploads/emargy-geo/ in configurable batches. Action Scheduler is used when available, with WP-Cron as a fallback.

Stored audit results

Readiness results are stored in a dedicated database table so dashboards and delta audits do not have to rescan a large catalog on every page load.

Operational guidance

• Use a real server cron for reliable WordPress scheduled events.
• Keep the uploads directory writable.
• Watch the generation status and last error fields after major imports.
• Run a full audit after bulk migrations; use delta audits for daily changes.
• For catalogs above 2,000 products, the first feed request waits for background generation instead of building the entire feed inside a web request.

License activation fails

• Confirm the key belongs to Emargy GEO and has an available site activation.
• Confirm outbound HTTPS requests to https://emargy.com are allowed.
• Deactivate the old domain before moving a limited-site license.

Duplicate schema or metadata

Open Compatibility, confirm the detected SEO plugin, clear every page/CDN cache, then inspect rendered source again. Avoid enabling the same output in two plugins.

Feed remains pending

Confirm WP-Cron or Action Scheduler is running and the uploads directory is writable. Open Merchant Feed for the last error, then use the manual regenerate control.

Products are missing from output

Check publication status, catalog visibility, noindex settings, price, and variation status. Supported SEO-plugin noindex rules intentionally remove products from discovery output.

Getting support

Contact [email protected] with the plugin version, WordPress/WooCommerce/PHP versions, affected URL, relevant status screen, and sanitized logs. Never send API keys or feed tokens.