Armandi Content Sync
Import published posts from another WordPress site using the REST API or a standard WordPress export XML file.
Use with caution
Armandi Content Sync works, but test it on a staging site before relying on it in 2026. Was last updated 3 months ago, and scores 49/100 on our health check.
- Small user base (<10 active installs)
- Very few reviews so far
How does it stack up?
Side-by-side on installs, updates, ratings & support
Daily downloads
Download spikes usually follow a new release β each site that auto-updates counts as a download.
Rankings
Where Armandi Content Sync stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| content sync | >100 |
| migration | >100 |
| rest-api | >100 |
| wordpress export | >100 |
| XML Import | >100 |
About Armandi Content Sync
From the official readme Β· v0.1.3Description
Armandi Content Sync helps administrators import content from another WordPress installation in a controlled and secure way.
You can work with two import methods:
- REST API import, started manually or scheduled with WP-Cron.
- Classic XML import using a standard WordPress WXR export file.
The plugin is designed for content migrations, editorial consolidation, syndication between WordPress sites, and recovery workflows when the source site exposes only part of its content through the REST API.
Main features:
- Manual REST API import.
- Classic XML WXR import.
- Classic XML import from a local server path for large files that cannot be uploaded through the browser.
- Dry run mode for REST API and XML imports.
- Pause, resume, and cancel controls for active imports.
- Scheduled REST API imports with a fixed execution time and a repeat frequency of daily, every 7 days, every 15 days, or monthly.
- Import of categories, tags, featured images, inline images, authors, and SEO metadata.
- Fallback local author assignment when the source site does not expose author details.
- Per-run logs with CSV export.
- Blocked media host reporting for failed image imports.
- Optional allowlist for trusted external media hosts such as source CDNs.
- Optional Visual Composer/WPBakery content normalization for cleaner imported HTML.
- Optional authentication with WordPress Application Passwords when anonymous REST access is restricted.
- REST API overview in the manual import screen showing the active authentication mode and primary endpoint.
External services
This plugin does not send data to the plugin author or to any third-party SaaS service.
When you use REST API import, the plugin connects only to the source WordPress site that you configure in the plugin settings. If you enable Application Password authentication, those credentials are used only for requests to that configured source site.
Security notes
To reduce risk during media imports:
- By default, remote images are downloaded only from the configured source host or its subdomains.
- If the source site uses a CDN or a separate image host, an administrator can explicitly allow those hosts.
- Blocked media hosts are listed in the import logs so administrators can review them before allowing any additional hosts.
Installation
- Upload the
armandi-content-syncfolder to the/wp-content/plugins/directory, or install the plugin through the WordPress admin. - Activate the plugin through the
Pluginsscreen in WordPress. - Open the plugin settings page from the WordPress admin menu.
- Enter the base URL of the source WordPress site.
- If the source REST API is restricted, configure an Application Password with a valid user account from the source site.
- Adjust the import options to match your workflow.
- Open the manual import page and run a dry run or a full import.
- For very large XML files, copy the WXR file to the recommended uploads subdirectory and use the local server path import option instead of a browser upload.
Frequently asked questions
What is the difference between REST API import and XML import?
REST API import fetches content directly from the configured source WordPress site. XML import works from a previously exported WordPress WXR file. Large XML files can also be imported from a local server path when the hosting environment rejects browser uploads with errors such as 413 Request Entity Too Large.
Why are authors not always imported?
Some source sites block endpoints such as users through security plugins or custom rules. In those cases, the plugin may not have enough data to resolve the original author and will assign the post to the configured fallback local user.
When should I use an Application Password?
Use it when the source WordPress site restricts anonymous REST API access or blocks some of the endpoints required for a complete import.
How do scheduled imports work?
Scheduled imports run through WP-Cron. You can choose the execution time and the repeat frequency. Available frequencies are: Daily Every 7 days Every 15 days Monthly WP-Cron is traffic-based, so the task will usually run around the configured time rather than at the exact second.
Why are some images shown as blocked in the logs?
The plugin limits remote media downloads to the source host and to any extra hosts that you explicitly allow. If the source site uses a CDN or a separate media domain, review the blocked hosts in the run detail view and allow only the trusted ones.
Does the plugin depend on external services?
No. The plugin only needs: a source WordPress site that can be reached through the REST API, or a WordPress WXR export file. It does not depend on the plugin authorβs servers or on a third-party SaaS platform.
Changelog
Fixes inline image imports so resized source images and srcset entries are rewritten to valid local media URLs.
0.1.3
- Fixed inline image imports to prefer the original source image from srcset when available.
- Rebuild local src and srcset attributes after importing inline media.
- Avoid reusing previously imported media when the local attachment file is missing.
- Repair imported post media on subsequent runs even when the source post content has not changed.
0.1.2
- Added optional Visual Composer/WPBakery content normalization for imported content.
- Improved cleanup of builder shortcodes, classes and attributes while preserving HTML, inline styles and images.
- Tested with WordPress 7.0 and PHP 8.3.27.
0.1.1
- Added WordPress.org plugin listing assets.
- Added Spanish translation support if translation files already exist.
- Improved release metadata.
0.1.0
- Initial public release.
- REST API post import.
- Classic XML WXR import.
- Local server path import option for large XML files.
- Author, taxonomy, image, and SEO metadata import support.
- Dry run support for REST API and XML imports.
- Per-run logging and CSV export.
- Pause, resume, and cancel controls.
- Scheduled imports with fixed execution time and repeat frequency.
- REST API details panel showing authentication mode and primary endpoint.
- Security hardening for remote media and authenticated requests.
Screenshots
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own β no account needed.
Best Armandi Content Sync alternatives
All content sync plugins β
FAQ
Armandi Content Sync: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org Β· checked Oct 4, 2026
Is Armandi Content Sync free?
Yes. Armandi Content Sync is free to download and use from the official WordPress.org plugin directory.
Is Armandi Content Sync safe to use in 2026?
Armandi Content Sync works, but test it on a staging site before relying on it in 2026. Was last updated 3 months ago, and scores 49/100 on our health check.
How many websites use Armandi Content Sync?
Armandi Content Sync is active on <10 WordPress websites and has been downloaded 334 times since it launched in May 2026. It was downloaded 66 times in the last 30 days.
Does Armandi Content Sync work with WordPress 7.1?
Armandi Content Sync is officially tested up to WordPress 7.0.6, while the latest release is 7.1.2. It may still work, but try it on a staging site first.
What PHP version does Armandi Content Sync need?
Armandi Content Sync requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Armandi Content Sync last updated?
The latest version, 0.1.3, was released on June 23, 2026 (3 months ago).
Who makes Armandi Content Sync?
Armandi Content Sync is developed and maintained by acaballerop.
What are the best alternatives to Armandi Content Sync?
The most popular alternatives to Armandi Content Sync are Arkwell SEO Connector (20+ installs), WPSiteSync for HTTP Authent⦠(10+ installs) and Redaquest Connector (<10 installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages β with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org β no credit card
