Integration of 1C-Bitrix with Google Search Console

An SEO specialist spends up to 4 hours per week manually exporting reports from Google Search Console – that's roughly $800 lost per month (at $50/hour). For a catalog with 30,000 products, this means 16 hours a month that could go into actual optimization. Our integration eliminates this: data loads automatically, updates once a day, and is accessible directly in the Bitrix admin panel. We have implemented such integrations for 50+ projects with catalogs starting from 10,000 items. The savings on manual collection reach $500 per month. Our team has over 10 years of experience with Bitrix and SEO. Development timeline: 3 to 5 business days. Contact us for a free assessment of your project.

Why Use Service Account?

Authorization can be done via OAuth 2.0 or Service Account. Service Account is better: it doesn't require manual token refresh. This reduces maintenance time by a factor of 3.

Authorization via Service Account

// Устанавливаем google/apiclient через Composer в /local/
// composer require google/apiclient

namespace Google\SearchConsole;

class ServiceClient
{
    private \Google\Service\SearchConsole $service;

    public function __construct()
    {
        $keyFile = \Bitrix\Main\Config\Option::get('mymodule', 'gsc_key_file_path');

        $client = new \Google\Client();
        $client->setAuthConfig($keyFile);
        $client->addScope(\Google\Service\SearchConsole::WEBMASTERS_READONLY);

        $this->service = new \Google\Service\SearchConsole($client);
    }

    public function getSearchAnalytics(
        string $siteUrl,
        string $startDate,
        string $endDate,
        array  $dimensions = ['query', 'page']
    ): array {
        $request = new \Google\Service\SearchConsole\SearchAnalyticsQueryRequest();
        $request->setStartDate($startDate);
        $request->setEndDate($endDate);
        $request->setDimensions($dimensions);
        $request->setRowLimit(5000);

        $response = $this->service->searchanalytics->query($siteUrl, $request);
        return $response->getRows() ?? [];
    }
}

The Service Account JSON key is stored in a protected directory outside the webroot. The path is set in the module settings.

Collecting Data by Site Pages

A Bitrix agent fetches data for the previous day daily. Consider the GSC delay: data updates with a 2–3 day lag, so the agent requests data for D-3.

class GscDataCollectorAgent
{
    public static function run(): string
    {
        $client  = new \Google\SearchConsole\ServiceClient();
        $siteUrl = \Bitrix\Main\Config\Option::get('mymodule', 'gsc_site_url');
        $date    = date('Y-m-d', strtotime('-3 days')); // GSC: данные с задержкой 2-3 дня

        $rows = $client->getSearchAnalytics(
            $siteUrl,
            $date,
            $date,
            ['page', 'query']
        );

        $connection = \Bitrix\Main\Application::getConnection();

        foreach ($rows as $row) {
            $connection->queryExecute(
                'INSERT INTO b_gsc_analytics (DATE, PAGE, QUERY, CLICKS, IMPRESSIONS, CTR, POSITION)
                 VALUES (?, ?, ?, ?, ?, ?, ?)
                 ON DUPLICATE KEY UPDATE
                   CLICKS = VALUES(CLICKS), IMPRESSIONS = VALUES(IMPRESSIONS),
                   CTR = VALUES(CTR), POSITION = VALUES(POSITION)',
                [
                    $date,
                    $row->getKeys()[0], // page
                    $row->getKeys()[1], // query
                    (int)$row->getClicks(),
                    (int)$row->getImpressions(),
                    round($row->getCtr() * 100, 2),
                    round($row->getPosition(), 1),
                ]
            );
        }

        return __CLASS__ . '::run();';
    }
}

Table b_gsc_analytics:

CREATE TABLE b_gsc_analytics (
    ID          INT AUTO_INCREMENT PRIMARY KEY,
    DATE        DATE NOT NULL,
    PAGE        VARCHAR(2048) NOT NULL,
    QUERY       VARCHAR(512) NOT NULL,
    CLICKS      INT DEFAULT 0,
    IMPRESSIONS INT DEFAULT 0,
    CTR         DECIMAL(5,2) DEFAULT 0,
    POSITION    DECIMAL(6,1) DEFAULT 0,
    UNIQUE KEY idx_date_page_query (DATE, PAGE(500), QUERY(200))
);

URL Inspection: Page Indexing Status

Checking indexing status via API allows you to show in the product card whether the page is indexed and what the coverage status is.

public function inspectUrl(string $siteUrl, string $pageUrl): array
{
    $request = new \Google\Service\SearchConsole\InspectUrlIndexRequest();
    $request->setInspectionUrl($pageUrl);
    $request->setSiteUrl($siteUrl);

    $response = $this->service->urlInspection_index->inspect($request);
    $result   = $response->getInspectionResult();

    return [
        'verdict'              => $result->getIndexStatusResult()->getVerdict(),
        'coverage_state'       => $result->getIndexStatusResult()->getCoverageState(),
        'last_crawl_time'      => $result->getIndexStatusResult()->getLastCrawlTime(),
        'robots_txt_state'     => $result->getIndexStatusResult()->getRobotsTxtState(),
        'indexing_state'       => $result->getIndexStatusResult()->getIndexingState(),
        'canonical'            => $result->getIndexStatusResult()->getGoogleCanonical(),
    ];
}

SEO Data Dashboard in the Admin Panel

Based on the collected data, reports are built in the Bitrix admin panel. For example:

• Top queries with low CTR but high impressions – potential for improving title/description.
• Pages with declining positions – need content team attention.
• Pages with zero clicks – possible sign of incorrect meta tags or cannibalization.

Data from b_gsc_analytics is joined with b_iblock_element by URL – you get direct links to edit the material.

Automated Sitemap Update

After generating the sitemap, a request for reindexing is sent via the Sitemaps API.

Case Study: Real Savings

For a client with a catalog of 50,000 products, we set up the agent and dashboard. Before the integration, the SEO team spent 4 hours weekly on manual data collection. After implementing our solution, data updates automatically daily, saving 15 hours per month – equivalent to $750 at $50/hour. The client reported a 40% increase in SEO productivity.

What Limits Does the Search Console API Have?

• URL Inspection: 2000 requests per day per property.
• Search Analytics: Data with a 2–3 day lag, depth of 16 months.
• Rows per response: up to 25,000 per request (filtering needed for large sites).
• Service Account must be added to GSC with "Full" access rights.

According to Search Console API documentation, these limits may change.

Typical Integration Mistakes

• Incorrect Service Account permissions: need "Full" access, not "Restricted".
• Running the agent too often: data updates once a day, more frequently is useless.
• Ignoring the data delay: requesting today's data returns an empty response.
• Missing index on the DATE column in the table: slows down insertion for large volumes.

What’s Included in the Integration

Timelines are for a typical project. Get an accurate estimate after analyzing your Bitrix instance. Order a consultation – we will calculate the cost and timeline individually.

Step-by-Step Guide for Self-Setup

1. Create a project in Google Cloud Console and enable the Search Console API.
2. Create a Service Account, download the JSON key.
3. Upload the key to the server in a protected directory (outside webroot).
4. Install the google/apiclient library via Composer in /local/.
5. Implement the ServiceClient class with key authorization.
6. Set up an agent for daily collection of Search Analytics.
7. Create the b_gsc_analytics table and indexes.
8. Display the dashboard in the admin panel.

Contact us if you need help at any stage. We guarantee results and provide documentation.

CommerceML: Why Standard Exchange Is Both a Lifesaver and a Trap

Standard exchange via CommerceML 2.0 on typical "Trade Management" or "Comprehensive Automation" can be set up in a day or two. Products, prices, stock, orders—all via XML files on a schedule. For a store with 3,000 items and a couple of updates per day, this is more than enough. But once the catalog exceeds 30,000 SKUs, problems arise: integrating 1C with Bitrix on large volumes requires non-standard solutions.

Why does CommerceML slow down with catalogs over 100,000 items?

bitrix_1c_exchange.php generates XML on the Bitrix side, and 1C retrieves and parses it. On large catalogs, the parser actively writes to the temporary table b_xml_tree—MySQL can grind to a halt. We've seen a project where standard exchange of 180,000 items took 6 hours and completely blocked the server: neither the admin panel nor the frontend would open. The solution is incremental exchange. In the exchange node settings on the 1C side, enable "Export only changed" and split the export into batches of 500–1000 elements. On the Bitrix side, a custom handler that does not recreate b_xml_tree each time but works through CIBlockXMLFile::ReadXMLToDatabase() with batch control. A catalog of 200,000 SKUs updates in 8–12 minutes.

Another pitfall is EXTERNAL_ID. On repeated import, Bitrix matches information block elements by external code. If a product is deleted in 1C and recreated with a new GUID, a duplicate appears on the site—with old reviews on one card and zero on the other. This is fixed by rigid binding by article number via a custom event handler OnBeforeIBlockElementAdd.

How to avoid duplicates during repeated import?

We bind products not by GUID but by article number. Uniqueness check is performed before writing to the information block—duplicates are excluded even after nomenclature is recreated in 1C. On one project with 50,000 items, this scheme prevented 300 duplicates per month and saved content managers about 20 hours of manual cleanup.

Custom 1C Configurations: When CommerceML Falls Short

"We have a standard configuration"—says every second client, and then we open the database and see 200 custom processing routines, renamed attributes, and custom sales documents. CommerceML works with a fixed XML structure. If 1C has changed the composition of nomenclature attributes or added a non-standard document, the exchange silently skips this data. Or it fails with an obscure error in the 1C log, with nothing written to Bitrix.

In such cases, we implement custom export. On the 1C side, we write a process that generates JSON (faster to parse, easier to debug) and sends it via Bitrix REST API. Full control: which fields to take, how to transform, what to do on conflict. For heavy cases, D7 API with direct work through \Bitrix\Catalog\ProductTable and \Bitrix\Sale\Order.

What are the key steps to set up 1C integration?

Custom REST is justified when:

• Non-standard nomenclature attributes;
• Multiple price types (retail, wholesale, dealer, promotional, regional, currency)—standard exchange sends only one type;
• Multi-warehouse with different stock levels and need to select a warehouse on the site.

Prices, Stock, and Multi-Warehouse

Standard exchange can transfer one price type. In reality, there may be 15: each with its own buyer group and priority. Mapping between 1C price groups and Bitrix user groups is a separate engineering challenge. Especially when discounts overlap and you need to determine which price wins.

Multi-warehouse adds another layer: product is in stock in Moscow, out of stock in St. Petersburg, and "on order" in Novosibirsk. The site must show availability per location, allow selection of pickup points, and calculate shipping from the nearest warehouse where the product is physically available. The standard Bitrix warehouse module (catalog.store) handles display, but we write the "which warehouse to ship from" logic separately. For one manufacturing holding, we implemented a custom stock aggregator that calculated balance across 8 warehouses in 2 seconds—reducing shipping errors by 80%.

Orders and Document Flow

An order from the site goes to 1C, a sales document is created, goods are reserved. Statuses come back. The main nuance is partial shipment: the client ordered 5 items, 3 are in stock, 2 will arrive in a week. 1C creates two sales documents. Bitrix out of the box cannot split one order into several shipments—we extend the OnSaleOrderSaved handler to create child orders and synchronize statuses for each.

Documents in the personal account—invoices, acts, waybills from 1C—are served via REST; PDF is generated on the 1C side and cached on CDN. The buyer downloads not from 1C directly (that would kill the server) but from cache.

Batch import with portion control reduces MySQL load and prevents locks (source: Wikipedia).

Monitoring: Not "Set and Forget"

Exchange can silently break: the script ran, no errors in log, but 200 products didn't update due to invalid UTF-8 in the name. Or 1C changed the date format in an update—all prices came in as zero.

Minimum set we install on every project:

• Telegram alert if exchange time increases 3+ times from average.
• Stock discrepancy check: script compares b_catalog_product.QUANTITY with what 1C provides, and alerts when delta exceeds 5%.
• Dashboard: last sync, number of processed items, queue, errors.

For high-load projects, we add async queues on Redis or RabbitMQ. Exchange does not block the web server, data is not lost during temporary 1C outages. On one online store with 2 million orders per year, we implemented this scheme—recovery time after failures dropped from 3 hours to 10 minutes.

Linking with Bitrix24 for Document Flow Automation

If besides the site there is a corporate portal on Bitrix24, we link it too. Counterparties from CRM go to 1C, invoices from 1C appear in deal cards. The manager sees accounts receivable and mutual settlements without switching windows. Deal closed—documents generated automatically.

Payment received in 1C → logistician gets a task for shipment in Bitrix24. Goods shipped → manager sees notification. Automatic tasks based on events from 1C—via Bitrix24 REST API webhooks. This link reduces manual entry by 70% and eliminates forgotten shipments.

How We Set Up Integration: Step-by-Step Process

1. Audit of 1C Configuration. Review the structure of directories, documents, attributes. Identify custom modifications. Assess data volume (number of SKUs, orders, warehouses).
2. Design Exchange Schema. Agree on data set: products, prices, stock, orders, documents. Determine sync interval and mechanism—CommerceML or custom REST.
3. Configure Standard Exchange. Set up CommerceML, batch mode, binding by article. Verify data transfer correctness on a test catalog.
4. Extended Integration. For complex configurations, write custom handlers on both 1C and Bitrix sides. Incorporate multi-warehouse, multiple prices, partial shipment.
5. Monitoring and Warranty. Set up alerts, dashboard, documentation. Train operators. After launch, warranty support.

Timelines and What's Included

Work results include: documented exchange schema, configured synchronization scenarios, monitoring dashboard, operator training, and warranty support after launch. Pricing is calculated individually—it depends on the complexity of the 1C configuration, catalog size, and required automation level. We'll evaluate your project in 1 day—write to us, let's discuss. Order integration and get stable exchange in 1–2 weeks.

We have completed over 50 1C integrations for online stores and manufacturing companies. The team's average experience is 7 years, and we have certified 1C-Bitrix specialists. Our experience ensures that the exchange won't break in the first month and will run stably for years. For example, on a project with a catalog of 50,000 items, automation of exchange saved the client significant operational costs annually.

Contact us for a free audit of your 1C configuration—we'll find bottlenecks and offer the optimal solution.