Tracy is different from prompt-to-site builders and generic chatbots because it works on real WordPress, Joomla and EmDash sites and lets you review recorded changes and use recovery options supported for the change and platform.
Most people who look after a website today make changes in one of a few ways: they click through the admin themselves, they ask a developer, they ask a chatbot for instructions, they use an AI plugin inside the CMS, or they rebuild the site on a new AI builder. This page compares Tracy with each of them, including the cases where Tracy is not the better choice.
At a glance
| Doing it in the admin | Asking a developer | ChatGPT or Claude Code | AI plugin inside WordPress | Tracy | |
|---|---|---|---|---|---|
| Works on your actual site | Yes | Yes | Only if you give it access and apply the result | Yes, inside WordPress | Yes: sites it builds, and copies of sites you import |
| Knows your site’s template and content | You need to know it | Yes, after onboarding | Only what you paste or connect | Partly, depends on the plugin | Reads the site before changing it |
| Effort per small change | You click through menus and settings | A message, then waiting | You copy instructions or code and apply them | Varies by plugin | One sentence in your own language |
| See exactly what changed | From memory or CMS revisions | Depends on the developer’s process | Depends on your own setup | Usually CMS revisions | Site changes, with available file Diff views on WordPress and Joomla; no EmDash file history |
| Go back | CMS revisions for some content | Ask the developer | Depends on your own backups | Usually CMS revisions | Undo a supported change, ask Tracy to revert it, or restore a backup of files and database on WordPress and Joomla, or database and media on EmDash, excluding template code |
| Platforms | Your CMS | Any | Any | WordPress only | WordPress, Joomla and EmDash |
| Best for | Occasional edits by someone who knows the admin | Custom code, integrations, complex work | Learning, drafting, developer workflows | Writing help inside WordPress | Frequent everyday changes on running sites |
Tracy or doing it yourself in the admin?
Doing it yourself costs nothing extra and keeps you in full control. The cost is time and knowledge: you need to know where the template keeps the footer, which module controls the mobile menu, and which override changed last year. For someone who edits one site once a month, the admin is fine.
Tracy fits when the changes are frequent or spread across several sites. You describe the change once, in your own language, and Tracy finds where it lives on the site and makes it. You still have the admin, since a Tracy site is an ordinary WordPress, Joomla or EmDash site, so you can mix both ways of working. The difference is the record: supported file changes Tracy makes on WordPress and Joomla are listed in Site changes, with available file Diff views. EmDash has no file history.
Tracy or asking a developer?
A developer brings judgment, accountability and custom code. For new features, integrations with other systems, performance work or anything that needs a code review, a developer is the right choice, and Tracy does not replace that.
For small requests, the trade-off changes. Each small request to a developer is a message, a wait and often a bill, and for the developer it is a context switch that is hard to charge for. Tracy handles that everyday layer, such as text, images, menus, modules and pages, and leaves the developer free for the work that needs them. Agencies often use Tracy exactly this way: see Tracy for agencies.
Tracy or ChatGPT and Claude Code?
General AI assistants are good at explaining how to do something and at drafting text or code. In their usual setup, they do not see your site unless you paste in its content or connect them to it, and applying the result is up to you. Coding agents such as Claude Code can edit files directly when a developer gives them access to a codebase, and they work well inside a developer’s own workflow with version control.
Tracy is built for a different job: making changes on a running CMS site for people who look after that site. It reads the site, makes the change on it, records supported changes in Site changes, and gives you ways back where available: undo a supported change, ask Tracy to revert it, or restore a backup. WordPress and Joomla full backups include files and database; EmDash backups include database and media, not template code. You do not need to set up a repository, a terminal or your own backups to get that record.
If you are a developer who already works on a site’s code with version control, a coding agent may suit you better. If you look after sites through their admin, Tracy is closer to how you already work.
Tracy or an AI plugin inside WordPress?
AI plugins for WordPress vary widely. Many focus on generating text or images inside the editor, and they rely on WordPress revisions for history. That can be enough if your need is writing help inside one WordPress site.
Tracy works at the level of the whole site rather than one editor screen: pages, menus, template files and settings, on WordPress, Joomla and EmDash. It keeps its own record of supported changes, with available file Diff views on WordPress and Joomla, and backups you can restore: files and database on WordPress and Joomla, or database and media on EmDash, excluding template code. See See what Tracy changed.
Can Claude Design build a WordPress or Joomla site?
Not directly, as of October 2026. Claude Design, from Anthropic Labs, turns prompts, images, documents and codebases into designs, prototypes, slides and one-pagers, and you refine them with chat, inline comments and direct edits on the canvas.
Its documented exports are ZIP, PDF, PowerPoint and standalone HTML files, and it can send work to tools such as Canva, Lovable, v0, Netlify, Vercel, Wix, HubSpot and Adobe Experience Manager, or hand it off to Claude Code. Its documentation does not describe sending work to WordPress or Joomla.
Tracy works on the website itself. It builds a real Joomla, WordPress or EmDash site, or imports an existing Joomla or WordPress site with its own admin, lets you change it by asking in your own language, and records supported changes in Site changes so you can review them and use available recovery options. EmDash has no file history or request Undo. The two fit together: Claude Design to explore and present ideas, Tracy for the site you keep running.
Sources: Introducing Claude Design by Anthropic Labs and Get started with Claude Design.
Tracy or a prompt-to-site AI builder?
Prompt-to-site builders generate a new site from a description, often on their own platform or format. They are quick for a brand-new site when you have nothing yet.
Tracy can also build a new site from a short brief: it starts from a ready-made design, writes your text and lays out the pages you choose, on WordPress, Joomla or EmDash. The difference is what happens next. The site stays an ordinary CMS site with its own admin, you can keep editing it by asking Tracy, and you can import copies of WordPress and Joomla sites you already run instead of rebuilding them. If your site already exists and works, Tracy lets you keep it.
When is Tracy not the right fit?
Tracy is not the right choice when:
- The site runs on Shopify. Shopify is not supported yet.
- The site is a custom-coded application without a CMS admin panel.
- You need custom development, such as new extensions or integrations with other systems.
- You need a Joomla 3 upgrade. Tracy does not offer a Joomla 3 upgrade path.
- The problem is on the server, such as email delivery, two-factor lockouts or database errors.
- Every change must be signed off before it happens. Tracy applies ordinary requests directly and you review afterwards; it does not wait for approval before each edit, but asks for targeted confirmation before consequential actions.
Tracy also does not promise that a change can never break a page. It lets you review recorded changes and use recovery options supported for the change and platform. For the detail, see Undo and backups.
Frequently asked questions
Is Tracy an AI website builder or an AI website editor?Both. Tracy can build new WordPress, Joomla and EmDash sites, and it can import copies of existing WordPress and Joomla sites. Most of its daily use is editing: ordinary requests in your own language on a site that keeps a record of its changes.
Can Tracy replace my developer?Not for custom code, integrations, audits or major upgrades. Tracy takes over the everyday small changes, so developers can spend their time where they are needed.
How is Tracy different from asking ChatGPT how to change my site?A chatbot usually tells you what to do, and you apply it. Tracy reads your site, makes the change, and records supported changes so you can review them and use available recovery options. File history and Undo availability depend on the platform.
Does Tracy work with Joomla?Yes. Tracy supports WordPress, Joomla and EmDash. See the Tracy for Joomla.