The playbook
Content Refresh: Template and Field Guide
This content refresh template turns a broad task into a record another person can use. It captures URL, stale element, verified update, then connects that information to a decision. Copy the table into your working document or system and create a separate record for each item in scope.
Put the task in context
An old software guide may need updated screenshots, feature availability, pricing references, and broken links checked independently. Keep facts that remain accurate. Record a material revision date only when the content has actually been reviewed or changed, rather than automatically replacing the year.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| URL | Record the URL associated with this page or query record. Use a stable reference so later updates can be matched. |
| stale element | Record the stale element associated with this page or query record. Keep the value specific enough for another owner to interpret. |
| verified update | Record the verified update associated with this page or query record. Keep the value specific enough for another owner to interpret. |
| review date | Record the review date associated with this page or query record. Keep the value specific enough for another owner to interpret. |
| Decision field | Entry instructions |
|---|---|
| Observed problem | Describe the actual condition and where it was observed. |
| Recommended action | State the smallest action that resolves the documented problem. |
| Evidence | Link to the record, observation, or test supporting the action. |
| Owner and next review | Name the accountable person and when the decision should be revisited. |
How to complete the worksheet
Begin with URL. Use the same reference throughout the record so notes are not attached to the wrong item. Then review dates product references and broken resources. This establishes the information required before the worksheet becomes a request for action.
Next, compare current search questions with the page's coverage. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as changing the date without changing stale information, rather than a broad instruction to “improve performance.”
Finally, record material changes and recheck the finished page. Put refresh the actual content and accurately record the review in the action field only when it addresses the observed condition. If the problem is different, change the action. The template is a structure for judgment, not a reason to apply the same fix everywhere.
Illustrative completed decision
| Part | Illustrative entry |
|---|---|
| Problem | Changing the date without changing stale information |
| Action | Refresh the actual content and accurately record the review |
| First check | Review dates product references and broken resources |
| Follow-up check | Record material changes and recheck the finished page |
| Outcome to define | stale high-value pages remaining |
Adapt the fields without losing meaning
You can add fields required by your team, but each should change a decision or preserve necessary context. Keep factual observations separate from recommendations. If stale element changes, record the new value and its effective date instead of silently rewriting the context of an earlier decision.
Use the record in a handoff
Ask the receiving owner to explain the next action using only the worksheet. Missing context becomes visible quickly during that exercise. Repair the record before applying the structure to a larger batch. Keep stale high-value pages remaining connected to the item so the team can later assess whether the action was useful.
Use query and landing-page context when comparing results. A page serving a broad informational query has a different job from a page answering a purchase question. Review whether the next step remains useful to the person arriving.
Skip the manual steps. Let AgentixSEO run this for every client.
Start now