01Blocked
Technical readiness
The HTML for /ua and /en contains noindex, nofollow. Organic visibility lacks a normal technical foundation until the directive is removed.
Public baseline / A-HOV
They build AI solutions. The site asks search engines not to show it.
A real report based on public sources. There is no invented score: every finding is tied to a page, date and check.
Three metrics
No overall AI score. Every status means only what was verified.
02Not measured
Observed AI visibility
The multi-engine run was intentionally deferred. We do not invent a zero without saved answers.
03Preliminary signal
Competitive and source gap
A control search mixes the brand with ABOV Dev, AHV Software and AHV Communities. A repeat measurement is needed after indexing.
Executive summary
The first problem is not inside the models. It is inside the HTML.
Primary blocker
noindex, nofollowWhile this directive is active, it makes no sense to evaluate content strategy as if the pages were normally participating in search.
Already verified
HTML for /ua and /en, metadata, canonical, Organization and FAQ schema, navigation, service structure and a control brand search.
Next measurementChatGPT, Claude, Gemini and Perplexity after noindex is removed, with repeat runs for Ukrainian, European and US markets.
Technical decision or mistake
We can see the directive. HTML does not reveal the developer's intent.
Noindex may have protected a test version, delayed indexing until launch or remained from staging. The business question is different: when was the site expected to start attracting organic demand?
Intentional
The site was not ready for organic traffic.
Temporary
Indexing was planned for a separate release.
Inherited
Production received the staging configuration.
Forgotten
The business expected organic demand, but the directive was not reviewed.
Finding register
Facts ordered by impact.
Critical
Indexing is blocked
Both /ua and /en serve meta robots: noindex, nofollow. This is a baseline blocker for organic visibility.
High
The name collides with other entities
The control search sample surfaced ABOV Dev, AHV Software and AHV Communities.
Strength
The owned source is already structured
UA/EN, canonical, Organization schema, FAQ schema, clear services, cases and accessible navigation.
Medium
Brand spelling varies
Ahov, A-HOV and ahov.dev all appear in communication. The entity needs one primary form and consistent sameAs signals.
First cycle plan
First return the site to the game. Then measure recommendations.
1Remove noindex, nofollowNowA-HOV / development
2Verify robots.txt, sitemap and Search ConsoleAfter releaseA-HOV / technical
3Agree one primary brand form and sameAs profilesWeek 1A-HOV / marketing
4Capture a baseline across four AI systemsAfter indexingGonenych
5Build sources and content around measured gaps30-90 daysJoint
This is a public technical baseline, not a completed multi-engine audit. Model answers were not simulated. They will be added only after real runs with saved evidence.
Published with the agreement of the A-HOV team as an example of an open baseline. A-HOV is the partner that development and automation work is referred to.
First step
Tell us about the task.
Complete the short form. Within 24 hours the team will review the context and tell you whether we can help and where it makes sense to start.
No files. No passwords. No automated promises.Scope and commercial terms are defined after the assessment.