Proxy infrastructure×9.2 traffic
From 2,400 to 22,000 visits in two years, on links
IndustryProxy infrastructure
MarketsUS and EU
StartedMay 2024
Duration24 months
×9.2organic traffic
1,400referring domains
486AI mentions
One-off engagement · 3 weeks
Technical SEO audit
We find what stops search from seeing your product and put a number on what it costs. Over 200 checkpoints, each checked by hand rather than exported from a crawler; every finding comes with a priority, a revenue estimate and a ticket your developers can pull into their tracker, plus a walkthrough call with them. We find and document – implementation by your developers is not in the price.
We reply within half an hour. Any longer and we're at lunch.
How much of this sounds familiar?tick what you recognise
Estimated traffic blocked0%
Tick what you recognise – the estimate updates as you go.
A rough estimate from our audits, not a measurement. The exact figure comes after the logs.
Scope
What the audit covers
Access and crawl
- Crawlability and crawl budget
- robots.txt and meta robots directives
- HTTP status codes and redirect chains
- XML sitemap: coverage and errors
Indexing
- Indexation and index bloat
- Canonicalisation
- Duplication across templates and parameters
- JavaScript rendering and SPA routes
Structure
- Site architecture and click depth
- Internal linking and orphan pages
- International SEO: hreflang and locale conflicts
- Structured data and rich result eligibility
Performance
- Core Web Vitals on real pages, not on the home page alone
- Mobile rendering
- Server logs for the last 30 days
- Over 200 checkpoints in total, run by hand
200+growth points checked
3 weeksstart to walkthrough
$500fixed price
100%of findings costed
A sample report
Findings from a typical audit
Findings from a typical auditSaaS, 180k pages
Issue
Pages
Severity
Blocked in robots.txt by mistake
12,400
critical
Content renders only in JS
31,800
critical
Duplicate titles across catalogue
3,100
high
Pages with no internal links
890
high
LCP above four seconds
4,200
high
Broken canonicals
640
medium
A real project, numbers rounded. We put the loss at $34,000 of quarterly revenue.
Why bother
An audit without priorities is a list nobody implements
What costs money comes first
Every finding is scored: how much traffic it blocks and what that means in revenue. Developers work down the list by impact, not alphabetically.
Written for developers
Not “fix your canonicals” but the file, the line, the expected result and how to verify it. Tickets go into your tracker as-is.
We find it, you fix it
An audit is a diagnosis, not a repair. We hand over the list, the priorities and ready-made tickets; your developer makes the changes. If you have no team we implement ourselves, at $40 an hour as a separate line rather than inside the audit price. A month after delivery we re-check what shipped, free.
Scope
What we check and what you get
What we check
Around fifteen areas, weighted towards indexation.
- Over 200 growth pointsby hand
- Indexation and crawl budget–
- JS rendering and SPA routes–
- Duplicates, canonicals, pagination–
- Core Web Vitals and speed–
- Internal linking–
- 30 days of server logs–
- Mobile and responsive–
- Schema and snippets–
What you get
All yours, even if you carry on alone.
- Prioritised reportseverity ranked
- Tickets in your trackerone per finding
- Revenue loss estimateper group
- Call with your developersincluded
- Re-checkone month later
- Implementation by our team$40 / h, separate
- Implementation by your teamcovered by the tickets
$500 for sites up to 500,000 pages. The price covers diagnosis and ticket writing only. If you want us to fix the issues, that is separate work at $40 an hour, quoted after the audit.
How it runs
Three weeks from access to tickets
Week 1Data collection
Crawl and logs
Full site crawl, log export, access to Search Console and analytics. We look at how the crawler actually moves through your site.
What we need
Access, plus half an hour on a call about the project's quirks.
Week 2Analysis
Prioritisation
We classify what we found, size each problem in pages and traffic, then convert it to revenue using your conversion rate and deal value.
What we need
Your conversion and deal-size numbers, if you're willing to share.
Week 3Delivery
Tickets, not a PDF
Report, tickets in your tracker, walkthrough with your engineering team. We answer questions until they run out.
What you get
A list sorted by money, and a clear idea of what to do on Monday.
FAQ
What people ask about audits
That's our home ground. We look at what the crawler sees after rendering, not what the server returns: we diff raw HTML against rendered HTML, check routes that only exist client-side, and test how lazy loading behaves. On half of our SPA audits the biggest finding sits right there.
A crawler gives you a list of errors. An audit gives you the order to fix them in and what each one costs. Screaming Frog won't tell you which finding is worth $30,000 a quarter and which you can safely ignore forever. We use a crawler too, but it's an instrument, not the deliverable.
Yes, and most clients do. Implementation usually goes to your own developers – the report is written for them. If you don't have any, we quote implementation separately.
Then you have a healthy site and we'll say so. It happens roughly one time in ten. The report is shorter and the conversation shifts to where growth actually is – but the price stays, because the work was done.
Some findings will, within six to twelve months. That's why the report flags what needs regular checking and includes a checklist for your team. A repeat audit makes sense after a major release or a migration, not on a schedule.
A typical audit is three hundred remarks sorted by error type. A developer opens it, sees three hundred equally weighted tasks and starts none of them. We sort findings by what each one costs you in traffic, so the top of the list is three items, not three hundred.
Alexei Rozenplenter · Founder and CEO · About the author · LinkedIn
Case studies
What this did for tech companies' revenue
Read the case
ITAM / ITSM×4.4 traffic
From 1,500 to 6,600 visits a month in the US market
IndustryITAM / ITSM
MarketUnited States
StartedJanuary 2024
Duration24 months
×4.4organic traffic
71%non-branded
31%of AI answers
Edtech40,800 visits
Online exam platform: three locales that were blocking each other
IndustryEdtech
MarketsGlobal, IT, TR
StartedJune 2023
Duration13 months
40,800visits a month
3locales
×2.3clicks QoQ
Software development1,083 in the top 30
Developer directory: from nothing to 1,083 queries in the top 30
IndustryDeveloper directory
MarketUnited States
StartedNovember 2022
Duration12 months
1,083in the top 30
218in the top 10
−5,471left beyond-200
Figures are taken from the clients' own analytics for the periods stated.
How we do it
What sits behind two hundred checks
What actually gets checked
Two hundred growth points is a working checklist accumulated across projects, not a marketing number. It splits into six groups: accessibility and indexation, crawl budget and log behaviour, rendering and client-side routing, structure and internal linking, markup and snippets, speed and Core Web Vitals. Each holds twenty to fifty checks. Some are automated; many are not, because a crawler cannot tell a deliberate decision from an accident.
Rendering is the clearest example. A crawler sees assembled HTML, while Googlebot queues the page for rendering and returns to it later. The gap between raw and rendered output is where entire catalogues disappear, and you only see it by diffing the two versions rather than reading one tool's report.
Why findings are ordered by money
A typical audit produces three hundred remarks sorted by error type. Nobody can work from that: a developer sees three hundred equally weighted tasks and starts none of them. We estimate how many pages each finding touches and how much traffic sits behind those pages, then sort by that. The top of the list is usually three to five items that account for most of the available gain.
The estimate is approximate and we say so. Precision is not the point here; the point is knowing whether to fix a forty-thousand-page catalogue that fell out of the index before a broken schema on ten pages.
Where our scope ends
An audit is a diagnosis. We find the problems, document them and write tickets a developer can pull straight into a tracker: what is broken, where, how to verify it, what counts as fixed. Your team implements. If you have no team we implement, but as separate work at a separate price. It is not inside the audit fee, and we would rather say that before the contract than in an invoice.
A month after delivery we re-check what shipped and what broke on the way, free. Something almost always breaks: a canonical fix on one template catches a neighbouring one, a redirect lands on the wrong URL. That is a normal part of the process, not a complaint about your engineers.
SK
Alex will walk you through the numbers
Head of Inbound Sales. He'll ask about your deal size and margin, then tell you whether this service is worth it – including when it isn't.
Request a forecast
or call +375 33 331-90-76
Order an audit of your site
We'll size the site, confirm the schedule and start. Fixed price, no surprises along the way.