Before launching a site on 1C-Bitrix, it is important to check not only the design, forms and catalog. If you open a project for indexing too early, search engines may see technical pages, duplicates, empty sections, test URLs, and wildcard meta tags. Fixing this after pages get into search is more expensive than covering the risks before release.
Pre-launch SEO setup is a check of the site structure, crawl rules, site map, meta tags, duplicates, redirects, catalog and analytics. Online stores, corporate websites with a large number of sections and projects where 1C-Bitrix is connected to CRM, warehouse, 1C or marketplaces should be especially careful about this.
Why SEO needs to be set up before opening the site for indexing
The launch of a website is often perceived as the moment when the project becomes available to users. Another point is important for SEO: when the site becomes available to search robots. If the structure is not ready by this time, crawling may begin not with commercially important pages, but with technical garbage.
On projects on 1C-Bitrix, problems often arise due to service sections, filtering parameters, catalog sorting, test pages, duplicate cards and incomplete landing pages. Externally, the site may look ready, but inside it already has dozens or hundreds of URLs that should not be indexed.
The main task of verification is not to “speed up progress in one day,” but not to lay errors in the technical basis. A properly prepared website is easier to develop: adding sections, expanding the catalog, connecting analytics, launching advertising and building a content strategy without constantly returning to basic problems.
Site structure and URL: what should be ready before release
Before launching, you need to check how the main sections of the site are organized: services, catalog, product cards, articles, contacts, landing pages. Each important page must have a clear meaning, the correct address and place in the structure. If the page is not needed by the user and does not cover the search intent, it is too early for it to get into the index.
For a corporate website, pages of services, directions, cases and contacts are critical. For an online store - categories, subcategories, product cards, brand pages and filters, if they are used as landing pages. An error at this level leads to the fact that search engines see not the business architecture, but a set of random addresses.
URLs must be stable. Before the release, it is undesirable to open indexing if the addresses of sections have not yet been agreed upon, the names of categories are changed, product cards are moved between sections, or the issue with Cyrillic and transliteration has not been resolved. The later the structure changes, the more redirects and manual checks will be required.
Robots.txt: which areas of the site should not be given to search robots
The robots.txt file helps manage the crawling of your site by search robots. On 1C-Bitrix it is usually used to restrict access to administrative, service and technical areas. But robots.txt cannot be considered a universal way to remove pages from search: it controls crawling, and does not guarantee the exclusion of already known URLs.
Before starting, you need to check whether the administrative part, customer portal, shopping cart, ordering, internal search results, test sections and URLs with technical parameters are open to bypass. Particularly dangerous for an online store are pages that create many combinations without independent value: sorting, time parameters, technical filtering options.
Reverse error - close too much. Sometimes robots.txt accidentally blocks CSS, JavaScript, images, or important sections of the catalog. As a result, the search robot sees the page differently than the user, or is unable to bypass commercially significant URLs.
Sitemap.xml: which pages should be included in the sitemap
Sitemap.xml helps search engines understand which pages the site owner considers important. But the sitemap should not be a list of all available URLs in a row. It needs to include canonical, useful and indexing-ready pages: main sections, services, catalog categories, product cards, articles and landing pages.
Before launching, it is important to check if the sitemap.xml contains duplicates, test pages, closed sections, URLs with parameters, empty categories and pages that give an erroneous status. If garbage gets into the map, the search engine receives a conflicting signal: the site asks to bypass pages that are not ready to be shown to the user.
On large directories, the sitemap can be split into several files. This is fine as long as the structure is clear and automatically maintained. When downloading from 1C or updating the catalog, you need to make sure that disabled products, old URLs and cards without content do not appear in the map.
Title, description and H1: how to avoid template duplicates
In 1C-Bitrix you can manage SEO fields of pages, sections and catalog elements. This is convenient, but at the start it often leads to another problem: meta tags are formed according to one pattern and begin to repeat themselves. For a small site this is several duplicates, for an online store - hundreds of identical title and description.
Before launching, you need to check the H1, title and description for the main commercial pages. H1 should accurately describe the content of the page, title should help the search engine and user understand the topic, description should briefly explain the value of the page in the snippet. Meta tags should not become a bunch of keywords.
For the catalog, it is better to define different templates in advance: for the category, subcategory, product card, brand and landing page. A universal template for the entire catalog quickly creates duplicates and weak snippets, especially if the site uses properties, regions or product types.
Canonical and duplicates: filters, sorting, parameters and pagination
Duplicates are one of the most common SEO problems on catalog sites. The same set of products can be accessed through a sort, filter, parameter, alternate path, brand page, or internal link. This may be convenient for the user, but for the search engine the question arises: which version is considered the main one.
Canonical helps specify the preferred page address, but should not be the only way to deal with duplicates. If internal linking, sitemap, redirects and actual content contradict canonical, the search engine may choose a different version. Therefore, before launching, you need to check the entire signal chain.
Filters require special attention. If the filter creates a full-fledged landing page with demand, products and clear navigation, it can be considered an SEO page. If a filter creates a technical combination without demand or value, it is better not to open such a page for indexing as an independent result.
Catalog and product cards: what to check before launching an online store
If a site on 1C-Bitrix is used as an online store, the SEO check should include the quality of the catalog. Search engines and users evaluate not the platform, but specific pages: categories, cards, product availability, descriptions, images, prices, characteristics and navigation.
Before launching, you need to check that the categories are not empty, the cards do not look like technical blanks, the products have names, characteristics, images and the correct membership in the sections. If a card is created from an upload, but does not contain a useful description and a normal image, it formally exists, but does not help sales.
The logic of remainders is also important. If the catalog is connected to 1C, a warehouse system or CRM, you need to check how the site displays products without availability. For some businesses, such cards need to be left accessible, for others they need to be hidden, transferred to an archive, or offered alternatives.
Images, alt and speed: where SEO intersects with UX
Images affect more than just the appearance of the site. They are involved in the perception of cards, loading speed, quality of snippets and page accessibility. At the start of a project, temporary images, heavy banners, empty alts and images with incorrect sizes are often left behind.
Before launching, you need to check hero blocks, images in the catalog, product cards, illustrations in articles and interface icons. Large images should be optimized, the dimensions should be appropriate for the place of use, and the alt should describe the meaning of the image where it is truly useful.
Alt does not need to be turned into an SEO field for a set of keys. If the image shows the product, it is logical to describe the product. If this is a decorative icon, there is no need for excessive description. If this is a diagram, it is worth briefly conveying its contents.
Redirects, HTTPS, site mirror and server response errors
Before starting, you need to check which version of the site is considered the main one: with HTTPS, with or without www, with or without a trailing slash. The user may not notice the difference, but to the search engine, different versions of the addresses may appear as separate URLs.
If a site moves from an old platform to 1C-Bitrix, redirects become a critical part of the release. Old pages that had traffic, links or rankings should not lead to an error or main page without logic. For them, you need to prepare a correspondence map in advance: old URL → new URL.
A separate risk is a test domain. If during development it was open for crawling, some pages could be included in searches even before the main site was launched. Before release, you need to check whether test addresses are visible to search engines and whether internal links lead to temporary URLs.
Analytics and webmasters: what to connect to the first visitors
SEO setup before launch does not end with robots.txt and sitemap.xml. You need to connect tools in advance that will show how the site is indexed, what errors occur and what the first visitors do. Without analytics, a release turns into a blind launch.
The minimum set for most projects is Yandex Metrica, Yandex Webmaster and Google Search Console, if the project is focused not only on Yandex. For a commercial site, it is also important to set up goals: submitting a form, clicking on the phone, submitting an enquiry, going to the messenger, placing an order, adding a product to the cart.
For an online store, you need to check e-commerce analytics separately. If a store is launched without correctly transmitting events for product views, carts, and orders, the marketer will not be able to accurately assess the effectiveness of the catalog and advertising channels.
Pre-launch SEO checklist for a site on 1C-Bitrix
Before opening a site for indexing, you should go through a short but substantive checklist. Its task is not to replace an SEO audit, but to identify errors that are most dangerous to carry into release.
| What to check | Why is it important | Risk due to error | Who should participate |
|---|---|---|---|
| Site structure and URL | Search engines should see a clear hierarchy of sections | Random, temporary or weak pages are included in the index | SEO specialist, project manager, developer |
| Robots.txt | The file controls bypass of service areas and technical sections | Important pages are closed and junk URLs are crawlable | SEO specialist, developer |
| Sitemap.xml | The map must pass ready-made and canonical URLs | Duplicates, empty pages or old addresses are sent to search engines | SEO specialist, developer |
| Title, description and H1 | Metadata helps create relevance and understandable snippet | Template duplicates and weak commercial pages appear | SEO specialist, editor, content manager |
| Canonical and duplicates | You need to specify your preferred page versions | Filters, sortings and options compete with the main pages | SEO specialist, developer |
| Catalog and product cards | Commercial pages must be complete and useful | The search includes empty categories, cards without descriptions and products without value | E-commerce manager, content manager, developer |
| Redirects and site mirror | All versions of addresses must lead to the main structure | There are duplicates of HTTP/HTTPS, www/non-www and losses when moving | Developer, SEO specialist |
| Analytics and goals | After launch, you need to immediately see requests, errors and user behavior | The team does not understand which pages work and where conversion is lost | Marketer, analyst, developer |
This checklist should be repeated not only before the first launch. It is needed before major changes: moving the catalog, changing the URL structure, connecting new filters, redesign, integration with the accounting system, or launching regional sections.
When SEO settings require a developer, not just an editor
Some SEO tasks can be solved by an editor or content manager: fill out H1, prepare descriptions, check category texts, clarify alt for images. But on a website based on 1C-Bitrix, many problems are deeper: in templates, information blocks, URL generation rules, filter logic, redirects, exchange with 1C and catalog settings.
If the title and description are formed incorrectly for hundreds of pages, this is not a task for manual filling. We need the correct template. If filters generate thousands of technical URLs, it's not a matter of text. It is necessary to change the indexing logic, canonical, links and crawl rules. If goods come from the accounting system without descriptions, images or correct sections, you need to sort out the data exchange.
Pre-launch SEO should be part of development, not a separate last-day review. DevAstro can connect to the site's technical support, check the SEO basis before indexing, fix problems in templates and the catalog, and also finalize the architecture as part of website development or online store development. For projects with data exchange, it is important to test API integrations in advance so that the catalog, stock levels and commercial pages do not break SEO after launch.
FAQ
What should be configured for Bitrix SEO before launch?
Clean URLs, titles, descriptions, H1, canonical tags, sitemap.xml, robots.txt, redirects, breadcrumbs, metadata templates, catalog indexation, images, speed and analytics should be prepared before publication.
Why should SEO not wait until after release?
After release, search engines can discover duplicates, empty metadata, closed pages, 404 errors and weak structure quickly. These issues can be fixed later, but part of indexation quality may already be lost.
Should catalog filters be indexable?
Only commercially useful filter combinations should be indexed: those with search demand, unique copy and correct canonical rules. Indexing all filters can create thousands of duplicates.
Which structured data is useful for ecommerce?
Organization, BreadcrumbList, Product, Offer, AggregateRating when data exists, and FAQPage for visible questions are usually relevant. Structured data should match visible page content.
How should SEO be monitored after launch?
During the first days, monitor sitemap processing, robots, canonical tags, redirects, 404 errors, indexation, server logs, organic traffic and goals against a recorded pre-launch baseline.
Should every catalog filter be indexable?
No. Index only combinations with real demand, stable URLs, unique metadata and useful content. Other parameters should follow controlled non-indexable rules.
