WP SITEMAP PAGE
WP Sitemap Page translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what WP Sitemap Page 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
- Adds a sitemap to a page via the shortcode [wp_sitemap_page].
- Generates a single-page list of site pages and posts for human navigation.
- Can include pages, posts, categories, custom post types, and taxonomies.
- Supports filtering to one content type with the shortcode attribute only.
- Can exclude selected pages or custom post types.
- Displays posts and categories hierarchically.
- Can be customized through the admin panel and CSS classes.
Distinctive features
Shortcode-based sitemap page output, hierarchical display for posts and categories, and exclusion controls for selected pages or custom post types are the main differentiators shown in the evidence.
Dynamic content
The evidence shows the sitemap content is generated for a page and can include pages, posts, categories, custom post types, and taxonomies. It also supports filtering to one content type through a shortcode attribute. Other runtime content behavior is not established.
SEO and metadata
No SEO metadata behavior is established in the supplied evidence. The plugin is described as a sitemap page for human navigation rather than a metadata tool.
URLs and navigation
The plugin creates a sitemap page that helps users navigate site content. The evidence does not establish URL rewriting, redirects, or other navigation behavior beyond the sitemap page listing.
Forms and commerce
No forms or commerce behavior is established in the supplied evidence.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what WP Sitemap Page 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
- This plugin is used to add a sitemap page for human navigation. The available evidence shows it can list pages, posts, categories, custom post types, and taxonomies, but it does not establish support for every site structure or content setup. Filtering to a single content type is available through the shortcode attribute only, and selected pages or custom post types can be excluded. The evidence does not establish broader behavior beyond the sitemap page output described here.
COMMON QUESTIONS
WP Sitemap Page and REEID Translate FAQ.
Does the current evidence establish translation scope for WP Sitemap Page?
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.