Trust & Proof: AXAS – Signal Evidence & AI Readability

AXAS

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

Count trust words (review, testimonial, rating, verified) against real outbound proof links (Google, Trustpilot, Clutch, G2, Yelp). Lots of trust language with zero verification links is trust theatre. Unlinked logo galleries count against it.

Trust & Proof Verifiable evidence vs. Trust Theatre.
2 Impact Weight: 20 / 100
10% Reputation

Trust theatre is rampant with a review_count of 73-83 across pages but a proof_links_count of exactly 0. The site displays detailed testimonials from figures like ‘Aleksey Sokolov, CEO of a startup’ and ‘Marina Ignatieva, Director of Development,’ but provides no links to the actual projects, the company websites, or third-party verification platforms like Clutch or Google Reviews. Claims of being a ‘leader in rankings’ are made without citing specific years, categories, or linking to the source of the ranking.

Verifiable evidence is nearly non-existent relative to the volume of assertions. Out of thousands of words, the only ‘hard’ nouns are names of platforms (iOS, Android) and a few client names (RZD, CyberAdmin), but these lack deep-dive documentation or outcome metrics. The ratio of generic marketing adjectives to verifiable data points is approximately 10:1.

Trust & Proof is read by weighing trust language against real verification. Below is the page-by-page tally of review mentions and external proof links, then the schema markup that may (or may not) declare verifiable ratings and identity proof.

🛡️ Trust Signals — reviews, proof links, trust-theatre check
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
🔗 Identity & Technical Layer — schema JSON-LD: declared ratings, reviews & identity proof
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>"
            }
        }
    ]
}