Discovery and baseline
Document the website, goals, access, current performance, stakeholders, and constraints. Unavailable data or access is visible from the start.
HomeHow It Works
How we work
We agree the scope, complete the work and review it with your team before moving to the next priorities.
Every step leaves something you can review.
The exact workflow is tailored to your organization and platform.
Scope and acceptance
Choose the first service, define outputs, identify reviewers, and write acceptance criteria for the work that will be handed back.
Production and QA
Specialists complete approved tasks, attach relevant evidence, test their work, and flag dependencies. An agreed reviewer checks the result.
Approval and release
The client or agency approves publishing when required. Tasks record what is live, what is still a recommendation, and the verification date.
Reporting and improvement
Review completed work, search performance and outstanding tasks, then agree the next priorities.
What an approved SEO ticket contains
A task should carry the page or profile, priority reason, source evidence, expected output, responsible role, and review test. Technical changes may need an implementation owner and re-crawl; content changes may need brand and subject-matter signoff.
How white-label responsibility is different
For agencies, client contact and final delivery generally remain with the agency. The SEO team should not change client commitments or contact the end client without permission. Direct businesses can choose a simpler approval loop while keeping their own business facts and sensitive decisions.
What we measure
Delivery measures include accepted work and blocked dependencies. Search measures include dated ranking positions, Search Console trends, landing-page performance, and conversions where measurement is reliable. A single movement should not be claimed as a guaranteed result of one task.
Acceptance checklist for one SEO task
A task is ready for review when the other person can independently confirm what changed and why.
| Buyer or scenario | Recommended path | Review standard |
|---|---|---|
| Request | Specified target URL, outcome, evidence and exclusions | Brief approved |
| Work in progress | Owner, blockers, source files and status visible | No silent scope change |
| Review | A reviewer checks source accuracy and technical behavior | Accepted, returned or blocked |
| Release and retest | Publisher is known and a validation record is attached | Change can be independently verified |
A “complete” status without evidence or responsible reviewer is not the same as accepted, published SEO work.
One work item, four roles
A concrete approval model that can be adapted to the client’s process.
| Role | Decision or responsibility | Visible handoff |
|---|---|---|
| Business / agency lead | Defines the objective and approves the commercial scope | Approved brief and market facts |
| SEO delivery owner | Prepares work and supporting evidence | Versioned draft, issue list or implementation ticket |
| QA reviewer | Checks accuracy, links, acceptance criteria and blockers | Accepted, returned or blocked decision with rationale |
| Authorized publisher | Implements approved changes and records validation | Published URL, change log and retest proof |
White-label work should not put the outsourcing team in direct contact with an agency’s end client unless that boundary is approved. A useful weekly check-in highlights completed work, blocked tasks, decisions needed and next priorities instead of only reporting hours.
Tell us what you need help with.
Send your website, target market and requirements. We’ll reply with the proposed work and pricing.