Quick summary
A WordPress implementation note about preparing draft location-page imports, metadata, schema, map embeds, and Elementor template JSON for review.
The problem
A multi-location page set needed safer import tooling that could create draft pages, preserve metadata, avoid overwriting live slugs, and prepare builder-ready content.
What I checked
- WordPress export files
- Local service and location HTML folders
- Available PHP and Node.js import options
- Existing live slugs and parent path mappings
- Elementor template structure
What I changed
- Shifted import tooling to Node.js after PHP access was ruled out
- Built draft-only import workflows to avoid overwriting live pages
- Generated metadata-only draft imports with schema, map embeds, SEO fields, image IDs, source tracking, and parent IDs
- Converted service HTML content into Elementor-compatible JSON outputs
- Uploaded generated drafts and reviewed pages individually in the builder
Result
The location page import became safer and more reviewable, with generated drafts and builder templates prepared before final internal linking and image updates.
What I'd watch next
- Whether generated pages receive final internal links
- Whether images are replaced before launch
- Whether future imports keep draft-only safeguards