# Freshness (https://app.infrasity.com/docs/content-planning/freshness)





Freshness is where a topic's lifecycle ends up once it's live: as covered in [Sprints](/content-planning/sprints#after-publish-freshness), a published topic is tracked here instead of by its old sprint status, using a **Fresh** or **Stale** pill based on time since publish rather than a further planning stage. Every published topic is checked against how long it's been since publish and flagged, so stale content is easy to spot and prioritize for a refresh.

<Screenshot src="/images/freshness-table.png" alt="Freshness table showing published topics with Fresh and Stale status pills" caption="The Freshness view, showing published topics and how long it's been since they went live." />

## Columns [#columns]

* **Topic**: the article's title.
* **Keyword**: the focused keyword, with a copy-to-clipboard icon.
* **Publish date**: the date the article went live.
* **Freshness**: a status pill:
  * 🟢 **Fresh**: recently published or updated.
  * 🔴 **Stale**: published long enough ago that it may need a content refresh.
  * Each pill is paired with "Since publish \[date]", showing time elapsed.

<Callout type="gotcha" title="Freshness only applies to published topics">
  Topics with no publish date show `–` for both the date and freshness columns rather than a status: freshness can't be calculated until a topic has actually gone live.
</Callout>

## Why freshness matters [#why-freshness-matters]

Search engines and AI models both weigh recency: an article that hasn't been touched in a long time is more likely to cite outdated statistics, reference product details that have since changed, or simply rank behind a competitor's more recently updated take on the same topic. Freshness turns "has this gotten stale" from something someone has to remember to check into something the list surfaces on its own.

<Callout type="info" title="How long until a topic goes stale">
  The [Content Freshness Audit report](/performance-reporting/content-freshness-audit-report) uses three bands: **Fresh** (0–30 days since publish), **Aging** (31–89 days), and **Stale** (90+ days). This table shows Fresh or Stale only.
</Callout>

## Refreshing a stale topic [#refreshing-a-stale-topic]

Refreshing typically means going back to a published topic, updating anything time-sensitive (statistics, screenshots, product details), and republishing under the same URL rather than creating a new topic. Not every topic needs the same refresh cadence: a foundational guide meant to stay evergreen usually warrants a different review schedule than a timely or news-style piece, though the specific cadence per content type isn't something this view enforces or recommends automatically.

<RelatedPages
  pages="[
{ title: &#x22;Topics&#x22;, description: &#x22;Manage individual content topics across all your sprints.&#x22;, href: &#x22;/content-planning/topics&#x22; },
{ title: &#x22;Sprint Overview&#x22;, description: &#x22;Deep dive into the sprint board and topic management.&#x22;, href: &#x22;/content-planning/sprints#sprint-overview&#x22; },
]"
/>
