ACF: BETTER SEARCH
ACF: Better Search translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what ACF: Better Search 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
- Extends the default WordPress search query to search content from selected Advanced Custom Fields fields.
- Supports searching whole phrases instead of splitting the query into individual words.
- Works automatically without requiring additional code.
- Works with WP_Query and custom WP_Query loops, including get_posts() when a search parameter is added.
- Supports Text, Text Area, Number, Email, Url, File, Wysiwyg Editor, Select, Checkbox, and Radio Button fields.
- Can search fields inside Repeater or Flexible Content fields.
- Includes an Incorrect Mode that ignores _postmeta record order when database data is arranged incorrectly.
- Includes a Lite mode that searches phrases across all ACF fields without checking field types.
Distinctive features
ACF-focused search enhancement with phrase searching, support for several common ACF field types, and search coverage for fields inside Repeater or Flexible Content structures. The evidence also highlights automatic operation without extra code and a Lite mode for phrase searching across ACF fields.
Dynamic content
The evidence shows search can include selected ACF field content and can work with WP_Query, custom WP_Query loops, and get_posts() when a search parameter is added. Runtime behavior for other dynamic content sources is not established.
SEO and metadata
The plugin is presented as an SEO integration, but the supplied evidence does not establish specific SEO metadata handling, indexing controls, or metadata generation behavior.
URLs and navigation
The evidence includes support for Url fields as searchable ACF field types. It does not establish URL rewriting, navigation controls, or broader link-handling behavior.
Forms and commerce
The supplied evidence does not establish forms or commerce behavior.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what ACF: Better Search 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
- Search behavior is limited to the selected Advanced Custom Fields fields described in the plugin evidence. The available evidence does not establish support for other content types, translation handling, or any admin-only, exclusive, or complete coverage claims. Phrase searching and field-type handling are described only for the field types listed in the evidence.
COMMON QUESTIONS
ACF: Better Search and REEID Translate FAQ.
Does the current evidence establish translation scope for ACF: Better Search?
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.