# Content Updates

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/insights/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/insights/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: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

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

The question should be specific, self-contained, and written in natural language.
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.