LOCAL GOOGLE FONTS
Local Google Fonts compatibility with REEID Translate
Local Google Fonts compatibility with REEID Translate is being evaluated from available plugin evidence. Hosts used Google Fonts locally on the site’s server instead of loading them from Google’s servers. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Local Google Fonts.
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
Local Google Fonts is documented in the Performance 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 Local Google Fonts 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
- Hosts used Google Fonts locally on the site’s server instead of loading them from Google’s servers.
- Provides an option to automatically load detected fonts locally, with manual triggering otherwise.
- Stores downloaded font files under wp-content/uploads.
- Includes cleanup behavior on plugin deactivation and on plugin switch.
- Supports choosing which fonts should be loaded locally from the WordPress settings page.
- Can load only the woff2 font format, and the FAQ says this is the format it loads.
- Notes that it only checks fonts embedded via wp_enqueue_style, not Google Fonts loaded via @import.
CONTENT BOUNDARY
Local Google Fonts 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
Local Google Fonts and REEID Translate FAQ.
What does Local Google Fonts do according to the available plugin evidence?
Local Google Fonts 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 Local Google Fonts?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Local Google Fonts?
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 Local Google Fonts in a multilingual WordPress workflow.
REEID documents Local Google Fonts 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.