Identity & Authority: AXAS – Signal Evidence & AI Readability

AXAS

(https://axas.ru) 📸 Data Snapshot: June 20, 2026
Identity & Authority — The Lens

Inspect the JSON-LD. Is there an Organization or Person schema, and does it carry sameAs links to real external profiles (LinkedIn, socials)? Missing schema or no identity declaration signals an anonymous entity.

Identity & Authority Expert verifiability & Schema depth.
2 Impact Weight: 15 / 100
13% Reputation

While the site names specific team members like CEO Sergey Maybrodsky and Backend Dev Artyom Shchelkunov, it lacks the necessary technical footprint to establish authority. There is no schema_json for the Organization or individual Persons, meaning there are no sameAs links to LinkedIn, GitHub, or professional certifications. The absence of an H1 on the homepage further indicates a lack of professional technical oversight, contrasting their claim of ‘technical expertise.’

The disconnect between claims and evidence is highlighted by specific performance numbers that are untethered to reality. For instance, a testimonial claims a ‘40% increase in conversions,’ yet there is no link to the case study or the website where this occurred. The placeholder stats ‘0+’ projects and ‘0 years’ experience completely negate the marketing tone of being a ‘reliable partner’ with ‘rich experience.’

Identity & Authority is read from the structured data first: whether the site declares who it is in machine-readable schema, with verifiable identity links. Below is the schema captured per page, then the external proof links that support (or fail to support) that identity.

🔗 Identity & Technical Layer — schema JSON-LD: identity chains, entity gaps
Homepage — no schema detected (entity gap)
/contacts/ — no schema detected (entity gap)
/awesome-team/ — no schema detected (entity gap)
/razrabotka-mobilnyh-prilozheniy/
{
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
        {
            "@type": "Question",
            "name": "Сколько времени занимает разработка мобильного приложения?",
            "acceptedAnswer": {
                "@type": "Answer",
                "text": "<p>Сроки варьируются в зависимости от сложности проекта, но в среднем от 2 до 6 месяцев.</p>"
            }
        },
        {
            "@type": "Question",
            "name": "Сколько стоит разработка мобильного приложения?",
            "acceptedAnswer": {
                "@type": "Answer",
                "text": "<p>Стоимость зависит от функциональности и сложности проекта. Мы предоставляем детальную смету после обсуждения требований.</p>"
            }
        },
        {
            "@type": "Question",
            "name": "Предоставляете ли вы поддержку после запуска приложения?",
            "acceptedAnswer": {
                "@type": "Answer",
                "text": "<p>Да, мы предлагаем различные планы поддержки и обновления приложений после их выпуска.</p>"
            }
        },
        {
            "@type": "Question",
            "name": "Можете ли вы обновить или улучшить существующее приложение?",
            "acceptedAnswer": {
                "@type": "Answer",
                "text": "<p>Конечно! Мы проведем аудит вашего приложения и предложим план по его оптимизации и обновлению.</p>"
            }
        }
    ]
}
🛡️ Trust Signals — external proof links that back the declared identity
302Review mentions (all pages)
0External proof links (all pages)
PageReviewsProof links
/ (home) 73 0
/contacts/ 73 0
/awesome-team/ 83 0
/razrabotka-mobilnyh-prilozheniy/ 73 0