Refresh a page because its answer, evidence or customer task has changed. Preserve useful material and URLs, correct dated facts and repair resources. Change the modification date when the work is substantive, then check whether the revised page resolves the original problem.
Refresh the answer, not just the date. Review what changed, what the reader needs and whether the existing page still serves that task.
Use the four-pillar framework to keep content and technical questions distinct.
1. Reconfirm the reader task
Read the article and write its intended question in one sentence. Can the reader find a useful answer quickly?
Compare the scope with the actual current offer or procedure. Mark gaps without immediately expanding the page into every related subject.
2. Verify time-sensitive claims
List platform steps, capabilities, policies and named results. Check each against its approved or current primary source.
Google's people-first guidance warns against changing dates without substantive changes. Mark claims accurate, needs revision or unverified. Remove unsupported results.
3. Choose keep, revise or consolidate
Keep an accurate useful page. Revise a specific missing or outdated answer. Consider consolidation only when pages genuinely serve the same task.
For consolidation, plan content preservation, relevant URL handling and link updates with SEO review. Smaller traffic alone is not a deletion reason.

4. Edit from a focused brief
Name the changed question, supporting evidence and reviewer. Our content brief workflow provides the structure.
Check references, internal links, illustrations and captions alongside the edit. Rewrite metadata only when needed to describe the revised answer accurately.
5. Publish truthful dates and verify
Retain the original publication date. Record a real modification date for a substantial update. Google's sitemap guidance describes accurate last-modification values for significant changes.
Open the published page and test updated links. Generative search optimization benefits from verifiable explanations, but a refresh does not guarantee citations. Do not invent a future year's rules to make an evergreen procedure look newer.
Keep this refresh record
- Reader task and reason for the review.
- Claims checked and current source URLs.
- Keep, revise or consolidate decision.
- Changed sections and approved reviewer.
- Actual modification date and release check.
- Next review trigger, such as a platform or product change.
Preserve the evidence behind the edit. A future reviewer should understand what changed and why.
Example: an obsolete setup instruction
Here is a completed illustrative refresh record for advice that does not match this site’s chosen service-aligned structure. Calling a comprehensive guide a pillar page is valid in other models; the defect here is inconsistent instructions for this website:
| Field | Filled review |
|---|---|
| Reader task | Organise advice around the services the business sells |
| Before | “Write one pillar page and put every related topic underneath it.” |
| Problem | The instructions omit this site’s explicit service assignment, category overview and return links |
| After | “Assign each article to one service-aligned pillar. Link it directly to that pillar, its service and useful supporting articles; link back from the pillar and service.” |
| Basis | The site's actual service/category architecture and the approved editorial model—not a claim that Google requires one naming convention |
| Affected material | Article explanation, architecture diagram, worksheet labels and related briefs |
| Decision | Revise those items together; retain useful linking and measurement guidance |
| Verification | Open the category and its articles; check the diagram and downloaded worksheet use the same relationships |
The example changes an instruction, not merely the article date. Copy these fields into your content brief worksheet when assigning the correction.
Keep sections that still answer the reader’s question. Check downloadable copies and related articles for the same obsolete instruction. Use the category map from the content-hub workbook to find the other pages affected by the change. Record the substantive revision and its date; preserve the original publication date. After release, follow the full procedure from a clean starting point. A title change and a newer date do not repair a broken how-to.
Sources
- people-first guidancedevelopers.google.com
- sitemap guidancedevelopers.google.com
