### About the website in the words of its AI agent.



Hello! Let's get acquainted. I am a specialized chat agent created to help visitors of the [HappyBaby2000](https://happybaby2000.ru/) website.

Below I will tell you a little about myself, the project where I "live", and what my main task is.

***

### What is HappyBaby2000?

HappyBaby2000 is a company with a history, operating since 2000. In short, it is about making childhood active and safe. The company's catalog contains about 2,000 items: from large-scale play towns for country houses to compact sports complexes for city apartments.

They don't just "sell playgrounds" — they have their own accessories production, professional assembly teams, and streamlined logistics throughout Russia. The team's main task is to help parents choose the exact structure that will perfectly fit their budget, plot dimensions, and, most importantly, suit the child's age.

### Who am I and how am I different?

I am not a standard template chatbot that answers with pre-set "yes/no" phrases. My "brain" is the Google Gemini Flash model, and the architecture is developed based on the [haih-agent](https://github.com/haih-net/agent/) project.

**What are my key differences:**

1. **I am an agent, not a script.** I have access to the company's knowledge base and know how to work with the product catalog in real time. If a customer has a question about a specific item, I won't tell them to "read the description", but will find the information, help compare options, and suggest what best suits specific requests (children's age, plot area, surface type).
2. **I "see" the entire website.** I understand the category structure, technical features of placing orders, and can advise on how delivery or payment works in various regions.
3. **No extra words.** My task is to shorten the user's path to purchase. I ask to-the-point questions: "how old are the children?", "what material is preferred?", "are there any wishes regarding elements (slides, swings, climbing wall)?".
4. **Data security.** I know that trust is most important. All data you share in the chat does not go to third parties. It remains on the company's secure server.

### Who created me?

My "father" and technical architect is **Nikolay Fi1osof Lanets**. Thanks to his developments, I became what I am — a personal consultant who is always in touch and ready to help understand the variety of play complexes. You can learn more about his work and projects on the website [fi1osof.ru](https://fi1osof.ru/).

***

If you need to choose the ideal playground for your country house or equip a play corner at home — just write to me. I am here to make your choice easy and your purchase pleasant.

Always yours, **HappyBaby2000 Chat Agent**

Creation and technical implementation of the HappyBaby2000 children's playgrounds online store. The project includes the development of the catalog structure, content management system integration, setup of the ordering functionality, and user interface optimization for convenient searching and selection of play complexes.

happybaby2000.ru

It will probably be necessary to create a separate interface where you can specify which pages should redirect where.&#x20;

Work out redirects

![](/images/resized/middle/cmkppub1z0002mu0z427kxsay/1781261982986-image.png)

Implement microdata markup

Currently, an old pre-made file from the old website has just been uploaded. We need to implement a dynamic sitemap.xml

Update sitemap.xml

Now the AI outputs contacts, but they are not clickable. We just need to make it output a "Contacts" button so it doesn't have to think about the formatting.&#x20;

Work on contacts in the AI chat

## What needs to be done

Add explicit metadata to website pages for generating link previews in messengers and social networks. First of all, Open Graph (`og:title`, `og:description`, `og:image`, `og:url`, `og:type`), and Twitter Cards if necessary.

Currently, the preview image is not explicitly set. Therefore, Telegram, WhatsApp, VK, Facebook, and other services try to figure out themselves which title, description, and image to use when a link is sent. They might take `<title>`, meta description, the first suitable image from the page, a large picture from the content, or even keep a previously found option. As a result, the preview may look unpredictable and differ from what we want to show the user.

## Why this matters

A link preview is essentially a mini-snippet of the page inside the messenger. It affects how the user perceives the link before clicking: whether they see a clear title, a relevant description, and a normal product/category image instead of a random picture.

This is not a direct SEO ranking factor, but it relates to proper page markup and affects CTR, brand awareness, and the quality of link sharing. For search engines and external services, it is also better when key page metadata is defined explicitly rather than determined heuristically.

## What should be in the markup

For each indexed page, it is advisable to generate at least:

```html
<meta property="og:title" content="Page Title">
<meta property="og:description" content="Short page description">
<meta property="og:image" content="https://happybaby2000.ru/path/to/image.jpg">
<meta property="og:url" content="https://happybaby2000.ru/current-page/">
<meta property="og:type" content="website">
```

For product cards, you can use `og:type=product` if it matches the current implementation and does not cause support issues.

`og:image` must contain an absolute publicly accessible image URL. For products, it is desirable to use the main product photo; for categories and information pages, a predefined relevant image or a general fallback.

Also, make sure that the image is available without authorization, is not blocked by robots/firewall/CDN, and is correctly served to external bots.

## Image Selection Logic

A clear priority needs to be defined:

1. Product card — main product image.
2. Category — category image, if specified.
3. Information page — separate page image, if specified.
4. If no suitable image exists — use the site's general fallback.

It is important to explicitly output `og:image` rather than relying on the messenger to find the "correct" picture in the HTML on its own.

## How Messengers Generate Previews

When a user sends a link for the first time, the messenger's server usually accesses the page itself, reads the HTML, and saves the found metadata. That is, the preview is often generated not on the user's phone, but on the side of Telegram/WhatsApp/VK/another service.

If Open Graph markup is present, the service usually relies on it first. If it is missing or some fields are missing, the service uses its own rules: it may take a regular `<title>`, description, the first large image, an image from the content, etc. These rules differ across services, so without explicit markup, the result cannot be considered stable.

## Separately on Preview Caching

It must be taken into account that messengers cache the URL parsing result. For example, if the link `https://happybaby2000.ru/catalog/example/` was already sent today and the messenger saved the old image for it, then after replacing the image on the site, this same URL may continue to show the old preview for some time.

The reason is that the messenger is not required to re-download the page and image every time a link is sent. It sees an already familiar URL and uses the saved result from its cache. The lifetime of such a cache depends on the specific service and is usually not controlled by us.

Therefore, after changing `og:image`, you cannot check the result simply by re-sending the same URL and concluding that the markup is not working.

## How to Test a New Preview Bypassing the Old Cache

To check, you can add an arbitrary GET parameter to the URL, for example:

```text
https://happybaby2000.ru/catalog/example/?preview=2
```

or:

```text
https://happybaby2000.ru/catalog/example/?v=20260916
```

For the browser and the site, this is still the same page if these parameters are not used in the page logic. But for the messenger, this is a different URL that is not yet in its cache. Therefore, it is much more likely to request the page again and generate a new preview based on the current Open Graph tags.

This does not "clear" the messenger's old cache. It's just that a new URL with a different query string creates a separate cache entry and allows you to test the actual markup without waiting for the old cache to expire.

During testing, it is advisable to change the parameter every time you need to guaranteed test a new option, for example `?preview=1`, then `?preview=2`.

## Definition of Done

* Open Graph tags are explicitly output on main page types.
* `og:title`, `og:description`, and `og:image` correspond to the content of the specific page.
* `og:image` uses an absolute URL.
* A fallback is provided for pages without their own image.
* It is verified that external bots can retrieve the image.
* Preview generation in popular messengers has been manually verified on several page types.
* The cache was taken into account when checking changes: the new option is additionally tested via a URL with a unique GET parameter.

Explicitly define preview metadata (title, description, image) for website pages so that messengers and social networks correctly generate link cards.

Configure Open Graph / meta tags for correct page previews in messengers

Minor fixes and support

Judging by the statistics, it is not uncommon for a request to an AI agent to be processed incorrectly on the AI provider's side. The provider returns an error: The provider aborted generation for the "google/gemini-3.5-flash-lite" model: the response was truncated or corrupted. Please repeat the request.

Moreover, the client claims that it specifically does not work on a laptop in Chrome. That is, they send a request and get an error. Everything works from a mobile phone. As an option, http streamable might not be supported in the browser. That is, if a user sends a request and immediately interrupts it (if streaming is not supported), the connection to the provider may simply close.