LS – AI Editorial Engine
| 开发者 |
lakestylez
freemius |
|---|---|
| 更新时间 | 2026年6月21日 23:42 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Generate full blog post drafts from a prompt or topic
- Enhance and polish existing content (grammar, flow, structure)
- Generate SEO meta title, meta description and a focus keyword
- Choose between OpenAI (ChatGPT) and Google Gemini models
- Control output language, formal/informal address and anglicism level
- Define a brand persona and global context for consistent results
- Works in the Block Editor (sidebar) and the Classic Editor (metabox)
- Inline optimization of selected text (rephrase, clarify, SEO, tone, and more)
- Auto-Blogger: scheduled automatic post creation via WP-Cron
- Strategic topic pool generator
- AI-based category assignment
- Style learning from a writing sample, preferred key terms and minimum length
- Default writing styles
- Affiliate Link Assistant: store your own affiliate links once and let the AI weave fitting ones into the content (inline keyword links and/or a recommendation block). Links use rel="sponsored nofollow noopener", a server-side maximum-links limit is enforced, and only the exact URLs from your settings are used.
- Optional AI featured-image generation (works together with the separate, free "LS – AI Image Generator" plugin; if it is not installed, the option is simply skipped)
安装:
- Upload the
ls-ai-editorial-enginefolder to the/wp-content/plugins/directory, or install the plugin through the WordPress "Plugins" screen. - Activate the plugin through the "Plugins" screen in WordPress.
- Go to "Editorial Engine" → "Settings" and enter your OpenAI and/or Google Gemini API key.
- Choose your default model, language and persona.
- Open a post in the Block Editor or Classic Editor and use the LS – AI Editorial Engine panel to generate or enhance content.
常见问题:
Do I need an API key?
Yes. You need your own OpenAI and/or Google Gemini API key. The plugin sends requests using your key, and any usage is billed by the provider to your account.
Does the plugin store my API keys securely?
Your keys are stored in the WordPress options table on your own server, like other plugin settings. They are never displayed in the front end and are only sent to the respective provider to authenticate your requests.
Which editors are supported?
Both the Block Editor (Gutenberg) via a sidebar panel and the Classic Editor via a metabox.
Is any content sent anywhere without my action?
No. Content is only sent to OpenAI or Google Gemini when you actively trigger a generation, enhancement, inline action, SEO or topic action. The optional Freemius usage report is opt-in only.
How does the Affiliate Link Assistant handle my links?
You store affiliate links once in the settings. When you enable the assistant for a post (a Pro feature), the AI may add fitting links using the exact URLs from your settings — it never invents or alters URLs. Links receive rel="sponsored nofollow noopener" and a server-side maximum-links limit is enforced.
What does the Pro version add?
Pro adds inline text optimization, the scheduled Auto-Blogger, the strategic topic generator, AI category assignment, style learning, preferred key terms, minimum length, default writing styles, the Affiliate Link Assistant and optional AI featured images.
Does it require the LS – AI Image Generator plugin?
No. The optional AI featured-image feature can work together with the separate, free "LS – AI Image Generator" plugin, but it is not required. If that plugin is not installed, the option is simply skipped.
更新日志:
- First public release as "LS – AI Editorial Engine".
- Added the Affiliate Link Assistant (Pro) with strict, server-side URL integrity and rel="sponsored nofollow noopener".
- Full internationalization of admin and editor strings.
- Hardened settings handling with full per-field sanitization and improved output escaping.
- Switched cache-busting to the plugin version and replaced date() with gmdate() where appropriate.
- Freemius-compatible uninstall cleanup via the after_uninstall callback.