Skip to content

À La Carte SEO / Fix

Fix the problem without buying the whole department.

Choose a bounded audit, strategy project, technical review, tracking cleanup, or implementation scope when one problem deserves a clear answer and a defined endpoint.

Fit check

Know which kind of engagement you are choosing.

The same capability can belong in a website build, a focused project, or ongoing work. The difference is the decision, boundary, and operating rhythm.

A fit when

  • One decision or constraint is holding up the team.
  • An audit or roadmap is needed before committing to implementation.
  • Internal developers or writers can execute from clear priorities and requirements.
  • A launch, migration, content plan, analytics setup, or AI-search question needs specialist review.

Not the right fit when

  • Priorities change every month and require ongoing coordination.
  • Several connected workstreams need one accountable operating rhythm.
  • The request is only for guaranteed rankings, an unreviewed tool export, or an unsupported forecast.
  • The website itself needs to be replaced or substantially rebuilt.

What this engagement does

A useful scope has a job and an edge.

Focused work should answer a defined question, produce a usable output, and stop at an agreed boundary. It should not become an open-ended invoice.

01

Diagnose

SEO, technical, buying-journey, analytics, reputation, or AI-search audits tied to business and search implications—not a raw tool export.

02

Plan

Content, information architecture, internal linking, migration, measurement, or entity plans with priorities and owner assignments.

03

Implement

Agreed technical fixes, tracking setup, priority-page updates, schema, redirects, internal links, or launch QA where the stack and scope fit.

How it works

A defined path without pretending every scope is identical.

Focused projects are priced after diagnosis because complexity, access, research depth, implementation needs, and site condition change the responsible scope.

  1. 01

    Define the decision

    Identify the question, blocker, or deliverable the project must resolve.

  2. 02

    Confirm the evidence

    Establish the systems, access, data, stakeholders, and technical inputs the work requires.

  3. 03

    Set the boundary

    Document outputs, responsibilities, exclusions, schedule, and review points.

  4. 04

    Do the work

    Audit, research, plan, or implement the agreed scope.

  5. 05

    Hand off the next move

    Deliver findings, completed changes, or a roadmap. Any follow-on work is quoted separately.

Questions before scope

The boundary should be understandable before the proposal.

Can we buy only one SEO service?

Yes. A focused audit, strategy project, technical review, or implementation scope can stand alone when it produces a useful next step.

Is this just a tool report?

No. Tools can surface symptoms. The work is to interpret the evidence, connect it to the business problem, and prioritize what should happen next.

Can you implement the recommendations?

Yes, when implementation fits the stack and agreed scope. Otherwise, we can provide requirements, tickets, QA, or review for your team.

Can a focused project become ongoing support?

Yes, but it does not roll over automatically. If the roadmap requires recurring prioritization and delivery, that becomes a separately defined fractional engagement.

What if you find a larger problem?

We explain the issue, identify what the current scope can responsibly resolve, and price additional work separately.

Start with the real constraint

Bring the problem that needs a decision.

Send the site, what feels stuck, what has already been tried, and who will implement the result. We will recommend the smallest useful scope—or say when a focused project is not enough.

Review pricing logic, capacity, and commercial terms