Skip to content

One Time Services · Search eligibility

Find the technical problem worth your engineers' time.

A senior technical review of how search engines discover, render, index and evaluate the site, translated into evidence-backed tickets your developers can ship.

Price
$1,000
Timeline
15 business days
Scope
One primary domain
Technical SEOIllustrative
01Crawl02Ticket03Validate
Screaming Frog/products/trail-pack

Fix the product canonical

SEO-042 · Template change · Acceptance criteria

Jira
Rendered tagRecrawlURL inspection
Illustrative sample · Not client data or a performance claim
Engagement plan15 business days
  1. 01
    Days 01-02
    Access + intent
    Access register + audit hypothesis
  2. 02
    Days 03-07
    Crawl + render
    Combined technical dataset
  3. 03
    Days 08-11
    Validate impact
    Validated issue ledger
  4. 04
    Days 12-15
    Specify + hand off
    Executive summary + 90-day plan
Handoff · 8 working files
Executive technical diagnosisInventory of pages that should be indexedTemplate and rendering map+5 more
As cited on
Search Engine Land
Moz
Backlinko
Yoast
Coursera

Logos show where our team has worked or been cited.

When to buy it

Know when this is the narrowest useful engagement.

One-time work is valuable when it resolves a named decision and leaves an implementation-ready handoff.

01

Use it when

Engineering wants to know which SEO defects are really holding growth back, or a migration or replatform needs a sign-off check you can defend.

02

Do not use it when

The primary problem is unclear demand, weak content, absent external authority or no internal capacity to implement.

03

Decision it resolves

What should engineering ship first, how will it be validated, and which tempting fixes should be deferred?

Technical checks

Six technical areas we verify before we prioritise the fixes.

Every significant finding includes the evidence, the affected pages, the business impact, a recommended fix, a named owner and a release check.

01 · TECHNICAL CHECK

Crawl + indexation

Robots rules, status codes, canonicals, sitemap accuracy, parameter traps, duplicate clusters, crawl frontier and which pages should be indexed.

02 · TECHNICAL CHECK

Rendering + parity

Server output, hydration, JavaScript dependencies, mobile parity, content visibility and discoverability across critical templates.

03 · TECHNICAL CHECK

Architecture + links

Taxonomy, click depth, orphaned pages, pagination, navigation logic and how internal links spread authority.

04 · TECHNICAL CHECK

Performance

Core Web Vitals by template, third-party cost, render blockers, performance budgets and regression checks at release.

05 · TECHNICAL CHECK

Structured data

Rich-result eligibility, match with visible content, consistent entities, validation, and who maintains each supported schema type.

06 · TECHNICAL CHECK

Migration + release

Redirect mapping, canonical and metadata retention, launch batches, rollback thresholds, monitoring and post-release checks.

What the work looks like

See the technical evidence before the engineering roadmap.

Technical search control roomEVIDENCE RECONCILED
Primary view
Indexable URLs62,418 · 7 templates
Eligible54.9K
Indexed39.8K
Valuable25.6K
Priority decisions
01Canonical conflict on collectionsP0
02Rendered parity gapP1
03Internal-link depthP1
Validated constraints
14
Release tickets
26
Decision horizon
90 days

How the engagement runs

Four stages, each with a written output.

  1. 01Days 01-02

    Access + intent

    Agree the business-critical templates, which pages should be indexed, release history, analytics scope and engineering constraints.

    What you receive
    Access register + audit hypothesis
  2. 02Days 03-07

    Crawl + render

    Combine crawl, rendered-page, Search Console, analytics and server data for each URL and template group.

    What you receive
    Combined technical dataset
  3. 03Days 08-11

    Validate impact

    Reproduce significant defects, count the pages affected, and separate root causes from crawler noise.

    What you receive
    Validated issue ledger
  4. 04Days 12-15

    Specify + hand off

    Convert priorities into implementation tickets with acceptance criteria, owners, release checks and rollback triggers.

    What you receive
    Executive summary + 90-day plan

What you receive

Not a deck to admire. A handoff to use.

01
Executive technical diagnosis
02
Inventory of pages that should be indexed
03
Template and rendering map
04
Validated issue ledger
05
Prioritised engineering tickets
06
Structured-data specification
07
Release QA checklist
08
90-day technical roadmap

Access and boundaries

Clarity before the clock starts.

We need from your team

Evidence, access and an owner.

  • Search Console owner access
  • Analytics read access
  • CMS or template walkthrough
  • Recent release and migration history
  • Named owner for handoff
Not included

The limits, in writing.

  • Writing production code
  • Executing the migration
  • Unlimited post-audit QA
  • Guaranteed ranking recovery
  • Content strategy beyond what the technical fixes need

What the fixed price covers

A published price for one decision.

Technical SEO Audit
$1,000 · 15 business days

One primary domain. GST additional. The published price assumes the scope and dependencies described on this page.

Get started

There is no checkout. Send your company and contact details, and we check fit, confirm access and limits, and reply with a detailed start plan.

Questions before you buy

The useful caveats, up front.

No. Tool output is only an input. We reproduce each significant finding, check it against search and business data, group the pages it affects and turn it into a ticket with acceptance criteria.

Technical SEO Audit

Technical SEO Audit, get the answer and keep the working files.

Share the company, contact details and selected service. The enquiry form is pre-filled; no payment is requested.