Sitemaps, canonical URLs and languages: which store addresses should Google discover?

A sitemap is not a list of every address you can copy from a browser. A canonical URL is not a redirect moving the customer elsewhere. Arabic and French text do not automatically create two independent search pages. Confusing these concepts can produce conflicting signals. Start with the published versions you want people to discover, then seek consistency across store navigation, sitemap and preferred content addresses.

List the addresses your store uses

Begin with the published domain, then important products, categories and policies. Record historical URLs, previews, UTM variants and any platform address alongside a custom domain. Not every variation constitutes another page worth indexing. Different URL spelling does not necessarily provide different information or serve an independent customer need.

Open sample pages without signing in and record the final destination. If an old address redirects, document the relationship rather than counting another independently published page. Private receipts and access links should not be treated as public catalog content, because their purpose differs from product discovery.

Separate three mechanisms

Mechanism	Purpose	Does not guarantee
Sitemap	Describe selected discovery URLs	Indexing every address
Canonical	Indicate a preferred content version	Forcing Google’s selection
Permanent redirect	Move visitors to a new destination	Suitability of an unrelated replacement

A genuinely moved product may require an appropriate redirect preserving visitor intent. Two addresses showing the same content do not become two products merely by including both in the sitemap. Base choices on what is actually public and available rather than artificially increasing your page count.

Handle languages according to actual pages

Separate content language from independent addresses. If the store displays one language on the same URL, filling two translations in an editor does not necessarily create two paths. Where a platform genuinely publishes separate stable language versions, their relationships and language signals can be examined. Do not invent a French URL for your sitemap when it does not open a published French page.

Optional Arabic and French product fields may be available in Matjri. By themselves, they do not promise separate language URLs or automatic hreflang in every situation. Check the public store language and what your interface supports. Organize product descriptions and language in Matjri, then inspect the customer-visible result.

A fictional store with 12 products

A shop sells 12 products and maintains Arabic and French text for each in a working file. If it currently publishes 12 URLs using the store language, completing translations has not automatically created 24 published pages. If separate language versions are genuinely published later, review addresses and signals according to that implementation rather than adding imaginary paths beforehand.

Suppose 90 TND is allocated to reviewing three main descriptions, an illustrative 30 TND per product. That pays for editorial work, not indexing or a guaranteed position. Record which content, language and address are published instead of measuring progress by the number of tags added without checking them.

Check before submission

1. Select the correct domain and important public pages.
2. Open the actual store-provided sitemap and examine sample entries.
3. Compare product, final URL and language with the intended destination.
4. Review the declared canonical and Google’s selection where information is available.
5. Correct conflicts or request technical assistance using a specific example, then submit the appropriate sitemap.

Do not arbitrarily remove click identifiers or campaign parameters from advertising destinations because a canonical should be clean. Arrival URLs and preferred content addresses serve different purposes. Review the implementation before broadly changing links in ways that could disrupt measurement.

Keep changes coherent

After a domain move or product URL change, inspect destinations, internal links, sitemap and significant older addresses. Do not redirect every missing page to the homepage when it does not answer the same need. Maintain a change record explaining historical versions. For a permanently removed product, decide what serves customers rather than retaining empty pages for a page counter.

Your next step is a small table of address, product, language and publication status. If you are starting, build an understandable catalog in Matjri before expanding content. Consistent information supports review without giving you the power to force indexing or search-result language.

Frequently asked questions

Should every UTM variation appear in the sitemap?

A campaign label does not create a new content page. Select preferred published addresses and retain parameters for marketing purposes without multiplying variations that serve no independent need.

Does canonical change the browser address?

It is not the redirect mechanism that moves a visitor. It indicates a preferred content version. To move an old address, discuss an appropriate redirect and equivalent destination with the implementation owner.

Does adding French text automatically require hreflang?

Start with what is genuinely published. A translation field does not establish two independently addressed versions. Do not refer to nonexistent pages; check platform capabilities before adding language signals.

Sources and review

• Google: building and submitting a sitemap
• Google: consolidating duplicate URLs
• Google: localized page versions

Editorial review: 15 October 2026. Numerical examples are illustrative learning exercises, not promised results or market prices.