Answer Engine Optimization — being the source, not the tenth link
Search is increasingly answering the question instead of listing pages that might contain the answer. When that happens, there is no tenth result to be. You are either the source it used, or you are not in the conversation.
What an answer engine is
Ask Google something specific now and you will often get a written answer at the top of the page, assembled from several sources, with the links folded underneath or off to one side. Ask ChatGPT or Perplexity the same thing and you get only the answer, with citations. That is an answer engine: a system that reads sources and responds, rather than handing you a list and wishing you luck.
For a local service business this changes the shape of the opportunity. In a list of ten results, being sixth still earns some clicks. In an answer, there is no sixth. Two or three businesses get named. Answer engine optimisation is the work of being one of them.
What answer engines need that search engines do not
A search engine can rank a vague page. An answer engine cannot quote one. To be used as a source, your facts have to be unambiguous, current, and available in a form that is cheap to read — no clicking through a booking widget, no prices that only appear after selecting three dropdowns, no hours buried in a footer image.
This is where most booking platforms quietly fail their customers. If your services and prices only exist inside a JavaScript booking widget hosted on somebody else's domain, they are effectively invisible to anything that is not a human with a mouse.
Your site publishes a plain-text briefing
Every Atelier site — on every plan, the free one included — publishes a machine-readable summary of your business at a standard address that AI systems have converged on looking for. It is written in plain, structured text and it contains your services with their real prices, your opening hours, your locations with full addresses, your published team, your booking links, and your booking phone or text number.
It is generated from live data, so it is correct by construction rather than by somebody remembering to update it. There is a compact version and a fuller one, so a system fetching it can take as much detail as it needs.
Beyond that, our hosting deliberately serves a clean text version of any public page to software that asks for one, instead of making it parse a page built for browsers. The easier you are to read accurately, the more likely you are to be read accurately.
Your answers, in your words
Automatic facts get you into the conversation. Your judgement is what makes the answer sound like you rather than like a directory entry.
Website plans include operator-managed FAQ sections. You write the questions your customers really ask and the answers you would actually give, group them into sets, and they publish two ways at once: as a readable page for humans, and as tagged question-and-answer markup for machines. The same content also flows into your plain-text briefing, so an assistant reading about you gets your answers rather than an inference.
There is also a short settings screen where you can write a one-line summary of the business, an "about" paragraph, and a handful of plain facts you want stated. That text goes into the briefing verbatim. It is the place for the things no database field captures — a parking quirk, an access note, an unusual policy.
If you leave a gap, something else fills it
Worth being concrete about why this matters, because it is easy to treat as theoretical.
One business running on this platform found an AI assistant confidently answering customer questions about the shop with details it had assembled from scattered review text. The answer was fluent, specific, and wrong in the particulars — it had merged two things into one and stated the result as fact. Nothing on the shop's own site addressed the question, so the model did what models do: it filled the gap from whatever it could find.
The fix was not clever. It was writing the answer down somewhere machine-readable. That is the whole discipline, really: decide what is true about your business, publish it plainly, and stop leaving the description of your shop to the aggregate opinion of strangers.
Read next
Being quotable is one thing; being recommended is another — that is generative engine optimisation. Or step back to how customers find a local business.
Four things every Atelier tenant gets, on day one
- A brand-fit URL. Pick a vertical-branded subdomain on day one (yourshop.atelier.salon, .tattoo, .spa, .dance, .fitness, .golf, .dog, .pet, .skin, or seated.studio). Connect a domain you own any time, no upgrade tier.
- Pick a plan, not a parts list. Forms, staff profiles, two-way calendar sync, no-show protection, waitlists, resource scheduling, multi-location support, reviews and in-person card payments, all in the plan, including the free one. Gift cards, packages and text reminders come with every paid plan. That leaves a short list of clearly-priced extras, the Marketing Suite, the AI Suite, window kiosk displays, and branding removal, and the higher plans fold some of those in too.
- Flat as your team grows. Unlimited staff, services, and customers: the same bill with five team members as with fifty, on every plan. Additional locations are a flat $25/month each, with your full plan at each.
- A free directory listing. Every paid plan (Booking Pro and up) is auto-listed in the public Atelier directory. New customers find you there and click straight through to your booking URL, no commission, no per-booking fee, no marketplace cut.
Start free. Take real bookings today.
Free to start, and your first month of any paid plan is free: paid plans from $29 a month after that. Cancel any time. Bring your domain, your brand, even your own Stripe, Square or Clover account. Atelier Booking handles the rest.