Message
Does the headline explain the offer, audience, and next step quickly?
All use cases
For client approval
Share a client website preview without the production handoff.
Clients should be able to open the draft, understand what changed, and tell you what to adjust. A browser preview link keeps that conversation around the work instead of around attachments and setup instructions.
Review lens
What the client should review
Use the preview to ask a bounded question. A clear review surface produces better feedback than a request to review everything.
Experience
Can the client follow the page on a phone and desktop without needing your development setup?
Approval
Is the current version ready to move forward, or is there one concrete change to make first?
A real moment for the page
A browser link makes the next conversation concrete.
Homepage approval
Send the current hero, navigation, and first-scroll story before you connect the CMS or production domain.
Campaign landing page
Let marketing and legal reviewers click the same static draft and leave a focused list of changes before launch.
Handoff before handoff
Give a client a stable browser link to confirm copy, responsive behavior, and content hierarchy before engineering takes over.
Why this handoff works
Keep the useful part close to the artifact.
Reduce review friction
Clients do not need a local server, repository access, or a development environment to open the draft.
Create a shared reference
A URL gives every comment a common version of the page, which makes revisions easier to name and compare.
Protect the production boundary
Keep an unapproved draft out of the final deployment while still giving the client something real to react to.
A three-step workflow
From the right files to the right reaction.
- 01
Prepare the review build
Export the current HTML and include CSS, JavaScript, images, and fonts. Use a ZIP if the draft has assets.
- 02
Open and check the page
Test the link yourself, especially mobile layout, navigation, forms, external links, and image paths.
- 03
Send a bounded ask
Share the preview with the review goal and deadline so the client knows whether you need copy notes, approval, or a new brief.
Know the boundary
A preview is useful because it is honest.
HTMLShare publishes browser-ready static output. Keep builds, source tools, private access, live data, and production operations in the systems built for them.
A preview is not approval software
HTMLShare provides the browser link. Keep comments, change requests, and sign-off in the client workflow your team already uses.
Noindex does not restrict access
A noindex preview is not a password-protected client portal. Avoid placing confidential data or credentials in the page.
Use production hosting at launch
Move the approved page to production hosting when it needs a custom domain, CMS, analytics, or a permanent audience.
Keep exploring
The next useful page is nearby.
Before you publish
Client website preview FAQ
How do I send a website draft to a client?
Upload the single HTML file or a ZIP containing the static project, verify the browser preview, and send the resulting URL with a short review request.
Can a client edit the preview directly?
The preview is for viewing and review. Clients can respond through your normal feedback process; HTMLShare does not replace your project-management or commenting system.
Can I use a client preview as the final website?
Use it for review and approval. Deploy the approved output to production hosting when the site needs a canonical URL, custom domain, analytics, or ongoing operations.
Ready for the next review
Put the current page in front of the right person.
Create a noindex preview link for the static HTML or ZIP project, then move approved work to production when it is ready.