Separate new inventory from improvement to existing inventory
Record which URLs were revised and compare them separately from newly published pages. Combining all content changes makes it difficult to understand whether maintenance or expansion helped.
A refresh changes an existing answer; a new post adds another destination. Reporting their combined growth can obscure whether either approach worked. Keep fixed cohorts and record the nature of each revision.
A worked example
A hypothetical library grows traffic after publishing 20 posts and updating five older guides. The total does not establish that the refresh program succeeded. Compare the five revised URLs with their own prior relevant observations, while separately reviewing new-page discovery.
How to apply it
- Record publication dates, revision dates and substantive changes.
- Track refreshed, new and unchanged cohorts without silently moving pages between them.
- Review query fit, useful next steps and external changes affecting the comparison.
What the result can establish
Before-and-after performance remains observational when other conditions change. Do not refresh dates without improving content or call every traffic increase a causal result of editing. The decision is which work is delivering useful answers and deserves further effort.
Reference: Google: Search Console performance report.
Supporting documentation
Google: Search Console performance reportGoogle: generative AI content guidance