Docs › Connections

Vercel

Connect Vercel so EOMA can publish redirects at the CDN and find the repository the rest of your site is built from.

#In 10 seconds

• Redirects EOMA prepares for you in Vercel itself. They wait in your Vercel dashboard until you press Publish — EOMA never presses it.
• Everything else — page text, titles and descriptions, structured data — cannot be changed from outside Vercel. That work goes to the repository your site is built from.
• Connecting Vercel is also how EOMA finds out which repository that is, so you never have to type its name.

#Before you start

• You must be the owner of the brand in EOMA. Others see "Owner only" instead of the Connect button.
• You need to be able to install an integration on the Vercel account or team that owns your project.

#Steps

#1 — Open Settings → Integrations

Settings is at the bottom of the left sidebar; Integrations is in the Workspace group. Vercel is in Publishing — CMS & Sites.

#2 — Install the EOMA integration

Press Connect, then Continue to Vercel. Vercel shows you what EOMA is asking for and where to install it. There is nothing to copy and no token to create.

EOMA asks to read your projects and their settings, and to work with deployments. It does not ask for your environment variables, your domains or your billing.

#3 — Pick the project that is your website

You come straight back to EOMA, and it lists the projects the installation can see. Each row shows how that project deploys:

Choose the one that serves your website and press Save project.

#4 — Connect GitHub

If your project deploys from a repository, EOMA now tells you which one and takes you to GitHub. When you install EOMA there and grant it access to that repository, the publishing target is filled in for you — no repository picker, no branch to choose.

If the repository is not in your own account, EOMA names the account it is in. Forward that to whoever built your site: they need to install EOMA on GitHub and give it access to that repository.

#What you'll see

"One more step — connect GitHub". The screen after you pick a project, when that project deploys from a repository. It names the repository and explains that changes will arrive there as pull requests you review and merge.

The repository already selected. After the GitHub install, the publishing target is set. If you look at the GitHub row you will see the repository and branch already filled in.

A named account when access is missing. If EOMA was not given access to the repository your Vercel project names, it says so and names the account that owns it, rather than showing you an empty list.

#Reading the numbers

The deploy badge is the whole decision, and it is the only one you have to read.

What EOMA can publish through Vercel, and what it cannot. Vercel sits in front of your site as a CDN, and it can be told to answer a request differently before your site ever sees it. That is enough for a redirect — an old address that should send visitors to a new one — so EOMA prepares those in Vercel directly.

It is not enough for anything that lives inside the page. A title, a description or a block of structured data is part of the HTML your site returns, and the CDN cannot reach into that. Vercel is where your site is hosted, not where it is written: when your project is connected to a Git repository, that repository is the real source, and Vercel deliberately does not let anything change it from the outside — ask its API for the files of a Git-based deployment and it declines. That is a good thing. It means nobody, including us, can quietly rewrite your site behind your developer's back.

So that work goes where your site is actually written. EOMA opens a pull request on your repository, you review it and merge it, and Vercel builds and publishes the result the way it always does.

Nothing goes live in Vercel until you press Publish. When EOMA prepares a redirect, it lands in your project's staging list under CDN → Routing Rules, exactly where a change you made yourself would land. Production traffic is untouched until you publish it. EOMA holds a credential that could publish it — we do not, by choice, because it is your site.

If you already have an unpublished routing change of your own waiting there, EOMA will stop and say so rather than adding to it. Publishing yours would otherwise publish ours in the same press, and the other way round.

The reason to connect Vercel at all is that the repository is often not yours to name. It frequently belongs to the agency, freelancer or developer who built the site, under an account you have never seen. Vercel knows which one it is. Connect it, and we read that from your project instead of asking you a question you cannot answer.

What EOMA can read. Your projects and their settings, and your deployments. Not your environment variables, not your domains, not your billing. You can remove the integration from your own Vercel dashboard at any time, and EOMA finds out immediately when you do.

#When it goes wrong

#Related

• GitHub — where a Vercel site's changes are actually published
• Actions — where you approve the work
• Integrations — every connection in one place