A driving school website built to be found locally and quoted by AI
A single bilingual page for a driving instructor in Ashkelon, Israel. Hebrew by default, English on a toggle, structured so that search engines understand the service area and answer engines can lift the answers verbatim.
A good instructor with an invisible website
The instructor had three decades of experience, genuine five-star reviews, and a free theory practice tool that competitors charge for. None of it was reaching anyone. The site read like a leaflet: a logo, a paragraph, and a list of bullet points with a plain text link to WhatsApp.
What was holding it back
- No structured data, so search engines could not tell it was a driving school or where it operated
- Service area never named, in a market where every query is "driving school in [city]"
- Reviews existed but lived off-page
- The contact link looked like a footnote instead of the main action
- English speakers, a real segment in the area, had nothing to read
What the rebuild set out to do
- Make the business machine-readable as a local entity with a defined service area
- Answer the questions buyers ask before they ask a human
- Turn WhatsApp into the spine of the page rather than a link at the bottom
- Serve Hebrew and English without splitting the domain in two
- Speak to the segment that actually drives volume: first-licence teenagers and their parents
Three layers, one page
Local search, answer engines and conversion are usually treated as three separate projects. On a single-page local business site they are the same page, and they either reinforce each other or quietly cancel each other out.
Entity and geography
DrivingSchool schema with coordinates, founder, languages spoken and fifteen explicitly named service areas covering both city neighbourhoods and the surrounding kibbutzim, each one also written into visible page copy so the markup and the content agree.
Answers a model can lift
Eight questions, each answered in a self-contained paragraph that makes sense with no surrounding context, marked up as FAQPage. The two paragraphs that define the business carry speakable markup for voice assistants.
A CTA that knows where you are
The floating WhatsApp button rewrites its own message as you scroll. Reading the section about driving anxiety opens a different conversation than reading about service areas, so the first message already carries the visitor's intent.
Bilingual without a second URL
The usual answer to two languages is two sites, or a plugin that generates a parallel URL tree and quietly creates duplicate content, thin translated pages and a maintenance burden nobody signed up for.
Here the page is Hebrew-first and right-to-left by default. Every translatable element carries its English inside a data attribute, and one toggle swaps the text, flips the document direction and mirrors the entire layout through CSS logical properties. The choice persists on the next visit. One URL, one file, both audiences, and no duplicate content to explain to anyone.
The same discipline applies to the audience segment. The first-licence section is written for a sixteen-and-a-half year old reading on a phone, with a parent paragraph directly beneath it, because in this market the teenager chooses the instructor and the parent pays.
Common questions about builds like this
What should a driving school website include?
Four things decide whether it converts: an instant contact channel people actually use, which in Israel means WhatsApp rather than a form; named service areas so local search can match the school to a city or neighbourhood; real student reviews on the page rather than only on Google; and a clear answer to the questions every new student asks first, such as minimum age, how many lessons are required, and whether the car is automatic.
How do you build one website that works in both Hebrew and English?
The page is written Hebrew-first with right-to-left as the default direction, and every translatable element carries its English text as a data attribute. A single toggle swaps the text, flips the document direction and mirrors the layout using CSS logical properties, so there is no second URL to maintain and no duplicate content risk. The visitor's choice is remembered on their next visit.
What is AEO and how is it different from SEO?
SEO earns a ranked link. AEO, or answer engine optimization, earns the answer itself when someone asks an AI assistant instead of running a search. It is won by publishing short, self-contained, factually clean answers to the exact questions buyers ask, and marking them up so a model can lift them without ambiguity. On this build that meant a FAQ written as standalone answers, FAQPage markup, and speakable markup on the two paragraphs that define the business.
Why is WhatsApp better than a contact form for a local service business?
A form asks a stranger to type their details and then wait. WhatsApp opens a conversation they are already comfortable with, on an app they have open, with the first message pre-written. Here the pre-written message changes with the section being read, so the owner knows the intent before replying.
How long does a build like this take?
A single-page build of this scope, including the bilingual layer, schema, answer set and CTA logic, is a short engagement rather than a multi-month project. The longer part is gathering the real inputs: verified service areas, genuine reviews and correct business facts, because none of it can be invented without damaging the local search signals.
Local business, two languages, one page that answers first
If your customers are searching by city and asking AI assistants before they call anyone, the same three layers apply to your market as well.