Why structured data matters for a Bitrix site
Search engines read the text on a page, but they do not always understand what each number means. A figure next to the word “sum” could be a price, an old price or a delivery fee. Schema markup removes the guesswork by labelling the name, price, availability, author and publication date explicitly.
The upside is a chance of rich results in search: price, availability, breadcrumbs. There is no guarantee, because the search engine decides whether to show them. Without correct markup, though, the chance does not exist at all.
Some off-the-shelf Bitrix templates already include markup, but it is often outdated, incomplete or lost when a designer customised the layout. So the first step is checking what your pages output today.
Format and placement in Bitrix templates
Google recommends JSON-LD: a separate script holding the data, independent of the page layout. It is easier to maintain than attributes scattered through HTML tags. Yandex also reads JSON-LD for the main types. If old microdata attributes remain in the template, make sure they are not describing the same product a second time.
The code goes into the component template that outputs the data: the product card, the detail page of a news item or blog post, the breadcrumb chain. Edit a copy of the template inside your own site folder, not the system file, because a core update will wipe changes made to system files. Pull values from infoblock and trade catalog fields through variables rather than typing them in by hand.
If composite cache is enabled, check that the markup does not keep showing an old price after the catalog changes.
Which schema types you actually need
You do not have to mark up everything. Cover the main templates first:
- Organization or LocalBusiness — on the home page or in the shared template: name, logo, phone, address, opening hours
- Product and Offer — on the product card: name, description, images, brand, SKU, price, UZS currency, availability, page URL
- BreadcrumbList — the home, catalog, section, product trail, added once in the navigation component
- Article or BlogPosting — headline, publication and modified dates, author, image
- FAQPage — only when the page has a genuine question-and-answer block
Products without a published price
Many companies in Uzbekistan do not show prices and ask visitors to submit a request or message them on Telegram. That is a legitimate choice, but you must not invent a price for the markup. Keep Product with its name, description, images and brand, and leave out the Offer block with the price. You will not get a price snippet, but search engines still receive a structured description of the item.
In practice this is a condition in the template: if the price field is empty or says “on request”, the Offer block is skipped. Without that check the markup goes out with a zero price and validators start complaining.
The same logic applies to ratings. Mark them up only when real reviews are visible on the page. Putting an identical rating on every product breaks search engine guidelines.
Common Bitrix markup mistakes
These problems appear most often after a template change or a module installation:
- The price in the markup differs from the price on the page
- The currency is missing or wrong
- Markup appears on only some products because the template ignores empty properties
- Two sets of markup for one product, one from the old template and one from a new module
- A rating is marked up while the page shows no reviews
- A Marketplace module was installed without checking it against your infoblock structure
Rollout and testing steps
Ready-made modules save time, but they also deserve a test on several page types before launch. A sensible sequence looks like this:
- List your page templates: product, category, article, contacts
- Decide the markup type and required fields for each
- Find out where the template gets its data and whether it is always filled in
- Implement on a test copy of the site
- Run pages through Google’s Rich Results Test and the Yandex markup validator, including a product with a price, one without a price and one without stock
- After moving to the live site, review the enhancement reports in Search Console once pages have been recrawled
Where to start
A practical order is products, breadcrumbs, company details, then articles. Markup placed in a template works at once for every page of that type, so the effort scales well. Keep a note of which template received which markup, so a future redesign does not silently drop it.
If your site runs on Bitrix and markup is already in place but Search Console shows errors, or you are planning wider SEO optimisation in Uzbekistan, the markdev team can review your templates and point out what to fix first. Send us a short description of the task and we will talk it through.
FAQ
Which schema format should I use on Bitrix?
JSON-LD suits most cases. Google recommends it, it is separate from the layout and easier to maintain, and Yandex supports it for the main types. Just make sure old attribute-based markup is not duplicating the new one.
What if my website does not show prices?
Do not make up a price. Mark up Product with its name, description, images and brand, and omit the Offer block with the price. You will not get a price snippet, but search engines still get a structured description.
Where in Bitrix do I add schema markup?
In a copy of the relevant component template inside your own site folder: product card, article detail page, breadcrumb chain. Do not edit system files, because a core update will erase the changes.
Does correct markup guarantee a rich snippet?
No. Correct markup only makes rich results possible. Whether they appear is the search engine’s decision.
Let’s look at your task for free
Leave your contact — in a 15-minute call we’ll show where leads get lost and what to fix first.