Skip to content

Pricing

Pricing scoped to the work, not the hour.

Three engagement models cover most technical SEO and prerendering work: a fixed-scope audit, a project-based engineering engagement, and an ongoing retainer for teams shipping continuously. Pricing is set on the scoping call based on site size and stack complexity. There are no hidden tiers and no hourly billing.

Book scoping callHow we work

Engagement tiers

Diagnose

Technical SEO Audit

A fixed-scope review of crawlability, rendering, indexation, structured data, and AI search readiness — delivered as engineering-ready findings, not a slide deck.

Fixed-scope audit

Pricing is set during the scoping call based on site size, stack complexity, and route inventory. Audits are quoted as a single fee, not hourly.

Best fit

Teams who know something is wrong with crawl, indexation, rendering, or AI visibility and need a prioritized fix list before committing engineering capacity.

Includes

  • Full route-family rendering and indexation review
  • JavaScript-SEO regression detection (App Router, SPA, hydration)
  • Crawler-facing HTML parity verification (curl-based)
  • Structured data and AI-extraction readiness check
  • Findings prioritized by impact × effort, with engineering tickets
  • 30-minute walkthrough call after delivery
Typical duration2 to 4 weeks
Scope an audit

Implement

Engineering Engagement

A scoped project to ship the fixes that matter — rendering changes, prerendering rollout, structured-data architecture, or migration recovery — alongside your engineering team.

Project-scoped

Engagements are quoted per project after the audit (or after a discovery call if no audit is needed). Fixed scope, fixed timeline; we do not bill hourly.

Best fit

Teams who already know the problem and need senior technical-SEO engineering capacity to ship the fix without derailing the rest of the roadmap.

Includes

  • Implementation plan with PR-ready specs
  • Pair-coding or PR-review across rendering, redirects, schema, sitemap
  • Rollout validation: first-response HTML, canonical parity, crawl checks
  • Post-deploy monitoring and incident response for 30 days
  • Handoff doc for ongoing internal ownership
Typical duration4 to 12 weeks
Discuss the scope

Defend

Ongoing Monitoring

A retainer that keeps technical SEO from regressing — release QA, route monitoring, incident response, and quarterly architecture reviews for engineering teams shipping continuously.

Monthly retainer

Retainer pricing scales with site size and release cadence. Includes hours bank, on-call response, and quarterly review cycles.

Best fit

Teams shipping weekly or daily where rendering and indexation regressions cost real revenue, and where one missed canonical drift becomes a recovery project.

Includes

  • Release-time rendering and SEO QA
  • Route-family monitoring with alerting
  • Incident response within agreed SLA
  • Quarterly architecture review and roadmap
  • Direct Slack channel with engineering ownership
Typical durationMonth to month
Discuss a retainer

Track record

Why teams trust the engagement scoping.

  • 25+

    Projects Covered

    Audits and sprint engagements across SaaS, editorial, fintech, and large content sites.

  • 450k+

    URL Scale

    Experience auditing both lean product sites and multi-language content estates at scale.

  • End to End

    Technical Scope

    Rendering, crawlability, CWV, schema, indexation, and AI visibility mapped into one plan.

Verticals served

  • SaaS

    Next.js, Webflow, React apps

  • Marketplaces

    Large URL inventories and template complexity

  • Publishers

    Multi-language content and crawl budget tuning

  • Fintech

    High-trust templates with strict performance requirements

GDPR-aligned data handlingMSA / DPA on requestReply within 1 business day

How pricing is set

Three inputs decide the fee.

Route inventory

How many distinct route templates the site renders. A 4-template SaaS marketing site is not the same scope as a 40-template marketplace.

Stack complexity

Framework, rendering model (SSG / SSR / ISR / SPA / mixed), CMS or headless layer, edge configuration, and existing prerendering setup.

Problem depth

Whether the site has a known acute symptom (indexation drop, AI Overviews silence) or a broader strategic review across visibility surfaces.

The scoping call is 30 minutes. Bring the domain, the stack, and the symptom — leave with a quoted scope or a clear reason it is not the right fit.

Book scoping call

FAQ

Pricing questions, answered.

The FAQ on this page is meant to make the content easier to evaluate in practical terms. Instead of leaving important points implied, the answers below clarify the questions visitors usually have when they are comparing fit, understanding scope, reviewing expectations, or trying to decide what the next step should be after reading the page.

On a specialist services site, FAQ sections do more than fill space. They reduce friction between learning and decision-making. They help readers translate a page from marketing language into clearer operational meaning, which is especially useful on pages dealing with technical SEO audits, process, case studies, deliverables, legal terms, and trust-related information.

Why is there no public price list?+

Technical SEO work scales with route inventory, stack complexity, release cadence, and the depth of existing problems. A fixed price list would either be wrong for most teams (too low for complex sites, too high for simple ones) or hide the real scope. The scoping call sizes the work honestly before any commitment.

Do you offer fixed-fee audits?+

Yes. The Technical SEO Audit tier is always quoted as a single fixed fee after the scoping call. The fee is based on route-family count and stack complexity, not on hours. There are no surprise overages.

What is the smallest engagement you take?+

A scoped technical SEO audit is the smallest engagement. Below that, a one-hour technical SEO consultation may be enough — book it as the standard 30-minute audit call and ask for an extended slot.

Do you bill hourly?+

No. All work is quoted per scope. Audits are a fixed fee. Engagements are quoted per project. Ongoing retainers are a monthly fee with a defined scope and hours bank. Hourly billing creates the wrong incentives.

How does pricing compare to a self-service tool like Prerender.io?+

A self-service prerendering tool is closer to infrastructure than to a service — you pay a per-page or per-render rate. Prerendering.com is an audit-and-engineering engagement: we diagnose why a JS site loses visibility and ship the fixes. Many teams use both: a SaaS prerendering layer plus an external audit.

Is there a discount for non-profits, OSS projects, or small teams?+

Sometimes, on a case-by-case basis. Mention the context on the scoping call. Open-source SEO infrastructure work and academic-adjacent projects are easier to fit; commercial discounts are rare.

What payment terms do you support?+

Audits and engagements are typically 50 percent on signature, 50 percent on delivery. Retainers bill monthly in advance. Bank transfer (US/EU) and credit card supported. Net-30 is available for established companies on request.