Compose Arabic with links, handles, and numbers without direction errors

Answer first: write the sentence for meaning, then isolate fragile Latin runs with spacing and deliberate line breaks. Keep a handle, URL, version, or price together; do not surround it with ambiguous punctuation. Review the exact per-platform preview and one real low-risk post before a campaign.

Start with a stable content pattern

For a Riyadh product announcement, prefer a structure such as:

أطلقنا تحديث Naasher 2.4 اليوم. التفاصيل: https://example.com/release

شاركونا رأيكم عبر @naasher_app.

The Arabic sentence carries the meaning. The product/version, URL, and handle form separate runs. A line break prevents the URL from pulling nearby punctuation into an unexpected visual order. If the destination supports link cards, keep the human sentence useful even when the raw URL is shortened.

Preflight every fragile element

Mixed-direction Arabic preflight

Element	Risk	Safer check
Element@handle	RiskPunctuation appears on the wrong visual edge	Safer checkPut the handle in its own phrase or line
ElementURL	RiskQuery strings and parentheses reorder visually	Safer checkUse a clean HTTPS URL and preview the final link
ElementPrice or date	RiskDigit style changes or units detach	Safer checkKeep number and unit together; apply one locale rule
ElementHashtag	RiskArabic and Latin parts split	Safer checkUse one script per hashtag when possible
ElementEmoji	RiskNeutral direction changes nearby punctuation	Safer checkPlace emoji after a complete clause, then preview
ElementQuoted English	RiskQuotation marks become ambiguous	Safer checkUse a separate sentence or line for the quote
ElementLocalized alt text	RiskArabic meaning is omitted while artwork contains key text	Safer checkWrite independent Arabic alt text and test what the provider retains
ElementUTM punctuation	RiskAmpersands, equals signs, and closing punctuation reorder	Safer checkKeep the full URL on its own line and verify the destination parameters
ElementDigit variants	Risk١٢٣ and 123 normalize inconsistently across copy and artwork	Safer checkChoose one audience rule and compare stored, previewed, and published forms

Review meaning before typography

Ask the reviewer to read the post aloud in its intended order. Confirm which account, time zone, date, price, discount, and link the reader will understand. Then inspect cursor movement, selection, wrapping, truncation, character count, and the provider preview. A visually neat post with a reversed date or detached negative sign is still wrong.

Do not paste invisible bidirectional control characters from random fixes. They are hard to audit and may behave differently after provider normalization. Prefer semantic layout, clean runs, and platform preview. If a CMS or editor intentionally supports isolation controls, document their use and test copy/paste into the target network.

Normalize deliberately, not blindly. NFC can make equivalent Arabic sequences stable for comparison, but do not change approved spelling, Quranic marks, brand forms, or a URL. Compare code points when a hashtag or mention looks identical but fails to match. Keep the original and normalized value in a test fixture, never two visually identical live hashtags by accident.

Test truncation at the actual mobile preview boundary. A platform may cut between the Arabic call to action and its Latin URL, hide the end of a UTM query, or move punctuation beside “more.” The first visible lines must remain complete, and the expanded copy must preserve the approved link.

Adapt instead of cloning

LinkedIn can carry a longer Arabic explanation with an English product term. X may need the link on a separate line to protect the short opening. Instagram captions can use line breaks, but the first visible lines must still make sense before “more.” For a bilingual campaign, do not alternate every word between scripts. Publish a complete Arabic version and a complete English version when audience context allows.

A Naasher worked example

Naasher's composer is RTL for Arabic content and uses Western digits in the product interface. Treat that as an editing aid, not proof of the remote result. Select each destination, review its preview and limit, schedule a low-risk test, then compare the provider's final post with the approved copy. If a destination preview does not preserve the intended order, use its native composer or change the copy structure before publishing.

Approval checklist

• Arabic meaning is complete before the first Latin run.
• Handles, URLs, prices, dates, and versions read in the intended order.
• The same digit style is used across copy and artwork.
• Every image has localized alt text where the provider supports it.
• Unicode normalization, digit style, UTM punctuation, and mobile truncation were checked.
• The reviewer checked desktop and mobile wrapping.
• The publisher verifies the remote post, not only the scheduler status.

Direction quality is an operational check, not a decorative one. It protects dates, prices, identities, and calls to action from becoming ambiguous after the provider renders them.