Governance: who can change what
On a large site, a single template change can affect thousands of pages. Governance means documenting SEO standards, deciding who owns each area, and requiring an SEO check for changes with search impact.
It doesn’t have to slow teams down. The aim is lightweight rules that catch the expensive mistakes, such as a noindex tag pushed to production or a navigation change that orphans a whole section.
Working inside development workflows
SEO advice only matters once it ships. I write recommendations as tickets with acceptance criteria that fit your sprint process, join refinement sessions where useful and review staging builds before release.
- SEO requirements for new templates and features
- Acceptance criteria written in developer language
- Staging review before major releases
- Automated checks for titles, canonicals, robots and status codes
Reporting that leadership reads
Executives, product managers and content teams need different views of SEO performance. I set up reporting that shows each group what matters to them, from revenue and pipeline for leadership to page-level metrics for content teams, and explains changes rather than just showing charts.