Skip to content

WhatsApp order button checker

Do your WhatsApp buttons open the right number with the Arabic message ready?

  • Checks your page
  • Reads:HTML
  • 2 rules
  • Last updated

Reads: HTML

Free, no sign-up.

What we keep

We keep the address exactly as you send it, including anything after a “?”, and its report shows it. Anyone who has the report’s link can open it, so leave out tokens, keys and personal data.

The result appears here

Enter your page’s address and press “Check the page”. This is what the tool runs on it:

  • WhatsApp link number not in international formatnot started
  • WhatsApp link message is encoded wronglynot started

What it checks

  • That the number is digits only in international format, with the country code and without a plus, a leading zero, or Eastern Arabic digits.
  • That the message (text=) is encoded once, as UTF-8: not twice (%25D9…), not in Windows-1256, and with no stray %.
  • That a # in an order number does not end the link and drop the rest of the message.
  • That the message arrives as Arabic and not garbled, and that no template placeholder such as {{product_name}} was left in.

Example

WrongHTML
<a href="https://wa.me/0501234567?text=%25D9%2585%25D8%25B1%25D8%25AD%25D8%25A8%25D8%25A7">اطلب عبر واتساب</a>
RightHTML
<a href="https://wa.me/966501234567?text=%D9%85%D8%B1%D8%AD%D8%A8%D8%A7">اطلب عبر واتساب</a>

How to fix

  1. Write the number as country code + number without its local 0: 966501234567 for a Saudi mobile, 96891234567 for an Omani one.
  2. Encode the message once, as UTF-8, with encodeURIComponent, rawurlencode or the platform's URL-encode filter, and put it after ?text=.
  3. Write # as %23, & as %26, a space as %20, a new line as %0A.
  4. For a product button, build the message from the product's name on the server, encoded once; do not leave the placeholder for the browser.
  5. Open the button on a phone and read the chat box: it should show the Arabic message, the number's account and nothing else.

For example:

HTML
<a href="https://wa.me/966501234567?text=%D9%85%D8%B1%D8%AD%D8%A8%D8%A7">اطلب عبر واتساب</a>

FAQ

That tool checks the number alone. This one checks the number and the ready-made message, which is where Arabic stores go wrong most: encoding.

Desktop browsers and WhatsApp Web repair some malformed links and phones do not. The links this tool reports are those that fail somewhere, even if not everywhere.

No. It reads the links in your page's HTML and checks their form. It never contacts WhatsApp, and it cannot tell if the number has an account.

Open the plugin's settings for the message and enter the text in plain Arabic; the plugin should encode it. If it shows the encoded text, it is encoding it twice or not at all; try a different plugin or the generator.

How we measure

Last updated Methodology and scoring

We find the WhatsApp links in the page's HTML (wa.me, api.whatsapp.com/send, web.whatsapp.com/send, whatsapp://send) and check the number with libphonenumber's data, as the link-format rule does. The message is read as written in the link: a raw # ends it, %25 and two hexadecimal digits mean it was encoded twice, escapes that are not valid UTF-8 are reported, and the decoded message is read for garbled Arabic and unfilled placeholders. See each rule's page for the details.