How to work with AI on Vehica

An AI assistant works on a Vehica site the way a good freelancer would: it logs in, reads the screens, changes what you asked and shows you. What makes it work well on Vehica is that nothing is hidden. Every page, vehicle, field and setting has a name and an address, so the assistant can find it and you can check it.

This article is about three ways of working, when each one is worth it, and what we do ourselves when we build a site for a client. It is not tied to one tool. Claude, ChatGPT and the rest change every few months; the three ways do not.

Three ways an assistant can work on your site

1. In the browser, like a person

Claude in Chrome, ChatGPT agent or a similar tool opens wp-admin in a browser and uses the same screens you would: the Vehica options, Elementor, the vehicle form, the menus. You watch it work and can stop it at any time.

Best for setup, anything visual and small changes: colours and fonts, a new page laid out in Elementor, a menu, a form. Anything where the result needs eyes.

2. Through the WordPress REST API

WordPress has a built-in API at /wp-json/. Pages, posts, media, users and their fields are all reachable through it, and an assistant with an application password (a WordPress feature, under Users) can read and write them without a browser. One run can create dozens of pages, change a field on every one of them, or fill in SEO titles for the whole site.

Best for content in bulk and repetitive edits. For vehicles specifically, ask us before a big import: whether your version exposes them to the API depends on the theme version, and where it does not, WP-CLI on your server or the importer does the same job.

3. Through an MCP server

MCP (Model Context Protocol) is the standard that lets an assistant use tools directly instead of typing into a browser. A WordPress MCP server, of which several exist, connects your site to Claude Desktop or another client. You then say what you want in plain words and the assistant does it through the API underneath, every day, without scripts.

Best when you want to talk to your site as part of your routine: "add these three vehicles", "change the phone number everywhere", "which pages have no description".

What to use when

• Setting up a new site. Browser. Import a demo, then let the assistant set the options, colours, menus and pages.
• Filling the site. REST API or MCP. Give the assistant a spreadsheet and the field names.
• Design changes on Elementor pages. Browser. Elementor data can be written through the API too, but the result has to be seen.
• Custom CSS and small code. A code snippets plugin (WPCode or similar) through the browser. One change per snippet, each with a name, so any of them can be switched off later.
• Moving from another theme. REST API to read the old data, REST API to write it into Vehica's fields, browser to check the pages.
• SEO titles and descriptions. REST API, in bulk, from a list you approve first.

How we do it on a client site

This is the order we follow when we build a Custom Website on Vehica. It works the same on your own site.

1. 1 Start from a demo

   Import the demo closest to the result, so the structure, menus and sample content exist before anyone touches a setting.

2. 2 Give the assistant a brief

   Logo, colours, fonts, the list of pages, the tone of voice. It sets the palette in the site settings, builds the pages in Elementor and adds the people.

3. 3 Content in bulk through the API

   Team members, testimonials, blog posts, the SEO title and description of every page, in one pass from a spreadsheet.

4. 4 CSS as named snippets

   Every visual change that the options do not cover goes in its own snippet with a name and a number. One can be switched off without touching the rest, and a theme update cannot overwrite it.

5. 5 A backup before every change

   A draft copy of the page, an export of the settings. The assistant makes them itself if you ask, and you can ask it to restore them.

6. 6 Check at three widths

   Every page as a screenshot at 1440, 820 and 390 pixels. Ask for the screenshots; they are the fastest way to see what the assistant did.

Rules that keep it safe

• Work on a copy first. A free trial site on our servers is a good place to try anything before it touches your live site.
• Give the assistant its own WordPress user with an application password, and remove it when the job is done.
• Never paste a password into a chat. Let the tool log in through its own browser, or use an application password made for it.
• Ask for a backup before any change that touches more than one page.
• Review the result yourself. An assistant is fast and confident; it is not always right.
• Keep changes as snippets, options and drafts, never edits to theme files. An update overwrites theme files.

Prompts that work

Say what the result should be, what not to touch, and what to show you at the end. Three we use, with the parts you fill in brackets.

If you would rather we did it: with a licence bought here, Premium Support covers installation, setup and small changes for 12 months, and a Complete Website plan for as long as it runs. Discover Premium Support.