Choose the AI workflow that matches the job: content tools for drafting and page creation, WordPress Engineer for site investigation and development, and Hosting Engineer for supported account-management work on the relevant hosting service.
IN THIS ARTICLE
01 Match the task to the available tool
- Use AI website writing tools for a new post, page, translation or description.
- Use the full website builder when creating a broader page and design starting point, with its publication and theme-change behaviour understood.
- Use WordPress AI Engineer to inspect WordPress files, logs, configuration and available site tools, then propose or perform reviewed technical changes.
- Use the appropriate Hosting Engineer for account operations such as supported mail, domain, database or hosting configuration tasks.
02 Start with the correct service
- Open the client area service that owns the website or hosting account.
- Confirm the selected website and whether it is live or staging.
- Choose the relevant tool and describe the intended outcome.
- State any boundary, such as drafting only or diagnosing before writes.
- Review the actual proposed action and the available recovery method.
- Verify the result in the system where the change belongs.
Can a content prompt create a working mailbox or payment gateway?
Writing a page that describes those features does not configure the underlying service. A Contact page still needs working delivery, and a store still needs an approved payment integration. Use the appropriate account or application setup workflow and test the actual function.
Does Engineer access include root control?
No. The Engineer uses the tools and permissions available to the selected website or hosting account. SSH work is account-scoped where available, and external services may require an authorised administrator outside that scope. Do not interpret broad development assistance as unlimited server access.
Are all changes reversible through one Undo button?
No. Eligible WordPress file edits can have limited Undo snapshots, while database, shell, mail and other hosting changes need their own recovery plan. A backup remains important for work with wider effects.
03 Keep the outcome clear
When a task crosses layers, ask for the dependency sequence and verify each part. For example, configure and test a form's delivery before publishing a claim that customers can contact you through it. Record what is completed and what still needs account access or human support.