FOUNDASH AI ACCESS CHECK
Foundash AI Access Check compatibility with REEID Translate
Foundash AI Access Check compatibility with REEID Translate is being evaluated from available plugin evidence. Distinguishes between search-time AI agents (OAI-SearchBot, ChatGPT-User, Perplexity-User, Claude-SearchBot) and training crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) to assess recommendation eligibility No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Foundash AI Access Check.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Foundash AI Access Check is documented in the SEO category with 8 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How Foundash AI Access Check compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Distinguishes between search-time AI agents (OAI-SearchBot, ChatGPT-User, Perplexity-User, Claude-SearchBot) and training crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) to assess recommendation eligibility
- Validates robots.txt directives by parsing real rules, including handling of commented lines, site-wide vs.
- specific user-agent rules, and Allow overrides for Disallow
- Detects WordPress 'Discourage search engines' setting impact by checking for noindex tags on the front page rather than relying solely on robots.txt content
- Verifies presence of structured data on the front page to ensure assistants can extract factual information from the site
- Checks for the existence of an llms.txt file as part of AI visibility diagnostics
- Uses Googlebot requests as a control mechanism to differentiate between general bot blocking issues and specific AI crawler restrictions
- Reports raw HTTP status codes (401, 403, 429) and exact robots.txt lines to provide verifiable evidence for access refusals
Distinctive features
Distinguishes between search-time AI agents (OAI-SearchBot, ChatGPT-User, Perplexity-User, Claude-SearchBot) and training crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) to assess recommendation eligibility Validates robots.txt directives by parsing real rules, including handling of commented lines, site-wide vs. specific user-agent rules, and Allow overrides for Disallow Detects WordPress 'Discourage search engines' setting impact by checking for noindex tags on the front page rather than relying solely on robots.txt content Verifies presence of structured data on the front page to ensure assistants can extract factual information from the site Checks for the existence of an llms.txt file as part of AI visibility diagnostics Uses Googlebot requests as a control mechanism to differentiate between general bot blocking issues and specific AI crawler restrictions Reports raw HTTP status codes (401, 403, 429) and exact robots.txt lines to provide verifiable evidence for access refusals Operates entirely locally without sending data to third parties, requiring no API keys or external accounts
CONTENT BOUNDARY
Foundash AI Access Check capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Foundash AI Access Check and REEID Translate FAQ.
What does Foundash AI Access Check do according to the available plugin evidence?
Foundash AI Access Check has 8 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for Foundash AI Access Check?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Foundash AI Access Check?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate Foundash AI Access Check in a multilingual WordPress workflow.
REEID documents Foundash AI Access Check functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.