Omnikyo/Help Center
Reference

Store SEO and visitor tracking

Your storefront appears in Google with a title, description and canonical URL; robots and a sitemap guide crawlers; and Meta Pixel tracks every shopper interaction so you can build audiences and measure ads.

বাংলায়: আপনার স্টোর Google এ একটা শিরোনাম, বর্ণনা এবং ক্যানোনিক্যাল ইউআরএল নিয়ে দেখা যায়। বট নির্দেশিকা এবং সাইটম্যাপ Google-কে বলে কোন পাতা দেখতে হবে এবং কোনটা নয়। Meta Pixel ক্রেতার প্রতিটা পদক্ষেপ পর্যবেক্ষণ করে যাতে আপনি দর্শক তৈরি করতে এবং বিজ্ঞাপন পরিমাপ করতে পারেন।

Where to find it: Settings › Store › the SEO and tracking section

Store titles and descriptions in Google

When your storefront is live and indexed, Google shows shoppers a title and description in search results. The title comes from your store name or a custom title you set; the description is your store name followed by "online store" or a custom description.

On your home page, Google uses the title and description you set in Store settings. On product pages, Google uses the product name as the title and the product description if one exists. On collection pages, the collection name is the title and the collection description (if you added one) is shown. On custom pages and blog articles, the page title is used; for articles, the article description or excerpt appears if one exists.

How your canonical URL is decided

A canonical URL is the unique address Google should treat as the real version of a page. Your storefront has two possible canonical origins: your custom domain (if you have one and it is active) or your free <slug>.omnikyo.com subdomain (for example, shopname.omnikyo.com). Google always chooses the custom domain if it is active; otherwise it uses the subdomain.

All shopper-facing URLs resolve to the same store one way or another — via your subdomain, custom domain, or a path on the app host — but only one of these origins appears in Google and in the sitemap.

When your store can be indexed

Your store appears in Google search results only when all of these are true: you are on a production deployment (not a local test or preview), your store is marked live, you have published a theme, your store has a resolvable canonical origin, and the page itself is indexable.

Pages that are never indexed, no matter the store's state, are cart (per-visitor state), checkout, confirmation (confidential) and search (unlimited facet combinations).

If your store is password protected, no page is indexed.

If any of these conditions fails, Google sees noindex instructions — the pages can still be crawled by Google (so links pass equity), but they will not appear in search results.

What robots.txt says

Your store automatically generates a robots.txt file at https://<your-store-origin>/robots.txt. When your store is live and indexable, the file tells crawlers not to index the cart, checkout, confirmation and search pages. The file also lists your sitemap.xml location so Google knows where to find your complete catalogue.

When your store is not live, not published, password protected, or cannot resolve its own canonical origin, robots.txt contains a single directive: Disallow: /, instructing crawlers to avoid the entire store.

The sitemap

Your store automatically generates a sitemap.xml file at https://<your-store-origin>/sitemap.xml. The sitemap lists up to 2,000 products, 500 collections and 5,000 URLs total. The sitemap includes your home page (updated daily), the /shop catalogue page (daily), the collections list (weekly), each individual collection (weekly), each product page (weekly), and any custom pages you have published (monthly).

The sitemap does not list cart, checkout, confirmation, search or unpublished pages.

If your store is not indexable — not live, not published, has no canonical origin, or is password protected — the sitemap returns a 404 instead of listing pages, because publishing a URL list for a hidden store defeats the point of the indexing rules.

Setting up Meta Pixel

Meta Pixel is a tracking code that collects data about shopper behaviour on your storefront so you can build advertising audiences and measure ad performance. To set it up, you need a Meta business account and a Pixel ID.

In Settings › Store › the SEO and tracking section, paste your Pixel ID. If Meta provides a test event code for testing before going live, you can paste that too. Both must be valid: Pixel IDs are digits only (1–32 digits), and test event codes are letters, numbers, hyphens or underscores (1–64 characters). Invalid codes are silently rejected.

Meta Pixel begins firing immediately once you save.

Events the Pixel fires

Meta Pixel tracks a shopper's journey through your store. Every page fires a PageView event. When a shopper views a product, a ViewContent event fires with the product ID, name, price and currency (BDT). When they add an item to the cart, AddToCart fires. When they open the checkout, InitiateCheckout fires. When they choose a payment method, AddPaymentInfo fires. When they place an order, Purchase fires with the order total, item count, items in the order and currency.

All pixel events carry an event ID for deduplication and a timestamp, so Meta can match pixel events with Conversions API events and deduplicate them.

Conversions API (server-side tracking)

In addition to the browser pixel, Omnikyo mirrors the PageView, ViewContent, AddToCart and InitiateCheckout events to Meta's Conversions API so those events are sent from your server instead of the shopper's browser. This server-side tracking is more reliable (ad blockers cannot prevent it) and gives Meta richer data.

Conversions API requires your Pixel ID, an access token from your Meta Ads account, and the platform flag to enable it. If the token is missing or invalid, API mirroring silently fails and only the browser pixel fires. Omnikyo never stores or displays the token — it lives in your business settings and is used only to send events to Meta.

Conversions API is configured in Settings › Integrations › Meta Ads rather than this section.

What the Pixel sees about orders

When a shopper completes an order, the Pixel captures the order total, item count, item IDs, and any UTM parameters (utm_source, utm_medium, utm_campaign, utm_term, utm_content) from the landing page. It also captures fbclid (Meta's click ID from ads), gclid (Google's), and several other marketing-source click IDs that may be present.

This attribution data lands on the order record in your Orders view under Source and Campaign, so you can see which ad account, campaign or creative drove each order.

Troubleshooting Pixel setup

If the Pixel is not firing, check that your Pixel ID is saved in Settings and is valid (digits only). Check your browser's developer tools (F12, Network tab) for requests to connect.facebook.net; if none appear, the Pixel is not loaded. If the Pixel is loaded but no events appear in Meta's Events Manager within a few minutes, check that your test event code (if you set one) matches the code in Events Manager.

If your Pixel ID is set but reviews are not showing on your storefront, that is a separate issue — reviews require merchant approval in the dashboard, not Pixel setup.

Other ways people ask this

  • সাইটম্যাপ কীভাবে কাজ করে
  • গুগলে স্টোর দেখাতে রোবটস ফাইল
  • মেটা পিক্সেল আইডি কোথায় পেতে হবে
  • স্টোর এসইও সেটআপ কীভাবে
  • ক্যানোনিক্যাল ইউআরএল কি
  • sitemap.xml kothay pabo
  • robots.txt e ki likha ache
  • Meta Pixel id paste korbo kothay
  • google e amar store dekhbe ki
  • search result e store title badlabo kivabe
  • facebook pixel tracking
  • Meta pixel ID validate korbo kivabe

Related pages

Related guides

Checked against the product on 2026-10-03.