You rewrite a product guide, publish it, and discover that the old setup table disappeared. A customer’s bookmarked link now lands at the top of the page. The copy reads better, but two things that helped readers do their jobs are gone.
Before an SEO refresh, save a copy of the existing page and list the jobs its useful parts perform. Give each part a decision to keep, revise, replace or remove. After publishing, test those jobs on the public page.
What belongs in the inventory?
Start with the public URL and the date you captured it. Save the editable source and a screenshot of any interactive or visual element. If the editor and public page look different, record both so you can see what the template adds.
- Reading aids. Note the headings and fragment links, definitions, comparison tables, examples, downloadable files and images that answer a question.
- Paths to action. Record calls to action, form destinations and the next page a reader reaches. If you can safely test a form in a preview environment, check the confirmation step there.
- References. Save inbound links you know about, useful outbound sources, publication and revision dates, and the title and description shown in the page source.
Give every entry a reason. “Setup table helps developers confirm permissions before installation” is a better preservation instruction than “keep table.” If the same job can be served by a clearer table, the reason tells the editor what the replacement must retain.
How do you decide what to keep?
Use a fictional product guide as a rehearsal. ExampleCo has a setup table, a link to an old integration video and a demo form. The table correctly explains which roles can install an integration, the video shows a retired interface and the form still reaches the right team.
| Element | Decision | Check after publishing |
|---|---|---|
| Setup table | Keep the role distinctions and improve the labels. | A reader can still identify who may install an integration. |
| Outdated video | Replace it with current steps and record why. | Each step matches the current interface. |
| Demo form | Keep the working path and accessible labels. | The form and confirmation work in preview. |
A component can be valuable even when its page has few visits. The inventory helps you preserve what readers need while making deliberate cuts where evidence has aged or instructions overlap.
Keep the URL when the reader’s job stays the same
If the existing page still serves the same intent, a rewrite can usually stay at that address. Preserve useful section IDs where you can. For a genuine permanent move, map the old URL to its relevant replacement and check the redirect. Google treats permanent redirects as a signal about the preferred URL. Google’s redirect guidance
Keep the original publication date where it remains accurate. Record the actual revision date for meaningful changes. Google’s self-assessment guidance cautions against changing dates simply to make pages appear fresh. Google’s helpful content guidance
Use the inventory as a release checklist
Open the public page after deployment. Compare the saved title and description to what is served. Follow the preserved fragment links, check the mobile table and confirm that the source links and downloads still go where readers expect. Keep a short change record that says what you changed, why and when you’ll review the result.
If the refresh was prompted by an AI answer, keep that answer and its sources in the baseline. A corrected page and a later answer are separate observations. How to check whether a citation supports a claim
Start with the three elements you’d be most reluctant to lose. Write down the reader job each one serves before opening the editor.
