Connect the repo your site already builds from. Verand reads it once, works out what kind of site it is, and writes files in the shape your site already expects. Your host deploys when you merge, the way it always has.
One token that sees one repo. Verand reads the file list and tells you what it found.
You see what passed and what needs a look before anything leaves Verand.
The article and its images in one commit, on a branch of its own.
An approved edit to a page you published years ago, without rebuilding it.
You create a fine-grained token on GitHub that can see one repository, and paste it in. Verand checks it can reach the repo, whether it can push, and then lists the files once to work out what kind of site you have.
Every article is checked before it can go anywhere. Are the numbers cited, is the disclaimer your industry needs actually in there, does anything read like a promise you are not allowed to make. You get the answer on one screen, in words.
Verand writes the files your site expects, on a branch of its own, and opens a pull request. The images ride in the same commit, because an article whose hero arrives separately is a broken page the moment you merge.
Say you want to add a source to one sentence, or move a date on to this year, on a page that has been live since 2023. You approve that one change in Verand and it commits the edited file to your main branch. Your host deploys it like any other commit.
No. Verand opens it and stops. Merging is the moment your site changes, and that stays a person pressing a button.
That is the normal case. The token is scoped to the one repo you point it at, and Verand only ever talks to GitHub, never to your host.
It says so. An unknown repo gets the plain article HTML and an honest label, rather than a guessed layout committed into your site.
No. Vercel, Netlify, Cloudflare Pages and GitHub Pages all deploy on merge exactly as they do today. The integration is with GitHub, not with them.
Nothing here needs a developer beyond making a token, and nothing here touches your host.
On GitHub: Settings, Developer settings, fine-grained tokens. Give it read and write on contents and pull requests, for the one repository.
Settings, then Integrations, then GitHub. The owner, the repository and the branch your site builds from.
Verand lists the repo once and tells you the site type and the files it saw. Green means the next article can open a pull request.
Seven days, every feature unlocked, one click to cancel.
Content built to rank in
Google and get cited by
ChatGPT
Perplexity
Gemini
Claude, with every claim checked before it goes live.