How We Rebuilt Our Website With Claude Code

What the session covered

We recently rebuilt vertodigital.com from the ground up using Claude Code. Instead of just telling people it worked, Zoran Arsovski and Nikol Anestieva walked the room through how it actually went - the approach, the workflow, and the parts that didn't go as smoothly as the hype suggests.

They covered why they chose Claude Code and what they expected going in, then the actual workflow: planning, prompting, reviewing, and publishing, page by page. That included where it handled the work well, and where it needed a human to step in - on copy accuracy, brand tone, and judgment calls a model can't make alone.

• SEO and AEO were built into the brief from day one, not bolted on after launch - schema, sitemaps, markdown mirrors, and llms.txt were part of the initial build plan.
• The design system was built with Claude directly, using written brand voice and visual identity references so the output stayed consistent page to page.
• Going CMS-free and what the new technical infrastructure looks like - static HTML on Cloudflare Pages, a staging and production branch workflow, and no build step to maintain.

They also covered time and effort saved versus a traditional build, and how the team is approaching maintenance now that the site is live - and one honest note: the session ran well over its 90-minute slot, because once the questions and stories started, nobody in the room wanted to cut it short.

The bigger takeaway for attendees: marketers can get a lot closer to the build process now. You don't need to start by shipping a full production website - start with a prototype, learn how the workflow actually works, then build from there.

If your own rebuild is really a migration - an existing domain, existing rankings, existing content to carry over - the considerations are different. Our website migration SEO insights video covers the planning and traffic-loss questions this kind of rebuild doesn't have to answer.