Custom Pages
A Custom Page lets you upload a landing page you built yourself (the output of any website builder or AI tool) and have linkable.id host it on your own domain. You get complete design freedom, and your page still uses everything you already rely on: a short link and QR code, privacy controls, password / visitor‑pass access, search‑engine settings, versioning and analytics.
Use a Branded Page when you want to assemble a page from ready‑made widgets without touching code. Use a Custom Page when you already have a finished, fully custom design and just need somewhere to host it.
One rule makes this work: your build must be configured for the sub‑path we host it on (
/c/your-slug/), so its assets load correctly. See Preparing your Custom Page build before you upload: it includes a ready‑to‑use AI prompt.
The Custom Pages list
The list shows each page's internal name, its domain and slug, a status badge (Ready, Processing, Failed), its access mode, and the published size. The short Link column is copyable. Select a row to open it. Each row has a Preview icon for the live page and a More actions menu (⋯) with link share, the page's Branded URL and, last, Delete. The Trashed filter shows deleted pages (read‑only until restored). When you force-delete, you can keep the short link: give it a new destination and it becomes a regular Branded URL, with the same short address, QR code, stats and tags, so printed codes keep working. Bulk force delete asks once, with one destination for all.
Creating a Custom Page
After Internal Management (internal name, description, tags), fill in the Custom Page section:
- Domain: the domain your page is published under (required). Your workspace's admin domain, where the panel runs, isn't offered: Custom Pages are never shown there. If you have no other domain, add one in Domains first.
- Slug: the address of your page:
https://yourdomain.com/c/<slug>/. Leave blank to auto‑generate. It locks after your first successful upload, because your build is configured around it (changing it would break your assets). - Build base path: a read‑only reminder of the exact base path to build against (
/c/your-slug/). Copy it into your build tool before you build. - Access: Public (anyone with the link) or Private (only your workspace members). You can also gate any page behind a visitor pass (see below).
- Entry file: the document served at the base path. Defaults to
index.html; change it only if your build's entry document is named differently. - Single‑page app (SPA): turn on if your page uses client‑side routing (React Router, Vue Router, etc.) so deep links and refreshes work. Leave off for a normal multi‑page static site.
- Allow search engines to index this page: controls whether the page can appear in search results (public pages only).
- Upload build (.zip): the zipped output of your build. We validate and extract it in the background and notify you when it's live (or tell you exactly what to fix if it isn't).
- Branded URL (set on create, locked afterwards): your page's own short link: its Domain, Slug, and QR Code Design Template.
- Embeds & external domains (optional): the external services your page uses (analytics, booking or form widgets, iframe embeds). Leave it empty for a fully self‑contained page. See Embeds, analytics and external services below.
Uploading and versioning
Each upload becomes a new version. We validate it, extract it, and (once it's ready) make it live instantly, replacing the previous build with no downtime. We keep your most recent versions so you can roll back with one click from the Versions tab; older versions are pruned automatically.
If an upload fails validation (for example, a missing entry file or assets pointing at the wrong path), your current live version keeps serving and the rejected upload is discarded: you'll get a clear message explaining what to fix. The total size of your stored builds counts toward your plan's storage.
Versions tab
Lists every upload with its version number, status, file count, size and who uploaded it. The live version is marked active. You can Activate any previous ready version (an instant rollback) or delete a version you no longer need (you can't delete the active one).
Single‑page apps vs multi‑page sites
- SPA mode on: any address under your page that doesn't match a real file is served your entry document, so a client‑side router can handle it. This is what makes deep links and browser refresh work in React/Vue/Svelte apps.
- SPA mode off: only real files are served; an unknown address returns a normal "not found". Choose this for classic multi‑page static sites (
about.html,pricing.html, …).
Privacy and access
- Public: anyone with the link can view it. The default for marketing and landing pages.
- Private: only signed‑in members of your workspace can view it. Handy for staging a page before it goes public. When a member of your workspace opens a private page, the portal asks them to sign in if needed, then opens the page on its own address with a small Previewing as a member bar. That preview lasts 8 hours and ends as soon as they leave the workspace.
- Visitor pass: issue a tokenized share link (optionally with a password, an expiration date, and a usage limit) so someone outside your workspace can open a private page without an account. This is something most hosting platforms can't do.
Search-engine indexing
The Allow search engines to index this page toggle decides whether search engines may list your page. Private pages and pages opened through a visitor pass are always kept out of search results, regardless of the toggle, so gated content never leaks into search.
Your build owns its own <head>, so your page title, description and social‑share image come from your build, not from a linkable template.
Share links and invitations
On a private Custom Page, the Share links tab lets people outside your workspace in, as on Branded Pages and Sites: a share link anyone can open (with an optional password, usage limit and expiration), or a personal email invitation. See Share links and email invitations.
Stats
The Stats tab shows your page's visits over time, with country, device, browser and traffic‑source breakdowns and a human/bot toggle, and an Export to CSV action. Custom Page visits also appear in your workspace Analytics snapshot (scope it to Custom Pages) and count toward your monthly views, just like Branded Pages and Sites. (Analytics requires the analytics feature to be enabled on your plan.)
How your page runs (the security sandbox)
Because we host the code you upload, every Custom Page is served inside a browser security sandbox (a strict Content‑Security‑Policy with the sandbox directive). This guarantees that a page can never reach another customer's data (or your own private pages on the same domain) no matter what code it contains. It also means a few browser capabilities are intentionally switched off.
Works normally
- HTML, CSS and JavaScript (inline, or bundled in your build).
- External fonts, images, stylesheets and JavaScript libraries loaded over https (Google Fonts, a CDN library, etc.).
- Forms that submit to an external service (e.g. Formspree).
- Links: both in‑page navigation (on click) and links that open a new tab.
- File downloads.
Not available, by design
- Cookies,
localStorage,sessionStorage, IndexedDB: the page runs in an isolated origin and can't store data in the browser. Cookie‑consent banners that remember a choice, carts, "remember me", etc. won't persist. (Lifted when the page is served Isolated; see Serving.) eval()/new Function(): a few older libraries need this; use a modern build instead.- Calling APIs from the browser (
fetch/ XHR / WebSocket) to third parties, unless you declare the service under Embeds & external domains (see the next section). Undeclared client‑side analytics or runtime API calls won't work. (Static content and external form posts are fine.)
If your page genuinely needs any of the "not available" items and Isolated serving isn't available on your workspace yet, it isn't a fit for Custom Pages today: use a Branded Page, or host that app elsewhere and link to it. See Preparing your Custom Page build for how to build within these rules (the AI prompt there already accounts for them).
Serving: Isolated or Classic
Where Isolated serving is available on your workspace, the page's form has a Serving option.
- Isolated (recommended). The page runs on its own secure address, separate from your domain and from every other page. Nothing it does can reach your other pages, so it needs no sandbox: iframe embeds (YouTube, calendars, forms, reCAPTCHA, embedded checkouts), browser storage and ES modules work as on any website, and its files are served from a global network close to each visitor. Your link stays the same: visitors open
https://your-domain/c/your-slug/, and the page appears there in a full-window frame, with your page's name as the tab title. Available for public pages; private pages use Classic for now. - Classic. The page runs on your domain inside the security sandbox described above.
How to choose. Pick Isolated for landing pages, prototypes, reports and anything with embeds or widgets. Pick Classic when the page must be found through search engines, or when an analytics tool inside the page has to report your domain. What to know about Isolated:
- Search engines don't index it, since the content sits in a frame on another address.
- An analytics tool inside the page (Google Analytics, a pixel) records the page's secure address (
….pages.linkableusercontent.com) rather than your domain. linkable.id's own stats are unaffected. - The page's own cookies may not stick: Safari and Brave block cookies inside a frame from another site. Browser storage (
localStorage) works, so a banner or setting that remembers a choice should use it. Embedded widgets are unaffected. - Navigating inside the page doesn't change the address bar. Links that open the page at a sub-path still work.
- Link folders with a trailing slash (
/c/your-slug/guide/). A folder link without the slash isn't found on an Isolated page, while Classic redirects it. Most site builders, VitePress included, already link that way.
Uploading a new build. Visitors keep seeing the current build until the new one is fully processed. On an Isolated page they keep seeing it for up to a minute more, until the new build is ready on the global network, and then it switches over.
Embeds, analytics and external services
Real landing pages usually need a few outside services: analytics, a booking widget, a form service that submits via JavaScript, an embedded video. These are opt‑in on a Custom Page: open Embeds & external domains on the page's form and declare what your page uses.
- Known providers: pick services like Google Analytics, Meta Pixel, Calendly, Tally, HubSpot, Mailchimp, Formspree, YouTube, Vimeo or Google Maps from the list. We maintain the exact domains each provider needs, and keep them up to date for you.
- Custom domains: add any other hostname your page talks to (your own API included), e.g.
api.yourservice.com. A leading*.covers subdomains.
Your account decides which providers appear in the list and whether pages may add custom domains, in Embeds and scripts. A provider switched off there, or custom domains switched off, stop working on every page at once; what each page declared is kept.
How it behaves:
- Declaring anything switches the page to governed mode. From then on the page may only call APIs, embed iframes and submit forms to itself plus the declared list, so put everything external your page touches on the list: the analytics endpoint, the form service, every iframe embed. A page that declares nothing keeps the strict defaults above.
- Changes apply immediately, without re‑uploading your build. Edit the list and save: the page's next load uses it. Visitors who already have a cached copy of a public page may take up to 5 minutes to pick up the change.
- Declaring domains covers your page's own scripts: analytics beacons, JavaScript form submissions, calls to your own API. Iframe embeds and cookie-based widgets (YouTube, Google Calendar, Tally, reCAPTCHA, embedded checkouts) don't work in Classic serving, whichever domains you declare: browsers extend the page's sandbox into every iframe, so those widgets can't reach the cookies and storage they rely on. Serve the page Isolated for them.
A widget loads but silently does nothing? If it's a script widget, declare its service. If it's an iframe embed (YouTube, a calendar, a form), serve the page Isolated. More troubleshooting in the build guide.
Limitations and restrictions
Custom Pages are static hosting, so a few rules apply:
- No server‑side code runs. Your build is served as static files. PHP/Node/other server code is rejected on upload.
- In Classic serving the page runs in a browser sandbox: no cookies/
localStorage, noeval, and client‑side API calls only to services you declare under Embeds & external domains (see How your page runs). - Forms need an external destination. A contact or lead form must submit to your own API or a third‑party service (e.g. Formspree). linkable.id doesn't receive form submissions for you.
- You own the whole page head. Meta tags, favicon and social‑share image come from your build, not a linkable template.
- Static file types only. Web assets such as HTML, CSS, JS, JSON, images, fonts and common media are allowed; anything else (including executables) is rejected.
- Size and file‑count limits apply to each upload: keep builds lean (large unoptimized media is the usual culprit).
- The slug locks after the first upload, because your build's base path depends on it.
- Built against the base path. Your assets must resolve under
/c/your-slug/: this is the single most common cause of a page that loads blank. See Preparing your Custom Page build. - Your link is always on your existing domain at a sub‑path (
/c/your-slug/), in both serving modes.
Limits
| Limit | Value |
|---|---|
| Upload (zip) | 50 MB |
| Unpacked build | 200 MB |
| One file in the build | 100 MB |
| Files in the build | 2,000 |
| Versions kept for rollback | 5 (the oldest is removed when a sixth is activated) |
| Embed and external domains per page | 20 |
Builds also count toward your plan's storage.
With Claude
With the Claude connector, Claude can create a Custom Page, upload a build (in the chat, or through an upload link for a large zip), switch the active version, and change its access. New pages start private.
- Connection permissions: View custom pages and their builds; Create and edit custom pages to upload to private pages; Make custom pages public to publish or upload to a public page. Your role's permissions still apply.
- Goes live: a new active version of a public page replaces it for visitors at once.
- Stays in the panel: deleting pages and versions, visitor passes and share links, and stats.
Try asking:
- "Create a private Custom Page at /c/launch on our main domain and upload this build."
- "Roll the pricing Custom Page back to the previous version."