**bizneshelper.ru** is a web project in the field of business consulting and management expertise.

## Project Purpose

The website presents areas of professional assistance to business, publishes expert materials, and serves as a public entry point to get acquainted with the team's approaches, competencies, and experience.

## Topics

The public section of the project features materials related to:

* management and strategic consulting;
* sales and marketing development;
* production and crisis management;
* business processes and organizational changes;
* HR, legal, foreign economic, and other applied areas;
* practical case studies and expert publications.

## Audience

The project is aimed at owners, managers, and specialists of operating companies who need external expertise in management, development, and improving business efficiency.

## Role of the Website

The website simultaneously performs several functions:

* presents competencies and work areas;
* builds trust through public materials and experience;
* accumulates expert content;
* helps visitors understand what tasks they can turn to for consulting assistance;
* serves as a basis for the further development of the project's digital presence.

## Project Management Principle

Only open information is recorded in the project card and related public entities. Internal agreements, financial indicators, access credentials, personal data, client information, and other sensitive data are not published.

## Related Entities

* Technical modernization concept: [bizneshelper.ru — modernization and migration to haih-cms](/concepts/bizneshelper-ru-modernizatsiya-i-migratsiya-na-haih-cms).
* Current work is carried out through project tasks; individual technical initiatives do not define the content of the project itself.

bizneshelper.ru is a website about business consulting, management, and organizational development.

bizneshelper.ru

# Objective

Eliminate the mismatch between the main site mirror and the URLs published in the sitemap.

## Current State

The main site mirror is used without `www`, but the links in the sitemap are generated with `www`. This creates unnecessary ambiguity for search engines and contradicts the chosen canonical URL structure.

## What to Do

- Locate where the base host for the sitemap is generated.
- Modify the URL generation so that the sitemap uses the canonical domain without `www`.
- Verify that all URLs in the sitemap are generated in a single format.
- Compare the result with canonical settings, redirects, and the main site mirror.
- Verify that the version with `www` is correctly redirected to the main mirror without `www`, if necessary.
- After the fix, re-check the sitemap for mixed host variants.

## Result

The sitemap contains only canonical URLs of the main mirror without `www`.

## Acceptance Criteria

- There are no URLs with `www` in the sitemap.
- All links use a single canonical host.
- The sitemap is consistent with canonical and redirect rules.
- Search engines are not offered two variants of the same host.

Align the links in the sitemap to the main canonical mirror of the site without www.

Fix URLs in sitemap: remove www

# Context

On the original legacy site bizneshelper.ru, the search is currently broken: when attempting to execute a search query, the user receives a standard Rails error `We're sorry, but something went wrong.`.

This is a defect in the old Ruby implementation, not the new version of the site.

## Goal

Understand the actual cause of the legacy search crash and ensure a working search scenario in the new implementation on haih-cms.

## What to do

- Reproduce the error on a locally running copy of the legacy site.
- Check if the failure is related to Sunspot/Solr, missing index, connection configuration, or result handling in the Rails application.
- Document which content types historically participated in the search.
- Determine which search scenarios are actually needed by the user on the new site.
- Do not consider restoring the old Solr mandatory by itself: if the legacy search is only needed as a source for understanding behavior, implement the new search using the current stack.
- Test search across main public entities and typical queries.
- Provide clear behavior when there are no results and in case of a technical error.

## Result

The cause of the old search crash is understood, and the new version of the site has a working and predictable search scenario.

## Definition of Done

- The legacy error is reproduced and its source is identified.
- It is clear which entities should be indexed in the new search.
- Search in the new version does not depend on the old Rails/Solr circuit without explicit necessity.
- The user receives results, an empty state, or a controlled error message rather than a generic 500 page.

## Constraints

Do not publish internal Solr addresses, connection secrets, production logs, and other sensitive parameters in the open task.

On the original Ruby site, the search fails with `We're sorry, but something went wrong.`. We need to identify the cause and implement a working search in the new version.

Tasks

Fix search: legacy site crashes on search query

Fix URLs in sitemap: remove www