New website design + layout

Create a modern, premium, fast website for the service @BuyDomain_BOT (buying and managing domains via Telegram), which:

• increases trust,

• explains value in 20–40 seconds,

• leads to Telegram (main conversion),

• helps SEO (page structure + future sitelinks),

• displays correctly in Google snippets and social media.

2) Technologies and limitations

• Only HTML + CSS + JS (no WordPress/React/Vue, etc.).

• Is Tailwind allowed? — no, need custom CSS (or a very lightweight mini-framework by agreement, but preferably pure).

• The code must be easily portable to any hosting (Nginx/Apache).

• No heavy libraries without necessity.

• Maximum speed: LCP/CLS/INP in the green zone (Core Web Vitals).

3) Website structure (mandatory)

Create the website not as one huge “sheet”, but as a landing page + several internal pages, so Google can provide sitelinks.

Minimum set of pages:

1. / — Home (landing page)

2. /pricing/ — Prices and zones (approximate, without tying to specific numbers, but with “from …” and examples)

3. /features/ — All features of the bot (in detail, in lists)

4. /api/ — API for developers (access conditions, brief documentation)

5. /faq/ — FAQ (structured)

6. /support/ — Support + contacts (Telegram)

7. /legal/terms/ — Terms of use

8. /legal/privacy/ — Privacy policy

Important: links to these pages must be in the header and footer. This will help Google choose sitelinks.

4) Design / style

• Style: premium-tech (like Stripe / Linear / Vercel in feel).

• Colors: brand colors (blue/purple gradient is acceptable), but not “acidic”.

• Dark theme — preferable, but can be a “toggle” (optional).

• Animations: light (fade/slide), without overload.

• Lots of space, neat typography, soft shadows.

5) Key meanings (mandatory content blocks)

The homepage must have blocks with clear benefits:

Hero (first screen)

• Headline (option):
  “Buying and managing domains directly in Telegram”

• Subheadline:
  “Domain check, registration, DNS/NS, Cloudflare, SSL, and redirects — all in one bot. Payment in cryptocurrency.”

• Buttons:

  • Start @BuyDomain_BOT (main CTA)

  • “View features”

Block “What the bot can do” (briefly in cards)

Must list:

• Buying domains in 1–2 clicks

• Managing DNS records (A, AAAA, CNAME, MX, TXT, etc.)

• Managing NS (changing nameserver)

• Integration with Cloudflare (zone connection/management)

• Free SSL / SSL management

• Redirects (301/302, www/non-www, URL forwarding)

• Bulk operations

• API for developers

• Asynchronous processing (nothing “hangs”)

• Payment in crypto (including payment via CryptoBot/invoices — if relevant)

• No unnecessary data / no KYC (if you really want this on the site — can be done carefully, without triggering phrases)

“How it works” (3–4 steps)

• Domain check → zone selection → payment → domain ready → management.

“Why it's safe”

• Registration with ICANN-accredited registrars (if true)

• Account/domain control protection (e.g., transfer lock)

• Transparent payment

• 24/7 support (if available)

“Prices” (preview on homepage + link to /pricing/)

• Table/cards (approximate prices and popular zones)

• Separate block “Additional services”: SSL / DNS / Transfer / API

“API”

• Briefly: why, for whom, how to get access

• Link to the page /api/

FAQ (5–8 questions)

• Briefly on the homepage + button “all questions”

Final CTA

• “Start the bot” / “Go to Telegram”

6) SEO requirements (strict)

On each page:

• Unique <title> (up to ~60 characters)

• Unique <meta name="description">

• One <h1> per page

• Canonical:
  <link rel="canonical" href="https://buydomainbot.com/...">

• OpenGraph + Twitter cards (as you have, but correctly and uniquely if necessary)

Schema.org markup (mandatory)

Insert JSON-LD:

• Organization

• WebSite (+ SearchAction if there will be site search — can be omitted)

• BreadcrumbList on internal pages

• FAQPage on /faq/ and FAQ block on the homepage

Technical:

• sitemap.xml listing all pages

• robots.txt (allow indexing)

• Clean URLs without parameters

7) Navigation and UX (important for sitelinks)

• Header: Home / Features / Prices / API / FAQ / Support

• Same structure everywhere

• Footer: duplicate links + legal pages

• “Start” button always visible (sticky is acceptable)

8) Performance

• Google PageSpeed 90+ on mobile.

• Images: WebP/AVIF, lazyload

• Minimal JS, without heavy animations

• Fonts: system or 1–2 variants, preload

9) Responsiveness and compatibility

• Mobile-first

• Chrome/Firefox/Safari/Edge

• Correctly at 360px width

10) Interactivity (JS)

• FAQ accordion

• Smooth scrolling to anchors

• Language switcher (optional) — RU/EN (if you want)

• “Copy link to bot” (optional)

• Mini-demo “how the bot works” (chat simulation) — nice, but easy

11) Analytics

• Connect Google tag (gtag.js) as you have

• Events:

  • click_telegram_start (click on all CTAs)

  • click_pricing

  • click_api

  • scroll_50 / scroll_90 (optional)

12) What the developer must deliver

• Project folder:

  • /index.html

  • /pricing/index.html

  • /features/index.html

  • /api/index.html

  • /faq/index.html

  • /support/index.html

  • /legal/terms/index.html

  • /legal/privacy/index.html