Case study: building a site with Grok Bot and Claude

What is this case study about?

About this site. VibecodeZero is a free guide for people who want to build apps with AI without coding. It is built and run with a Grok Bot, which drives Claude Code to write the site. A person is involved at specific points, described below.

Everything on this page is a description of how the site works. There are no revenue, traffic or earnings numbers, because the site is new and there’s nothing meaningful to report.

1. Who bought the domain?

The human. Vercel blocks purchases made by agents, so the Bot couldn’t have finished the purchase even if we’d wanted it to. We’d keep it that way regardless: anything that spends money is done by a person.

Accounts are the human’s call too: creating them and deciding what the Bot can connect to.

2. How was Search Console verified?

Google Search Console is where you tell Google that a site exists and see how it appears in search. Before it shows you anything, it asks you to prove that the site is yours.

This site was verified through DNS, by adding a record to the domain’s settings. It’s the method that covers the whole domain at once, including the Portuguese pages under /pt/. If the word DNS is new to you, the domain entry in the glossary is a good starting point.

3. Who wrote the code?

Claude Code, driven by the Bot. The Bot gave Claude Code the brief, followed the work and checked the results, all on the Bot’s cloud computer.

The site is built with Astro as a static site: plain pages, with no login and no database. That keeps it fast and leaves little that can break.

The working rule is that every change goes through two commands before it’s saved: one builds the site, and another checks the result. That check looks for broken links, missing page descriptions, invalid structured data and pages whose translation links don’t match. When it fails, the change is fixed first. This page went through the same check.

4. How do the two languages work?

English is at the root of the domain and Portuguese is under /pt/. Each page links to its translation, so search engines know which version to show to whom. Section names are translated too: the English guide to errors is at /errors/ and the Portuguese one is at /pt/erros/.

The site started in Portuguese and the English version came later, translated by AI agents. The English text was spot-checked but hasn’t been read in full by a person yet. We’d rather say so than pretend otherwise.

5. Which routines run on a schedule?

The Bot runs these routines on a schedule, on its cloud computer, so they continue when nobody’s laptop is open:

• Health check. Checks that the site is up and working.
• Daily content. Works on new and updated pages.
• Weekly SEO. Reviews how the site is set up for search engines.
• Trends radar. Looks for new topics worth covering.
• Quality review. Rereads pages for mistakes and outdated information.
• Distribution drafts. Prepares posts to share the site, as drafts for approval. Nothing is posted without a person saying yes.
• Revenue review. Looks at how the site makes money. Today the answer is that it doesn’t: ads are off and no affiliate links are live.

You don’t have to write a routine from scratch: you can show a Bot a workflow once and it saves it as a routine.

6. What does the human still approve?

Three kinds of things:

• Money. Buying the domain, paying for any service.
• Accounts. Creating them and deciding what the Bot connects to.
• Posting. Anything published on other channels in the site’s name starts as a draft and waits for approval.

The Bot comes back when it needs approval, and drafts are approved before they are sent. Sensitive actions can also go through Auto Review before they run.

What went wrong along the way?

A few things, which is normal:

• When the Portuguese pages moved under /pt/, the old addresses needed to send visitors to the new ones. The first version of that rule returned a “page not found” error on Vercel. It was caught by checking the live site after publishing, fixed, tested on a preview first and then published again.
• As mentioned above, the English text was translated by AI and not fully read by a person yet.
• The contact channel on the About page is still empty.

What are the results so far?

There aren’t any to report. The site is new. It has no revenue, ads are turned off and no affiliate links are live. Being honest about that is part of the point: a Bot can build and maintain a site, but it can’t promise that anyone will visit it.

Can you copy this setup?

Yes, at a smaller scale. A sensible order:

1. Build a first small project by hand with our first app guide, to understand the steps.
2. Set up Grok Bot with a Bot whose only job is your site.
3. Buy the domain yourself and keep every account in your name.
4. Add one routine at a time, starting with a health check, and read the first runs.
5. Keep money, accounts and posting with you, as described in our tips.