• Pricing
  • Docs
Log inStart building

The platform that grows with your business.

From your first sale to global expansion. One unified platform for retail, wholesale, and everything in between.

Backed by

Zemuria Venture Studio

Commerce

  • Platform
  • Storefront Builder
  • Commerce
  • Digital Products
  • Payments
  • Shipping
  • Integrations

Growth

  • AI Sales Agent
  • Optimize
  • Marketing & Email
  • Content & Blog
  • Reviews
  • Customer Accounts
  • Analytics
  • SEO Features

Company

  • About
  • Pricing
  • Customers
  • Careers
  • Partners
  • Experts
  • Startups
  • Changelog

Developers

  • Developer overview
  • API documentation
  • API reference
  • Quickstart
  • Authentication
  • MCP server
  • CLI
  • Open source

Support

  • Contact us
  • Help centre
  • System status
  • Trust centre
  • Security policy

Compare Platforms

  • Mercemur vs Shopify
  • Mercemur vs WooCommerce

Legal

  • Legal overview
  • Terms & Conditions
  • Privacy Policy
  • Cookie Policy
  • Refund Policy
  • Sub-processors
  • Accessibility

Contact

Zemuria Inc.

1007 N Orange St., 4th Floor, #1189
Wilmington, Delaware 19801

support@mercemur.com

Copyright © 2026 by Mercemur, a Zemuria Inc. brand.

  • Terms of service
  • Privacy
  • Refund

Built for search engines from the start

Structured data, sitemap, robots, social cards, canonicals, RSS auto-discovery. The technical SEO work that usually takes two weeks is already done.

SEO is the difference between a store that has to buy every visitor and a store that gets visitors for free. Paid traffic costs more every year. Organic traffic compounds. The brands that win on a five-year timeline are the brands that took SEO seriously from day one.

Most ecommerce platforms treat SEO as an add-on. Structured data is a plugin. Sitemap is a plugin. Canonical URLs require a developer. Open Graph cards work on the home page but not on category pages. Multi-language hreflang requires three settings that nobody documents.

Mercemur builds SEO into every page. Structured data on products, blog posts, and breadcrumbs. Sitemap and robots routes generated automatically. Open Graph and Twitter Cards on every URL. Canonical URLs emitted server-side. RSS feeds auto-discoverable. The technical SEO work that usually takes a developer two weeks is already done before you log in for the first time.

You focus on content, products, and reviews. The platform handles the technical SEO that crawlers care about.

Structured data

Every page emits structured data so search engines understand what they are looking at:

Product pages

Product schema with name, image, description, brand, SKU
Offer schema with price, currency, availability, return policy
AggregateRating with average rating and review count (from the reviews module)
Review schema for individual reviews

Result: search engines can show product cards with stars, prices, and availability directly in search results.

Collection pages

CollectionPage schema with name and description
BreadcrumbList schema for the category tree

Result: search engines understand the catalog structure and rank category pages for category searches.

Blog posts

BlogPosting schema with author, publish date, image, and body
BreadcrumbList for the blog-to-category-to-post path

Result: blog content is eligible for news, top stories, and article rich results.

Blog index

Blog schema describing the publication
WebSite schema for the site itself with a SearchAction

Result: search engines can present a search box scoped to your site in their results.

CMS pages

WebPage schema with name, description, and breadcrumb
FAQ schema where applicable

Result: FAQ pages and policy pages render rich snippets for relevant queries.

Brand

Organization schema on every page with logo, sameAs links to social profiles, contact information

Result: search engines build a knowledge graph entry for your brand.

All structured data renders server-side, so search engines see it on the initial response without waiting for client-side JavaScript.

Auto sitemap.xml

The sitemap is generated automatically and includes:

Home page
Every product (with last-modified timestamp)
Every collection
Every blog post
Every category landing page
Every published CMS page

The sitemap updates within minutes of a publish. Search engines pick up new content on their next crawl.

The sitemap is automatically discoverable through the robots.txt file. Configure Google Search Console once and the search engine finds the sitemap on its own.

Environment-aware robots.txt

Production stores get a real robots.txt that allows search engines to crawl public content. Staging and preview environments handle crawlers differently so the wrong subdomain never out-ranks the real one.

Disallowed paths by default

/checkout (no point indexing checkout pages)
/account (private customer dashboards)
/api/ (developer API, not for crawlers)
/admin/ (admin dashboard)
/preview (preview tokens for in-progress storefronts)

Allowed paths by default

/
/products/*
/collections/*
/blog/*
/pages/* (CMS pages)
Storefront search results (with limited depth)

The configuration is sensible by default and customizable on Enterprise plans.

Canonical URLs (server-rendered)

Every page emits a canonical URL in its server-rendered metadata. Search engines see the canonical instantly, without waiting for client-side JavaScript.

Pagination canonicalizes to the unsuffixed URL (page one is the canonical, page two and beyond reference it)
Filter URLs (?color=red) canonicalize to the unfiltered category page
Search engine query parameter variations (utm_source, fbclid) canonicalize to the clean URL
Multi-language pages canonicalize to the same content in the user's language

The result: no duplicate-content penalties, no thin-content traps, no crawl-budget waste.

Open Graph and Twitter Cards

Every product page, blog page, and CMS page ships with Open Graph and Twitter Card metadata.

Open Graph tags

og:title (custom per page)
og:description (custom per page)
og:image (hero image or custom OG image)
og:type (website, product, article as appropriate)
og:site_name (your brand name)
og:locale (matching the storefront language)

Twitter Card tags

twitter:card (summary_large_image for most pages)
twitter:title
twitter:description
twitter:image
twitter:site (your brand's Twitter handle)

When customers share a product or article on Twitter, Facebook, LinkedIn, WhatsApp, or any other social or messaging app, the preview is branded, accurate, and inviting.

RSS auto-discovery

The blog emits an auto-discovery tag in the HTML head so feed readers and search engines find the RSS feed automatically. The tag references the RSS feed URL and identifies it as the right feed for the page.

Multi-region URL structure

The storefront uses country-based routing for multi-region stores. Different regions get their own URL space:

/in/

for India

/us/

for the United States

/eu/

for the European Union

/uk/

for the United Kingdom

Each region has its own SEO meta, its own currency, and its own tax rules. Customers in each region see their localized URLs and content.

Page-level SEO controls

Every editable surface in the admin (product, collection, blog post, CMS page) includes an SEO panel:

SEO title

override the default page title for search engines

SEO description

custom meta description

OG image

custom image for social shares

Canonical URL

override (rarely needed, but available)

Index / no-index

control whether the page is indexable

You can write copy specifically for the search snippet. Title and description fields surface character counts so you stay within the limits Google truncates at.

What SEO does for ecommerce

Organic search is the most valuable traffic source for most ecommerce stores:

Free

no per-click cost

High intent

visitors typed in what they want to buy

Compounding

rankings improve over time as content and links accumulate

Recession-resistant

paid traffic budgets get cut first in downturns, organic keeps flowing

The platform that does SEO well unlocks all of this. The platform that does SEO badly forces you to buy every visitor for the rest of your operation's life.

Common SEO traps Mercemur avoids

Duplicate content from pagination : canonical URLs handle pagination correctly
Duplicate content from filter URLs : canonicals route ?color=red back to the clean URL
Thin content on collection pages : structured data and content slots add real signal
Slow page loads hurting Core Web Vitals : the storefront is built for speed
Missing or broken Open Graph cards : every page has them
Sitemap that does not update : the sitemap regenerates as content changes
Wrong robots.txt rules : sensible defaults out of the box
Multi-region without hreflang : country-based routing handles localization

How it works

1

You add a product, post, or page.

2

Edit the SEO meta in the same admin where you edit the content.

3

Publish.

4

Sitemap updates automatically.

5

Structured data emits server-side on the next visit.

6

Open Graph and Twitter Cards generate from the SEO meta and hero image.

7

Search engines find the new content on their next crawl.

Use cases

DTC fashion brand

Product pages with full Product schema and AggregateRating from real customer reviews. Star ratings appear in Google search results. Blog content ranks for style guides and "what to wear" queries.

Software vendor

Product pages with Offer schema (price, currency). Blog posts ranking for long-tail technical queries ("how to integrate X with Y"). CMS pages for documentation indexed and ranked.

International beauty brand

Multi-region storefronts with country-based URLs. Each region's content ranks in its own region. Localized SEO meta per language.

Furniture brand

Product pages with detailed Product schema including material, dimensions, and care information. Long-form blog content ranking for interior design queries.

B2B industrial

Product spec pages with technical Product schema. Blog and CMS pages ranking for industry-regulation searches. Trade-show calendar pages indexed.

Frequently asked questions

Yes. Products, blog posts, and CMS pages all carry their own SEO meta.

Yes. Emitted in the server response, not injected client-side.

Yes. Slug-based, lowercase, hyphen-separated.

Yes. The sitemap includes products, collections, blog posts, and CMS pages.

Yes. Add the sitemap URL to Google Search Console once and the search engine picks up updates automatically.

Country-based routing handles localization. Each region has its own URL space, which functions similarly to hreflang for SEO.

Yes. The SEO panel includes an index / no-index toggle.

Yes. Override the default canonical when needed.

The sitemap updates within minutes of a publish. Search engines pick up new content on their own crawl schedule (typically hours to days).

No. The SEO infrastructure is built into the platform.

Yes. FAQ pages (built as CMS pages with FAQ structured data) qualify for FAQ rich results.

Yes. The reviews module emits AggregateRating and individual Review schema on product pages.

Yes. Every page has full Open Graph and Twitter Card metadata.

Yes. The storefront is built for speed with image optimization and aggressive caching.

Sensible defaults out of the box. Custom rules available on Enterprise plans.

No. Modern AMP usage is declining. The platform prioritizes fast standard pages over AMP variants.

Yes. Canonical URLs route page two and beyond back to the first page as the canonical.

Yes. Filter URLs (?color=red) canonicalize to the clean category page so they do not create duplicate content.

Yes. The storefront passes most automated SEO audit tools out of the box.

Best practices for ecommerce SEO

Treat product pages as SEO landing pages. Customers search for specific products. Make each product page the best result for its specific query. Long product descriptions, unique meta titles, custom OG images.
Use the blog for category-level queries. Customers search "best running shoes for flat feet" not "Acme Brand RunPro 5". Blog content can rank for the category-level queries that bring customers in.
Get review velocity going. Star ratings in search results increase click-through rate. The first 50 reviews matter more than reviews 50-500 because they unlock the rich-result eligibility.
Map FAQ schema for high-question products. Products with predictable customer questions (sizing, fit, materials, warranty) benefit from FAQ structured data. Build the FAQ as a CMS section with the right schema.
Internal link with anchor text discipline. Avoid "click here". Use descriptive anchor text that includes the target page's keyword. "Read our leather care guide" beats "Click here for our care guide".
Update old content instead of writing new. An old blog post that ranks for a query is worth more than a new post that does not. Refresh the old post, expand it, re-publish.
Submit the sitemap to Google Search Console once. After that, the sitemap updates automatically and Google picks up changes. No re-submission needed unless the sitemap URL changes.

Common SEO mistakes to avoid

Generic meta titles like "Acme Brand - Online Store". Every page should have a specific, search-friendly meta title.
Duplicate content from URL parameters. Filter and sort URLs that create new pages dilute SEO. Canonical URLs handle this automatically in Mercemur.
Slow page loads. Slow pages drop in rankings. Mercemur's storefront is fast by default, but bloated images can still slow things down. Use optimized image sizes.
Missing or weak OG images. A page without an OG image is much less likely to be shared on social. A generic OG image (just the logo) reduces share clicks dramatically.
Ignoring international SEO. If you sell internationally, configure multi-region URLs. Country-based routing handles this in Mercemur.

Related

Content and blog→

Pages and posts that bring people in.

Storefront builder→

Build and theme the shop your customers see.

Analytics→

What sold, to whom, and what it cost.

Get your store SEO-ready on launch day

Get your store SEO-ready on launch day.

Start fast, compare plans, or talk through the details with us.

Read the SEO guideSee pricingTalk to sales