Keep a product or variant’s identity separate from its translated name and URL. Arabic and English pages should describe the same commercial item while using appropriate language-specific content. Prefixing an Arabic category URL with /en does not establish that an equivalent English route exists.
Model identity before importing content
Give each product a stable identifier, and each variant a SKU or another explicit internal identity. Colour and size are commercial attributes; their labels are translations. Renaming “large blue shirt” must not create a different inventory item merely because a translated name was used as its key.
Do the same for categories. Link translations through the category identity rather than by manipulating URL strings. A language switch should resolve the equivalent category’s actual route. If an approved translation does not exist, show an honest unavailable state instead of an invented link or Arabic body text under English headings.
Test a small but difficult sample
| Sample case | What to verify |
|---|---|
| Product with two variants | Both languages refer to the correct inventory records |
| Category with a translated slug | Language switch reaches the corresponding category |
| Long Arabic name | Phone layout preserves variant controls and readable labels |
| Out-of-stock product | Availability is clear; a useful URL is not deleted automatically |
| Published slug changes | Internal links update and an appropriate redirect is reviewed |
| Filtering and sorting | Indexing behavior is deliberate, not thousands of accidental copies |
Run this sample before importing the entire catalogue. Record missing specifications and who will supply them. Do not fill gaps with invented attributes or unreviewed translation. Test combinations too: a long Arabic variant name inside a filtered, empty category can reveal an issue that separate checks miss.
Match search signals to the rendered page
Complete language versions need suitable titles, descriptions, canonical URLs and reciprocal language annotations linking equivalent pages. Do not canonicalize Arabic to English merely because the pages concern the same item. Decide separately whether parameterized filters and variant URLs have distinct search value; not every colour selection needs an indexable page.
Product structured data must agree with visible price, currency and availability. Never invent an offer to satisfy a structured-data validator. A valid JSON document cannot make incorrect commercial information true. The actual product model and Google’s current documentation should guide whether product-variant markup is appropriate.
Make updates testable
Name the owner of source specifications, translation review and category changes. Add route tests that open category links in both languages, switch between equivalents, and detect repeated locale prefixes or missing destinations. After a rename, inspect the navigation, sitemap and any reviewed redirect instead of leaving links on the old path.
The acceptance record should include sample product identities, language URLs and expected inventory behavior. That makes failures reproducible without exposing customer orders or payment information. Repeat the checks when the importer or route-generation logic changes.
Plan these responsibilities within custom ecommerce development. The small-business store launch guide and RTL-first design guidance cover related operational and interface decisions. This is a general catalogue model, not a verified list of ShopTek features.
Sources and editorial status
- Google: localized versions of pages.
- Google: product variant structured data.
- Original contribution: the catalogue acceptance sample and identity-versus-translation decision model.
