Turn a website review into a Claude Code artifact: one page you can read in a browser and update at the same link. You will check its contents privately, then choose an appropriate audience for sharing.
Before you start
- An interactive Claude Code CLI session signed in with /login to a Pro, Max, Team, or Enterprise claude.ai account, using Anthropic as provider.
- Artifacts enabled for your session and organization. API-key sessions and third-party model providers cannot publish; organizations with CMEK, HIPAA, or Zero Data Retention enabled are excluded.
- A short set of non-private review notes, real findings, and a decision about who should see them. Use a current Claude Code version; /artifacts requires v2.1.208 or later.
Want to do it yourself?
- Difficulty
- 6 out of 10
- Estimated completion time
- 45–90 minutes for a small page
Skills you’ll need: Provide a clear page brief, inspect the live artifact, and test interactions and sharing access.
How this helps your brand
A clear review artifact can give collaborators one current account of website findings and next actions. Evidence labels and deliberate sharing help keep that account useful without presenting unverified suggestions as completed work.
Step 1: Choose information that belongs on one page
For a first artifact, use a review you already understand: three website issues, the evidence for each, and the next action. Remove customer information, keys, internal links, or material your audience should not see.
An artifact is a self-contained page without an application backend. Keep this example to a review summary and checklist. A working customer database or booking system needs a different implementation.
Step 2: Ask for a private review artifact
Paste the prompt below into the session with your notes. Ask for a clear title and distinguish confirmed findings from suggestions. Do not ask Claude to fetch live customer data for this first page.
Claude returns the published URL. New artifacts are private to you until shared. Open the link, read the page, and compare it with your original notes before distributing it.
Illustrated exampleA review page built from evidenceIllustrative artifact Private to youNorthline website review Two observed issues. One recommendation to consider.
Confirmed findingsEvidence → next action- 01 Home · quote link
Tapping “Request a quote” opens a 404 at
Next: point the link to/quote./contact.- 02 Contact · hours
The page says “Open Sunday”; the supplied hours say closed.
Next: correct the Sunday hours.
Illustrative content, not a Claude interface. Compare the private page with your original notes: each finding needs evidence and an action, while an untested idea stays a recommendation. Step 3: Test the page and correct its claims
Check that every issue has the right page name, evidence, and next action. If the page includes checklist controls or links, try them. A visual status such as Complete should describe verified work, not a recommendation.
Ask for one correction and tell Claude to update the existing artifact. Reopen the same URL and check the correction. Updating in place keeps readers on one link; it does not mean the page automatically reads fresh website data.
Illustrated exampleCorrect the claim, keep the linkOne published URLReopen the original link after each update.- 1Read the first page
“Quote link fixed · Complete”
The review describes a fix nobody has tested.
- 2Ask for one correction
Update this existing artifact: change the quote-link status to “Awaiting check”. We have not tested the fix.
- 3Verify at the same link
Quote link · Awaiting check
Next test: tap Home’s quote link on a phone and confirm the Contact page opens.
An updated artifact reflects the facts you provide. It does not automatically recheck your website.
Updating a status is not proof that the website is fixed. This example corrects an unsupported “Complete” claim and leaves the real-world test clearly pending. - 1
Step 4: Choose sharing deliberately
Open Share in the artifact page header. On Team and Enterprise you can grant access to specific people in your organization or the organization as a whole. A public link can be opened by anyone without signing in; public sharing on organizational plans needs Owner enablement.
Select the narrowest audience that fits the review. If you share publicly, remove anything that only your team should see before enabling that link. Test the link in a separate browser session for the intended audience.
Illustrated exampleChoose how far the page travelsStart private.Expand access only as far as the review needs.
- Only youInitial review
Read and correct the page before sharing.
- People in your organizationMatch the team
On Team or Enterprise, choose specific people or the whole organization.
- Anyone with the public linkWidest audience
No sign-in required. Remove team-only details before enabling it.
Test the chosen audienceOpen the link in a separate browser session with the intended access.
Public sharing on organizational plans requires Owner enablement.
These are audience scopes, not a sequence you must complete. Use the narrowest available scope that fits your readers, then test their access. Step 5: Recover a missing page or lost link
If Claude writes local HTML without a published URL, ask which artifact requirement failed. Check your login, provider, and organization settings; a local preview is not a shareable artifact.
If you lose a working link, run /artifacts. Select the artifact and press o to open it. For updates from another session, provide its URL or attach it through /artifacts so Claude updates the intended page.
Step 6: Keep the shared version accurate
When a finding is resolved, give Claude the exact result and ask it to update that artifact. Read the changed page again, especially after changing the audience or public version.
Keep a brief note of what was tested and when. If you cannot verify a fix, label it as awaiting a check instead of turning the item green.
You're done when
- The published URL opens and the contents match your source notes.
- A correction appears at the same URL.
- Sharing matches the intended audience and you have tested the audience’s access.
- The page separates verified results, pending checks, and recommendations.
Your prompt
Show promptHide prompt
COPY AND PASTE
Create a Claude Code artifact titled [review title] from these website review notes: [notes]. Make one readable page with a short summary, a table of confirmed issues and their evidence, and next actions. Separate recommendations from observed problems. Use only the facts in my notes and mark missing evidence as unverified. Keep the artifact private; do not enable public or organization sharing. Do not connect live data sources or change the website. Give me the published URL and a short list of things I should check before sharing.
Paste this into an eligible interactive Claude Code session with the notes available. Replace the bracketed fields before publishing.
FREE BY EMAIL
Get the full AI guide
Our complete, step-by-step guide to using AI in your business, sent straight to your inbox.