How to Preview a Weebly Site Before Publishing
Use Weebly Preview to check desktop, mobile, links, and layout before publishing. Learn how to share drafts, test limitations, and capture previews.
To preview a Weebly site before publishing, open the site in the Weebly editor and click Preview in the top toolbar. Weebly opens a full-width view of the site as visitors will see it. Use the phone and computer icons to check responsive layouts, use Share if someone else needs to review the draft, then return to the editor, fix issues, preview again, and click Publish only when the site is ready.
1. Open Weebly Preview
- Open your site in the Weebly editor.
- Click Preview in the top toolbar.
- Review the full-width rendering outside the editing canvas.
- Toggle the phone and computer icons to inspect mobile and desktop layouts.
Preview is separate from publishing. You can inspect the draft without making it live. Weebly describes Preview as a way to see the site outside the editor environment before publication.
2. Run a complete pre-publish review
Do not stop after checking the home page. Walk through every page and navigation path as a visitor would.
| Area | What to check | Typical failure |
|---|---|---|
| Pages and navigation | Open every navigation item, dropdown, footer link, and call-to-action. | A page is missing from navigation or a link points to an old URL. |
| Responsive layout | Switch between computer and phone views. Check headings, columns, buttons, images, and spacing. | Text wraps badly, content is clipped, or a button is difficult to tap. |
| Content | Proofread headings, body copy, prices, contact details, and page titles. | Placeholder text or incorrect business information remains. |
| Images | Check cropping, resolution, alt text, and loading behavior. | An image is stretched, blurry, or crops out the subject. |
| Forms | Confirm fields, required settings, confirmation text, and recipient addresses. | The form looks correct but cannot be functionally tested in Preview. |
| SEO basics | Review each page title and description and confirm the intended site address. | A draft title or temporary address is published accidentally. |
Check the mobile view deliberately
Mobile preview is not only a smaller desktop view. Look for navigation that becomes difficult to open, long headings that push key content below the fold, buttons that are too close together, and sections whose order no longer makes sense. Check the first screen visitors see and the final call to action on every important page.
3. Share a private preview
When another person needs to review the draft, click Share while Preview is open and send the private link. Ask reviewers to report the page, device view, and exact problem so corrections are easy to reproduce.
Weebly Cloud documentation also describes a temporary preview URL that can be copied from the browser address bar and sent to site owners or team members. That documentation says the URL remains valid for 30 days. The Cloud Admin preview button is not available to users who enter the site from the User Portal.
Keep preview access controlled
- Send preview links only to the people who need them.
- Remove access when feedback is complete if your workflow supports it.
- Do not treat a preview URL as a substitute for authentication or production access control.
- If you need a controlled audience after publication, use whole-site or page-level password protection in Weebly settings.
4. Understand what Preview cannot test
Preview is primarily a visual and navigation review. Weebly Cloud documentation lists several features that do not work in preview sites:
- Blogs
- Commerce and store workflows
- Search
- Forms
- Membership
For these features, use an appropriate test process after publication or in a controlled environment. For example, verify a form submission with a test address, place a test order where your payment setup permits it, and check member-only pages with a test account. A page can look correct in Preview while its server-side behavior remains unverified.
5. Confirm the address before publishing
If you do not have a custom domain yet, Weebly lets you choose a free yournamehere.weebly.com subdomain in Settings > General. Confirm spelling, capitalization, and the intended address before you publish. A correct preview at the wrong address still creates a launch problem.
If a published site is not visible, first confirm that you clicked Publish, then check the address for typos. Weebly also provides Unpublish in Site Settings if you need to take the site offline temporarily and republish it later.
6. A repeatable preview workflow
- Prepare: finish the page structure, content, images, links, and settings.
- Preview desktop: inspect every page at full width.
- Preview mobile: switch to the phone view and check layout, spacing, and tap targets.
- Navigate: follow the menu, footer, buttons, and internal links from the visitor’s perspective.
- Review with others: use Share or the documented temporary preview URL.
- Test unsupported functions separately: verify forms, commerce, search, blogs, and membership in a suitable environment.
- Correct and repeat: return to the editor, fix issues, and run the same checklist again.
- Publish: click Publish only after visual and functional checks are complete.
7. Capture a preview for review or documentation
A browser screenshot can preserve a visual record of a draft for a client, approval ticket, or regression check. Capture the preview URL after opening it in a normal browser session. If the preview requires a login or an access cookie, the capture tool must support custom cookies or headers; otherwise it may capture a sign-in page instead of the draft.
Or skip the browser setup
ScreenshotNeo provides a website screenshot API and MCP server. Send one GET request with the preview URL to receive a PNG, JPEG, WebP, or PDF. Its capture flow accepts cookie and consent banners like a visitor, then removes more than 60 known consent platforms, newsletter popups, and chat widgets before the shot. Each step can be turned off.
Only clean shots are billed. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and the response identifies the result with X-Page-Verdict and X-Billed headers. The API also supports custom cookies, headers, user agents, authorization, waits, CSS selectors, full-page capture, device presets, PDF output, and signed links. An MCP server exposes take_screenshot, get_page_info, and capture_pdf to Claude, Cursor, and other MCP clients.
See the ScreenshotNeo API documentation for all parameters.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" \
-d access_key=YOUR_API_KEY \
--data-urlencode url=https://your-site.weebly.com \
-o weebly-preview.webp
Python
import requests
r = requests.get(
"https://api.screenshotneo.com/v1/shot",
params={
"access_key": "YOUR_API_KEY",
"url": "https://your-site.weebly.com",
},
timeout=90,
)
r.raise_for_status()
open("weebly-preview.webp", "wb").write(r.content)
Node.js
const q = new URLSearchParams({
access_key: 'YOUR_API_KEY',
url: 'https://your-site.weebly.com'
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot failed: ${res.status}`);
const fs = await import('node:fs/promises');
await fs.writeFile('weebly-preview.webp', Buffer.from(await res.arrayBuffer()));
For a private Weebly draft, supply the required cookie or authorization values using ScreenshotNeo’s request options. For a long page, enable full-page capture and lazy-image loading. For a specific section, capture an element by CSS selector. Use a cache TTL when repeatedly reviewing an unchanged draft, and disable caching when each capture must reflect the newest edit.
You can start with 1,000 screenshots a month free with no card. Paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account.
8. Troubleshooting
| Problem | Cause | Fix |
|---|---|---|
| Preview button is missing | You may be outside the site editor or using a different Weebly interface. | Open the site in the editor and look in the top toolbar. If using Weebly Cloud, check whether you entered through the User Portal, where the Cloud Admin preview button is unavailable. |
| Someone cannot open the preview link | The link is private, temporary, expired, or restricted to a specific account. | Generate a new Share link, confirm the recipient has access, or copy the current temporary URL again. Cloud preview URLs are documented as valid for 30 days. |
| Forms do not submit | Forms do not work in Weebly preview sites. | Test the form after publication or in a controlled environment with a test recipient. |
| Store or membership features fail | Commerce and Membership are preview limitations. | Perform a separate authenticated or transaction test outside Preview. |
| Search returns nothing | Search is not supported in preview sites. | Verify search on the published site or another supported test environment. |
| Published site is not visible | The site was not published or the address is misspelled. | Click Publish and check the exact domain or Weebly subdomain spelling. |
| Screenshot shows a login page | The preview requires a session cookie or authorization header. | Capture from an authenticated browser, or pass the required cookie or header to a screenshot API that supports them. |
| Screenshot contains popups or chat | The capture happened before overlays were dismissed. | Use a capture flow that can accept consent and remove known popups, or configure selectors and wait conditions before capture. |
9. Performance, reliability, and cost considerations
- Preview speed: Review the home page first, then work through secondary pages. Large images, third-party embeds, and scripts can make a preview appear incomplete until loading finishes.
- Reliable visual checks: Repeat a capture after edits and keep the viewport consistent when comparing versions. Use both desktop and mobile dimensions.
- Dynamic content: Wait for a selector, a fixed delay, or network idle before capturing content rendered by JavaScript.
- Long pages: Full-page captures can be larger and slower than viewport shots. Capture a key element when a whole-page image is unnecessary.
- Cache control: Caching reduces repeated work when a draft has not changed. Use a short TTL or disable caching while actively editing.
- Cost: ScreenshotNeo bills only clean shots. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers show the verdict and billing result.
10. FAQ
Can I see my Weebly site without making it live?
Yes. Click Preview in the editor. The site opens in a full-width visitor-style view without publishing it.
Can I preview both desktop and mobile layouts?
Yes. Use the computer and phone icons in Preview to switch between layouts.
How long does a Weebly Cloud preview URL last?
Weebly Cloud documentation says its temporary preview URL remains valid for 30 days.
Can I send a private preview to a client?
Yes. Use Share in preview mode, or use the documented temporary preview URL where available.
Why does my form work in the editor but not in Preview?
Forms are listed as a preview limitation. Test submissions separately in a suitable environment.
Should I publish to test a store?
Preview does not support Commerce workflows. Use a controlled test process that lets you verify checkout and order handling safely.
Can I take a screenshot of a private draft?
Yes, if the capture process has the draft’s required session cookie or authorization header and waits for the page to finish loading.
Final pre-publish checklist
- Every page opens from navigation and footer links.
- Desktop and phone previews have no clipped or overlapping content.
- Headings, images, buttons, links, page titles, and descriptions are final.
- The intended domain or Weebly subdomain is spelled correctly.
- Forms, commerce, search, blogs, and membership have been tested outside Preview where required.
- Reviewers have approved the shared draft.
- You clicked Publish only after the final correction and preview cycle.


