Track Content Update

Track page publish and refresh content updates for AEO and SEO Insights

What is the Track Content Update Step?

The Track Content Update step records page-level content updates, such as when a page is published or refreshed, directly from your workflow. These content updates feed into Content Updates, giving you visibility into your content publishing activity across all the pages tracked by your Brand Kits.

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 for the full list.

When to Use the Track Content Update Step

When your workflows create or update webpage content using a Code step, Call API step, or any other non-native CMS approach, AirOps has no built-in way to detect that a page was published or refreshed. The Track Content Update step closes this gap by letting you explicitly log these content updates as part of your workflow.

Use it when you:

• Push content via a Code step or API call to a CMS that doesn't have a native AirOps integration

• Publish new pages through a workflow and want Insights to start tracking that page immediately

• Refresh existing content and want to record when the update happened so you can measure its impact on SEO and AEO performance

---

How to Configure

Type

Select the type of content update you want to record:

• Page Published - use this when a new page is being created and published for the first time

• Page Refreshed - use this when an existing page is being updated with new or revised content

URL

Enter the full URL of the page being published or refreshed. This field supports Liquid templating, so you can reference outputs from previous steps.

For example, if a prior step returns the published page URL:

{{ publish_step.output.url }}

URL requirements:

• Must be a full URL (e.g., https://example.com/blog/my-post)

• The URL domain must match a Brand Kit domain in your workspace. The step automatically resolves the Brand Kit from the URL.

Custom Attributes

Add up to 20 key-value pairs of custom metadata to the content update. Both keys and values support Liquid templating.

Custom attributes appear alongside system metadata in the Content Updates table and page detail view. Use them to tag content updates with additional context, for example the workflow name, content author, or CMS status.

Soft Fail

When enabled (the default), the workflow continues even if this step fails. This prevents a tracking failure from interrupting your content publishing workflow.

---

Output

The Track Content Update step outputs the ID of the created content update record:

{
  "id": 12345
}

---

Example Use Case

A common pattern is to pair the Track Content Update step with a Code step or Call API step that publishes content:

1. Prompt LLM - generate or refresh article content

2. Code Step - call your CMS API to publish the content to your website

3. Track Content Update - record the publish so Insights can track the page

This way, every time your workflow publishes content through a custom integration, the content update is logged and reflected in your Insights dashboard.