=== Kotia Content Integration === Contributors: Serg25001 Tags: rest api, content import, seo, post import, media upload Requires at least: 5.8 Tested up to: 6.9 Requires PHP: 7.4 Stable tag: 2.4.1 License: GPLv2 or later License URI: https://www.gnu.org/licenses/gpl-2.0.html Secure REST API content importer for WordPress. == Description == Kotia Content Integration provides a secure REST API for content import: ✔ Create posts via REST ✔ Upload media ✔ Create categories and tags ✔ Set featured images ✔ SEO fields support ✔ Yoast SEO compatibility (if installed) ✔ Status endpoint for connection checks ✔ Token-based authentication If Yoast SEO is not installed, SEO fields are stored as custom fields and rendered in page head. == REST API Endpoints == POST: - /wp-json/kotia-content-integration/v1/post - /wp-json/kotia-content-integration/v1/media - /wp-json/kotia-content-integration/v1/category - /wp-json/kotia-content-integration/v1/tag - /wp-json/kotia-content-integration/v1/set-thumbnail GET: - /wp-json/kotia-content-integration/v1/status Authentication: Authorization: Bearer TOKEN == SEO Fields == Supported fields in post creation: { "meta_title": "SEO Title", "meta_description": "SEO Description", "focus_keyword": "Keyword" } If Yoast SEO is installed, fields are automatically mapped to Yoast meta. If not installed: - fields are stored as custom meta - fields are available in admin - fields are rendered in == Installation == 1. Upload plugin folder to /wp-content/plugins/ 2. Activate plugin 3. Generate API token in settings 4. Use REST API to import content == Changelog == = 2.4.1 = * Fixed tag assignment bug causing numeric tag names when importing posts = 2.4.0 = * Added SEO support * Added status endpoint * Improved REST API security * Yoast SEO compatibility * Custom fields fallback = 2.3.0 = * Initial REST API support * Media upload * Post import == Frequently Asked Questions == = How to get API token? = Go to Settings → Kotia Content Integration and generate new token. = Does it work without Yoast SEO? = Yes. SEO fields are stored as custom fields and rendered in page head. = How to check connection? = Use GET /status endpoint. == License == GPLv2 or later