FOUNDBYAI
FoundByAI — AI SEO, GEO & llms.txt for ChatGPT & AI Search compatibility with REEID Translate
FoundByAI — AI SEO, GEO & llms.txt for ChatGPT & AI Search compatibility with REEID Translate is being evaluated from available plugin evidence. HTTP Content Negotiation for Markdown: Automatically serves Markdown when crawlers request `Accept: text/markdown`. No specific visitor-facing translation surface is currently confirmed.
Visit FoundByAI — AI SEO, GEO & llms.txt for ChatGPT & AI Search ↗
AWAITING VERIFICATION
What the available evidence establishes for FoundByAI — AI SEO, GEO & llms.txt for ChatGPT & AI Search.
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
FoundByAI — AI SEO, GEO & llms.txt for ChatGPT & AI Search is documented in the SEO category with 7 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 FoundByAI — AI SEO, GEO & llms.txt for ChatGPT & AI Search 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
- HTTP Content Negotiation for Markdown: Automatically serves Markdown when crawlers request `Accept: text/markdown`.
- `.md` URL endpoints for posts/pages: Provides Markdown downloads via `/post-slug.md` and supports serving Markdown for Posts, Pages, or custom post types.
- YAML frontmatter in Markdown outputs: Each generated Markdown file includes metadata in YAML format.
- llms.txt generation with dual endpoints: Generates `llms.txt` at both `/.well-known/llms.txt` and `/llms.txt`, and includes one-line link descriptions sourced from SEO meta description, excerpt, or content.
- Clean Markdown targets inside llms.txt: llms.txt entries link to the clean `.md` versions of pages rather than the HTML pages.
- Full-content discovery file: Provides `/llms-full.txt` that embeds the complete Markdown of every listed page, per the llmstxt.org spec.
- Bot tracking and local logging: Tracks AI bot visits (with enable/disable controls) and stores bot visit data locally in the WordPress database with retention described as last 500 visits and auto-removal after 14 days.
Distinctive features
HTTP Content Negotiation for Markdown: Automatically serves Markdown when crawlers request `Accept: text/markdown`. `.md` URL endpoints for posts/pages: Provides Markdown downloads via `/post-slug.md` and supports serving Markdown for Posts, Pages, or custom post types. YAML frontmatter in Markdown outputs: Each generated Markdown file includes metadata in YAML format. llms.txt generation with dual endpoints: Generates `llms.txt` at both `/.well-known/llms.txt` and `/llms.txt`, and includes one-line link descriptions sourced from SEO meta description, excerpt, or content. Clean Markdown targets inside llms.txt: llms.txt entries link to the clean `.md` versions of pages rather than the HTML pages. Full-content discovery file: Provides `/llms-full.txt` that embeds the complete Markdown of every listed page, per the llmstxt.org spec. Caching and rebuild behavior for discovery: Rebuilds llms.txt when you publish or edit (not on a fixed schedule) and uses a 1-hour cache with smart invalidation. Bot tracking and local logging: Tracks AI bot visits (with enable/disable controls) and stores bot visit data locally in the WordPress database with retention described as last 500 visits and auto-removal after 14 days.
CONTENT BOUNDARY
FoundByAI — AI SEO, GEO & llms.txt for ChatGPT & AI Search 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
FoundByAI — AI SEO, GEO & llms.txt for ChatGPT & AI Search and REEID Translate FAQ.
What does FoundByAI — AI SEO, GEO & llms.txt for ChatGPT & AI Search do according to the available plugin evidence?
FoundByAI — AI SEO, GEO & llms.txt for ChatGPT & AI Search has 7 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 FoundByAI — AI SEO, GEO & llms.txt for ChatGPT & AI Search?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for FoundByAI — AI SEO, GEO & llms.txt for ChatGPT & AI Search?
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 FoundByAI — AI SEO, GEO & llms.txt for ChatGPT & AI Search in a multilingual WordPress workflow.
REEID documents FoundByAI — AI SEO, GEO & llms.txt for ChatGPT & AI Search 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.