Skip to main content
Open Biolinks in the dashboard and select the creation action. You need permission to create links in that workspace and an available Biolink allowance.

​
Create your page

  1. Switch to the workspace that should own the page.
  2. Select the action to create a Biolink and enter its name.
  3. Choose an available domain and alias. A custom domain must already be connected and usable in this workspace.
  4. Submit the creation dialog and open the editor.
  5. In Content, add a link or choose a content block. Complete its setup before publishing.
  6. In Header, add the title, bio and images visitors should see.
  7. In Design, choose readable colors, buttons and wallpaper.
  8. Review the preview and select Publish changes, or Publish from the mobile preview.
  9. Open the public URL in a signed-out browser and test the first action.
Success means the published page opens at the chosen address and its content performs the intended action. Creating the page does not finish configuring its blocks or connect an external provider automatically.

​
Choose the address carefully

Aliases must be available on the selected domain. Changing a domain or alias later changes the address you share; update social profiles, websites and printed materials accordingly. See Settings and Connect a custom domain. The dashboard name helps you identify the page. The public header title is configured separately under Header. Use a clear dashboard name when several campaigns share similar public titles.

​
Prepare before launch

If the page should remain unavailable while you work, use its page settings to disable public access. Hiding individual content blocks is a different operation: other published content can remain visible. Complete required fields, wait for image uploads or provider lookups and resolve validation errors. An incomplete PDF or invalid provider URL can prevent publication. Publication success is confirmed by Changes published; a populated preview alone is not confirmation. Follow Editing and publishing for saving behavior, Content blocks for setup options and Sharing and access for the final launch check.