A client who runs a tyre workshop in Plovdiv showed us the recordings on his phone. Instead of typing, he pressed the microphone and said: "where is there an open tyre shop right now". The answer came back immediately, without a list of ten results. One business won the customer, the rest simply did not exist for him in that moment.
That is the practical difference which makes voice search worth attention for small companies. It is not new technology and it is not a trend. The way people phrase a need has changed, and most Bulgarian websites are written for a completely different kind of query.
What voice search actually is
Voice search is any query a user speaks instead of typing. It travels through a phone microphone, a smart speaker, in-car navigation or a browser assistant. The system turns speech into text, interprets the intent and returns an answer that is often read out loud.
Three things happen at once. The query gets longer. It sounds like a question rather than a keyword. And the user expects one answer, not a page of links.
Who uses it
Based on our client projects the main groups are drivers, parents holding a child, people over fifty who dislike small keyboards, and anyone in a hurry. In Bulgaria the phrase for voice search itself gets roughly 880 monthly searches in Google Ads data, with clear growth over the past year. That is the volume of the topic, not of spoken queries, which are many times larger and spread across thousands of long phrases.
Why this changes SEO logic
Classic SEO was built around keywords with volume. Voice search works with intent. If your site is optimised only for "tyre repair Plovdiv" you miss "who changes tyres on Sunday near me". The second phrase has almost no measurable volume, yet it is the real question of a real person with a problem.
How spoken queries differ from typed ones
The difference is measurable. Typed queries in Bulgaria average two to three words. Spoken ones reach seven to nine. Typed queries are commands, spoken ones are sentences. Most importantly, spoken queries contain a question word in over half of cases.
| Characteristic | Typed query | Spoken query |
|---|---|---|
| Length | 2 to 3 words | 7 to 9 words |
| Form | keyword phrase | full question |
| Intent | often research | often immediate action |
| Local angle | sometimes | very often |
| Expected result | list of links | one specific answer |
| Device | desktop and phone | mostly phone and car |
| Moment | planned | on the move, urgent |
The table explains why a page that opens with a corporate introduction and reaches the facts on screen three loses. A voice assistant has no patience for scrolling.
Writing content for voice search
The approach that works for our clients is simple: turn the page into a series of short answers to real questions, arranged under clear headings.
Start from real questions
Do not invent questions at a desk. Pull them from three places: phone conversations, messages on Facebook and Instagram, and the internal site search box. If you run a shop, add the questions from Google Business Profile. Two weeks of collecting usually produces between thirty and seventy real phrasings.
Answer first, explain second
The rule is forty to fifty words for the first paragraph after a heading. It has to answer the question completely, even if the reader stops there. Details, exceptions and examples come afterwards. This structure suits both classic search and generative answers, which we covered in the piece on the difference between SEO and GEO.
Write the way you speak
Read the paragraph out loud. If you run out of breath, the sentence is too long. If you use a word you would never say to a customer at the counter, remove it. Voice systems handle natural language far better than bureaucratic phrasing.
Give big questions their own page
If one question generates several calls a week, it deserves its own page rather than a paragraph buried halfway down. A page with a clear question-shaped heading has a much better chance of becoming the source of a spoken answer.
The technical base nothing works without
Content is half of it. The other half is whether a machine can read the page quickly and unambiguously.
Speed
Spoken answers are almost always taken from fast pages. Check your site in PageSpeed Insights and aim for load under two seconds on a mobile connection. If you are not sure where to start, see the practical steps for site speed.
Mobile rendering
Over 90 per cent of spoken queries come from a phone. If the mobile version is a squeezed desktop with hidden content, you have hidden exactly the answers you want to surface.
Structured data
Schema.org markup tells the machine what is what: opening hours, address, price, question and answer. FAQPage and LocalBusiness are the two types with the most direct effect on voice results. Validate them in the Rich Results Test before celebrating.
HTTPS and a clean structure
A certificate, logical URLs, one H1 per page, meaningful H2 headings. Basic things, and exactly the things skipped during a rushed website build without a strategy.
Local voice search pays best
The phrase "near me" and its Bulgarian variants dominate spoken queries. For a company with a physical location this is the shortest path to a customer.
The practical minimum looks like this. A complete and current Google Business Profile with accurate hours including holidays. The same address and phone number everywhere online, character for character. Categories that match the actual business. Photos uploaded within the last thirty days. Replies to every review, including the weak ones. There is more on this in the article on local SEO through Google Business Profile.
Mistakes we see most often
The first is a keyword list stuffed into an FAQ section. Voice systems filter that out immediately and the visitor leaves.
The second is an answer that begins with "we are a company with many years of experience". Nobody asked that. The answer to "how much does a tyre change cost" starts with the number or the range, not with company history.
The third is blind copying of English questions run through machine translation. Bulgarians ask differently, and the phrasing matters more than the topic.
The fourth is neglect. Opening hours from 2023 sitting in structured data are worse than no data at all, because they send a customer to a locked door.
Measuring the result
Google does not provide a separate report for spoken queries, but there are workarounds. In Search Console filter queries containing question words such as how, how much, where, when, why and who. Watch their share and average position over time. Add queries with "near" and "opening hours".
The second source is Google Business Profile with its statistics on calls and direction requests. Growth there while advertising stays unchanged usually means local voice queries are working.
The third source is the phone conversations themselves. Ask new customers how they found you and record the answer in your CRM system. After three months you have data no tool provides.
Frequently asked questions
How long does it take to see results from voice search optimisation
The first movements in Search Console usually appear after six to eight weeks, provided pages are indexed and the technical side is in order. A noticeable rise in calls for a local business arrives between month three and month five. Speed depends heavily on competition in the sector and on how poor the starting position is.
Do I need a separate page for every question
No. Group related questions into one thematic page with clear subheadings. A separate page is justified only for a question with enough volume and commercial value, for example "how much does it cost" for your main service.
Does voice search work for an online store without a physical location
It works, but differently. For shops the winning queries are of the type "is it in stock", "how late do you deliver" and "how do I return an item". The main work sits in product descriptions, in clear delivery information and in structured data for availability and price. There are practical notes in the online store checklist.
Is an FAQ section enough on its own
It is not enough, but it is the fastest step with a visible effect. An FAQ section hands machines ready-made question and answer pairs. The rest depends on speed, mobile rendering and local signals.
Should I write in Bulgarian or English
In Bulgarian, if your customers are in Bulgaria. Voice systems recognise Bulgarian speech well and return Bulgarian sources. An English version makes sense only when you have genuine foreign customers.
Where to go from here
Voice search does not require a new platform or an expensive tool. It requires pages that answer specific questions in specific words, load quickly and tell machines what they contain. Most Bulgarian sites are two revisions away from that.
If you want us to check how your site behaves for spoken queries and what can be improved, write to us through the contact page. We review the content and the technical side and send an individual quote within 24 hours. If you also need broader work on visibility, see what our SEO and GEO service covers.
