Landing pages with Claude: what’s changed

What’s changed since 2024

The models. Claude 3.5 Sonnet was retired a while ago. The current line-up includes Claude Opus 5.5, Sonnet 5.5, and Haiku 5.5, plus Claude Fable 5.1. For page building, the useful change is context: the current models have a one-million-token window, so you can give Claude the brief, the brand guide, and your existing copy in one go and spend less time re-explaining.

Artifacts you can share. In 2024 an artifact was a preview stuck in the chat window. Now you can publish one to a link that anyone can open without a Claude account, and on Free, Pro, and Max plans you can get embed code for it. On Team and Enterprise plans, sharing stays inside the organisation unless an admin turns on external sharing.

Claude Code publishes pages too. If your team uses Claude Code, it can publish a live page from a working session to a private claude.ai link and update it in place as you go. Each publish is saved as a version, and you choose which one people see. You can share it within your organisation, or publicly where your plan and admin settings allow.

Your design system comes first. Before picking its own colours and fonts, Claude now looks for a design system in your project and gives it priority. Claude Design, a design tool inside Claude, can inherit your organisation’s design system and lets you mock up a landing page as artboards before anything is built. In Claude Code, /design drafts a design canvas from a brief.

Skills. You can package your brand rules (colours, type, logo use, tone) as a skill: a folder with a SKILL.md file that Claude loads when the task needs it. Anthropic’s own example is a brand guidelines skill. Keep it in a shared project folder and everyone on the team works from the same rules.

Getting it live. A published artifact is fine for a prototype or a quick campaign test, but it’s a single self-contained page with no backend, so it can’t handle a form or more than one route. When you’re ready to launch, Claude Design can export standalone HTML or hand off to hosting tools such as Vercel and Netlify, or to Claude Code to build into your real site.

What this means for business teams

The slow part of a landing page used to be the first draft, and all the back-and-forth between marketing, design, and a developer to get there. Now a marketer can get to a clickable first version in one sitting. The conversation moves from “can someone build this?” to “is this right?”

That means the people closest to the customer, such as product marketers, campaign leads, and founders, can build the first version themselves. Developers still matter. Their time just goes on the parts that need them: tracking, forms, performance, and getting the page onto the real domain.

What Claude can’t do is know your customers. The offer, the proof, and the one thing the page has to say are still your call. It will also write confident copy about things it has no way of checking, so every claim, price, and testimonial needs a person to read it. Under Australian Consumer Law, the business publishing the page is responsible for what it says.

The risks to manage

Brand drift. Left to itself, every page comes out a little different. Sort this once: put your tokens in a project file or a brand skill, or set up your design system in Claude Design, so every page starts from the same base.

Accessibility. A page can look polished and still fail people using a screen reader or keyboard, or anyone who struggles with low-contrast text. Ask Claude to check colour contrast, heading order, alt text, and keyboard focus, then run an accessibility checker yourself. Looking good isn’t the same as passing.

Sharing settings. Know what you’re publishing and who can see it. Public links are public. On a Team or Enterprise plan, check with your admin before sharing anything outside the company.

A short walkthrough

• Write a one-paragraph brief. Who the page is for, the one action you want them to take, and the proof you have. Paste in real copy and facts so Claude isn’t filling gaps.
• Give Claude your brand. Point it at your design system, a brand skill, or a short list of colours, fonts, and spacing. If you have none of these, start there.
• Ask for options first. Get two or three layout directions side by side (in Claude Design or as an artifact), pick one, then refine it.
• Iterate in plain language. “Move the testimonial above the fold.” “Cut the headline to eight words.” “Make the button say what happens next.”
• Check it properly. Read every claim, run an accessibility check, and look at it on your phone.
• Decide where it lives. An artifact link is fine for internal review or a quick test. For the real thing, export it or hand it to whoever runs your website, so tracking and forms are set up properly.