Why we built Tasadr, and who we are

Because the measurement changes with the language and the country. Someone looking for a flower shop in Riyadh types different words from someone looking in Dubai, the engine may answer the two of them differently, and it may cite different sites. A tool asking in English from an American address is measuring another market and handing you its number.

So the product was built on Arabic from the first line: the question is written about your market, the way your customers ask in it, Google's answers are read as they appear in your site's country, and every answer is read in Arabic. Our core markets are Saudi Arabia, the UAE and Egypt, and we serve the rest of the Arab world alongside them.

The idea itself, and what it means for your site, is explained in what GEO is.

We are the Tasadr (تصدَّر) team: an Egyptian team based in Europe, building Tasadr since 2026, with more than 14 years in SEO and more than 15 years in technology, much of it inside European companies.

Instead of promises, we put in front of you what we measured and when, and one team that answers every mail within one working day. We hang no client logos nobody approved and quote no testimonial nobody gave.

The rule the product was built on: no number without the evidence behind it. We keep the excerpt of the engine's answer that names you or your competitor, word for word as it wrote it, and the links it cited, so you can open any cell in your dashboard and read it yourself instead of trusting a bare figure.

We state the limits just as plainly. A chat engine's answer changes from one ask to the next, so one lucky answer is never counted as a change, and when a measurement spans a range we show the range rather than a single number. The score is ours, not Google's; what each measurement gives you is set out in how we measure your score, and what we learned from our measurements is published in the Tasadr guides.

We built our method on the Arabic question from day one: questions in your customer's words, about their own market; Google's answers as they appear in their country; repeated measurement that separates luck from fact; and text evidence under every verdict.

The eight points in full, and what we refuse to do, are in how we measure your score.

Your data is kept on servers inside the European Union, under the GDPR. Each account's data is held apart from every other, and we do not sell your sites, questions or measurements. Some of the providers we rely on are outside the EU; their names, and what we send to advertising platforms when you accept advertising cookies, are in our privacy policy. We do not store data in Saudi Arabia today; if your organisation requires data to stay in the Kingdom, write to us before you subscribe and we will give you a clear answer.

Connecting Search Console is optional, the grant is read-only, and we use what it returns under Google's Limited Use policy: to list the properties you have verified so you can pick one, to suggest questions from real searches that already reached your site, to find the country most of your site's impressions come from so it is measured in its market, and to set your site's clicks and impressions in Google Search beside your Tasadr score in your dashboard, and for the other uses our privacy policy lists in full, and for nothing else. You can revoke the grant whenever you like, and you can delete your account and everything in it yourself in Settings, with a code sent to your email.

Tasadr's guides and pages are written by the Tasadr team itself, the team that builds the product and measures what AI engines answer in Arabic. That is why every guide is signed "The Tasadr team" rather than by one person, and the whole team answers for what it says.

Every figure about our plans comes from our published plans, and every figure about how the engines behave comes from our own measurements, with its month. We quote no statistic we did not measure, and publish no client case study without permission. Every term we use has a one-sentence definition in the GEO glossary.

When we describe how an engine or a platform works, we go back to its official documentation, such as Google's guidance for site owners, not to what is said about it.

We use AI tools for research and drafting. The team then reads every page before it is published and checks every figure in it against its source, so no page goes out that one of us has not read.

We review every guide at least once every three months, and as soon as our prices or an engine's own documentation change. A page's date moves only when something in it changes in substance.

Our guides carry the date they were published and the date of their last update, and our pages the date of their last update. If you find a mistake, write to support@tasadr.ai and we will correct it and change the date. What we add to the product itself is recorded every week in what's new in Tasadr.

Write to support@tasadr.ai for support, sales@tasadr.ai for a Business quote, billing@tasadr.ai for billing and invoices, and partner@tasadr.ai for press and partnerships. We answer within one working day. What is worth putting in each kind of mail is set out under contact the Tasadr team, and more than 30 answers about the method and the plans sit in the questions people ask about Tasadr.