Help & quickstart
LandingConnect deploys static sites from Claude Cowork or Claude Code to <you>.landingconnect.com, with automatic SSL on your own domain.
1. Deploy your first site (≈2 minutes)
- In Cowork or Claude Code, add the connector:
https://connect.landingconnect.com/mcp - Run
account.signin. It gives you a short code — approve it on the pairing page with your email. - Tell it: “deploy my site to <name>”. The reliable path is inline files (the connector sends each file directly — no upload step), so it works even in sandboxed environments.
- Your site goes live at
<name>-xxxx.landingconnect.com. A clean, no-suffix “vanity” name is a Pro perk.
Updating & rolling back
Change your site and redeploy through the connector — the URL never changes, SSL stays automatic, and every deploy is versioned. Roll back to any previous version in one click from the site’s Overview.
Custom domains
On a site’s Overview, add a custom domain. Point a CNAME at edge.landingconnect.com (DNS-only, no proxy) and SSL is issued automatically within a minute or two. Watch it progress with domain.status.
Analytics
The Analytics tab shows requests over time, top pages, referrers, countries, status mix, and bandwidth — privacy-friendly and aggregate, updated within ~15 seconds. No cross-site tracking.
Visibility, password & robots
On the Settings tab, choose Public (indexed), Unlisted (link-only, not indexed — the default), or Private (password required). Toggle search engines and AI crawlers independently. The platform generates your robots.txt from these.
Connector tools
account.signin/account.poll/account.whoami— pair and identify.site.create/site.list/site.deploy/site.status/site.logs/site.rollback.domain.add_custom/domain.status/domain.verify.seo.audit/seo.tips/troubleshoot.
FAQ
Does it work in plain Claude chat? Yes — for hand-written pages, Claude writes the files and deploys via the inline path. Cowork/Claude Code are needed when there’s a real build step or binary assets.
How many sites can I make? As many as you want — everything is unlocked during early access.
Troubleshooting
Run troubleshoot from the connector for a diagnostic battery (deploy present? files on disk? DNS resolves? cert issued?). A 404 right after deploy usually means there’s no index.html at the site root.