Guide · updated
How to build a website by voice with Grok Bot
You don't need to write code to get a website made. This site, Bot Lodge, is built that way: the builder of this site talks to Grok Bot by voice, describing changes like "make the logo bigger" or "remove the email signup box", and the bots build, deploy and fix it. Here's how to work the same way. Voice and routine details are checked against the official Grok Bot help pages listed below.
How do I build a site by voice?
- Open the chat with one of your Bots in the Grok Bot app (desktop or phone).
- Start talking. With the message box empty, choose Start voice chat (the waveform button) to talk live. Prefer to read before sending? Use voice typing instead: Start voice input or Cmd+D / Ctrl+D on desktop, Start dictation on the phone.
- Describe the site in everyday words: what it's for, who visits it, which pages it needs and the feel you want. No technical terms needed.
- Ask to see it before it goes live, for example "show me a screenshot" or "send me a preview link". Check it on both your phone and computer.
- Give feedback like you would to a person, one or two changes at a time: "make the logo bigger", "remove the email signup box". Look again after each round.
- When you're happy, say "deploy it". Connecting your hosting account to the Bot first makes this a single request (see the guide to connecting apps).
- Keep it fresh with a routine. Say, for example, "Every day at 8:00 AM, check the site for broken pages and tell me what you fixed." Open the routine, check When to run, and use Test to try it right away.
Real requests from building this site
Bot Lodge is built this way. These are real change requests the builder of this site made in plain language, quoted or paraphrased from the site's build log:
- "Make the logo bigger."
- "Remove the email signup box."
- Add a search box so visitors can find things fast.
- Make the News cards more compact.
- Rename the email signup to match the new site name.
Before and after
Adding search
Before: Visitors had to browse page by page to find a use case or tool.
The request: The builder asked for a search box.
After: The Bot added instant search to the homepage and a smaller search bar on every other page, then deployed it.
Tidying the email signup
Before: The email signup was still branded with the site's earlier name, Tool Picks.
The request: The builder asked for it to be renamed.
After: The Bot renamed the signup to the Bot Lodge branding, simplified it, rebuilt every page and deployed.
Questions
Do I need to know how to code?
No. You describe what you want and give feedback in plain words. It still helps to look at every change before it goes live, the same way you would check work from a person.
What kinds of requests work?
Plain sentences work best, one or two at a time. Real examples from building this site: "make the logo bigger", "remove the email signup box", add a search box, make the News cards more compact, and rename the email signup to match the new site name.
What's the difference between voice chat and voice typing?
Per the official help, a voice chat is a live spoken conversation where the Bot talks back. Voice typing turns your speech into text in the message box so you can read and edit it before you send, and the Bot replies in text. Voice chat works with one Bot at a time and not in group chats.
Can I do this from my phone?
Yes. Voice chat works in the desktop and phone apps, and the phone app has Start dictation for voice typing.
How do routines keep the site updated?
A routine tells a Bot when to run a task: on a schedule or when something happens, such as an email or a webhook call. Routines run in the cloud while your laptop is closed. Ask for one in chat, check When to run, and use Test to try it.
Will routines use up my plan?
Each run spends usage, so frequent schedules spend more. The official help suggests pausing routines you don't need and widening schedules if usage drops quickly.
Is this a real example?
Yes. Bot Lodge is built and maintained this way: changes are described to Grok Bot by voice, and bots build, deploy and fix the site, with daily and hourly routines doing checks and updates.
