

Yamandu Native AI Content Creator adds practical AI writing, image generation, image titles, and alt text generation to native WordPress workflows. It is built for publishers, agencies, marketing teams, and site owners who want faster content production without moving editorial work into a separate platform.
Use Yamandu to generate post text in the editor, create images from prompts, improve image alt text for accessibility and image SEO, and organize media with useful attachment titles. The plugin works inside familiar WordPress screens: Gutenberg, Classic Editor, the Media Library, attachment edit screens, row actions, bulk actions, and the Yamandu settings page.
Yamandu 1.1.2 supports the WordPress AI Client and Connectors when available. That means compatible sites can use AI providers configured in Settings -> Connectors, including Google/Gemini and OpenAI through their connector integrations. For older WordPress environments or sites not using connectors, the legacy direct Gemini API integration remains available as a fallback.
Yamandu focuses on the editorial tasks that WordPress teams repeat every day:
Many WordPress AI plugins focus only on chat, only on alt text, only on filename-based image attributes, or only on a separate content platform. Yamandu combines AI writing, AI image generation, and native image metadata workflows in a focused plugin designed for professional publishing.
Core advantages:
When WordPress AI Client and Connectors are available, Yamandu can use compatible providers configured in WordPress:
When Connectors are not available or not configured, Yamandu can continue using the legacy direct Gemini API integration configured in Settings -> Yamandu.
Yamandu lets administrators choose model preferences for the main generation tasks:
The available options depend on the providers connected in WordPress. If a compatible model is not selected, Yamandu can use the automatic recommended option.
Yamandu does not treat AI as invisible background automation. Administrators control whether third-party requests are enabled, which provider path is used, which model preferences are selected, and when metadata should be generated or regenerated.
This matters for real editorial operations. AI can speed up drafting, image creation, alt text, and media organization, but teams still need human review, predictable settings, and clear control over external processing.
Yamandu connects to external AI services only after an administrator enables third-party requests in the plugin settings and configures either a WordPress AI connector or the legacy Gemini API key.
Depending on the enabled workflow, data sent to an AI provider may include text prompts, selected post text, draft instructions, image prompts, selected image file content, image URLs or file data, filenames, existing image metadata, site language information, and generation settings.
Requests are made only when an authorized administrator or editor triggers generation through the post editor, Media Library, attachment edit screen, row actions, bulk actions, or image creation interface.
Services that may be used depending on configuration:
When Yamandu uses WordPress AI Client and Connectors, provider credentials are managed by WordPress and the corresponding connector/provider plugin. When Yamandu uses the legacy fallback, the Gemini API key is entered directly in Settings -> Yamandu.