Fake reviews and spam on Google Business Profile are not just a Jeddah problem — they affect every city in the Hijaz. A competitor with a grudge, a bot campaign, an AI service writing plausible-sounding nonsense, a real customer who posted on the wrong listing by accident: each scenario calls for a different calibration, but the same underlying principle. Respond calmly. State facts. Invite the reviewer to verify privately. Flag the review with Google without waiting for the reply to "fix" it.
The Hijazi register is unusually well suited to this. The Hijaz has centuries of experience handling commercial disputes across language and cultural barriers — the same warmth-without-groveling tone that works for a genuine 1-star complaint works even better when the review is probably not genuine. It reads as concerned rather than combative, which is exactly the signal you want both the original poster and every future reader to receive.
The Hijazi 'we have no record of you' reply — warm-but-firm
The most common fake review scenario is also the most delicate: a review from someone your team has no record of ever serving. They may have the wrong listing. They may be a competitor. They may be a genuine customer who visited so briefly that nothing was logged. You cannot know from the outside — and that uncertainty is exactly why the accusatory approach fails.
A Najdi-inflected "هذا الحساب مشبوه" or a stiff MSA "لم يتمكن فريقنا من إيجاد أي سجل" both carry the same problem: they sound like you have made up your mind before investigating. The Hijazi register allows you to express genuine puzzlement — "أهلين، بحثنا عن زيارتك في سجلاتنا وما لقينا شيء" — in a way that reads as honest investigation rather than defensive dismissal.
The structure that works in Hijazi for a no-record reply is: open with warmth ("أهلين"), state the factual gap without editorializing (we searched and found nothing for the date or description), express genuine interest in understanding what happened, and invite direct contact with a specific channel. The key discipline is to stop there. Do not speculate publicly about why there is no record. Do not name alternative explanations. The reader can draw their own conclusions; your job is to appear thorough and open, not to try to "win" the public exchange.
Specific facts anchor the reply. If the reviewer mentioned a date, reference it. If they described a dish or service that you do not offer, note the discrepancy factually — "we do not have [X] on our menu" is a verifiable statement that any reader can check, not an accusation. For internal links to the broader flag workflow and what Google actually removes, see how to respond to fake Google reviews in the GCC.
The three fake-review patterns and the Hijazi approach to each
Fake and spam reviews do not all look the same. Knowing which pattern you are dealing with changes which template you reach for.
Pattern 1: No record of the customer. The review describes a visit, a product, or a staff interaction — but your team cannot find any booking, transaction, or visit log that matches. This is the most ambiguous scenario because it covers both genuine errors (wrong listing, misspelled business name) and deliberate smears. The Hijazi approach: state the factual gap clearly, keep the door open for the reviewer to send proof, and avoid any phrasing that closes the conversation. "نعتذر لو كانت هذه تجربتك" ("we apologize if this was your experience") is stronger than "نعتذر عن ما حصل" because it is conditionally warm rather than unconditionally apologetic for something that may not have happened.
Pattern 2: Competitor smear or personal grievance. The review contains unusual language — mentions of competitor brands by name, specific insider knowledge that a regular customer would not have, or a profile with no history and ten reviews all posted on the same day. Do not call this out publicly. Hijazi businesses that publicly accuse reviewers of being competitors look petty; businesses that reply professionally and flag through proper channels look secure. The template for this scenario is deliberately generic: you are not acknowledging the smear, you are documenting for every reader that you engaged and found nothing matching.
Pattern 3: AI-generated or off-topic word salad. These are increasingly common — reviews that describe a plausible-sounding experience that has no internal consistency, or reviews about a business category you do not operate in. A review praising the "fast delivery service" on a restaurant that only offers dine-in, or describing a "medical procedure" at a café. The Hijazi-tone reply here can afford a light touch of genuine puzzlement — "هذا الوصف ما يطابق خدماتنا" — because the mismatch is obvious to any reader and your puzzlement is credible. Still invite contact. Still flag. For the full context on when Arabic-language review replies affect your GCC search visibility, see how to write Arabic Google review replies.
Hijazi templates in Arabic script
Each template below is a complete reply ready to adapt. Bracketed fields require your input before posting. These are written in authentic Hijazi register — use them as written for Jeddah, Mecca, and Medina; adjust toward neutral Gulf Arabic for locations outside the Hijaz.
Template 1 — No record of customer (date mentioned)
أهلين، شكراً على وقتك. رجعنا على سجلاتنا ليوم [التاريخ المذكور] وما قدرنا نلقى زيارة تطابق اللي وصفته. نعتذر يا غالي لو حصل خلط في الأماكن — عندنا أكثر من فرع وأحياناً يكون في لبس. تواصل معنا على [واتساب / الرقم] مع أي تفصيل إضافي وراح نرجعوا عليك مباشرة.
Transliteration: Ahleen, shukran 'ala wagtik. Rja'na 'ala sijillatna l-yom [il-tarikh il-madhkur] w-ma gidirna nilga ziyara tutabiq illi wasafta. Na'tadhir ya ghali law hasal khalt fil-amaakin — 'indana akthar min far' w-ahyanan yakun fi labs. Tawaasal ma'na 'ala [WhatsApp / il-raqam] ma' ay tafsiil idaafi w-raa'h nirja' 'alaik mubashiran.
Template 2 — No record of customer (no date mentioned)
أهلين، اهتمامك بالكتابة بيّن لنا إن في شيء ما كان صح. بحثنا في سجلاتنا ما لقينا زيارة تطابق الوصف. حابين نفهم وين صار اللي صار — تواصل معنا على [واتساب / الرقم] وحدثنا بوقت وتاريخ زيارتك وراح نرجع عليك بشكل كامل.
Transliteration: Ahleen, ihtimamak bil-kitaba bayyan lana inn fi shi' ma kan sah. Bahathna fi sijillatna ma ligina ziyara tutabiq il-wasaf. Habeen nifham ween sar illi sar — tawaasal ma'na 'ala [WhatsApp / il-raqam] w-haddithna b-waqt w-tarikh ziyartak w-raa'h nirja' 'alaik b-shakl kamil.
Template 3 — Wrong business / mistaken identity
أهلين، شكراً يا غالي على الكتابة. التجربة اللي وصفتها — [تفصيل محدد من التقييم] — ما تطابق أي خدمة من خدماتنا في [اسم النشاط]. إمكانية إن الحساب تشابه مع نشاط ثاني واردة. راجع إعداداتك وحطنا في الصورة على [واتساب / الرقم] إذا حابب نساعد.
Transliteration: Ahleen, shukran ya ghali 'ala il-kitaba. Il-tajruba illi wasaftha — [tafsiil muhaddad min il-taqyeem] — ma tutabiq ay khidma min khidmatna fi [ism il-nashat]. Imkaniyyat inn il-hisab tashabbah ma' nashat thani warida. Raji' i'dadatak w-hatna fil-sura 'ala [WhatsApp / il-raqam] idha habib nisa'id.
Template 4 — Competitor mention spotted (do not name them)
أهلين، قرأنا تقييمك وما قدرنا نتعرف على التجربة اللي وصفتها في سجلات [اسم النشاط]. لو في أي تفصيل يساعدنا نفهم — تاريخ الزيارة، الخدمة تحديداً، أي رقم طلبية — تواصل معنا مباشرة على [واتساب / الرقم]. حابين كل تقييم عندنا يعكس تجربة حقيقية.
Transliteration: Ahleen, qara'na taqyeemak w-ma gidirna nita'arrif 'ala il-tajruba illi wasaftha fi sijillat [ism il-nashat]. Law fi ay tafsiil yisa'idna nifham — tarikh il-ziyara, il-khidma tahdiidan, ay raqam talabiyya — tawaasal ma'na mubaashiran 'ala [WhatsApp / il-raqam]. Habeen kill taqyeem 'indana yi'kis tajruba haqiqiyya.
Template 5 — AI-generated or off-topic description
أهلين، اطلعنا على تقييمك بعناية. الوصف اللي ذكرته — [الوصف المشكل] — ما يطابق الخدمات اللي نقدمها. عندنا [وصف مختصر لما تقدمه فعلاً] وبس. لو في لبس في الموقع أو الاسم، يسعدنا نساعد — تواصل معنا على [واتساب / الرقم].
Transliteration: Ahleen, itla'na 'ala taqyeemak b-'inaya. Il-wasaf illi dhakarta — [il-wasaf il-mushkil] — ma yutabiq il-khidmat illi niqaddimha. 'Indana [wasf mukhtasar lima tuqaddimhu fi'lan] w-bas. Law fi labs fil-mawqi' aw il-ism, yis'idna nisa'id — tawaasal ma'na 'ala [WhatsApp / il-raqam].
Template 6 — Calm generic reply when you cannot identify the pattern
أهلين، شكراً على التقييم. راجعنا سجلاتنا ومواعيدنا وما لقينا ما يطابق التجربة اللي وصفتها. نعتذر يا غالي لو في خلط حصل. بنسعد جداً نسمع منك مباشرة على [واتساب / الرقم] لو حابب توضح التفاصيل — هدفنا نفهم كل تجربة.
Transliteration: Ahleen, shukran 'ala il-taqyeem. Raji'na sijillatna w-mawa'idna w-ma ligina ma yutabiq il-tajruba illi wasaftha. Na'tadhir ya ghali law fi khalt hasal. Bansa'ad jiddan nisma' minnak mubaashiran 'ala [WhatsApp / il-raqam] law habib tuwaddih il-tafasiil — hadafna nifham kill tajruba.
Pitfalls — what to avoid in Hijazi fake-review replies
Getting the templates right matters less than avoiding the mistakes that undermine them. Four recurring errors across Hijaz-market business profiles:
Najdi accusatory tone. The Najdi register handles directness well — "هذا التقييم غير صحيح وسنتعامل معه قانونياً" reads as firm and credible in a Riyadh context. In a Jeddah context it reads as aggressive, and aggressive business replies to potentially fake reviews invite sympathy for the reviewer. Hijazi businesses that stay warm even when they are skeptical come across as confident, not weak.
MSA stiffness. "تفيد إدارة المنشأة بأنه لم يتسن لها التحقق من هذه الزيارة في سجلاتها" is grammatically correct and communicates the right information — but it reads as a legal disclaimer, not a human response. Every reader, including the fake reviewer, can tell this was copied from a template. Hijazi Arabic even in its business register has a pulse; MSA in this context does not.
Defensive multi-paragraph reply. Fake and spam reviews tempt business owners into over-explaining — three paragraphs about the business history, five sentences about quality standards, a list of accolades. This signals anxiety, not confidence. A fake-review reply should be four to six sentences maximum. If your reply is longer than that, you are either trying to win an argument in public (do not) or you have not decided whether you believe the review is fake (decide before replying).
Ignoring the Google flag flow. A reply is audience management. A flag is the actual mechanism for removal. Do not post a reply and consider the problem handled. Flag the review through your Google Business Profile dashboard simultaneously — and if the first flag is rejected, escalate through the Google Business Profile support forum with documented evidence of the discrepancy. Businesses in Jeddah and Mecca that have dealt with coordinated review attacks report that documented patterns (multiple reviews from accounts created the same day, reviews that mention services not offered) significantly improve flag success rates. For the full flag workflow walkthrough, see how to respond to fake Google reviews in the GCC and start your free review management setup.
What to do next
Reply to the fake or spam review using one of the templates above — edit the bracketed fields and match the template to the pattern (no-record, wrong business, competitor-mention, AI-generated). Keep the reply under six sentences. Post it within 24 hours of the review appearing.
Simultaneously, flag the review through your Google Business Profile dashboard using the "Report a review" option. If the review describes services you do not offer, note the specific discrepancy in the flag report — this improves the chance of removal.
If you have received more than three suspicious reviews in a short period, document the pattern: screenshot the profiles, note the account creation dates, and note any similarities in phrasing. Google's review removal team responds to patterns more than to individual flags. If you need a systematic process for managing this across multiple locations or in Arabic and English simultaneously, set up your Taqymat account and let the platform track review patterns for you.