We have just gone through a massive transition in how authors use AI, and almost no one is talking about it.

Most of the discussion around AI has focused on writing. But AI can now do something different: it can perform tasks for you. As an author, that means you can delegate many non-writing tasks that eat up your time.

Instead of AI telling you what to do, you tell the AI what to do, and it does it.

In this tutorial, I'll show you how to create a Grok Bot that can update your website for you.

What is a Grok Bot?

A Grok Bot is an AI agent with its own computer that can do tasks for you even after you close your computer.

I already have several Grok Bots working for me (see left panel in the above screenshot):

• A Chief of Staff bot that delegates tasks to other bots.
• A PR bot that helps schedule interviews and find podcast opportunities.
• An ISBN bot that checks metadata across Bowker, Amazon, and other retailers.
• A Social Media bot.
• An Advertising bot.
• An Amazon bot.

Today we're going to create a Webmaster bot that can update a WordPress website.

Step 1: Create a New Webmaster Bot

Start a new chat and select Create New Bot.

Name the bot Webmaster.

Normally, Grok will begin asking setup questions, but I use a starter prompt instead.

The prompt is simple:

“You are the webmaster for example.com. Explore the site, log in, and then connect with a WordPress application password. Use the REST API whenever possible. Don't publish or delete anything until I approve.”

Send the prompt.

Since Grok Bot has its own computer and browser, it can do tasks for you:

• Log into WordPress through a browser just as a human would.
• Connect directly through WordPress application passwords and the REST API.
• Switch between browser automation and API access depending on the task.

The first time it connects, you'll need to help it log in.

After sending the prompt, Grok begins exploring the site and identifying the WordPress setup.

It typically responds by summarizing what it's about to do and asking for confirmation through its actions rather than immediately making changes.

Step 2: Log In and Connect the Bot

Eventually, Grok reaches the WordPress login page and needs your assistance.

I can now control Grok Bot's computer, so I open the remote browser session and log in to the website.

After logging in:

1. Save the session.
2. Click “I'm done. Continue.”
3. Hand control back to Grok.

Grok will then create and configure its own WordPress application password and establish a connection to the REST API.

Previously, this process required manually creating credentials and configuring tools yourself. Grok handles that setup automatically.

Once connected, it reports back on what it finds:

• WordPress version
• Installed plugins
• Themes
• Number of pages and posts
• Other site details

Grok Bot is not fast. In a way, it’s like a Roomba, running into things in your living room while it vacuums. You could vacuum your living room faster than a Roomba, but the Roomba’s slower work still frees you to do something else.

That's the real advantage.

You can send Grok instructions from your phone and let it work while you're writing, traveling, or doing other tasks. It doesn't need access to your computer because it has its own.

Adding the Bot to a Team

After connecting the Webmaster bot, I add it to my publishing team alongside my other Grok Bots.

I also use a Chief of Staff bot that delegates tasks one at a time. This helps conserve usage limits, since Grok currently restricts how much activity your bots can perform. Over time, usage limits will likely improve, and direct integrations with websites and applications will become more efficient.

Step 3: Give the Bot a Task

Once the bot reports that it's connected and ready, it's time to assign a website update task.

In my case, I wanted to update my podcast page.

I recently launched a new podcast called Daily Aristotle, but it wasn't listed anywhere on my website. Rather than updating the page myself, I asked Grok to do it.

My instruction was:

“I want you to add the podcast Daily Aristotle to the list of podcasts on my podcasts page. You can find out more about Daily Aristotle at dailyaristotle.com.”

That's it. No detailed instructions or explanation of where to place it. There’s no description of the formatting. I’m being intentionally vague so you can see what Grok Bot is capable of, so I simply told it the outcome I wanted.

One of Grok Bot's strengths is handling outcome-based instructions. Instead of telling it exactly how to perform the task, I simply told it what I wanted.

Grok responded by:

1. Reviewing the existing podcast page.
2. Visiting DailyAristotle.com.
3. Finding the podcast information.
4. Locating the cover art.
5. Determining how the existing podcast listings were structured.
6. Planning a matching addition.

It even decided to follow the formatting pattern already used elsewhere on the page.

That was exactly what I wanted, yet I never explicitly told it to do that.

Step 4: Let the Bot Gather Information

As Grok worked, it reported its progress.

It found:

• The podcast website
• The podcast cover image
• Descriptive text
• Existing page formatting patterns

It then prepared a draft that matched the layout of the other podcast listings.

This is one of the most impressive aspects of modern AI agents. Rather than waiting for detailed instructions, they can infer the intended result from context.

What other tasks can Grok Bots do?

Grok Bots can do much more than update websites.

For example, you could create routines that:

• Check Amazon reviews every week.
• Collect new reviews into a document.
• Summarize reader feedback.
• Identify recurring praise.
• Highlight constructive criticism.
• Draft newsletter content.
• Gather information from multiple sources automatically.

You can also build workflows where multiple bots collaborate.

For example:

• A Webmaster bot could request book information from an Amazon bot.
• An Amazon bot could gather metadata.
• A Chief of Staff bot could coordinate the process.

The bots can even message one another and share information.

What happens when Grok Bot hits an obstacle?

While updating my site, Grok discovered that one of my plugins didn't expose the functionality it needed through the REST API. Instead of stopping, it switched to browser automation and continued working through the WordPress dashboard.

This is one of the reasons Grok is so useful. When one approach fails, it often finds another.

Occasionally it will need your help. You will occasionally need to help by entering passwords or answering questions, but it is surprisingly capable of solving problems independently.

Step 5: Review the Proposed Changes

After completing the draft, Grok Bot asked whether I wanted to publish the changes because my initial prompt said, “Don’t publish or delete anything until I approve.”

Now, rather than publishing immediately, I requested a preview.

I replied, “Can I see a preview?” (Normally, I would just tell it to publish, but I want to demonstrate how you can supervise the bot if you want).

Grok created a draft version while leaving the live page unchanged.

The preview showed:

• Cover art
• Description
• Website links
• Podcast links
• Formatting that matched the rest of the page

It even noted a formatting inconsistency and suggested improvements before publishing.

Step 6: Publish the Update

Once I reviewed the draft, I approved the changes.

I told Grok Bot, “Publish it now and tweak it to look closer to Novel Marketing.”

That was enough. I simply talked to it the same way I would talk to a human webmaster. After a few moments, the changes appeared on the live site.

The new Daily Aristotle section had been added successfully. If I wanted further adjustments, I could continue giving simple instructions such as, “Move the image to the right,” or “Change the shade of blue,” and Grok Bot would then make those changes.

Grok Bot vs. Claude Code and other AI Agents

Some people may wonder how Grok compares with tools like:

• Claude Code
• Codex
• Cursor

In my experience, Grok is easier to use for tasks involving:

• Website logins
• Passwords
• Browser automation
• WordPress administration

Claude Code is powerful, but credential management can be cumbersome. It often requires terminal commands, scripts, or additional setup. If you are familiar with those technicalities, Claude Code is a fine choice. If you are not, Grok Bot will be easier for you to use.

Claude Code would likely be my second choice for a project like this. Cursor and similar tools can also perform these tasks, but I've generally found them less capable when interacting with complex WordPress interfaces.

Building Websites from Scratch

We're entering an era of agentic AI, where multiple AI systems can perform real-world tasks on our behalf. There's also nothing preventing Grok from building an entire website.

I'm considering adapting my free author website course into a Grok workflow.

In theory, you could provide Grok with instructions, and it could:

• Register a domain
• Set up hosting
• Install WordPress
• Configure Divi
• Build pages
• Assemble the website

It would still prompt you to handle payments and account logins, but Grok Bot could perform much of the technical work. Building a complete site would take longer than updating a page, but it could work in the background while you focus on other tasks, like writing your novel.

Why does this matter for authors?

For years, authors worried that AI would take away the creative parts of writing while leaving them with administrative work. What excites me about Grok Bot is that it does the opposite.

It allows you to delegate:

• Marketing tasks
• Website maintenance
• Administrative work
• Data collection
• Reporting
• Routine updates

That means you can spend more time writing, and that's the promise many authors have hoped AI would deliver.

A Simple Example

One of the first tasks I gave Grok was updating a small design element on AuthorMedia.com.

There was a blue hover line in the navigation menu that didn't match the blue used elsewhere on the site. Fixing it wasn't difficult, but it would have required me to spend time figuring out where the setting lived.

Instead, I simply told Grok, “Change that blue line to match the blue in the logo.”

Grok analyzed the site, identified the difference, found the correct setting, and made the change on its own. That was the moment I realized how much this technology changes the way we interact with websites.

Instead of learning how to perform every technical task yourself, you can simply describe the result you want.

Final Thoughts

Grok Bot is still new, and we're only beginning to see what these AI agents can do. Updating a website is just one example.

The larger opportunity is having a digital team that handles routine work while you focus on creating books, articles, podcasts, and other content. This tutorial only scratches the surface.

If you're curious, visit Grok.com and explore what Grok Bots can do.

Related Patron Toolbox Website Tools

Analysis and Diagnostic Tools

• Homepage Scanner: This tool audits your website for clarity and usability so you can turn more visitors into subscribers.
• About Page Scanner: You can scan your bio and layout to receive expert feedback on your storytelling and professional presence.
• Book Page Scanner: This diagnostic tool reviews your individual book pages for completeness and selling power.
• SEO/GEO Optimizer: You can audit any page to get AI-ready titles and meta descriptions that help search engines and AI assistants find your work.

Content Drafting Tools

• About Page Drafter: This tool acts like a marketing consultant to help you blend your personality with professional accomplishments into a memorable bio.
• Landing Page Drafter: You can generate text for newsletter signups or book sales pages to build your email list faster.
• Blog Optimizer: This tool brainstorms magnetic titles and provides search optimization tips for every post you write.