Публикувано: Обновено:
Google Shopping has been announced for Bulgaria, but as of 29 October 2026 there is no confirmed launch date. On 14 July 2026 the Google Merchant Center Help Center listed Bulgaria among 14 new markets for Shopping ads and free listings. By 18 August that announcement had been removed, and Bulgaria is still missing from Merchant Center’s table of supported countries. The launch is expected, but the date is not confirmed, so the safest move is to have the store technically ready before it happens. The short answer to the “are we ready” question: if your product pages have structured data (schema markup), accurate real-time prices and availability, and images that meet minimal technical requirements, your store can participate technically, regardless of ad budget.
This article breaks down exactly the technical readiness of the site itself – not how to manage an ad campaign, but what needs to be in place at the code and product page level so your data can actually be accepted by Google Merchant Center. If you’re still building your store, see our pillar guide on online store development or the direct guide for the store product page, since that’s where much of this readiness is decided.
The quick reference: technical checklist

| Requirement | Why it’s mandatory |
|---|---|
| Structured data (Schema.org Product markup) | Google extracts price, availability, and attributes directly from the code |
| Unique GTIN/barcode for each product | A required identifier for most product categories |
| Synchronized price site ↔ product feed | Mismatches lead to product rejections |
| Images of at least 500×500 px (Google’s minimum for all products from 31 January 2027), clean background | Products with poor images get rejected or shown lower |
| Clear availability status (in stock/out of stock) | Showing a sold-out product hurts account trust |
| SSL certificate and a secure checkout | A mandatory condition for approving a Merchant Center account |
Structured data: the foundation without which nothing else works

Google Shopping doesn’t “read” your product page the way a human reviews it visually – it relies on structured data embedded in the code to extract precise information about price, availability, brand, and category. Without properly implemented Schema.org Product markup, even a perfectly presented product page remains invisible to the system.
According to Google’s documentation on structured data, a product page needs the product name, image, price and currency, and availability is strongly recommended. A page that misses a required field is not eligible for product results. The gap usually comes from the theme or plugin, so it tends to affect the whole catalog at once. If your platform is WordPress with WooCommerce, most modern themes and extensions implement basic structured data automatically, but a technical check is warranted rather than assuming it works out of the box.
Product feed: the bridge between the site and Google Merchant Center
The product feed is a structured file (typically XML or CSV) that sends information about your entire catalog to Google Merchant Center – separate from the site itself, but mandatory to keep synced with it in real time. A mismatch between the site’s price and the feed’s price leads to product disapprovals, and repeated mismatches can put the whole account at risk, because Google treats the discrepancy as potentially misleading for consumers.
For WooCommerce or OpenCart stores, extensions exist that generate the feed automatically based on the existing product data, but the quality of the resulting feed depends entirely on how complete and accurate the underlying data in the system is – categories, brand, GTIN code, attributes. Empty or incomplete fields in the store admin get carried straight through as empty fields in the feed.
Images and visual requirements
Product images for Google Shopping have specific technical requirements, different from general web design best practices. Google has announced a minimum of 500×500 pixels for all products from 31 January 2027 and recommends 1500×1500 pixels or larger for the best results in every listing format. The background should be clean (typically white or neutral), and the image must not contain overlaid text, logos, or promotional elements – a requirement many stores violate by reusing the same images optimized only for visual appeal on the site itself.
If your product images are currently marketing-oriented (with promotional text or badges), you’ll need separate, clean versions specifically for the feed. That’s a technical detail easily overlooked in the initial readiness planning.
Beyond Google’s own compliance requirements, the image files themselves should also be technically optimized for speed – a product page with dozens of heavy, unoptimized images slows down the load time regardless of Shopping readiness. According to web.dev’s course on images, correct format and image compression are among the most common factors slowing down pages with heavy visual content – which by definition is every product catalog.
Availability and price: why real-time synchronization is critical

Google actively checks whether the displayed price and availability match the site’s actual state at the moment a customer visits. A store that updates its availability just once a day through a manual process risks systematic mismatches – especially for products with high turnover of stock.
The technically safest solution is a direct link between the store’s database and the product feed, with no manual step involved – automation that should be in place before Google Shopping launches in Bulgaria, not built afterward under pressure.
For stores with a large catalog and frequent availability changes – especially during the pre-holiday season when both traffic and order volume grow rapidly – manual feed updates are simply not practical. That’s exactly why automated synchronization isn’t a “nice to have” feature, but a baseline requirement for any store with realistic ambitions to participate fully in Google Shopping from day one.
Common technical mistakes
Certain technical mistakes are common. The first is a missing GTIN. Products that genuinely have none (custom or handmade items) should be marked with identifier_exists set to no, never given an invented code. The second is a mismatch between the store’s own categories and Google’s official Product Taxonomy, leading to incorrect categorization. The third is images containing overlaid text or logos that violate the visual requirements. The fourth is neglected “sold out” statuses, remaining active long after the actual product has run out. The fifth is missing SSL on the entire site, not just the checkout page. The sixth is a slow, irregularly updated feed instead of an automated link to the database. The seventh is underestimating the time needed for first-time Merchant Center account approval – a process that takes days, not hours.
Frequently asked questions
When exactly does Google Shopping launch in Bulgaria?
There is no confirmed date yet. Google listed Bulgaria among 14 new Shopping markets on 14 July 2026, then removed the announcement by 18 August 2026. As of 29 October 2026, Bulgaria is not in Merchant Center’s supported countries table, so treat any specific date as unconfirmed.
Do I need an active ad campaign to be checked technically?
No – the technical readiness (structured data, feed, images) is independent of the decision whether to run a paid campaign. Building it in advance is worthwhile regardless of when you decide to launch ads.
Do all products need a GTIN code?
Most categories require one, but exemptions exist for products with no standard produced barcode (for example, custom-made items). In these cases you set the identifier_exists attribute to no. Google warns products where it is set to no but a GTIN actually exists.
How do I know if my product images meet the requirements?
Check the resolution (at least 500×500 px, the minimum Google has announced from 31 January 2027), the cleanliness of the background, and the absence of overlaid text or logos. Google Merchant Center gives specific feedback on rejected images after the initial feed submission.
Is WooCommerce’s automatic schema markup enough?
The default implementation in most modern themes covers the basic mandatory fields, but it warrants a technical check on the specific site – not all themes and extensions implement the full set of recommended (not just required) attributes.
How long does it take to make a store technically ready?
It depends on the current state of the data – a store with clean, complete product data can be ready in days, while a store with incomplete or unstructured product information may need weeks of technical work on the data before the feed can be used.
Is it worth preparing the store now, if the launch date is not confirmed?
Yes. Structured data, feed automation and image reshoots take real time. If the launch is announced close to a peak season such as Black Friday, a store that is already ready loses nothing, while a store that starts then risks missing the strongest sales period.
Conclusion: technical readiness is a prerequisite, not an option
Google Shopping in Bulgaria opens a real new opportunity for online store visibility, but only for those whose technical foundation is ready to receive it. Structured data, a synchronized product feed, and correct product images aren’t “advanced” features – they’re the baseline conditions for the account to even be approved.
If you’re not sure whether your online store is technically ready, the CreateWeb team can review your structured data and feed products. Get in touch with us for a technical audit before Google Shopping launches.
For related resources, see also: online store development: complete guide · store product page · which e-commerce platform to choose · WooCommerce vs OpenCart · technical SEO for WordPress · online payments in Bulgaria
CreateWeb services: website development · website maintenance