Custom growth project
Handle the technical work that does not fit inside a monthly backlog.
Scope major migrations, rebuilds, indexation problems and technical remediation as defined projects with clear boundaries and approval.
Typical timeline: 4–8 weeks · fixed price agreed after scoping
- 01Technical diagnostic
- 02Migration planning
- 03Crawl/indexation remediation
- 04Rendering analysis
- 05Architecture changes
- 06QA and post-launch verification
When to use it
Scope this separately when the opportunity is concentrated enough to deserve a project.
Growth Services sit beside managed search work rather than inside every retainer. The goal is to make scope boundaries clearer, not to create surprise add-ons.
A migration or rebuild creates concentrated technical risk.
The remediation backlog is too large for normal monthly capacity.
Rendering, crawl or indexation issues require engineering coordination.
Project model
Evidence → scope → build → verify.
Define the constraint
Start from the search, funnel or operational evidence that justifies the project.
Lock the scope
Agree the deliverables, required inputs, acceptance criteria and limits on included work.
Implement
Build the agreed work without silently expanding into unrelated tasks.
Verify
QA the output and, where measurable, reconnect it to the visibility or conversion signal that started the project.
Deliverables
What you receive.
Technical diagnostic
A crawl-based audit of indexation, rendering, internal linking, redirects and performance issues, ranked by search impact and engineering effort.
Remediation specification
Ticket-ready requirements for each fix, written for your developers, with acceptance criteria, examples and the affected URLs.
Migration plan
For moves and rebuilds, a URL mapping, redirect plan, launch checklist and rollback triggers, agreed with your engineering team in advance.
Rendering and crawl analysis
A review of how search engines and AI crawlers fetch and render your key templates, with fixes for content they cannot see.
Implementation support
Working sessions with your engineers during the build, plus review of staging changes before they reach production.
Post-launch verification report
Checks of redirects, indexation, crawl errors and priority rankings after changes ship, with any open issues listed for follow-up.
Timeline
Typically 4–8 weeks.
The exact schedule is set in your proposal. It depends on scope, approvals and how quickly we receive access and inputs.
What we need from you
- Search Console, analytics and server log access where available
- A technical lead or developer who can implement and discuss changes
- Staging environment access for testing before release
- Your release calendar, including any fixed launch date for a migration
- Weeks 1–2
Diagnostic
We crawl the site, review server logs and Search Console data, and identify the technical issues that matter most for search.
- Weeks 3–4
Specification and planning
We write remediation tickets or the migration plan, review them with your engineering team, and agree the release sequence.
- Weeks 5–6
Implementation support
We answer engineering questions, review staging environments, and check each change against its acceptance criteria before release.
- Weeks 7–8
Verification
We verify changes in production, monitor crawl and indexation, and document anything still open for your team or managed plan.
Questions
Common questions about this project.
How do you price technical SEO projects?
We quote a fixed price after a short scoping call and a first look at the site. The quote reflects site size, the number of templates involved and how much implementation support your engineers need. Anything found later that falls outside that scope needs your written approval first.
How long does a site migration take?
It depends on your launch date and how much is changing. We need to be involved before the new site is built, so URL mapping and redirects are planned rather than rushed. Monitoring continues for a few weeks after go-live. We set the timeline around your release plan, not a fixed template.
Do you make the code changes yourselves?
Usually your developers implement the changes, working from our specifications and review. Where we have suitable access and you prefer it, we can make some changes directly, such as redirects, metadata or template edits in common CMS platforms. Either way, every change is documented, and the work and documentation are yours.
Commercial terms
A scoped project—not open-ended hourly billing.
Your proposal sets out the deliverables, fixed project price and agreed labor limit. Work outside that scope requires your approval before it starts.