Content agent
Content agent
The Content agent reviews the project's content entries in Collections and reports what needs attention. It is there in every project's Operations Center.
What it reads
- The project's content entries, which every environment of the project shares.
- Up to 500 entries a run.
- Its counts are recorded only when every entry was read, so a part is never shown as the whole.
The agent only reads. It changes nothing.
Signals
| Signal | What it means | On target at | Critical past |
|---|---|---|---|
| Content entries | How many entries the project has | ||
| Drafts that do not validate | Drafts that could not be published as they are | 0 | 5 |
| Entries never published | Entries that are not live yet | 0 | 10 |
| Published entries with unpublished changes | Live entries whose draft has changes not published yet | 0 | 10 |
A value between the two lines is Watch. The targets are general defaults, not a measure of your project.
Findings
A finding names the collections, the entries and what to do. See Findings and actions.
What the Content agent found is shown only to people who may edit content.
When nothing was reviewed
| The group says | What to do |
|---|---|
| Content editing is not on for this project | Run the agent again once it is on |
How often it may run
- There is no hourly or daily limit: it runs whenever a person starts it.
What a run costs
- At most 10 credits a run.
- The estimate is shown before it starts; see How an agent run is paid.
SEO agent
The SEO agent reads the storefront's sitemap, checks a sample of its live pages for what keeps them from being found and reports what to fix.
Findings and actions
The four tabs of the Operations Center, what you can do with a finding, how a proposed change moves across the Actions board, and what History records.