> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/actions/workflow-concepts/workflow-steps/content-updates.md).

# Content Updates

Track and record page-level content updates for AEO and SEO Insights

Content Update steps allow you to record page-level activity, such as publishing or refreshing a page, directly from your workflows. These content updates feed into [Content Updates](/insights/onsite/content-updates.md), giving you visibility into how your content publishing activity correlates with SEO and AEO performance.

The Content Update steps include:

1. [**Track Content Update**](/actions/workflow-concepts/workflow-steps/content-updates/track-content-update.md) - record a page publish or refresh content update for a Brand Kit

{% hint style="info" %}
Some native CMS integration steps (WordPress, Webflow, Shopify, Ghost) capture page content updates automatically. For those integrations, you do not need to add a Track Content Update step. See [Content Updates](/insights/onsite/content-updates.md) for the full list of supported integrations.
{% endhint %}

Content Update steps are intended for workflows that create or update webpage content without using a native CMS step, for example when you use a Code step or Call API step to push content to an external CMS. In those cases, AirOps has no built-in way to detect the publish or refresh, so the Track Content Update step lets you log it explicitly.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.airops.com/actions/workflow-concepts/workflow-steps/content-updates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.