Identify the change
Change ID · date in UTC · client/site · page URL · category · field or element
Agency resource · free CSV
SEO change log template.
Record the exact page-level change, before-and-after evidence, approval, validation, rollback plan, and outcome—without rebuilding a spreadsheet from scratch.
✓ No email gate✓ Excel and Sheets compatible✓ Blank and example files✓ Commercial use allowed
Why this structure
A useful log explains the decision—not just the edit.
“Changed the homepage” is not enough when traffic moves, a client asks what happened, or a release needs to be reversed. A reliable row preserves the exact affected URL and field, the old and approved values, the intended outcome, and the evidence required to validate it.
Use one row per meaningful page-level decision. Duplicate the workbook by client or keep one filtered master log, depending on who needs access.
From request to outcome in one row.
The blank download contains these 18 fields in a practical review order. The example file shows how three fictional SEO changes can be documented without exposing any real client.
Preserve the evidence
Before value · after value · reason or hypothesis
Record ownership
Requested by · implemented by · approval status · approved by
Control the release
Ticket or reference · validation check · rollback plan
Review the outcome
Outcome review date · outcome or notes
Preserve what future-you will need.
ChangeBefore → afterControlOutcome
CHG-001Example Store · category page title
Summer Footwear
→ Trail Shoes for Weekend HikesApprovedConfirm 200, canonical, and live titleReview scheduledRollback value preservedAll company names, URLs, tasks, and values in the example are fictional.
The limit of a manual log
It records approved work. It cannot catch what nobody logged.
Keep the spreadsheet for intent, ownership, experiments, and outcomes. Use public-page monitoring for the different question: did a protected field change later, including through an unlogged CMS edit, template, plugin, cache, or deployment?
Start monitoring free ↗RANKLATCH / UNLOGGED DRIFTCanonical target changed
APPROVED https://example.com/serviceLIVE https://example.com/↳ Confirm the change was approved. Otherwise restore the protected canonical target.
Continue the workflow
Verify, document, then protect.
The template is the manual decision record. These free RankLatch resources help with current-state verification and launch control.
Free SEO risk scannerCheck one live page before recording the approved state ↗Website launch SEO checklistWork through pre-launch, launch-day, and post-launch controls ↗Focused SEO checkersVerify canonicals, robots, redirects, schema, links, alt attributes, and more ↗Sample RankLatch workspaceSee the before-and-after evidence produced by monitoring ↗
Template questions
Use the log deliberately.
A change log is most useful when it preserves decisions the team could otherwise misremember—not when it becomes another unchecked box.
01What is an SEO change log?+
An SEO change log is a dated record of intentional changes to pages and technical signals. It preserves what changed, the previous and approved values, why the change was made, who approved it, how it was validated, and when the outcome should be reviewed.
02What format is the template?+
The downloads are standard UTF-8 CSV files. They open in Excel, Google Sheets, Apple Numbers, LibreOffice, and most database tools. The blank version contains the 18 agency-focused columns; the example includes three fictional rows.
03Do I need to provide an email address?+
No. Both files download directly, with no account, email gate, tracking parameter, or locked template platform.
04Which SEO changes should be logged?+
Log deliberate changes that could affect discovery, search snippets, targeting, or page behavior: titles, descriptions, canonicals, robots directives, redirects, headings, copy, schema, internal links, image alt decisions, templates, and important response changes.
05Should every small content edit receive a row?+
Use judgment. The log is most useful for changes with a testable reason, meaningful search or conversion impact, approval requirement, or rollback risk. Recording every typo can bury the decisions the team will need later.
06Does a spreadsheet detect unapproved website changes?+
No. A manual log records changes people remember to enter. It cannot detect an unlogged CMS edit, template release, plugin change, CDN rule, or accidental removal. RankLatch addresses that separate problem by comparing approved public-page snapshots.
07When should outcomes be reviewed?+
Set the review date when the team can reasonably evaluate the intended result using the relevant evidence. Search performance often needs more time than a response or indexability validation, so do not use one fixed review window for every change.
08Can I customize the columns?+
Yes. Rename, reorder, filter, or extend the CSV for your workflow. Keep the before value, after value, reason, approval, validation, and rollback fields if the log must support reliable incident review.