Until recently, asking an AI for help with my website meant one of us doing all the clicking, and it was always me.
I’d describe the problem. Claude would give me steps. I’d go and look, find the menu wasn’t where either of us thought, come back, describe what I could see instead, get new steps, try again. It worked, and it was still far faster than working it out on my own, but there was always this gap. Claude knew what needed doing. I was the pair of hands.
That gap is where most of my website jobs died. Not because they were hard, but because “find the setting, follow six steps, check it worked” is exactly the kind of task that gets postponed when you have an hour in the evening and a full-time job in the morning.
So when I found out Claude could work inside my browser, I was curious and a bit uneasy about it. Here’s what happened when I tried it on something real.
What it actually did
My site needed a privacy policy link in the footer. Small job. Legally not optional, and it had been on my list for weeks.
I prompted it. Then I watched.
Claude opened my Squarespace admin in a new tab, scrolled down to the footer, clicked into the text block, added the line, linked it to the privacy policy page, changed it from a heading style to small paragraph text so it didn’t shout, and saved. Then it loaded my live site and checked the link was really there and really pointed at the right page.
Two points worth mentioning:
The first is that it did not go smoothly on the first attempt. The Squarespace text editor behaved oddly, arrow keys didn’t do what they should, and the first try mangled the line. Claude undid it, worked out why, and tried a different way that worked. That is roughly what I would have done, except I’d have sworn at it for twenty minutes first.
The second is that I could see all of it. It wasn’t off doing things somewhere I couldn’t follow. Each step appeared on screen in front of me, and I could have stopped it at any point.
What I don’t let it touch
I do the signing in. Every time. Claude has never had a password of mine and never will, and when a login screen appears it asks me to do it rather than trying. Same with any code that arrives by text or email.
I do anything involving money. Card details, payment setup, buying a plan. Not because something went wrong, but because that’s a line worth having before you need it.
I approve anything that can’t be undone. Publishing, sending, deleting. It asks first, and I say yes or no.
I stay in the loop. Especially at the start, I watched every step rather than wandering off to make a cup of tea. I trust it more now than I did a month ago, and I still watch.
None of that is paranoia. It’s the same sense you’d use handing anyone else the keys to your work. The useful thing is that the tool is built to work this way, so you’re not fighting it to stay in control.
What it’s really useful for
It earns its place on the jobs that are fiddly rather than difficult. Settings buried four menus deep. A change that has to be made in the same place on nine pages. Checking whether something you changed last week is still working. Anything where the hard part is the clicking, not the thinking.
It is less useful when the job needs taste. Deciding how a page should feel, what your homepage should say, which of three layouts is better: those are still yours, and that’s fine, because those are the parts you would want to do yourself.
It is also no faster than you for things that are already one click away. If you know exactly where the setting is, go and change it.
What surprised me most wasn’t the speed. It was how many small jobs stopped being postponed. The privacy policy link had sat on my list for weeks because it was boring, not because it was hard. Removing the friction removed the excuse.
If you want to try it
You’ll need Chrome and the Claude extension, and you grant permission one website at a time, which you can take back whenever you like. I keep the current link and setup steps on my tools page, because these things change and a blog post written in November is not the place to promise what a button looks like in March.
Start with something small and reversible. A text change on one page. A setting you know how to undo. Watch it work, see how it behaves, build your own sense of what it’s good at before you hand it anything that matters.
And the habit that makes all of this work, whether Claude is doing the clicking or you are: describe what you can see.
Not “it’s not working”. Say what you were doing, what you clicked, what’s on the screen now, and what you expected instead. Paste the error message word for word. Send a screenshot. Every time I’ve been stuck for an hour, it’s been because I described the problem in four words and expected magic.
That was true when Claude could only tell me what to do. It’s still true now it can do it.