How Futuro became the most-cited name in AI salon answers | Trakkr
A crowded market. A very specific opening.
Ask an AI engine which receptionist to buy and it has plenty of answers: established software companies, YouTube explainers and Reddit discussions. Futuro had a more specific place to start.
It builds voice agents that answer the phone for salons and restaurants. So it focused on the questions those businesses ask. By the August snapshot, no domain was cited more often across the salon questions Futuro tracked.
The most-cited site on its salon questions.
| Salon questions | Broad questions | Relative citation frequency | Leading site = 100% |
|---|---|---|---|
| 1. futurocorp.com | 100% | ||
| 2. cloudtalk.io | 65% | ||
| 3. youtube.com | 43% | ||
| 4. bookingbee.ai | 34% | ||
| 5. qlient.ai | 33% |
Thirty days to 27 Aug 2026, across the tracked salon questions. Bars are indexed to the leading domain within each group, not to all citations. These are different question groups in the same period, not a ranking change over time.
Built around the front desk.
Brandon Gillespie founded Futuro to handle the calls a business’s front desk would. While evaluating several GEO platforms, his team connected Trakkr to its server logs and began checking the same buyer questions every day.
Futuro Corporation · Tampa, Florida
First, make the site work for the machines.
The site looked fine in a browser. The server logs told a different story. AI crawlers were hitting a certificate error between Cloudflare and the origin, while Cloudflare’s strictest setting challenged automated visitors.
Trakkr made those failures visible. The certificate fault stopped within days, and Cloudflare came off its most restrictive setting on 25 May. The team could then turn to individual pages.
The pricing page hid the clearest problem.
On 2 June, Trakkr found that AI bots requesting /pricing received a 404, even though the page loaded normally for people. The first fix did not hold. The next morning’s logs caught it.
From a crawler error to an AI citation.
| Date | Status | Notes |
|---|---|---|
| 2 Jun | 404 Not found | The fault is found |
| 4 Jun | 404 Not found | The first fix fails |
| 12 Jun | 200 Page readable | AI can read the page |
| 24 Jun | Cited In AI answers | The page earns a citation |
The fault is found. People could open the page. AI crawlers received “not found”. The second fix held. Crawlers started reading the pricing page.
Recommendations became a publishing routine.
Trakkr supplied dated actions and draft pages. Futuro’s writers and developers built and published the changes through their own repository. The work arrived in three pushes.
1. May
- Give the site clearer answers.
- Industry FAQs, direct answers near the top of pages, ranked comparisons and repaired guide links.
2. June
- Fix what crawlers could read.
- The pricing fault, structured product and FAQ information, and a stronger content hub.
3. July & August
- Make the comparisons explicit.
- Pricing comparisons, buyer’s guides, named competitors and an llms.txt file to surface the work.
Explore the recorded milestones
19 to 26 May
- 19 May Ranked comparison of business-call voice agents, naming Retell, Bland, Vapi, Synthflow and GoodCall
- 25 May Answer capsules on every industry page; broken guide URLs fixed
- 26 May Industry FAQs written from the questions engines were already answering
2 to 16 Jun
- 12 Jun The /pricing crawler fault fixed for good, at the second attempt
- 15 Jun FAQ Page schema on the FAQ entries; Offer and Product schema on /pricing
- 16 Jun /explore rebuilt from a link hub into content that earns citations
23 Jul to 19 Aug
- 23 Jul llms.txt deployed and the last crawler blocks removed
- 23 Jul Voice AI pricing comparison for commercial queries
- 19 Aug Buyer's-guide comparison series added to llms.txt
AI came back more often.
Over 5× the daily reading rate between the opening and closing fortnights
Seven-day average
| Date | Daily reading rate |
|---|---|
| 11 May | 1× |
| 1 Jun | 2× |
| 1 Jul | 4× |
| 1 Aug | 6× |
| 19 Aug | 5× |
A page went live. Then came the wait.
Futuro’s own category term, human staff mirroring, was an early opening. Once ChatGPT first named the company for it, at least one engine continued naming Futuro every day that question remained in the record.
A competitive salon question took longer. Trakkr had followed “voice AI for nail salons” from the first day. Early appearances came and went.
On 28 June, Trakkr sent Brandon a comparison-page mock-up. His team published its own version the following day. Engines picked it up, then let it go again for weeks. On 6 August, Perplexity’s answer began to hold.
One question, followed through
“voice AI for nail salons”
| Date | Event |
|---|---|
| 14 May | Tracking begins |
| 29 Jun | The page goes live |
| 6 Aug | The answer holds |
A foothold to build on.
The broad market remained competitive. The salon record showed where the approach was working: a page the crawler could read, a direct answer, a useful comparison, and repeated checks to see whether the result lasted.
Explore consistency across the tracked questions
| Question | Days named |
|---|---|
| What are the top 10 best conversational AI solutions for beauty salons? | 100% |
| What is the conversational AI for beauty salons? | 100% |
| What’s the difference between human staff mirroring and an AI receptionist? | 95% |
| voice AI for nail salons | 67% |
| Best AI receptionist for beauty salons | 59% |
| What are the best voice AI companies for nail salons? | 38% |
| best conversational AI for real estate? | 38% |
| Best AI phone answering service | 0% |
| Best AI receptionist for inbound calls | 0% |
The visitors AI sent were more likely to enquire.
5.7× the site’s conversion rate
More visitors took the next step.
| Conversion | Engagement |
|---|---|
| Visitors from AI assistants | 30.4% |
| Site average | 5.3% |
About the record
What the charts measure
Daily reading comes from Futuro’s Cloudflare logs. Citation rankings come from Trakkr’s tracked answers. Conversion and engagement rates come from Futuro’s Google Analytics. Page fetches, mentions, citations and human visits are separate measures.
The dates and scope
Daily records end on 19 August 2026. Citation rankings cover the thirty days to 27 August. Analytics cover 1 May to 22 August. The salon ranking covers the tracked salon, nail and beauty questions, not every salon query on the web.