Search signal / violet and carbon

A technical SEO audit proposal for a site with indexing and speed problems. It covers the site’s numbers today, the five audit areas, the checks and tools, a five-week timeline, what you receive, a similar client’s results and three one-time options.

Technical SEO Audit Proposal

<h1 style="font-family:Space Grotesk;font-weight:700;line-height:1;text-align:left;color:#F8F5FF"><span style="font-size:clamp(42px,7.2cqw,76px)">Technical<br>SEO audit</span></h1>

<p style="font-family:Inter;color:#F8F5FF;text-align:left;font-size:18px;line-height:1.5">Proposal for {{CLIENT_COMPANY}}<br>by {{SELLER_COMPANY}}</p>

Overview

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.6cqw,52px)">Your technical SEO audit</span></h2>

<p>Hello {{CLIENT_NAME}},</p><p>Organic search brings {{CLIENT_COMPANY}} its most qualified visitors, but new pages take weeks to be indexed and several templates are slow on mobile. Before your developers spend more time on fixes, you need to know which problems cost you traffic and in what order to fix them.</p><p>This proposal sets out what the audit checks, how we run it, what you receive, the five-week schedule and the fixed price.</p><p><strong>{{SELLER_NAME}}</strong>, {{SELLER_COMPANY}}</p>

Introduction

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.6cqw,52px)">Where your site is today</span></h2><p>What we saw in a first look at your site and Search Console. The audit confirms each point and finds the rest.</p>

<p>About a third of your key pages are crawled but not indexed, so new content takes weeks to appear in search.</p>

New pages are slow to be indexed

<p>Old URLs pass through two or three redirects, which wastes crawl budget and dilutes links.</p>

Redirect chains from the last migration

<p>Product and blog templates fail Largest Contentful Paint on mobile, the measure Google uses for page experience.</p>

Slow mobile templates

<p>Filter and tracking parameters create thousands of near-identical URLs without clear canonical tags.</p>

Duplicate URLs from filters

Where Googlebot spends its visits

Your site today

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.6cqw,52px)">What the audit covers</span></h2><p>Five areas, each checked against your own crawl, log and Search Console data.</p>

<p>How search engines find, crawl and index your pages.</p><ul><li>Status codes, redirects and redirect chains</li><li>robots.txt, XML sitemaps and noindex rules</li><li>Pages crawled but not indexed, and why</li><li>Crawl budget spent on low-value URLs</li></ul>

Crawl and indexing

<p>How your pages link together and pass authority.</p><ul><li>Click depth of key pages</li><li>Orphan pages with no internal links</li><li>Internal link anchor text</li><li>Canonical tags and duplicate content</li></ul>

Site architecture

<p>Field data from real visitors, not only lab scores.</p><ul><li>LCP, INP and CLS per template, mobile and desktop</li><li>Images, scripts and fonts that slow pages down</li><li>Caching, compression and CDN set-up</li></ul>

Page speed

<p>What Google sees once your JavaScript runs.</p><ul><li>Content and links that only appear after rendering</li><li>Lazy-loaded content that is never indexed</li><li>Differences between mobile and desktop versions</li></ul>

Rendering

<p>The markup that earns rich results.</p><ul><li>Schema.org markup by page type, with validation errors</li><li>Titles, meta descriptions and headings at scale</li><li>Hreflang, if you serve more than one country or language</li></ul>

Structured data

What the audit covers

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.6cqw,52px)">How we run the audit</span></h2><p>Every finding comes with the data behind it, so your developers can reproduce it.</p>

How we run the audit

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.6cqw,52px)">Five weeks from access to readout</span></h2><p>The schedule starts when we have access to Search Console, analytics and your server logs.</p>

<p>Connect to your data, run the full crawl and collect 30 days of logs.</p>

Access and crawl

<p>Work through the five areas and confirm every issue with page examples.</p>

Analysis

<p>Rank issues by traffic impact and effort, and write briefs for the top ten.</p>

Findings and priorities

<p>A 60-minute session with your developers and marketing team to agree the fix order.</p>

Readout

<p>Recrawl the fixed areas and confirm each issue is resolved in Search Console.</p>

Retest

Timeline

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.6cqw,52px)">What you receive</span></h2><p>Built to be handed to your developers, not filed away.</p>

What you receive

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.6cqw,52px)">Results for a similar client</span></h2>

Results for a similar client

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.6cqw,52px)">Options and fees</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">One domain of up to 50,000 URLs, including the retest. We recommend Audit and fix support.</p>

The audit, the issue register and fix briefs for your developers.

Audit

Plus ten hours of help while your developers make the fixes.

Audit and fix support

Plus a short re-audit every quarter for a year.

Audit, fix support and checks

<p>Fees are in USD and exclude tax. Further implementation support is $150 an hour. This proposal is valid until {{VALID_UNTIL}}.</p>

Options and fees

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.6cqw,52px)">Common questions</span></h2>

<p>The audit finds and ranks the issues and writes the fixes up as briefs. Your developers make the changes, or we can help at the hourly rate above.</p>

Will you fix the issues for us?

<p>No. We need read access to Search Console, analytics and your server logs. We do not change anything on your live site.</p>

Do you need access to our CMS or code?

<p>Tools list every warning. We confirm each issue against your own data, remove the noise and rank what is left by the traffic it affects.</p>

How is this different from an automated SEO tool?

<p>We crawl a representative sample of each template and quote any full crawl beyond 50,000 URLs before we start.</p>

What if our site has more than 50,000 URLs?

<p>Rankings depend on more than technical health, so we do not promise positions. We measure what the fixes control: indexed pages, crawl errors and Core Web Vitals.</p>

Will our rankings improve?

<p>You do. The issue register, fix briefs and crawl data are yours to keep, and your site data stays confidential. More sites or templates are quoted in writing before we start.</p>

Who owns the findings?

Questions

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.6cqw,52px)">Next steps</span></h2>

<ol><li>Accept this proposal and we send the first invoice.</li><li>Share access to Search Console, analytics and server logs within three working days.</li><li>We start the crawl in week 1 and share first findings at the end of week 2.</li></ol>

<p><strong>{{SELLER_NAME}}</strong> · {{SELLER_COMPANY}}<br>{{SELLER_EMAIL}}</p>

Technical SEO Audit Proposal - Preview