makeitrun

MakeItRun blog

Beyond the Chat Window: What Happens After Claude or ChatGPT Builds Your Tool

2026-08-11 · MakeItRun team

The direct answer. Nothing happens to it, by default. Whatever Claude or ChatGPT just built (a menu, a calculator, a dashboard) sits inside that one conversation until you do something about it. Claude renders it as an Artifact; ChatGPT hands it back as a code block or, on older models, a Canvas panel. Neither one is a website yet. Three things change that: getting the HTML out of the chat, deciding where it should live (Claude's own Publish button, ChatGPT's Share link, a general host like GitHub Pages, or a purpose-built tool like MakeItRun), and choosing who's allowed to see it, because "public" and "findable on Google" turn out to be two different settings, not one. This page is the map. Every post linked below covers one leg of that trip in more depth; read this one first if you're not sure which leg you're on.

What "Claude built it" actually means right now

Open the artifact pane or the code block and it looks finished: styled, interactive, working. It isn't public. It's rendering inside your browser, tied to that one chat, and nobody else has a link to it. Claude calls this an Artifact. ChatGPT calls it a code block today (OpenAI folded Canvas into inline blocks for its default models in May 2026; a few legacy models still show the old side panel). Different names, same fact underneath: it's HTML text sitting in one conversation. It isn't a program, nothing was installed, and nobody else can open it yet.

If that paragraph is the confusing part, if "HTML" and "artifact" and "code block" all sound like the same fog, start with ChatGPT Gave You HTML. Now What? A Non-Developer's Guide to Making It Real. It's written for the reader who doesn't yet know what a "file" is supposed to do, and it stays there rather than jumping ahead to hosting options.

The moment you hit "Publish"

Both Claude and ChatGPT have a native button for this, and for a one-off share, it's the right tool: free, already open, no setup. But "Publish" and "Share" both mean the same specific thing: a standing public URL, viewable by anyone with the link, no account required on their end. Claude's own help center says so directly, and it adds two catches most people don't find out about until they matter: unpublishing is one-way (you can't republish that same artifact; you rebuild it from scratch), and Team/Enterprise accounts can't publish publicly at all. How to Share a Claude Artifact So It Doesn't Disappear When You Delete the Chat covers that trap in full, with the fix.

There's a second catch that has nothing to do with permanence: a public link with no login is also, mechanically, a public web page, and public web pages can end up in Google. Your Claude Artifacts Are Showing Up in Google covers what actually happened when a Reddit thread turned up hundreds of published Claude pages in ordinary search results, why a robots.txt block isn't the same protection as noindex, and how to check what you've already published. Read it before you publish anything with a client's name, a price list, or internal numbers on it.

Every place it can live, compared honestly

Claude's and ChatGPT's own buttons aren't the only options, and neither is the tool putting the demo link at the bottom of this page. We've written two full, vendor-checked comparisons, and they answer slightly different questions:

The short version, true as of today: MakeItRun doesn't have a custom domain yet (AppDeploy and livemy.app both beat us there), and we don't have analytics, where static.app is ahead. What we do have: publishing straight from the chat via the MCP connector, four access modes (public, signed-in, allowlist, private), noindex by default so a page only shows up on Google if you flip that on yourself, RSVP capture with a CSV export if the page collects anything, and a QR code (a real SVG download from your dashboard, not something stamped onto the page automatically).

What actually changes once it's a URL you control

This is the part that's easy to undersell: publishing isn't just "now there's a link." A few things become real that weren't options inside the chat.

Permanence. Re-publishing an update lands on the same URL instead of minting a new one. There's no new link to redistribute every time you change a price or fix a typo.

Who can see it. Public, signed-in-only, an allowlist of specific people, or fully private. Claude's and ChatGPT's own share links don't give you any of that control.

Whether it's findable. Separate from who can open the link, whether a search engine can find it is its own toggle, off by default.

A QR code that doesn't require a third-party tool. Every page's dashboard has a QR download next to it. It's genuinely useful the moment a link needs to end up on a menu, a flyer, or a door.

Somewhere for responses to land. If the page collects anything, like an RSVP form, an intake sheet, or a signup, submissions land somewhere real instead of going to a mailto: link nobody checks.

None of that exists the moment Claude or ChatGPT hands you the code. All of it exists the moment you publish somewhere built for it.

Picking the right path for your situation

You're a shop owner and you just want it online. Skip the coding-agent detour entirely. Should a Shop Owner Use Claude Code? An Honest Answer (With a Worked Example) makes the case, plainly, that most shop owners don't need Claude Code at all. It's a narrower question than this page (Claude Code vs. the regular chat), useful if someone told you to "use Claude Code" for something that's really just a page.

You're already using Anthropic's back-office bundle. Claude for Small Business connects Claude to QuickBooks, HubSpot, PayPal, and the rest. It's genuinely useful for the operations side, and it has no publish button at all. Claude for Small Business Automates Your Back Office. Here's How to Publish What You Build With It. covers exactly that gap. Skip it if you're not using that specific product.

You don't have a project yet and want ideas. Three of our posts are browsable idea lists, and they overlap with each other more than they differ, so pick one rather than reading all three back to back. 18 Things to Build with Claude (and Actually Put Online) is the broadest, covering menus, calculators, dashboards, link pages, and event pages, each with a starter prompt. Five Things People Are Building in Claude (and How to Put Them Online) walks the same ground through five specific personas (a bar owner, a florist, a founder, an EA, a coffee roaster) if you'd rather see the whole build-to-publish arc told as a story once. Free Calculators Built with Claude (And Live Online in Minutes) is the narrowest and the most concrete: six calculators that are actually live right now (coffee ratio, dog age, cat age, sleep cycles, pizza dough, startup dilution), useful if you specifically want a calculator and a prompting pattern to copy, skippable otherwise.

A real one, built and published, not a hypothetical

We asked Claude for a class sign-up page for a small yoga studio in one prompt, then published the resulting single-file HTML exactly the way this post recommends.

Sunroot Yoga: Class Sign-Up. Tap a class to see real capacity (Vinyasa Flow, Restorative, Power Hour), enter your name and email, and reserve a spot. Fill the class and the button switches itself to "Join the waitlist" instead of failing silently.

See it live: https://sunroot-yoga-signup.clientview.page

QR code linking to the live Sunroot Yoga class sign-up page

Reserve the last two spots in Restorative and watch the next signup land on the waitlist automatically. On a real MakeItRun page, turning on RSVP capture means every one of those signups lands in a dashboard the studio owner can actually read, instead of a form that quietly emails no one.

FAQ

What actually happens to my Claude artifact or ChatGPT output if I do nothing?

It stays exactly where it is: inside that one conversation, visible only to you, with no link anyone else can open. Nothing expires on a timer, but nothing becomes shareable either, until you either click the native Publish/Share button or move the HTML somewhere else.

Is a "published" Claude artifact the same as a website?

Functionally, yes: it's a public URL anyone can open, no account required. It differs from a normal website in ways that matter: no custom domain, no owner control over search indexing, and unpublishing is permanent for that specific artifact.

Do I need to pick one hosting option forever, or can I switch later?

You can switch any time: the HTML itself is portable. Nothing about publishing through Claude's own button, ChatGPT's Share link, or a third-party host locks the underlying file to that platform; you can always copy it out and republish elsewhere.

What's the single biggest thing people get wrong about "publishing"?

Assuming "I sent someone a link" and "this is now a public web page a search engine might find" are the same decision. They're not, on most platforms, which is exactly the gap Your Claude Artifacts Are Showing Up in Google covers.

What should I actually do right now?

Copy the HTML out of the chat, then either paste it at app.makeitrun.ai or ask Claude/ChatGPT to publish it directly if you've added the MakeItRun connector. A live link and a downloadable QR code show up in seconds, and you decide who can see it and whether it's findable on Google, not the chat app.

Built something in Claude or ChatGPT?
Get a live link, decide who sees it, and keep it out of Google unless you say otherwise.
Get your link →

Read next: Where Should You Put the Thing Claude Built? Every Option, Compared · More from the MakeItRun blog →