SEO Audit for Your Website and Online Store

I bill by the hour: EUR 70 net per hour, with a cap on hours set before the start. A diagnostic audit of one or two problems is usually 10-16 hours, and a full audit with a prioritized action plan 32-50 hours. The price includes the analysis, a report with recommendations, a meeting where we discuss it and the check after implementation.

• 77audit documents from 2020-2026 in the archive, prepared by me alone or with a teamAudit archive 2020-2026
• 938findings in 63 audits across 50 sitesCatalog of October 11, 2026
• 256issue types in the catalog, each with a priority rule and a way to check after implementationCatalog of October 11, 2026

When does an SEO audit make sense?

An audit makes sense when a mistake in SEO is expensive or nobody knows what to fix first. Most often it is one of these situations:

• a migration, a change of store system or a site rebuild;
• a drop in traffic whose cause nobody can name;
• a store with thousands of URLs, filters and categories where indexing has gotten out of control;
• a site that builds no visibility despite its content and links;
• a planned link building campaign, before links go to pages that Google ignores.

You do not need an audit if you have a small business site and the time to go through it yourself. Search Console and the free version of Screaming Frog are enough to find the most common problems. I described how to do it in the post on how to do an SEO audit step by step.

How much does an SEO audit cost?

The price depends on the number of hours, and the number of hours on what has to be checked. A small site of up to 500 URLs is closer to the lower end, and a store with thousands of URLs and filters closer to the upper.

The implementation itself is done by your team, or I quote it separately. Implementation follows the audit exactly. If a cheaper variant comes up when I quote the implementation, the choice is yours and I record that explicitly in the document.

Without access to Search Console, the CDN panel and the hosting, I cannot fully check the technical part, and I say so before quoting. I then point out what I cannot verify without that access and narrow the scope accordingly.

What do you get after the audit?

The report starts with a table of all the issues with priority and effort. I describe effort in four categories: a few hours, a day or two, a week, or a whole project. A team with fewer resources gets a minimal variant next to the full one, with a description of what it loses by choosing the shorter route.

Each issue has four parts: the problem, why it hurts, a step-by-step fix and a way to check that the fix worked. Each comes with evidence: a code fragment, server HTML next to the version after JavaScript runs, a chart from Search Console or a speed measurement naming the element that slows the page. An issue without evidence stays in the report as “to be checked”, not as a recommendation.

This is what a single issue looks like in short:

• Problem: menu links lead to URLs without a trailing slash, which redirect to the version with a slash.
• Why it hurts: the menu is on every page, so every click and every bot fetch goes through an extra redirect.
• Fix: in the menu template, replace the URLs with the target ones, with a code fragment before and after the change.
• Check: after implementation a crawl shows no links to redirecting URLs in the template.

Before the report reaches you, someone who did not write it checks it. I do two rounds of checking: the first on the whole document, the second only on what changed after the first. The check recalculates the numbers from scratch and looks for claims that cannot be defended with evidence.

After implementation I check every issue on the live site and mark it as implemented correctly, partly or not implemented. Without this step an audit ends with a document, not with a change on the site.

What does a full audit cover?

A full audit answers four questions, and each needs different data.

In my archive the most frequently reported areas are redirects and response codes (50 of 63 audits), architecture and internal linking (49) and content on pages (47). Problems reported less often can cost more traffic: a missing page for an important keyword appeared in 15 of 63 audits, and a crawler will not report it on its own. That is why I set priorities based on traffic and demand data, not on the number of errors in a tool.

Every full audit also checks whether AI assistant bots get the page: robots.txt, the firewall, the CDN and HTML before JavaScript runs. The same firewall setting that blocks Googlebot can block them. I measure the brand's visibility in AI answers separately, on a set of customers' questions, and I described it in the post on brand visibility in AI.

How does the process work?

1. You describe the situation: what is happening with traffic, what you plan to change on the site and who will implement the recommendations.
2. I reply with a scope, a cap on hours and a date.
3. You give me access: Search Console and analytics, and for the technical part the CDN panel and the hosting.
4. I do the audit and two rounds of cross-checking.
5. We discuss the report in a meeting.
6. After implementation I check every issue on the live site.

The timeline depends mainly on how quickly I get access and on the size of the site. The first question before the start is always the same: is the site losing traffic, or not building it, because the answer decides the whole scope.

Who does the audit?

I do audits alone or with the VerticalSEO team, where I am the CEO, and I have worked in SEO since 2014. As Tech Lead SEO I advise Warner Bros. Discovery Polska (TVN) on indexing, internal linking and crawling of publishing sites. Earlier I was Head of SEO at LOANDO Group, where I ran SEO in 8 markets, and an SEO consultant for Betfan and STS.

Since 2021 I have judged entries in industry awards, 31 editions across 15 programs, including the Global, European, UK and MENA Search Awards. I write more about my experience on the about me page.

Questions before you order an audit