You update a service page on Tuesday. Someone changes the navigation on Thursday. A week later, search traffic moves—and nobody remembers exactly what went live.
An SEO change log template gives a small business a shared record of those changes. It will not prove that an edit caused a ranking improvement. It can make investigations much less dependent on memory, especially when a business owner, writer and developer all work on the same website.
Record what changed, not just the task name
“SEO completed” tells the next person almost nothing. A useful entry identifies the affected pages, the previous state, the new state and the actual deployment date. Keep planned work separate from published work.
For example, “Replaced the service-page title with a clearer description of the service” is more useful when the entry also preserves the old and new wording. If a navigation update affects the whole site, list the template or section involved rather than pretending it was a single-page edit.
Use the final public URL, not an admin preview link. Avoid storing passwords, access tokens or customer information in a shared log.
A copyable SEO change log template
Start with these fields in a spreadsheet or project document. One row per distinct change is usually enough; connect related rows with a release reference when they must ship together.
Change reference: ______
Page URL or template: ______
Reason for the change: ______
Previous state: ______
New state: ______
Owner: ______
Planned date: ______
Actual live date and time zone: ______
Deployment checks and evidence: ______
Review question and data filters: ______
Other changes or events: ______
Review findings: ______
Follow-up decision: ______
Add a link to a recoverable earlier version where appropriate. A screenshot can preserve visible content, but it is not a backup of a database, redirect rule or site configuration.
Write a specific reason before making the edit
The reason should describe a problem you can observe. “Visitors cannot tell which area this service covers” is more useful than “boost SEO.” Your proposed edit can then address that gap without adding unsupported service claims.
Separate the implementation check from the hoped-for outcome. A clearer title can be verified on the live page. Improved search performance requires later observation and may not occur.
If the change comes from an audit, link to the relevant finding. Our small-business technical SEO audit checklist provides a starting point for organising technical checks; the change log records what you actually decide to implement.
Keep deployment checks distinct from performance reviews
Immediately after publication, confirm that the intended content appears at the correct URL. Test relevant navigation and contact links, and check that the mobile layout still works. For changes to indexing settings, redirects or canonical URLs, record the specific verification performed by the person responsible.
Do not tick a generic “tested” box if only one part was checked. “Title visible on the live page; mobile navigation checked; contact form not tested” is an honest and useful record.
A planned review date is a reminder to inspect the evidence, not a deadline by which Google must reward the change. In its guidance on investigating search traffic changes, Google explains that effects can take different amounts of time and are not guaranteed. It also recommends examining comparable data and considering factors beyond a site's own edits.
A fictional change-log example
Imagine a local repair business with a service page that never states its coverage area. The business confirms the places it serves, and the editor adds an accurate coverage paragraph.
- Reason: the page omitted information customers need before enquiring.
- Actual change: one coverage paragraph added; no change to the page URL.
- Deployment check: paragraph visible on desktop and mobile; contact link opens the intended page.
- Review question: what happened to search visibility for this page and relevant queries after publication?
- Other events: record any simultaneous site edits or changes in the business's availability.
This is an illustrative record, not a case study or a claim of increased leads. Even if impressions rise afterward, the timing alone does not establish that the paragraph caused the rise.
Compare like with like
Record the date ranges and filters used for a review. Changing from one page to the whole site, or from one device category to all devices, can make a comparison misleading. Keep the question narrow enough that another person could repeat the check.
Look beyond a single number. A page may appear for a different mix of queries, and seasonal demand can change. A quiet period with very few impressions may not support a useful conclusion. It is reasonable to write “not enough evidence yet” rather than forcing a success story.
For a broader reporting structure, see our SEO reporting guide for local service businesses. Keep the log as the record of changes and use the report to explain the available results.
Make follow-up decisions explicit
Close an entry with a short decision: keep the change, investigate further, correct a deployment error or consider a documented revision. Include who owns the next step. Avoid repeatedly changing a working page because its position fluctuates on one day.
If several edits launched together, acknowledge that limitation. You may be able to assess the release as a whole without knowing which individual edit contributed to a result.
A useful SEO change log is deliberately modest: accurate dates, clear descriptions and evidence that someone else can understand. That discipline is more valuable than a long spreadsheet full of unverified wins.