Frontman – AI Website Editor

01 / SOURCE DETAILS

About this tool

Frontman is an AI editor for an existing WordPress site. Open Frontman from the WordPress admin menu, keep the page visible, and describe the result that you want. Frontman can inspect supported WordPress structures, make the change, and refresh the preview for your review. Use Frontman for focused site updates without hunting through page builders, theme screens, menus, widgets, and settings. One Task, From Request to Review The screenshots show one complete task: Open the page beside Frontman. Select the FAQ title that needs an update. Describe the new title in plain language. Frontman inspects the WordPress content and applies the supported change. Review the refreshed page before you continue. For headers and footers, Frontman can inspect candidate templates, template parts, menus, widgets, and Elementor content. The structure that controls the rendered page depends on the site. Learn how to identify and edit a WordPress header or footer . Before You Install Frontman requires: WordPress administrator access A Frontman account with GitHub or Google sign-in A supported AI provider connected with OAuth or an API key A current backup, with staging recommended for higher-risk changes Frontman does not include a model credential. Your provider can apply its own usage limits and charges. Common Tasks Use Frontman to: Update page copy, headlines, buttons, and calls to action Edit posts, pages, and Gutenberg blocks Adjust supported Elementor content with Elementor-aware tools Update WooCommerce products and other supported store data Change navigation menus, templates, template parts, and supported widgets Update Additional CSS and allowlisted site settings Read or update supported SEO title and description overrides when a tested provider is available Inspect a page and explain which supported WordPress structure can control it How Frontman Works Frontman puts an AI editor beside a live view of your site. Select mode adds context from the visible element to your request. Frontman then uses WordPress, Elementor, or WooCommerce tools that match the request. The preview refreshes after a supported change, so you can review the page in the same workspace. Frontman works with WordPress content and structures that its current tools support. Custom themes, custom plugins, hosting controls, and unsupported page builders can require a different workflow. Native Post Authors wp_create_post and `wp_update_post` accept an optional positive integer `author` account ID. Omission uses the current user on creation and preserves the existing author on update. These tools assign one native WordPress author, not guest authors or coauthors. They do not create accounts or change roles. The acting user needs the post type’s create capability or permission to edit the existing post. A new published or private status requires the mapped publish capability. An explicit other account requires the mapped edit_others_posts capability, even when that author stays unchanged. Target accounts do not need a particular role. Frontman also requires author support and, on multisite, current-site membership. These are Frontman safeguards, not additional WordPress directory policy requirements. For a user-requested author task, wp_find_users searches either login or display name on the current site. It requires both manage_options and list_users . Each page contains at most 20 candidates in account-ID order, with total and pagination metadata. Results contain only account ID, login, and display name. They do not prove assignment eligibility. Search uses a literal substring of at most 100 Unicode characters after whitespace trimming. Empty input and input that starts or ends with * are rejected before any lookup. This restriction includes whitespace-wrapped boundary asterisks and asterisk-only input. Interior * , % , _ , and quotes are literal. Case sensitivity depends on the database collation. Consider the remaining pages before selecting an account. If multiple accounts can match the requested identity, ask which account the user means. Never guess an ID or select the first ambiguous result. Read back successful assignment with wp_read_post . Optional SEO Tools wp_read_seo reads stored SEO title and description overrides. `wp_update_seo` updates one or both overrides. The tested versions are Yoast SEO Free 28.4 and 19.9. Frontman does not install Yoast. The route requires WordPress 6.9 or later. Tests cover Yoast 28.4 on WordPress 7.0.2 with PHP 7.4 and 8.4. Tests also cover Yoast 19.9 on WordPress 6.9.9 with PHP 8.2. Premium and active Rank Math, All in One SEO, or The SEO Framework disable these tools. Frontman cannot detect every custom SEO owner. wp_get_site_info returns `seo_unavailable_reason`. A nonempty reason explains why Frontman does not register the SEO tools. A null reason means the compatibility checks pass. Each post still requires edit permissions. Supported objects are posts, pages, and editable non-attachment custom post types with an admin interface, including authorized drafts and private content. Revisions, autosaves, attachments, and internal WordPress object types are not supported. The post ID must be a positive integer. An update must include a title or description. Omitted fields stay unchanged. Empty strings clear overrides and restore Yoast templates or defaults, not necessarily empty rendered tags. Results confirm stored overrides, not rendered HTML or search-engine indexing. Yoast expands variables on later requests. External full-page caches and CDNs have separate refresh behavior. Explicit social overrides stay unchanged and can differ from the SEO title or description. Persistence errors report observed state or mark readback as uncertain. A successful result for one page does not establish success for other pages. Public Text Files wp_read_public_file and `wp_write_public_file` support only `robots.txt`, `llms.txt`, and `llms-full.txt` at the site root. They do not expose theme, plugin, or arbitrary files. Each file supports at most 128 KiB of UTF-8 text. Reads show local content, a revision, and a separate public HTTP observation. Public output can come from WordPress, a host, or a CDN. Frontman cannot prove which system controls that output. Writes require administrator access, the edit_files capability, and host permission for file changes. Supported sites use a single-site, domain-root installation with matching home/site origins and a writable local filesystem. Multisite, subdirectory installations, symlinked roots, unsafe targets, and non-direct filesystem transports are not supported. Frontman does not change host security policies or request FTP credentials. Before each write, Frontman reads the current state and asks for approval of the proposed diff. A stale revision blocks the write. Revision checks are best-effort conflict detection, not a lock against external file writers. CAUTION: Before creating a physical robots.txt , review the loss of generated output. The physical file replaces generated rules and sitemap updates. Restoring generated output requires manual removal of the physical file in this version. An unavailable public observation blocks file creation. A successful public response that differs from an existing physical file blocks updates. Frontman stores one previous snapshot per filename in WordPress options, outside the public root. Reads expose that snapshot. To restore previous physical content, read the current revision and approve a write through the same tool. Files and snapshots remain after plugin deactivation. Write results distinguish saved from verified . A saved file is not necessarily the file that visitors receive. Public timeouts, unexpected status codes, size limits, or content differences mean verification failed. Frontman reports the reason without automatic retries or rollback. An existing physical file can be updated when public observation is unavailable, with an explicit warning. These tools do not guarantee crawler behavior. During a user-requested task, local content, public observations, and previous snapshots can enter AI request context and stored task history. Do not put secrets in these public files. Safety, Limits, and Data Only WordPress administrators with the manage_options capability can access Frontman. The plugin uses WordPress nonces, sanitizes inputs, and restricts option changes to an allowlist. Frontman for WordPress is production-ready. Compatibility depends on your theme, page builder, plugin stack, and hosting setup. Keep a current backup and review each change. Use staging for higher-risk changes. When you submit a request, relevant site content can pass through Frontman AI to your configured model provider. The Third-Party Services section summarizes this data flow. During an active, user-requested chat task, SEO tool results can include overrides from authorized drafts and private content. Frontman sends these results to the selected AI provider as request context. Frontman also stores the results in task history. This process uses the existing chat request and consent flow. During a user-requested author task, lookup account IDs, logins, and display names can enter the selected AI provider’s request context and stored task history. Names and logins can be personal data even though lookup excludes emails and private metadata. This feature uses the existing chat request and consent flow, not a new service. Open Source and Support The Frontman plugin is open source under GPLv2 or later. Browse the code on GitHub . For product details, visit Frontman for WordPress . To report a problem, open a GitHub issue . Third-Party Services This plugin and the hosted Frontman service connect to these external services: Frontman Client and API The plugin loads its interface from app.frontman.sh and connects to api.frontman.sh . Frontman processes prompts, relevant site or store content, tool results, and stored task history to run the agent. SEO tool results c

02 / SOURCE DETAILS

Getting started

Download the Frontman plugin release ZIP or upload the frontman-agentic-ai-editor folder to /wp-content/plugins/ Activate the plugin through the Plugins menu Open Frontman from the WordPress admin menu (you must be logged in as an admin) Sign in to Frontman at api.frontman.sh with GitHub or Google when prompted Reopen Frontman from the WordPress admin menu if Frontman does not redirect you back automatically Connect an AI provider with OAuth or add an API key Start describing WordPress edits beside the live preview

03 / SOURCE DETAILS

Frequently asked questions

What do I need before my first task? You need administrator access, a Frontman account, and a supported AI provider connected with OAuth or an API key. Frontman does not include model access. You do not need another server. What can Frontman change? Current tools support posts, pages, Gutenberg blocks, menus, templates, template parts, widgets, allowlisted settings, Additional CSS, Elementor content, and WooCommerce data. Does Frontman work with every theme? No. Support depends on the structure that controls the rendered page. Custom themes, plugins, hosting controls, and unsupported builders can require another workflow. Can I use Frontman in production? Yes. Frontman for WordPress is production-ready. Keep a current backup, review each change, and use staging for higher-risk changes. What data is sent to Frontman AI? The hosted service processes your prompts, relevant site or store content, tool results, and task history. It sends request context to your selected AI provider. See Third-Party Services and the Privacy Policy below.

Explore related topics