Feature/lovable

[AndreiDrang]

No description provided.

[github-actions]

Z.ai Code Review

## 🔍 Review Summary
This PR significantly enhances the site's SEO through expanded FAQ schemas, News Article datasets, and a new dynamically-updating market statistics section. It also introduces a well-thought-out robots.txt tailored for AI crawlers. However, there are a few content truncation issues and placeholder data that need to be addressed before merging.

## 🚨 Critical Issues & Bugs

• faq/index.html: The structured data answers for the investor qualification tiers are truncated and missing critical information.
  • For "Лицо без статуса квалифицированного инвестора", the text abruptly ends with: "...отвечающие всем следующим требованиям:" without listing the requirements.
  • For "Квалифицированный инвестор", it mentions "Соответствие минимум 2 из 5 критериев" but fails to list what those 5 criteria are.
  • Impact: This will result in a poor user experience if rendered on the page, and search engines may flag or ignore incomplete FAQ schemas.
• index.html: The NewsArticle JSON-LD schema contains hardcoded dates in the future (e.g., "datePublished": "2026-06-24" and "2025-12-01"). Search engines heavily penalize or ignore fictitious future publication dates. If this is a placeholder array, ensure it is populated dynamically via a backend or templating engine before going to production.

## 💡 Suggestions & Best Practices

• index.html: In the marketStats() Alpine component, the fetch call to https://hype.tokenbel.info/stats/overview is entirely commented out, leaving the component purely static. Additionally, there is a minor typo in the comment: "Рынок Белариси сегодня" should be "Рынок Беларуси сегодня".
• public/robots.txt: While explicitly allowing modern AI crawlers (e.g., Claude-SearchBot, Perplexity-User) is a great strategy, some of these User-Agents are highly speculative or non-standard as of yet. Since you already have a catch-all User-agent: * Allow: / at the bottom, the explicit blocks for undiscovered bots are functionally redundant. It's fine to leave them for documentation purposes, but ensure you monitor official announcements to keep this list accurate.

## 📊 Final Assessment

• Rating: Normal
• Reason: The core additions—particularly the structured data and the UI for market stats—are well-implemented. However, the hardcoded future dates and the truncated answers in the FAQ schema need to be fixed to avoid damaging the site's SEO integrity and user trust.