Automating 1C-Bitrix and Yandex Webmaster Integration

Automating 1C-Bitrix and Yandex Webmaster Integration

Imagine: a manager updates a product card, but the page gets indexed by Yandex only a week later – because they forgot to manually submit it for reindexing. Or you log into Yandex Webmaster every day to check for crawler errors. Sound familiar? We solve this once and for all. Consider: with 200 daily changes, manual submission takes up to 2 hours, and forgotten URLs lose up to 30% of potential traffic.

We set up full integration of 1C-Bitrix with Yandex Webmaster via API. Automatic reindexing with every content change, error monitoring right in the admin panel, sitemap management – all working without your involvement. Result: indexing in minutes, not days, and full control over SEO metrics.

Problems We Solve

• Manual reindexing after every update. With 100+ changes per day, that's hours of routine. Our mechanism tracks infoblock update events and queues URLs for reindexing. Automation reduces response time by 90%.
• Lost pages due to crawler errors. HTTP 404, 500, timeouts – without monitoring you find out only when traffic drops. We display error statistics right in Bitrix, allowing a response in minutes, not days.
• Outdated sitemap. After adding new sections, the sitemap often isn't updated. Auto-notification to Yandex via API solves it – the sitemap is always fresh.

Why Automating Reindexing Saves Time?

Manual URL submission is an extra step that's easy to skip. Automation ensures every updated page enters the reindexing queue within minutes. We use the OnAfterIBlockElementUpdate event and add the URL to the b_ya_reindex_queue table. The ReindexAgent agent sends batches of 200 URLs every minute – 10x faster than manual work.

\Bitrix\Main\EventManager::getInstance()->addEventHandler(
    'iblock',
    'OnAfterIBlockElementUpdate',
    function (array &$arFields): void {
        if (!in_array($arFields['IBLOCK_ID'], [CATALOG_IBLOCK_ID, ARTICLES_IBLOCK_ID])) {
            return;
        }
        $element = \CIBlockElement::GetByID($arFields['ID'])->GetNextElement();
        if (!$element) return;
        $url = \CHTTP::URN2URL($element->GetFields()['DETAIL_PAGE_URL']);
        if (!$url) return;
        \YandexWebmaster\ReindexQueue::push($url);
    }
);

class ReindexAgent {
    public static function run(): string {
        $connection = \Bitrix\Main\Application::getConnection();
        $urls = $connection->query(
            'SELECT ID, URL FROM b_ya_reindex_queue WHERE SENT IS NULL LIMIT 200'
        )->fetchAll();
        if (empty($urls)) return __CLASS__ . '::run();';
        $client = new \YandexWebmaster\ApiClient();
        $result = $client->request('POST', '/hosts/{host-id}/reindex/url/', [
            'url_list' => array_column($urls, 'URL'),
        ]);
        $ids = array_column($urls, 'ID');
        $connection->query(
            'UPDATE b_ya_reindex_queue SET SENT = NOW(), STATUS = "sent" ' .
            'WHERE ID IN (' . implode(',', $ids) . ')'
        );
        return __CLASS__ . '::run();';
    }
}

How to Set Up OAuth for the API?

Authorization in the Yandex Webmaster API is via OAuth 2.0. The token is obtained in the Yandex ID personal account and stored in \Bitrix\Main\Config\Option. We create a base ApiClient class with methods for GET and POST requests. The user-id is obtained via a separate request and cached.

namespace YandexWebmaster;

class ApiClient
{
    private const BASE_URL = 'https://api.webmaster.yandex.net/v4';

    private string $token;
    private string $hostId;

    public function __construct()
    {
        $this->token = \Bitrix\Main\Config\Option::get('mymodule', 'ya_webmaster_token');
        $this->hostId = \Bitrix\Main\Config\Option::get('mymodule', 'ya_webmaster_host_id');
    }

    public function request(string $method, string $endpoint, array $data = []): array
    {
        $http = new \Bitrix\Main\Web\HttpClient([
            'disableSslVerification' => false,
        ]);
        $http->setHeader('Authorization', 'OAuth ' . $this->token);
        $http->setHeader('Content-Type', 'application/json');

        $url = self::BASE_URL . '/user/{user-id}' . $endpoint;

        if ($method === 'GET') {
            $http->get($url . ($data ? '?' . http_build_query($data) : ''));
        } else {
            $http->post($url, json_encode($data));
        }

        return json_decode($http->getResult(), true) ?? [];
    }
}

Crawler Error Monitoring: Live Dashboard

Instead of logging into Yandex Webmaster once a week, get errors right in the admin panel. We query the Crawling API for the last 7 days and display error types with counts. Data can be visualized via bitrix:main.admin.list. This allows a response in minutes, not days.

$errors = $client->request('GET', '/hosts/{host-id}/crawl/stats/errors/', [
    'date_from' => date('Y-m-d', strtotime('-7 days')),
    'date_to' => date('Y-m-d'),
]);

Sitemap Management: No Routine

After publishing new content, we automatically notify Yandex about the updated sitemap. One request to the Sitemap API – and the sitemap enters the processing queue. The status is checked separately to confirm acceptance.

$client->request('POST', '/hosts/{host-id}/sitemaps/', [ 'url' => 'https://site.ru/sitemap.xml', ]); 

What's Included

• Development of the integration module with OAuth settings.
• Implementation of the reindex queue and agent.
• Crawler error monitoring in the admin panel.
• Automatic sitemap updates on content changes.
• API documentation and post-deployment support.

Process

1. Analysis – study the site structure, infoblocks, current processes.
2. Design – create module architecture, tables, agents.
3. Implementation – write code, configure authorization, queues.
4. Testing – verify on a test bench, simulate updates.
5. Deployment – roll out to production, train administrators.

With over 5 years of experience and 100+ successful integrations, our proven methodology guarantees reliable results.

Comparison of Manual vs. Automated Approach

Estimated Timelines and Costs

Cost is calculated individually – depends on site complexity and number of infoblocks. On average, integration pays for itself within 3–6 months. Get a consultation – we'll evaluate your project in one business day and propose the optimal solution.