Arabic and English category pages: deciding what should differ
Someone asks for the Arabic category page “exactly like the English one, just translated”. It sounds sensible. It also produces a page that reads like a translation, because it is one.
The two versions shouldn’t differ just because one was translated word for word. They should share the facts and purpose that need to stay consistent, and differ where language, terminology or the market genuinely differ. Decide from the audience and the offer, not from a rule that says every page must match, or every page must be separate.
Keep the core aligned
The product range, availability, key claims and purpose of the page must be accurate in both versions. Use one source record for the facts and agree how changes travel from it. If the offer differs by market, say so on the page. Don’t let the two pages drift apart without anyone noticing.
Adapt language and discovery
Category labels, supporting copy, examples and internal links may all need local review. Research how people actually describe the category, and check the Arabic sounds natural. Don’t stuff keywords or add local references that mean nothing operationally. My linguistics background makes me wary of any label that was chosen because it translates neatly rather than because people say it.
A fluent reviewer and the product owner may need to work together here. One knows the language, the other knows the range.
Check technical relationships
Confirm the URL, canonical and hreflang behaviour where you use them, and make sure both pages can be reached through navigation. Review the rendered right-to-left experience, not just the translated text. Filters, breadcrumbs and pagination are where RTL layouts most often break, so click through them.
Don’t forget the small stuff. Currency symbols, number formats, delivery notes and units can all differ between the versions, and shoppers notice the mismatch faster than you’d think. A short checklist of those items per category is quicker than debating each one every time.
A quick way to start
Pick your five most important categories. Put the English and Arabic pages side by side and tick four things: same range, same claims, same delivery and returns notes, same links in navigation. Anything unticked is either a deliberate difference or a bug. Write down which.
Then ask a native reader to describe, in their own words, what each Arabic page is selling. If their description doesn’t match the English, the translation has drifted from the purpose.
Mistakes to avoid
The first mistake is treating translation as the whole job. A page can be linguistically perfect and still miss how people search for the category.
The second is the reverse: rewriting the Arabic page so freely that it promises something the English page doesn’t. Facts must stay in step.
The third is forgetting the technical side. A beautifully adapted page that has no hreflang partner, or a canonical pointing at the wrong version, will struggle to be understood.
Make the review reusable
Begin by writing the decision the review needs to support, and the evidence that could change it. Otherwise “align the category pages” becomes a request to change every one of them.
Pick one real category and compare the English and Arabic versions line by line. Mark each difference as intended, accidental or unknown. That three-way sort is the most useful thing you’ll do in the review.
Ask the owner for a normal category and a tricky one, such as a range with an English-only brand name. A method that works only for the simplest page fails when the catalogue varies.
If the facts disagree between versions, mark the uncertainty and ask someone qualified. Don’t let a translator or a tool pick a winner.
Keep a note of why a difference exists. Then the next reviewer can tell a deliberate choice from an accidental one. Make exceptions visible and scoped, so one special case doesn’t become a rule for unrelated categories.
When you report back, separate what you saw, what might explain it and what you propose.
Picture a category for air conditioners. In English the page leads with BTU ratings and energy class. In Arabic, buyers in the Gulf may search first by room size or by how well a unit copes with summer heat. Same products, same facts, different way into the page. That’s the kind of difference worth designing for, and it won’t show up in a literal translation.
Compare that with a difference that isn’t worth keeping: a price that’s out of date on one side, or a missing delivery note. Those are drift, and drift needs fixing.
Agree who decides when the two versions disagree. If the English team and the Arabic reviewer each assume the other has final say, the page stays wrong for weeks.
Related reading
- Arabic CMS workflows: keeping translated pages aligned with source updates
- How to plan hreflang for Arabic and English pages
- A practical plan for maintaining Arabic content after launch
Test any new rule on one representative category and check the live result. Apps, themes and regional settings can change what visitors finally see. Revisit the pages when the range or the offer changes. What should remain consistent, and what should change, between your category versions?