AUTONOMOUSc CMS Documentation

This guide is written for humans first. You do not need to understand every feature to use AUTONOMOUSc CMS well. The simplest way to think about it is: pick one live page, review a safe draft, publish manually, then add heavier SEO or automation only when it earns its place.

The core structure: AUTONOMOUSc CMS stores content in a Website -> Collection -> Page -> Field model. Once those four layers make sense, the rest of the product becomes much easier to navigate.

1) Get started guide

If you want the easiest possible start, do these steps in order and ignore everything else for now.

Step 1: Paste one important live page URL from the home page or in Studio.
Step 2: Sign in when Studio asks. It can create the website, collection, and page record behind the scenes.
Step 3: Review the first suggested improvement in hosted preview and publish the version you trust.
Step 4: Open SEO when you want to add business context, page goals, or Search Console data.
Step 5: Add WordPress handoff, schedules, or slower automation after the first live improvement is already working.

Best first setup: aim for one live page, one published change, and one calm weekly rhythm. Once that feels stable, repeat the same workflow on more pages or more sites.

2) The 4 words that explain the CMS

Website: your project or website, such as my-company-site.
Collection: a group of pages, such as main, blog, or landing-pages.
Page: one page ID, such as homepage, pricing, or faq.
Field: one piece of content on that page, such as hero_title, intro_text, or faq.

If you remember only one thing, remember this structure. Most of the product gets much simpler once these four words feel familiar.

3) Daily use in Studio

Studio is easiest when you treat it like a sequence instead of a dashboard. Most days you only need a few actions:

Open the page you want to improve.
Review the suggested change and adjust the fields until the content looks right.
Publish manually when the page is ready.
Open SEO if you want to add metadata, page goals, or Search Console data.
Add schedules later only when the manual flow already feels stable.

Field types

Text: paragraphs, headings, short copy, CTAs.
List: bullet lists, FAQ-style items, feature lists.

Scheduled AI content jobs currently work best with text fields. Lists are still useful, but they are more of a manual editing workflow today.

4) Optional smart features

Everything in this section is optional. You can ignore it until manual publishing feels easy.

Content schedules

You can ask AI to update a text field later. There are two modes:

One-time schedule: run once at a chosen time.
Recurring schedule: repeat every X days.

Good prompts say what should stay the same and what should change. For example: keep the tone, keep the main promise, but refresh the wording for a new season.

Pick a text field you already understand.
Choose when it should run once, or how often it should repeat.
Write a short prompt that says what must stay the same and what should change.

SEO context

The SEO area lets you give the AI more context at three levels:

Site metadata: business name, audience, keywords, region, and brand notes.
Page metadata: what this page is for, which keywords matter, and what action you want the visitor to take.
Field metadata: what one specific block of content should do.

You do not need to fill in every box. Think of it as helpful notes for the AI, not homework.

SEO agent

The SEO agent is meant to be slow and careful. It looks at longer-term search data, uses your metadata for context, and makes gradual SEO suggestions or changes instead of changing pages every day.

You can turn the SEO agent on or off at the site level.
You can review agent history to see what it did and why.
You can roll back changes if needed.
You can pause manual content schedules site-wide if you want the SEO strategy to stay stable for a while.

Simple advice: only turn on the SEO agent after your content structure is stable and you understand where your main pages live.

5) Show content on your website

WordPress

Install the WordPress plugin and use the shortcode to render a field. This is the easiest path if your site already runs on WordPress.

Prefer a separate tab? Open the WordPress plugin tutorial.

[agentic_cell site="mywp" table="main" row="homepage" col="hero_title"]

Any backend, app, or build step

You can also fetch published JSON from your own code. The endpoint is private, so send your API key in the Authorization header.

GET https://cms.autonomousc.com/cdn/prod/:site/:table/:rowKey.json GET https://cms.autonomousc.com/cdn/prod/:site/:table/:rowKey/:colKey.json Authorization: Bearer acms_live_...

If you are technical, the private JSON endpoints above are the main integration you need. If you are not technical, you can ignore the API completely and just use Studio and the WordPress plugin.

6) Common questions

Do I need the AI features? No. The CMS is still useful as a manual content system.
Should I schedule content updates right away? Usually no. Publish manually first so you understand your content structure.
Can I turn the SEO agent off? Yes. There is a site-level on/off switch.
Can I see what the SEO agent did? Yes. Use the agent history panel to see actions, reasons, and rollback options.
Why did a schedule not run? Check your auth, confirm the field is text, and make sure the site-wide manual schedule pause is not enabled.
Why do dates look strict? Scheduled API calls use UTC timestamps, for example 2026-04-01T09:00:00.000Z.

Docs v9. Begin with a live page, publish manually, then add automation one layer at a time.