SEO & Storefront Promotion

Most of a store's SEO works automatically, with no manual setup: the platform prepares pages for search crawlers on its own, marks up products with structured data, and maintains a sitemap and product feeds. This page covers what happens by itself, and what's worth configuring further: product feeds into ad channels, redirects when URLs move, and connecting Search Console.

What works automatically

On every catalog, price or stock change, the platform regenerates crawler- and AI-agent-facing pages for your storefront — separate from what a live shopper sees (they get the regular fast web app).

• Meta tags and titles — title/description for the homepage, category, collection and every product, truncated by character (not byte), so multi-byte languages — Georgian, Arabic, Chinese — are never cut mid-character.
• Canonical URLs — every page has one "primary" address; duplicates (e.g. an old and a new product URL) correctly point to the current one, so link equity isn't lost.
• hreflang — if the storefront has several languages enabled, search engines get the language-version links tied together.
• sitemap.xml — the site map updates automatically and includes products, categories, collections and articles; product entries carry a last-modified date (lastmod) taken from the actual product data — search engines see what really changed instead of re-crawling everything. Products with photos also get an image sitemap entry — direct image links for Google Images indexing.
• robots.txt — generated and kept up to date automatically, no manual file editing.
• Structured data (JSON-LD):
  • on the homepage — Store/Organization plus site-search markup (Google can show a site search box right in results);
  • on a product page — Product/Offer with price, availability, barcode (GTIN), SKU, brand, condition, shipping and return terms;
  • for a product with several variants (color/size) — ProductGroup covering all variants at once: their SKU, barcode, price, weight — Google understands it's one product with option choices, not several separate listings;
  • breadcrumbs (BreadcrumbList) on every page.
• Bot- and AI-agent-facing prerender — the homepage, catalog, collection page, collections list and product page are served to search crawlers and AI crawlers as a fully rendered HTML page with complete content (not an empty JS shell) — this covers both regular search bots and AI shopping-assistant crawlers.
• Custom domain is reflected everywhere above: if the storefront has its own domain connected, canonical URLs, sitemap, robots.txt and llms.txt automatically point to your domain rather than the platform subdomain — see Custom domain.

None of this needs to be triggered manually — it refreshes on its own whenever the catalog or location profile changes.

Product feeds for ad channels

Beyond SEO markup for organic search, the platform can export the catalog as separate product feeds — for ad accounts and marketplaces that need a file in their own format (XML/CSV). These connect as extensions in the App Store, per location:

All feeds are built from the same catalog and update automatically as products, prices and stock change — nothing needs to be regenerated by hand.

Storefront readiness for AI agents

Separate from classic SEO, the platform prepares the storefront for being "read" increasingly not by people but by AI agents — voice assistants, shopping bots, AI search systems:

• every domain has an llms.txt page — a short machine-readable site map made specifically for language models: what the store is, what products and categories exist, where to find the API;
• product and catalog pages served to an AI crawler carry an expanded description — characteristics, variants, availability, shipping and return terms — things normally hidden behind interactive UI elements and invisible to a plain crawler;
• external AI agents can programmatically search products and place orders through the public Guest API/MCP — details in Guest API for AI Agents.

Redirect manager and 404 log

When a store's URL structure changes (migrating from another platform, changing category/product URLs), old links start returning 404s — you lose search-engine and social traffic and link equity. The Site Studio → Storefront → "SEO & Feed" section handles this without a developer:

• Redirects — a table of "from → to" rules: exact match, prefix match, or regex match; response code 301 (permanent), 302 (temporary) or 410 (permanently gone); rules can be toggled on/off and annotated.
• CSV import — if you're migrating from WordPress/WooCommerce and already set up redirects with the Redirection plugin, you can import the ready-made list as a single file instead of recreating rules by hand.
• 404 log — the platform tracks which addresses receive "dead" hits over the last 30 days (how many times, when last seen). Every log row has a "Create redirect" button that opens a new rule form with the address already filled in.
• A redirect applies to both search crawlers and live visitors: a bot gets an honest HTTP status (301/302/410) at the page-serving level — what matters for preserving rankings and link equity when URLs move; a person following an old link lands on the new address instead of a "Page not found".

Google Search Console and search analytics

Connecting Google Search Console to your domain gives you, inside Statistics, a breakdown of organic search queries: which keywords people find you by in Google, how many clicks and impressions they get, and your average ranking position. Regular traffic analytics (Google Analytics) doesn't provide this at all — search phrases are only visible through Search Console.

Organic-traffic rows in "Statistics" expand into a query table right there — no separate screen needed.

Connecting Search Console (verifying domain ownership) is a one-time step for the account; after that, data flows in for all your locations on that domain.

Custom domain and SEO

The public site lives on a platform subdomain by default (your-store.masamenu.tr). SEO addresses (canonical URLs, sitemap, product feeds, llms.txt) automatically rebuild around your custom domain once it's connected — that's the address worth using in ads, on signage, and the one search engines will see. Full setup instructions — Custom domain.

Related sections

• Online Store: Storefront and Selling — overview of the retail vertical
• Google Product Feed — the product feed for Google Merchant Center
• Custom domain — connecting your own domain
• Statistics — site traffic and organic queries
• Website builder — storefront styling
• Guest API for AI Agents — how AI agents see your storefront

FAQ

Do I need to configure anything manually for SEO to work?

Baseline SEO (meta tags, canonical, hreflang, sitemap, robots.txt, product structured data, bot prerender) works out of the box, no setup. The only things worth connecting manually are the ones that need an external account: product feeds (Google Merchant Center, etc.) and Google Search Console.

How does a search engine find out about a new product?

When a product is added, edited or removed, the platform regenerates that location's SEO pages and sitemap on its own — usually within seconds to minutes. From there, indexing speed depends on the search engine itself.

Do redirects apply right after saving?

Yes, a rule takes effect immediately for both bots and live visitors — no separate publish step is needed.

Can I bring over redirects from WordPress?

Yes — if you used the Redirection plugin (or another CSV export in its format), you can import the rule list as a single file in the "SEO & Feed" section.

What about Yandex and .ru domains?

Product export to Yandex exists (Yandex Goods), and baseline SEO (markup, sitemap, hreflang, redirects) works the same across every platform domain, including Russian brands. The "Statistics" organic-query breakdown is currently built on Google Search Console — for domains promoted through Yandex, that specific query breakdown isn't available yet; a Yandex.Webmaster-based equivalent is in progress.