Provide context before access
Supply objectives, markets, brand constraints, architecture and contacts. Define content approval, deployment and incident responsibilities. Grant only necessary permissions. The company should retain control of accounts and production resources.
Maintain a change register
For each proposal, record the observed problem, solution, expected effect, risk, owner and acceptance check. Changes should be reviewable and reversible where possible. Do not combine a navigation repair with an unrequested migration. Before-and-after captures supplement delivered files.
Accept the actual work
Request affected URLs, HTTP responses, links and appropriate rendered-page measurements. An invoice is not a work report. Separate completed tasks from outcomes still being observed. Agree on termination and transfer without locking the company out of its accounts.
- Context
- Responsibilities
- Changes
- Acceptance
Worked example
A minimal brief identifies audience, reader decision, affected pages, observed problem, approver, deadline and acceptance check. “Improve SEO” does not explain when the task is complete.
Check before moving on
These checkboxes are not saved.
Sources & method
Sources reviewed on 1 October 2026. Worked calculations use explicitly hypothetical inputs.
Topic provenance: Travailler avec son agence SEO, quelques rappels de bon sens (2010-06). Search Engine Feng Shui. Byline retained in the publication feed: fhouste.
This guide is newly written in 2026. It does not reproduce the earlier text and is not attributed to its historical author.