• Audit

Technical audit of the site: a document in which each item has a number

A technical site audit is a walkthrough of the site as seen by a search bot and a list of what is found, where each item has a response code, milliseconds, or count. It is ordered when there is less traffic than it should be, and the contractors name various reasons. We follow the route from the root address to the map, compare the site map with the actual structure, read the markup on live pages and server logs. The output is a document divided into emergency, important and cosmetic, according to which your developer sets tasks without us.

See how it works
Price
after a free audit
Guarantee
30 days after project sign-off
What's out
a document with findings, each with a number or answer code
after a free audit
Price
30
Guarantee

days after project sign-off

a document with findings, each with a number or answer code
What's out
5-20
Term of paid audit

working days, depends on the number of page types

free measurement from the outside, 2-4 working days, no accesses
In front of him
the sitemap returns 200 with a body of zero bytes
The most frequent find
raw crawl data with date even if patched by another contractor
What is left with you?
we do not name future items and do not count traffic growth
What we don't do

Free technical measurement of the site

We go through the site from the outside, without access, and measure what is visible to each search bot. That's enough to find most things that crash — and enough to see if you need a full-scale audit at all.

What we measure

  • Route from the root addressRedirect chain, protocol, response codes, www and non-www behavior. Here we found both a 301 on unprotected HTTP with a valid certificate and a domain with no redirect at all.
  • Sitemap and robots.txtHow many records are in the map and how many unique addresses are given or mutually agreed upon? A blank card that gives 200 with zero body is a find we've seen more than once.
  • Speed ​​on three types of pagesMain, category, card separately. The difference between them says more than the average number on the site.
  • Structured dataWhat is actually declared, not what the module promises. We check on live pages and check with what is visible on them.
  • Headings and meta tagsThe presence of a first-level title, the length of the page title and description, uniqueness by page type.
  • Analytics and platform versionIs there a working counter and is the language and engine version supported. Unsupported version of PHP from 2021 is both security and speed.

What you get

  • A document with findings, each with a number or answer code, not an eye score.
  • Division into emergency, important and cosmetic.
  • Assessing whether a full-scale audit is needed and what it will add.
  • Conversation for 30 minutes on the document.

Timeline: 2-4 working days

Why is it free

Because this measurement is automated with us, and the result almost always changes the conversation. We regularly close the topic with a free document: it turns out that a person needs two days of developer work, instead of a monthly contract.

What's next

If there is a lot of emergency equipment, we take it to work separately and quickly. If a deeper analysis is needed, we agree on the scope of the paid audit.

Short form: your contact and site URL

  • Contract, act and 30-day warranty

    Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.

  • Sole proprietor & bank transfer

    The contractor is a registered sole proprietor. Payment by invoice with closing documents.

  • Rights & access — yours

    Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.

  • Client portal instead of email chains

    During the project you get access to a portal: contracts, invoices, acts and project status in one place.

  • European clients

    Among our work — projects for Norway, Bulgaria, Moldova and Spain.

  • Verifiable numbers

    Every case in the portfolio comes with a link to a live site and a technical measurement.

  • Audit first, then pricing

    There is no price list on the site intentionally: the scope of the same work differs multiples between clients.

  • We say "no" when unsure

    If the task isn't ours or the deadline is unrealistic — we tell you upfront.

What affects the price

Why two seemingly identical tasks are priced differently

  • How many types of pages are on the siteA business card site is two templates. Store — main, category, faceted issue, card, cart, articles, tags. Each type is checked separately, because the markup and metatags are set by a template: one failure is replicated to thousands of addresses at once.
  • Directory sizeGoing through ten thousand addresses is not ten thousand times. Tool limits, batches, reruns, and a single job with the loop not completed appear. In the catalog of tens of thousands of pages, this part is longer than the writing of the report.
  • Did they give access to Search Console and logsWithout Search Console, you can see the prerequisites for indexing, but not the fact of it. Without logs, bot behavior remains a guess. With accesses, the report becomes a list of specific edits; without them, some of the conclusions are honestly marked as unverified.
  • Language versions and subdomainsEach language branch is a separate traversal and separate hreflang and canonical check. A blog on a subdomain or on another engine is counted as a separate site: it has its own map, its own titles and its own duplicates.
  • Status of previous editsThe site, which has already been "optimized" several times by various contractors, takes longer to understand: remnants of redirects, two analytics containers, markup from a disabled module. This is archaeology, and it takes days.
  • Is rechecking required after corrections?This is the second bypass with the same method after some time after the works. It is not included in the first document and is planned separately.
Who it's for

Situations where this service delivers results

Scenario 1 of 4

Traffic is lower than expected, no one has given reasons

Advertising is running, texts are being written, and organics are standing. The first audit question here is not "how to promote", but "does the search engine see these pages at all". A page outside the index brings neither visitors nor hryvnias — and no content work will change that. Fair limit: the actual number of indexed addresses is visible only in your Search Console, only the prerequisites are read from the outside.

We'll review your situation in a free audit
What's included

Complete list of work and what you get as a result

  • Full crawl of the site with response codes, redirect chains and depth of nesting - you can see which pages the bot sees and which it does not reach
  • Reconciliation of sitemap and robots.txt with each other and with the actual structure: how many entries vs. how many unique addresses, closed from crawling by mistake
  • A list of duplicate addresses with a breakdown of the reasons — sorting parameters, facets, versions with and without a slash: you can see what to glue canonical and what to close
  • Measuring the first response of the server separately on the main page, in the category and in the card, with a fixation of the weight of the document - the difference between the types of pages says more than the average figure
  • Validation of structured data on live pages, not in module settings: what is declared, is it actually on the page, where the markup promises non-existence
  • Audit of first-level titles, page titles and descriptions by page type - listing empty, short and duplicate
  • Checking language versions, hreflang and canonical links for consistency: a typical breakdown is canonical from one language branch to another
  • Analytics status: is the counter standing, is it collecting in the disabled property, are there duplicate events from two containers
  • Analysis of server logs, if access is granted: where does the bot actually go and how many requests are consumed by service addresses and filter pages
  • Fix plan with breakdown into critical, important and cosmetic and estimation of each item in working days - according to it the tasks are assigned without us
  • Raw file traversal data: the table of addresses with codes and headers remains with you regardless of who fixes
When this service isn't right

What's not included — so there are no surprises at delivery

  • The correction of what was found is separate work that is evaluated after the audit
  • Security auditing and vulnerability scanning
  • Legal verification of the site and compliance with the requirements for the processing of personal data
  • Traffic forecasts and post-fix position promises
  • Work with content: collection of semantics, texts, product descriptions
Process steps

Transparent stages with approval at every step

Total duration:5–20 days

  1. Crawling and collecting raw data

    1-3 working days

    We walk through the site from the root address in depth: response codes, redirects, nesting depth, response headers. We drag the sitemap and robots.txt in parallel. At this step, we do not interpret anything - we only collect a table, on which each conclusion is then based.

  2. Indexing, service files, duplicates

    1-3 working days

    How many entries in the map vs. how many unique addresses, what is closed in robots.txt, which addresses exist in multiple variants. Right here in the Search Console, if access was granted. An honest limit at once: the site map does not raise items and does not force indexing - it only removes the reason why the page was not found.

  3. Templates: titles, meta tags, markup, language versions

    1-4 working days

    We take several live addresses of each type and see what the server returns: first-level header, page name, description, JSON-LD, canonical, hreflang. We check the markup with what is visible on the page: the announced rating without any feedback is a risk of manual sanctions, not an advantage in issuing.

  4. Logs, speed, analytics

    1-4 working days

    We read the access log: where the bot actually goes and how many requests the service addresses take. We measure the first response on three types of pages. We check the counters. The meter doesn't improve anything by itself - it just gives you an opportunity to see, and GA4 shows a trend, not a cash register.

  5. Prioritization, document, conversation on it

    1-6 working days

    Findings are sorted by impact and cost to fix, not by report section. Each item is estimated in working days so that it can be taken to the developer. Then an hour of conversation — together with the one who will correct. What is not explained by the collected data remains in the document as unexplained.

Did not find your case?

Describe how it works on your side — we will tell you whether “Technical audit of the site” fits and what it means in your situation. No brief and no call: one question, one answer.

Cases

Tasks and results in numbers — all metrics measured by us

online store for the delivery of sweets, snacks and gift sets

Task
Understand the technical condition of the store, which looks working and fast, but gives less organics than expected.
Solution
Bypass from the outside without access: service files, headers, meta tags, structured data, counters, platform version, measuring the first response of the server.
Result
2026-07-31 Measurement: HTTP 200, valid HTTPS, HTTP/2, first server response 402.9ms and full HTML load 532.4ms with 303.4KB of markup, the fastest first response among batch stores on this platform. Then something else begins: /sitemap.xml returns 200 with a body of zero bytes, feed/google_sitemap — 404, the Sitemap line in robots.txt is commented with the default blank, that is, the search engine does not receive the sitemap at all. Zero JSON-LD blocks, zero h1 tags on the main page, 46 character page description. No analytics were detected - neither GTM, nor GA, nor Meta Pixel. PHP 7.3.33 - Unsupported as of December 2021. It was not possible to measure the size of the directory from the outside precisely because of the empty map.
Technologies & integrations

What we build on and what it connects to

Stack

  • Screaming Frog - crawl with response codes and depth; the free version stops at 500 addresses, a large catalog is available in the paid version and in batches
  • curl with repetitions - codes, headers and time to the first byte without browser add-ons; it's the backend, not the visitor's experience on his network
  • own traversal of sitemap.xml with counting of unique addresses — catches duplicate entries that are not visible until the map is disassembled
  • Google Search Console is the only place where the fact of indexing is visible; confirmed rights are required, we do not have access by default
  • nginx or Apache server logs — real bot visits; without them, Googlebot's behavior remains a guess
  • checking JSON-LD on live pages, not in module settings: the module promises, the page delivers
  • GA4 — is data collected at all; blockers and consent mode make numbers a trend, not accounting

Integrations

  • Google Search Console
  • Bing Webmaster Tools
  • GA4
  • Google Tag Manager
  • Cloudflare
Manual audit vs. automated online service report

How this option differs from the alternative

How the sitemap is checkeddrag the file, count entries and unique addresses, check with robots.txt
Markingwe compare the announced with what is actually on the page
Order of pointsby impact and cost of correction, estimated in days
To whom it is addressedto the developer: address what is wrong, what to do, how to check
Unexplainedremains in the document as unexplained with an explanation as to why
What we need from you

We can't start without this — best to prepare in advance

  1. Website address - nothing else is needed for a free measurement.
  2. Access to Search Console for a paid audit: without it, it is impossible to see what was actually found and made it to the index.
  3. Access to server logs or access log download in two to three weeks, if analysis of bot behavior is required.
  4. A developer contact to whom we can ask clarifying questions about the configuration is faster than correspondence through the manager.
  5. List the pages that are important to you: it makes sense to measure where the money comes from, not a random address from the directory.
  6. One person from your side, who makes a decision based on what is found - otherwise, the document is discussed, but not implemented.

If something is missing — let us know, we'll help you gather it or do it as a separate task.

FAQ

Most frequently asked questions — with concrete answers

How is this different from a speed audit?

By volume A speed audit answers one question — why the site takes a long time to load and what to do about it. Technical broader: indexing, address structure, markup, language versions, service files, analytics. Speed ​​is included in it in one section, so it is ordered separately when the rest is already in order.

Why a paid audit, if there is a free measurement?

Free shows what is visible from the outside - and this is really often enough. Paid adds three things that no one can see from the outside: bot behavior in logs, checking of each type of page instead of a sample, and a patch schedule with an estimate of work in days. If after the free it becomes clear that there is no point in going deeper, we will say so.

What are the most common findings?

An empty or inaccessible sitemap - by a large margin. We measured a store where /sitemap.xml returns 200 with a body of zero bytes, the engine feed is 404, and the Sitemap line in robots.txt is commented out with the default template. Such a site misses the automatic checklist: the response code is 200. Next in frequency is the absence of a first-level title, short descriptions of pages, and zero structured data.

Will you find anything if the site is new and fast?

Often yes, and this is not a paradox. The directory site we measured had a first response time of 320ms — fourth best among the sixteen sites in the sample — and had an empty sitemap, a commented blank in robots.txt, and no Google counter. Speed ​​and visibility depend on different things: the first depends on the server and the template, the second - on whether the search engine knows about your addresses.

Are you correcting what you found or just describing it?

We can do both, but these are different arrangements. Audit — document and plan; corrections are evaluated after it, when the volume is already visible. Some clients give the plan to their own developer, and this is a normal scenario: the document is written in such a way that tasks are set for it without us — address what is wrong, what to do, how to check the result.

Will traffic increase after the fixes?

We do not name it and do not calculate it in advance. Fixes remove the technical reasons why the page is not displayed or is displayed worse - they do not create demand. Separately, we warn about the non-obvious: after cleaning duplicates, the number of pages in the index may drop for some time. This is an expected course of events, but if not told in advance, it looks like a deterioration.

How long does it last and what is required of us?

Free measurement - 2-4 working days, you only need an address. Paid audit — 5-20 working days depending on the size of the site and the number of page types, and here accesses are already required: Search Console is mandatory, server logs are optional. The directory is tens of thousands of pages longer, because the traversal is done in batches and is repeated, not because we write slowly.

Do you need an audit if the site just works?

Once a year - just like a car inspection. Technical things break quietly: the version of the module has changed — the site map has become empty; renewed the certificate - the redirect broke. We found sites with an unsupported version of PHP from December 2021 that looked alive and served the customer just fine. But if the previous audit remains unimplemented, implementation is the first step.

What if our developer disagrees with the findings?

This is a normal part of the job, and that is why the document contains response codes, addresses and dates, not grades. The disputed item is checked by the same team at the same address - either confirmed or withdrawn. We are not ashamed to remove our points: the document is needed for work, not to win an argument.

Send the site address - we will do the basic measurement ourselves, without access.

In response - findings with response codes and numbers, divided into emergency and scheduled, and a direct answer whether you need a detailed audit. If you don't need it, you will hear exactly that.

View cases
  • Reply within 2 hours
  • No commitment
  • We work under a contract

There is no price list on the site on purpose: the same work differs several times over between two clients, and a “from” figure explains nothing in that case. First a free audit — we count your pages, duplicates and speed — then we name the sum and the deadline and fix both in the contract.