The Account Agent is your central chat panel that can carry out almost every function of the dashboard. It creates and edits websites, pages, sections, domains, SEO, emails, leads and media, and it controls the entire CMS. If you need custom code, the agent automatically writes it for you in the background.
You no longer have to click through workflows manually, simply describe the result you want.
Example prompt:
"Create a blog with five posts and place it under /blog."
You can find the Account Agent at the bottom left of the sidebar and in the editor:
📌Please note: This article is about the Account Agent working together with the CMS: how the CMS works, what the agent does for you in it, and how to use it in practice, both in a new project and on an existing website.
For everything about the Account Agent in general, such as where to find it, how sessions work and what it can do across your entire account, see the article Account Agent: Your AI assistant for your entire account.
How the CMS works
A collection is a list of similar content, for example your services, locations, reviews, blog posts or team members. You decide which details each entry has, such as a name, a photo, a price or a city.
You can display a collection on your website in two ways, and many websites use both:
1. In a section on any page: for example a grid of reviews on the homepage, your team on the About Us page, or the three latest blog posts in the footer. The section pulls the entries from the collection and is therefore always up to date.
2. As an item page for each entry: You design a template page, and each entry in the collection gets its own page from it, with its own address. This is how blog posts, service pages or city pages usually work. A list page then shows all entries and links to them.
Not every collection needs its own pages. Reviews or team members often appear only in sections. Blog posts usually get both: a list page and a page of their own for each post.
Whichever you choose, you only change something once, and it updates everywhere. Collections can also be linked to each other. If a review belongs to a location, each location page shows only its own reviews.
The role of the Account Agent: The agent sets up the CMS and at the same time builds the sections and pages that display your content. It writes them as code and connects your entries to them. You never have to touch this code: texts and images stay in the CMS, where anyone on your team can edit them.
What you can do with the agent in the CMS
The agent can build a collection, fill it, publish it and connect the pages in one conversation. Every change goes into the working copy first. The live site changes only when the agent publishes.
Below is an overview of what the agent can do:
1. Create a collection with 13 field types: plain text, rich text, URL, number, yes/no, date, image, gallery, video, option, multi-option, relation and multi-relation. It cannot create color, icon or location fields.
2. Create the pages. A list page at /{collection} and an item page. Visitors open each record at /{collection}/{record}. It can also turn an existing page into the list or item page, which moves that page's URL.
3. Link SEO on the item page: SEO title and description from text fields, the share image from an image field.
4. Add and edit records, one at a time or in bulk, with an option to publish the whole batch in the same step. Results come back per record.
5. Rich text is inserted as HTML: paragraphs, headings, quotes, lists, bold, italic, underline, strikethrough, links, line breaks, images and videos. Nested lists become one level. Other tags are removed but their text is kept.
6. Publish, unpublish, schedule, one at a time or in bulk. A scheduled time must be in the future. Unpublishing takes a record off the live site at once and keeps it as a draft.
7. Edit the collection: add fields, archive and recover fields, reorder them, mark fields required, set number format and Min/Max.
8. Keep things tidy:
Duplicate a record, or copy a collection's structure (also into another project; records and relation fields are not copied).
Search records by title, slug and text fields.
Find which records link to a record, and move all those links to another record.
Run a health check for broken links, removed option choices, empty required fields and archived fields that still hold data.
9. Revision history: list a record's revisions, open one, see what changed between two, and roll back. Rolling back replaces the current working copy, including unsaved edits. The live site stays the same until the record is published again.
The Data tab (CMS)
The CMS now looks and works like the other project tabs. In the dashboard, you can currently find it and its settings under the Data tab.
Sidebar: Collections are listed on the left. Drag them to reorder, and the order is saved. "Create collection" stays at the bottom.
Collapse the sidebar: Click the "Data" title to hide the sidebar. Your choice is remembered in the browser.
A link per collection: Each collection opens at its own address. Old CMS links still work.
Top bar: Search, column settings, "Collection Settings" and "Create record" sit next to the collection name.
Bulk actions: When you select rows, the top bar changes to "N selected" with "Publish", "Schedule", "Draft" and "Delete" (with confirmation).
Table: Status is the first column, but you can still move or hide it. The table has a thin border, and the header stays in place while you scroll.
Empty project: You'll see "Create collection" with a button to start.
Required fields: Custom fields have a "Required" switch next to "Hidden". Title and Slug are always required.
Number limits: A value outside Min/Max shows "Enter a value within …" and blocks Publish and Schedule in the record editor. The server also refuses to publish it, including in bulk. If Min is above Max, you'll see "Max must be greater than or equal to Min." and you can't save in Collection Settings.
Live site follows the collection: Hiding a field or moving it to Trash removes it from the live site on the next page load, with no republish. A field in Trash no longer blocks publishing, and its data is kept so it can be restored.
Live updates: The table refreshes after the agent's changes and after saves in another tab of the same browser. CMS sections in the editor load collections the agent just created.
Duplicates keep every collection: Duplicating a project, creating one from a template, or saving a project or page as a template copies all collections with their records. This includes collections that no page uses yet.
Practical example 1: New project – first the website, then the blog
To show you how easy it is in practice to create a website with a blog using the Onepage Account Agent, here is a concrete example.
You start in an empty project. We recommend this order: first the website, then the blog. That way, the agent already knows your business, your pages and your design, and builds the blog to match them right away.
Step 1: Create the website
Describe your business and the pages you need. Replace the parts in brackets:
Prompt:
"In this project, create a website for my [type of business], [name of business] in [city], with these pages: [list of pages]. Use realistic sample content. Publish everything when you're done."
The more specific you are, the closer the first result will be to what you have in mind. The agent first presents its plan and then builds the website in stages. In between, reply with "Continue" or say what you'd like to change.
Step 2: Create the blog with the CMS
Your website is ready. Now the agent adds the blog in the same chat:
Prompt:
"Create a blog for this website under /blog with 4 articles on the topic of marketing. Also create two different authors and assign two of the articles to each author. Generate detailed information about their studies and professional experience for both authors and create their own profile pages."
What the agent does automatically in the background
Even though your prompt is phrased like a normal conversation, the agent independently takes care of the complete, complex setup:
1. Creates & links collections
The agent sets up two databases: Blog and Authors, and automatically adds fields like Studies, Experience, and Biography, linking the two collections together.
2. Generates content & profiles
It writes 4 marketing posts, creates 2 complete author profiles (with CV and expertise), and assigns 2 articles to each author.
3. Builds pages & URLs
It creates the main blog page (/blog), individual article pages, and dedicated author profile pages (/autoren/{slug}).
4. Displays the blog layout
The blog page now features a finished article grid showing post details and author names.
Step 3: Connect the blog and the website (optional)
With short follow-up prompts in the same chat, you connect the blog to the rest of your website.
Show the latest posts on the homepage
Prompt:
"Show the three latest blog posts on the homepage and link them to the blog. Also add the blog to the menu."
Because the posts come from the CMS, this area is always up to date: every new post automatically appears on the homepage.
Add an authors section
To let visitors click directly through to the author profiles, simply tell the agent in the same chat:
Prompt:
"On the blog page, add an 'Our Authors' section below the articles. Display both authors there and link them to their profile pages."
The agent adds a section with author cards to the blog page. Clicking an author opens their full profile page with all the details about their background, experience and the articles they've written.
CMS example: https://ai-agent-beta-test.onepage.me/blog
🎉 And that's it! In just a few minutes, you've built a website with a fully functional blog using a single tool!🎉
Good to know: If your website from step 1 already contains content that fits into the CMS, such as services or team members, you can have it transferred later as well. Tell the agent "Keep the existing entries" so that it takes over your existing content instead of writing new content.
Practical example 2: Add a CMS to an existing website
Your website is already live, whether you built it in the editor or with code. Your texts are in place and your design works. Now you want the CMS to take over recurring content, and you want the agent to find more ways to expand your website.
The agent proceeds as follows:
Analyze your website and find out what already repeats and where there is potential
Create the CMS (collections, fields, entries)
Build sections and pages and connect them to the CMS
Check the result and hand it over
This is a lot of work and can take a while, so please be patient while the agent works.
💡Tip: It's best to start a new session for this task. Learn more in the article Account Agent: Your AI assistant for your entire account.
Step-by-step guide
Step 1: Get recommendations
Prompt:
"First, find out what my website is about. Actually read the texts on every page, not just the list of sections. Then give me a complete list of recommendations: which existing content could move into the CMS and which new content would be worthwhile."
The agent reads your website and replies with a short summary of what your business does and who the website is for. Two lists follow.
The first shows what you already have that fits into the CMS, for example services, references or reviews, each with the details every entry would have.
The second shows what you could add, such as a dedicated page for each service or city, or a blog. The agent also points out things worth improving, for example missing legal pages or buttons without a link. Nothing on your website changes in this step yet.
Read the summary first. If the agent has misunderstood your business, correct it now.
Step 2: Choose what the agent should build
Choose from both lists and tell the agent what to implement now and what to save for later. Replace the part in brackets with your selection:
Prompt:
"Implement the following items from both lists: [your selection]. Leave out the rest for now. Keep my texts and the design."
The agent creates the collections, takes over your texts word for word and builds the new pages in the style of your website.
Step 3: Connect sections on your pages to the CMS
Your content is now in the CMS. Next, the sections on your existing pages should pull their content from it.
The agent often already does this in step 2.
Only carry out this step if it hasn't yet connected your existing sections and pages.
Prompt:
"Based on the CMS, create or adjust the pages and sections that need to be connected, so that the content comes from the collections and nothing appears twice. Keep the design."
Editor sections (which you arrange yourself in the editor): For now, the agent creates a code copy of each section, styles it like the original and connects the copy to your collection. The copy sits directly after the original, and the original is hidden. Nothing is deleted, so you can compare both. When you're happy, ask the agent to remove the hidden sections.
React sections: The agent connects them directly to the CMS.
The agent can still change texts and links in your editor sections at any time. Only the connection to the CMS runs through code sections. This is a temporary limitation. If you want to keep a particular editor section, you can connect it to the CMS yourself in the editor.
When everything looks right, write to the agent: "Publish everything."
Step 4: Click through the live website
Open your live website and use it like a visitor: click the menu, open the new pages and follow the links. The agent builds and checks everything on its side; your look from a visitor's perspective completes the task. If something isn't the way you want it, describe what you see:
Prompt:
"On the live website, [what you see]. It should [what you expect]. Please fix this and publish."
🎉 Done! Your CMS is set up and live. From now on, you handle everything else via prompt.
The CMS in everyday use: example prompts
Once your content is in the CMS, simply tell the agent what you need:
Prompts
"Change [detail] of [entry] to [new value], but don't publish yet."
"Schedule [entry] for [date and time]."
"Take [entry] offline, but keep it as a draft."
"Show me what has changed in [entry] and restore last week's version."
Also ask from time to time:
"Check all collections for broken links and empty required fields."
Good to know: An entry's page is only live once the website, the item page and the entry itself are published.
Safety checks built into the tools
For the following actions, the tool refuses the first request, reports the impact, and only proceeds when the agent repeats it with an explicit confirmation:
Deleting a record that other records link to: Shows which records link to it and offers the option to move the links to another record.
Deleting several records: Shows how many, and which of them are linked from elsewhere.
Deleting a collection: Shows the number of records and that its views, view pages and page connections will be deleted too. Other collections that link to it are named.
Deleting a field permanently: Shows how many records contain data in it. Archiving the field is the reversible option.
Removing option choices: Shows how many records use the options being removed.
Changing the URL of a published or scheduled record: The old URL shows a "page not found" error, with no redirect and no undo. If the old URL was shared anywhere, ask the agent to set up a redirect.
(Deleting a record that nothing links to, and rolling back a revision, are covered by the agent's instructions to ask first, not by a tool check).
Rules the agent follows
Unknown fields: Writing to a field the collection does not have is refused, and the real field names are listed. The same applies to an option value that doesn't exist and to a link to a record that doesn't exist.
Limits: Record title up to 300 characters, URL slug up to 200. Lists show 20 records at a time by default.
Addresses: The agent is instructed to give the project's real address, not one made up from the project name.
React sections that read the CMS: On the live site, they show only published records. The editor also shows drafts and scheduled ones. Up to 12 collections per section, 1–100 records per page (default 12).
Live table: The Data tab refreshes after each agent change to records and switches to the collection the agent worked on. Creating, changing, or deleting a collection refreshes the collection list.
Plan restrictions: There is no plan restriction on the CMS tools. Creating pages can still hit the plan's page limit, which the agent points out.
Migrations: Moves from other platforms are still limited. For now, use MCP with an export file, or for complex websites, wait for the dedicated migration feature.
Links between collections: Each collection can currently only be linked from one other collection. For example, if reviews already link to services, projects can't also link to services. The agent points this out and suggests an alternative.
With the Onepage AI Agent, you no longer have to spend time clicking together CMS structures, links and layouts by hand. You simply describe the goal and the agent takes care of the technical implementation in the background.
💡Do you have feedback on this help article? Feel free to share it with us via live chat or at support@onepage.io so we can keep it up to date. 🙂