The company should own the domain, hosting, analytics and final business claims. The fractional CMO can own the site's marketing priorities and acceptance criteria, while a named designer or developer ships changes. Define who approves copy, checks tracking, publishes and can roll back a faulty release.
Separate the message from the release
A marketing leader may decide that the homepage must explain a different buyer problem. That does not mean they should be the only person able to edit, deploy or restore the site. Name the owner for message, design, development, approval, analytics and QA. A conversion project can fail between those handoffs even when the recommendation is right.
Give the company durable control
Check that the founder or authorised employee controls the domain, hosting project, analytics property, forms and asset storage. Providers should use named access rather than personal ownership. Keep a complete deployable backup and a rollback plan. A recent First 10 site incident showed why a partial Netlify Drop upload can replace the full site: a website change must be checked against all routes, not only the page being edited.
Write acceptance criteria for each change
For a new page, specify the intended buyer, main question, proof, CTA and measurement event. Before publishing, check the live URL, mobile layout, links, form, canonical and critical images. The website audit guide can identify which pages deserve work first. Record the release and what signal will tell you whether it helped.
A bounded example
A hypothetical SaaS company asks an agency to update its pricing page. The CMO approves the message, product verifies plan details, the developer ships it and sales confirms that a common objection is answered. Analytics records visits and relevant enquiry actions. Without this chain, the agency can deliver a beautiful page while the buyer's decision remains unchanged.
A publishing responsibility checklist
Before the next website change, write one name against each step: buyer question and evidence, copy, factual approval, design, implementation, analytics, accessibility check, live verification and rollback. The same person can hold multiple steps, but the list exposes omissions. For a new lead page, decide what a qualified enquiry means before building the form; otherwise the team may celebrate conversions that sales cannot use.
Keep a release record with the changed URLs, expected effect and verification result. Open the live page after deploy and test the important path from the homepage or blog to the CTA, including the form. Check that existing pages and assets still work, not only the page the team edited. A marketing leader should be accountable for the business rationale and acceptance criteria; the site owner should retain the access and backup needed to restore a faulty release. This is a practical operating boundary, not a claim that one role must write every line of code.
Frequently asked questions
Should the fractional CMO edit the website personally?
They may, if that work is in scope and they have the skill and safe access. Otherwise they should direct and verify a named maker.
Who should own the website accounts?
The company should retain administrative control of domain, hosting, analytics and source assets, with role-based access for providers.
Is your site everyone's priority and nobody's responsibility?
Bring the current page backlog and access map. We can set a practical ownership path from buyer insight to a verified live change.
Talk through the problem ↗See how we could work together
