Audit after a traffic drop
We break the drop down by section and date, match it against updates and your own changes, find the cause and tell you what will recover. Diagnostics are free.
A website SEO audit is a check of what stops your pages from reaching search results and earning clicks. We do not hand out a “site score”: we look at specifics — which URLs return the wrong status code, what is blocked from indexing, where the canonical points, whether hreflang matches across language versions, how heavy a page is, and whether the snippet answers the query it is shown for. The sources are Search Console, a crawl of the site under the Googlebot user agent, and our own checking tools. What you get is not “a hundred remarks” but a list of causes ordered by the cost of fixing them: what exactly is broken, what confirms it, and what the fix will give you. The first review of the task is free and takes 1–3 working days.
We break the drop down by section and date, match it against updates and your own changes, find the cause and tell you what will recover. Diagnostics are free.
We count the catalog from the outside, identify the real platform, review the domain history and list risks to raise in negotiation. The external check is free.
We count a competitor's catalog and structure two ways, measure its technical state and show which differences you can actually copy. One measurement is free.
We crawl the site like a search bot, measure speed, service files, markup and indexing, and sort findings into urgent and planned. The measurement is free.
The pages exist, the texts get written, and organic search stands still. The first question here is not “how do we promote this” but “does the search engine see these pages at all”: status codes, noindex, canonicals pointing elsewhere, sitemaps, and the real number of URLs in the index against the number on the site.
We'll review your situation in a free auditThere was a release, there was a migration, there was an algorithm update — or all of them at once. The breakdown starts with dates: what changed on the site that week, and what changed in the results. Sometimes the cause is not the site at all, and that is an answer too.
Here the question is not “how do we improve this” but “are you buying a problem”. Domain history, the real number of indexed pages against the claimed one, whether all the traffic rests on a single query, which domains link in and with which anchors. Analytics screenshots from the seller are not evidence.
We compare structure, catalogue, snippets and technical state, then say which of the differences you can realistically repeat and which come down to range or domain age. The real advantage often turns out to be somewhere other than where it was being looked for.
We establish what happened and when: whether traffic fell or never grew, whether there was a release or a migration, and what access exists to Search Console and analytics. That decides which of the four checks is needed — and whether one is needed at all.
We crawl the site under the Googlebot user agent and look at what is visible from outside: status codes and redirect chains, robots.txt and sitemaps, noindex in meta tags and in the X-Robots-Tag header, canonicals, hreflang across language versions, compression and page weight. That is enough to say whether there is a problem and how deep it goes.
We take Search Console: queries and pages with impressions but no clicks, the length and relevance of titles and descriptions, mobile Core Web Vitals, and crawl budget spent on URLs blocked from indexing. Then cannibalisation, where several of your pages compete for one query, internal linking, and the backlink profile: how many domains link to you and with which anchors.
We hand over the findings ordered by the cost of fixing them and walk through them with you. You should come out knowing what to do first and what it will give you — even if you do it without us.
This is how your store can look on a phone: a collection banner, popular products and a cart one tap away. Tap “Add to cart” and the counter in the header updates, just like in a real store.
The first review of the task is: 1–3 working days, with no obligation on your side. In that time we look at what is visible from the outside and tell you whether there is a problem and how deep it goes. The full check with access to your data is paid, and we name the sum after the review — before it the scope is invisible, and the same work by name differs several times over between two sites.
The first review takes 1–3 working days. The full check takes three to ten working days once we have access: a store with tens of thousands of products and faceted filters takes longer than a corporate site of thirty pages. We name the exact term after the first review, when the size of the site and the number of data sources to cross-check are clear.
A list of causes ordered by the cost of fixing them. Next to each one is the evidence: a status code, a line in robots.txt, a canonical value, the page weight, or data from Search Console. Plus what the fix will give you and what it will not. And a conversation over that list so it is clear where to start. There will be no hundred-page document: nobody can work from one.
An online service returns a list of remarks where “title too long” sits next to a whole section blocked from indexing. It cannot tell them apart by cost, because it knows neither your business nor which pages bring in money. We take the same data — a crawl, Search Console, our own tools — but the work starts where the service stops: in explaining why a number looks the way it does and what follows from it.
One question settles it: what happened. Traffic never grew — the technical audit. It dropped suddenly — the audit after a traffic drop. The site is not yours yet and you are buying or accepting it — the pre-purchase check. Your own site is fine but a competitor ranks above you — the competitor breakdown. If you are unsure, describe the situation and we will name the type ourselves, as part of the free review.
Yes, and it is a common scenario. The list is written so your own developer can verify and close every finding without us: it contains checkable numbers, not opinions. If it is clear that doing it in-house is cheaper for you, we say so in the first reply. Fixing things on our side is separate work with its own scope, term and contract.
Describe the task in your own words — we will tell you where to start and whether you need what you came for. If you do not, we will say so.