Blog / Arabic & GCC search /

A technical review of Arabic pagination and filters

The category page looks great in the design preview. Then you open the live Arabic version, and the next-page control is somewhere odd and the filters forget what the shopper picked.

That isn’t a translation problem. The interface, the URL behaviour and the page content all have to work together.

Pagination and filters help people move through a catalogue. Left unplanned, they also spawn piles of URL variations, duplicate pages and content nobody can reach. On an Arabic storefront you check right-to-left interaction as well as crawl behaviour and market-specific output.

Review the customer journey first

Pick a category with enough products to use pagination and a few meaningful filters. Open the page on a mobile device and follow a task: find a product in a particular size or material, move to another page, clear one filter and continue browsing. Note what happens to the selected options, the result count and the URL after each action.

Check the visual reading order. Arabic text runs right to left, but product grids, icons, breadcrumbs, sort controls and pagination may follow other design conventions. The previous and next arrows must make sense in context. Don’t mirror every icon automatically, because some symbols show an action, not a reading direction.

Review mixed content too: Latin product codes, prices, numbers, punctuation and brand names. Bidirectional text can appear in surprising sequences, especially in form controls and labels. I’d always ask a fluent reviewer to test the real interface, because a developer who can’t read the content may miss that a selected filter seems to change a different attribute.

Understand which URLs the filters create

Document how each filter changes the URL. Some systems use query parameters; others update a path or rely on client-side state. Determine whether the URL can be copied and shared, whether browser back restores the prior selection and whether a crawler can access the intended result.

Not every filter combination should be indexed. A colour or size filter helps a shopper but can create a thin page with no search purpose of its own. A category subset might deserve a stable landing page if it serves a real query and the business can maintain it. Decide which combinations justify crawlable URLs, and control the rest with the platform’s supported mechanisms.

Don’t block crawling across the board before you know what the URLs contain. A robots rule stops a crawler seeing a page, but it doesn’t guarantee the URL leaves search. Use canonical and indexation controls deliberately, and check what the storefront actually outputs. I’d rather read the generated HTML than layer custom rules on assumptions.

Test that every page of results is reachable through ordinary links and that the controls show the current page. Pagination shouldn’t rest entirely on a click handler that search engines and assistive technology can’t use. Confirm that page two has its own URL where users should be able to go straight to it, and that it holds the expected products.

Inspect canonical tags and internal links on paginated pages. The right behaviour depends on the site’s architecture, so don’t assume every page should canonicalise to page one, or that every page should be indexed. Make sure product links on later pages are crawlable, so items don’t end up isolated from the rest of the site.

When filters are applied, verify that pagination does not reset unexpectedly or carry a stale filter into an unrelated category. Sorting controls should not produce a separate indexable page for every order unless there is a specific reason. A URL strategy should be consistent across languages and markets, while keeping the user experience intuitive.

Validate translated filter labels

Use terms customers understand, not merely literal translations of the source labels. Check attribute names, values, singular and plural forms and abbreviated labels. A filter for a material, size or compatibility type should match the data shown on the product page. If the category uses local terms, maintain a glossary and have a fluent subject reviewer approve it.

Watch for truncation and text expansion. Arabic labels may take a different amount of space than English, and long labels can wrap or overlap controls. Test narrow widths, selected-filter chips and empty states. A translated label should remain understandable when a shopper has selected several options.

Search and filters should use consistent product attributes. If the page says one thing and the filter uses another term, customers may not realise that the same items are being grouped. The product data owner should confirm that the underlying values are complete and accurately mapped.

Test crawlability and rendered output

Crawl representative Arabic category URLs, including a base category, a paginated route and a useful filter state. Record response codes, canonical tags, robots directives, titles, language annotations and links to products. Compare with the equivalent language or market page if one exists, but do not assume it should contain exactly the same items.

Use a rendered crawl or browser inspection for controls built with JavaScript. Check whether content and links appear in the rendered page and whether the route works without relying on a browser session that only the admin can access. If the application changes results dynamically without a stable URL, decide whether that is acceptable for the user’s task and search visibility goals.

Search Console can show how Google has encountered URLs, but its reports are delayed and not a complete crawl log. Use it alongside direct testing, server logs and the site crawl. A report of duplicate or alternate URLs should lead to investigation of the pattern, not a blanket instruction to remove every filter.

Set rules and ownership

Agree which filter combinations are useful to expose, which should be excluded from search and who approves changes. Record how the Arabic version should behave and what the canonical relationship is to other language or market URLs. Keep the rule short enough that developers and merchandisers can use it.

Recheck the implementation after theme updates, catalogue imports and changes to the filtering app. A new attribute or translated value can change which combinations are generated. Include mobile interaction and URL behaviour in the acceptance check, not only a desktop screenshot.

Review one path end to end

Arabic pagination and filters work when a shopper can refine a category and carry on without losing their place, while search engines get deliberate, stable signals. The technical choice should serve the shopping task, not create URLs for their own sake.

So choose one Arabic collection, test its filters on a phone, then crawl the resulting URLs. Can a shopper understand the controls, and can your team say which filtered pages should be discoverable? If not, write the rule down before you extend the pattern.