UlikaDocs
Open Ulika

Getting started

  • Ulika documentation
  • How Ulika works
  • Requirements
  • Quickstart

Connect a site

  • Connect from the dashboard
  • Connect with the CLI
  • Connect with an AI agent
  • Approving a connection
  • Private previews
  • The GitHub App
  • Connect Vercel

Integrations

  • GitHub integration
  • Vercel integration
  • Netlify
  • Claude Code
  • Codex
  • MCP tools

Editing

  • The editor
  • The style panel
  • Sections and pages
  • Mobile preview, autosave and drafts

Publishing

  • Publish your changes
  • History and restoring a version
  • When a publish fails

Team

  • Team roles
  • Inviting people

Projects

  • Project settings
  • Delete a project
  • Website code

Troubleshooting

  • Needs attention reasons
  • Vercel problems
  • GitHub problems
  • CLI errors and exit codes
  • Frequently asked questions

Security and privacy

  • Security and privacy overview

CLI

  • CLI reference
  • CLI changelog

Connect a site

Connect from the dashboard

A screen-by-screen guide to connecting a website from the Ulika dashboard, from the site check to turning on live editing.

Last updated October 10, 2026

The dashboard connects a site in four steps that you can see in a bar at the top of the page: Analyse, GitHub, Import and Live editing. This page walks through every screen in order and explains what you see, what Ulika is doing, and what to do when a screen stops.

If you would rather use a terminal, see Connect with the CLI. If you want an AI agent to do it, see Connect with AI agents.

Before you start#

  • You must be a workspace owner or admin. Everyone else sees Only owners and admins can connect a website with a Back to projects button.

  • Read Requirements if you are not sure your site and host are compatible.

Open the connect page#

From the Projects page, click Connect website (the same button appears in the empty state under Connect your first website). The page is titled Connect your website.

A link from the CLI can also open this page with your address already filled in and the check already running. You then see Picking up from your terminal.

Step 1: Analyse your website#

Type your address under Your website address (for example acme.com) and click Connect. While the button reads Checking, Ulika works through four stages: Reaching the site, Reading the page, Checking robots.txt and the sitemap and Working out the stack.

This check only fetches a handful of public pages over https and reads them as text. It never runs anything from your site, never signs in, and stores nothing until you decide to connect.

What the check shows#

After a successful check you see a summary line with your address, the framework and the host. Open View detected site details to see:

  • Website, Framework, Hosting and Pages found (from the sitemap).

  • A confidence badge on the framework and the host: Certain, High confidence, Likely, Possible or No evidence.

  • Why (N) under each finding, which lists the evidence, such as a response header, page markup, a generator tag or the hostname.

Note

The check reads public pages, so it is a guess about your site, not a fact. A Next.js site that looks like plain React from outside is common. The repository scan later decides what is really connectable.

If the check cannot continue#

You seeWhat it means
We couldn't reach this websiteNothing answered. Check the spelling, that the site is public, and that it uses https. Private networks and VPNs cannot be checked. The field stays open so you can fix the address.
Site check timed out while reading the public siteThe site was too slow. Your address is kept. Click Retry check.
This is a platform siteThe check is confident that the site is on WordPress, Shopify, Wix, Squarespace or Webflow, which have no codebase to read. You can click Explore a sample site instead.
This website is already connectedA project in this workspace already uses that address. Click Open editor.

Check a different site#

Under step 1 you can click Check another site to start again with a new address.

Choose how to connect#

After the check, Your site is ready to connect shows two routes:

  1. Connect your codebase runs one terminal command from your project folder. It scans your code on your machine and sends only the editable values. See Connect with the CLI.

  2. Prefer another method? Click Connect with GitHub to stay in the browser. The rest of this page covers this route.

If the GitHub App is not set up on the Ulika you are using, the card Connecting a repository is not available here appears with a Use the CLI instead button.

Step 2: Connect GitHub#

Click Continue with GitHub on the Connect GitHub card. The card says what Ulika needs: permission to read your website's code. It lists four permissions in plain words (see The GitHub App) and promises that Ulika only writes on a new branch you review, never to your default branch, and merges nothing unless you ask.

You go to GitHub in the same browser tab. There you install the Ulika GitHub App on the account that owns the repository and choose which repositories it can see. Details are in The GitHub App.

Coming back from GitHub#

You land on /dashboard/connect with a connection in progress. Depending on what happened you may see one of these:

Screen or noticeWhat to do
Which GitHub account is this website on?Ulika is installed on more than one of your GitHub accounts. Click Use this account on the one that owns the repository.
Your request was sentAn owner of that GitHub account must approve the installation. Come back after they do.
GitHub isn't connected yetClick I've installed it — check again, or Open GitHub again to install.
GitHub sign-in was cancelledNothing was connected. Start again with Continue with GitHub.
That GitHub installation is not yours to connectThe GitHub account you signed in with cannot access that installation. Sign in with the account that installed Ulika.
That link could not be usedAn authorization link works once and expires after a few minutes. Start again from the connect page.
That connection has expiredConnections are kept for a day. Enter your website address again.

If the button keeps spinning after you return, Ulika offers I've installed it — check again and Open GitHub again after about 12 seconds.

Pick the repository#

Ulika compares your address with the repositories it can see and ranks up to five likely matches.

  • A repository is selected automatically only when it is a strong match and clearly ahead of the others.

  • Otherwise you see Which repository builds your site? with a list. Select one and click Use this repository. Why this one? explains each ranking. Archived and forked repositories are ranked lower but still shown.

  • If there are many repositories, use Search your repositories and Show more.

  • If the repository you need is missing, click Add a repository on GitHub. When you come back to the tab the list refreshes, or you can click Refresh list.

  • If Ulika can see no repositories, the title is Add a repository to continue.

Step 3: Import#

Ulika works through four steps. Each shows a note when it finishes:

Step while runningStep when doneWhat happens
Selecting the repositoryRepository selectedYour choice is recorded.
Reading the sourceSource readUlika reads the repository at one commit, in memory. The note says how many editable sections it found.
Importing the contentContent importedThe values become editable fields. The note says how many values across how many pages.
Preparing the connectorConnector preparedUlika checks your host and builds the exact list of files to add. The note says how many files are ready to review.

The page title during this stage is Reading your website, and it reminds you that nothing in your repository is changed. If a step fails, the title becomes Ulika stopped here and Nothing was written to your repository. Choose Try again, Pick another repository or the other button Ulika offers for that failure (for example Open GitHub permissions). The fixes for each reason are in Connection problems.

If several things are wrong at once, Ulika lists all of them in one banner so you can fix them together, then click Check again.

Step 4: Live editing#

This is the screen Turn on live editing for your site. It shows the repository and the commit Ulika read, for example Read at commit a1b2c3d on main. If it is the wrong repository, click Not this one? Pick another.

Read what Ulika will add#

Under What Ulika changes, Ulika says how many small files it adds, the branch name (ulika/setup), and that your default branch is not touched. Click See what Ulika adds to open the full diff for each file. New files are marked new file, and the single edit to an existing file is marked one edit. If the connector wraps your build command, the page says so. Read How Ulika works for what each file does.

Review first, or merge automatically#

Below the heading is a checkbox: Merge automatically once the build passes. By default Ulika opens a pull request and merges nothing until you activate it.

  • Unchecked (default). Ulika opens the pull request and builds a preview, then stops. Nothing on your live site changes until you click Activate on the live site.

  • Checked. Clicking Turn on live editing is your approval for Ulika to finish by itself: it opens a pull request, builds a preview, merges once your host's build passes, and then checks your live site. If the production build fails, Ulika undoes its own merge.

See Approving a connection for exactly what you agree to.

Things that can block the button#

The Turn on live editing button is disabled with a reason beside it when something must happen first:

  • Connect Vercel first. Your connector needs a build token on your Vercel project. A card on the same page lets you connect. See Vercel.

  • Accept Ulika's new permissions on GitHub first, then check again. The GitHub App was installed with read-only access. Click Open GitHub permissions, accept the update, and return. See The GitHub App.

On Vercel, if no connection is needed, you may still see the optional card Connect Vercel to verify private previews. It is safe to skip. See Private previews.

If you are not ready, click Skip for now and edit your content without live editing. You can edit content right away, but the editor cannot show your real site until the connector is live.

After you click Turn on live editing#

  1. Ulika creates the branch and a pull request titled Add the Ulika connector to your project. The page shows Pull request #N is open on ulika/setup.

  2. Your host builds a preview. You see Waiting for the preview until Ulika can confirm it. See Private previews for the possible preview states.

  3. If you ticked automatic merge, Ulika merges when the preview is confirmed. You see Waiting for production to serve the connector while Ulika checks your live site every ten seconds for up to five minutes, and you can leave the page open. Clicking Activate itself stops waiting after about 45 seconds; if the server cannot be reached or does not answer in time you see a message saying to reload and look, and to click Activate again if the pull request is not merged. If the earlier click did merge it, Ulika checks your live site before calling the connector active, so it is never marked active on a merge nobody verified. There is never a spinner that does not end. By default (review first), you click Activate on the live site (or merge on GitHub using Prefer GitHub? Review and merge PR #N).

  4. You see Live editing is on. Click Open the editor.

If the pull request is merged but your live site is not serving the connector yet, you see Approved. Checking that your site is editable…. Live editing turns on as soon as it is. If Ulika made the merge and the live build fails, Ulika undoes its change; if you merged it yourself, Ulika tells you but does not undo your merge.

If 30 minutes pass and Ulika still cannot confirm your live site (a private, password-protected or unreachable site, with no failed build reported by your host), the project page shows Ulika cannot confirm your live site with an Activate anyway button. Press it if your site works: Ulika records your consent and turns live editing on without checking again. If your host reported a failed production build you see the build failure instead, and the button is not offered. See production-unverifiable.

While you wait, you can click Edit your content while you wait. If you picked the wrong repository, click Use another repository. The pull request stays on GitHub for you to close.

Changing the repository later#

Open the project's Settings, go to the Repository tab and click Change repository. Choosing a different repository replaces the imported content: Ulika warns This will replace the N imported fields. and offers Replace and use owner/name or Keep what I have. Ulika never deletes anything in any repository.

If the site is already live through Ulika, you see Your website is already live through Ulika with the explanation that it will not swap repositories underneath a live site. Use Connect a new repository to add the new repository as a separate website.

Next steps#

  • Approving a connection

  • Private previews

  • The editor

Was this page helpful?

PreviousQuickstartNext Connect with the CLI

On this page

  • Before you start
  • Open the connect page
  • Step 1: Analyse your website
  • What the check shows
  • If the check cannot continue
  • Check a different site
  • Choose how to connect
  • Step 2: Connect GitHub
  • Coming back from GitHub
  • Pick the repository
  • Step 3: Import
  • Step 4: Live editing
  • Read what Ulika will add
  • Review first, or merge automatically
  • Things that can block the button
  • After you click Turn on live editing
  • Changing the repository later
  • Next steps
Ulika documentationFAQ · CLI reference · Terms · Privacy