A technical audit is not a list of general recommendations. It is a document that says what is broken on your site, what that means in traffic, and in what order it gets fixed.
On Moldovan websites, three problems appear in the majority of cases.
What we find most often here
Empty pages for crawlers. A site built as a JavaScript application serves
crawlers an empty <div>. Google renders on a delay, and several of the crawlers
feeding AI answers do not render at all. The symptom is "Internal links: 0" in
Search Console. We wrote about it separately.
Wrong hreflang between Romanian and Russian. The most specifically local problem. Two languages, URLs that do not reference each other, or prefixes that do not match the content. The result: the two versions compete with each other instead of supporting each other.
Structured data asserting what the page does not show. Invented review ratings, prices that do not exist on the page, addresses and phone numbers that appear nowhere. Google checks them, and when they do not confirm, it ignores the whole block.
On top of those: uncompressed images, menus as PDFs, wrong hours in the Google listing, and shops with no product structured data.
What you receive
A document with the problems found, each with what it means concretely and how urgent it is. The order of repair, from what changes the most to what matters least. An effort estimate for each.
Verification runs against real crawlers — Googlebot, Bingbot, GPTBot, ClaudeBot, PerplexityBot — not a simulation. The tool we use is public: crawlview.
What is not worth fixing
Half of a good audit is what it tells you to ignore.
The score from automated tools. A 92 instead of an 87 changes no position at all. Scores measure conformance to a list, not visibility.
Warnings about missing attributes on decorative images. An empty alt on a
background element is correct, not a mistake.
"Too many internal links." A complete menu is not a problem, it is navigation.
Speed measured on office wi-fi. What counts is the figure on a phone, on mobile data, in the conditions your customers are actually in.
An audit that lists 300 problems without saying which four matter has moved the work onto you rather than doing it.
Who it is for
Companies with a site that "looks good" but brings nothing. People who paid for optimisation and cannot see the difference. People who want to know what they have before deciding whether to repair or rebuild.
The audit does not assume we work together afterwards. The document is yours and can be handed to anyone.
Questions
How long does an audit take?
A few days for an ordinary site, longer for a shop with thousands of pages. The date follows from seeing the size.
Do I need an audit if the site is new?
If it is new and does not appear in search after two or three months, yes. Technical problems are clearest exactly then, before content accumulates on top of them.
Do you fix the problems you find?
We can, but it is not required. The document is written so anyone can execute it, including the team that built the site.
How is this different from an automated report?
An automated report lists hundreds of warnings with no hierarchy. An audit says which three matter, why, and what gets fixed first.