HREFLANG CUSTOMIZER
Hreflang Customizer compatibility with REEID Translate
Hreflang Customizer compatibility with REEID Translate is being evaluated from available plugin evidence. Standalone hreflang generation: outputs one “ element per selected language code in the “ of every page, pointing to the canonical URL of that page. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Hreflang Customizer.
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
Hreflang Customizer is documented in the SEO category with 6 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 Hreflang Customizer 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
- Standalone hreflang generation: outputs one “ element per selected language code in the “ of every page, pointing to the canonical URL of that page.
- Per-page hreflang control via editor meta box: allows disabling hreflang tags on a specific page/post, limiting output to a subset of global languages, mapping each language to a custom URL, and setting a custom `x-default` URL for that page.
- Optional Weglot integration for URL mapping: when Weglot is installed and active, the plugin maps Weglot translated URLs to the selected hreflang codes automatically.
- Hreflang audit tool: provides an admin audit that checks public URLs for issues including invalid locale code format, missing self-referencing tags, missing `x-default`, duplicate locale declarations, relative (non-absolute) URLs, and mixed http/https protocols; results can be exported to CSV.
- Dedicated hreflang sitemap output: provides a dedicated `/hreflang-sitemap.xml` that lists URLs with `xhtml:link` hreflang annotations, and can append hreflang alternates to Yoast SEO sitemap entries.
- Optional external language-list fetch with caching: can fetch an extended language list from `https://app.seo-hreflang.com/api/languages` at most once every 12 hours, cache the result using WordPress Transients, and fall back to a built-in 180+ language list if the service is unavailable.
CONTENT BOUNDARY
Hreflang Customizer 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
Hreflang Customizer and REEID Translate FAQ.
What does Hreflang Customizer do according to the available plugin evidence?
Hreflang Customizer has 6 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 Hreflang Customizer?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Hreflang Customizer?
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 Hreflang Customizer in a multilingual WordPress workflow.
REEID documents Hreflang Customizer 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.