BLAZE AI DISCOVERY FOR WOOCOMMERCE
Blaze AI Discovery for WooCommerce translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what Blaze AI Discovery for WooCommerce does, but does not yet establish specific visitor-facing content values that REEID should translate.
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- AI visibility reporting: generates a monthly report over a trailing 30-day window describing how often ChatGPT and Google AI answers mentioned the store, which pages were cited, and which other domains were named instead.
- ChatGPT Shopping feed generation: generates a product feed in OpenAI’s current CSV specification, validates products against required fields, and provides guidance for submission steps outside the plugin.
- AI traffic attribution and order tagging: detects AI-referred visits using referrer headers, UTM parameters, and URL text fragments (and sets a first-party cookie), then tags resulting WooCommerce orders with the AI source for dashboard attribution.
- Schema augmentation for Product structured data: augments existing Schema.org/JSON-LD Product markup by adding properties such as brand, multiple images, GTIN, dimensions, color, material, and itemCondition, and is designed to work alongside WooCommerce/Yoast SEO/Rank Math without duplicating schema blocks.
- llms.txt generation at site root: serves an llms.txt file at the site root listing store, categories, and key pages, with the plugin treating it as lower priority than crawler access and structured data.
- Client-side tracking designed to work with full-page caching: uses a lightweight inline script that delay-loads via requestIdleCallback and sends data to a local REST endpoint; tracking signatures expire after two full days on cached HTML, with an adjustable filter for the signature window.
Distinctive features
Per-crawler AI crawler access checks: determines whether multiple named AI crawler user agents can reach the store based on robots.txt verdicts, server bot logs, and (optionally) outside-network fetches; reports per-crawler results and links to the blocking layer fix. AI visibility reporting: generates a monthly report over a trailing 30-day window describing how often ChatGPT and Google AI answers mentioned the store, which pages were cited, and which other domains were named instead. ChatGPT Shopping feed generation: generates a product feed in OpenAI’s current CSV specification, validates products against required fields, and provides guidance for submission steps outside the plugin. Per-product AI readiness scoring: assigns each product a 0–100 score across 10 criteria (e.g., title quality, description depth, images, brand, category, attributes, price, identifiers like SKU/GTIN, reviews, and shipping/returns policies) and provides recommendations for what to fix. AI traffic attribution and order tagging: detects AI-referred visits using referrer headers, UTM parameters, and URL text fragments (and sets a first-party cookie), then tags resulting WooCommerce orders with the AI source for dashboard attribution. Schema augmentation for Product structured data: augments existing Schema.org/JSON-LD Product markup by adding properties such as brand, multiple images, GTIN, dimensions, color, material, and itemCondition, and is designed to work alongside WooCommerce/Yoast SEO/Rank Math without duplicating schema blocks. llms.txt generation at site root: serves an llms.txt file at the site root listing store, categories, and key pages, with the plugin treating it as lower priority than crawler access and structured data. Client-side tracking designed to work with full-page caching: uses a lightweight inline script that delay-loads via requestIdleCallback and sends data to a local REST endpoint; tracking signatures expire after two full days on cached HTML, with an adjustable filter for the signature window.
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what Blaze AI Discovery for WooCommerce does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Blaze AI Discovery for WooCommerce and REEID Translate FAQ.
Does the current evidence establish translation scope for Blaze AI Discovery for WooCommerce?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.