GitHubLive

Your articles arrive as a pull request.

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.

First

Connect

One token that sees one repo. Verand reads the file list and tells you what it found.

Every article

Check and approve

You see what passed and what needs a look before anything leaves Verand.

Then

A pull request

The article and its images in one commit, on a branch of its own.

Later

Change a live page

An approved edit to a page you published years ago, without rebuilding it.

1 Connect

One token, and it reads before it writes.

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.

The token is encrypted before it is stored, the same as the WordPress one.
It only ever talks to GitHub. Your host is not part of this: Vercel, Netlify, Cloudflare Pages and GitHub Pages need nothing at all.
If the token can see the repo but cannot push, you are told at the form rather than on your first article.
It never merges anything. That click stays yours.
Settings · Integrations · GitHubConnected
Repositorywillowdale/willowdale-site
Base branchmain
Token•••• •••• •••• ••••Saved safely
What it found
Repository reachable This token can push Astro, from astro.config.mjs 14 posts in src/content/blog
You are ready.One listing of the files. Nothing was written to work this out.
2 Check and approve

Nothing reaches your repo until you say so.

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.

Pass or Blocked on the compliance check, with the count beside it, so there is nothing to interpret.
Anything that needs attention links straight to the sentence it is about, with a suggested fix.
Then you choose: open the pull request now, or keep working on it.
No schedule, routine or robot can open it for you.
Before you publish · Depreciation recaptureReady
CompliancePass 12 of 12 checksPublishing unlocked
Search84
AI assistants79
Author and sources88
Send to willowdale-site Open a pull request
One button, one person.A blocked article cannot be sent to your repo at all.
3 A pull request

The article and its images land in one commit.

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.

On a site generator (Astro, Next, Hugo, Eleventy, Jekyll, Gatsby, Nuxt, Docusaurus and SvelteKit) it writes a content file, with the frontmatter copied from your own recent posts. Your layout wraps it at build, so a redesign re-wraps everything Verand ever published.
On a site of pre-built pages it takes the shell from one of your recent pages every time, so there is no template on our side to go stale.
Send the same article twice and the second time does nothing. Identical content makes no commit.
If it cannot tell what your repo is, it says unknown and hands you the plain article HTML rather than guessing at a layout.
Pull request · willowdale-siteOpen
Branchverand/publish-depreciation-recapture-2026-09-11
Filessrc/content/blog/depreciation-recapture.mdContent file
public/images/hero-depreciation-recapture.webpHero
Commits1article and images together
Frontmattertitle, description, pubDate, heroImage, authorSampled from your posts
Nothing is live yet.Merging is your click, and your host deploys from there the way it already does.
4 Change a live page

Fixing one line later does not mean rebuilding the page.

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.

The page is never regenerated, so the edits your team made over the years survive.
If it cannot find the exact spot it was approved for, it commits nothing and tells you which change and why.
Adding a source to one sentenceDone
blog/depreciation-recapture/index.html · paragraph 6
 the unrecaptured section 1250 gain is taxed at a
- maximum rate of 25 percent.
+ maximum rate of 25 percent.[1]
 For a partner in the top bracket that is the
ChangedOne sentence, the one you approved
Left alone1,842 of 1,843 lines
A small edit stays small.Run it twice and the second run politely does nothing.
Before you connect

The four things people ask first.

Will it ever merge its own pull request?

No. Verand opens it and stops. Merging is the moment your site changes, and that stays a person pressing a button.

What if my repository is private?

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.

What if you cannot tell what my site is?

It says so. An unknown repo gets the plain article HTML and an honest label, rather than a guessed layout committed into your site.

Do I need to change anything about my host?

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.

Setting it up

Three steps, all of them yours.

Nothing here needs a developer beyond making a token, and nothing here touches your host.

1

Create the token

On GitHub: Settings, Developer settings, fine-grained tokens. Give it read and write on contents and pull requests, for the one repository.

2

Paste it into Verand

Settings, then Integrations, then GitHub. The owner, the repository and the branch your site builds from.

3

Read what it found

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.

There is no step that skips your approval. A person approves the article, and a person merges the pull request.

Connect the site you have, then approve what ships.

Seven days, every feature unlocked, one click to cancel.

WordPress and static sites on GitHub today. Webflow, Wix, HubSpot CMS and Ghost are on the roadmap and marked as such.
Verand

Content built to rank in Google and get cited by ChatGPTPerplexityGeminiClaude, with every claim checked before it goes live.

support@verand.ai

© 2026 Verand. All rights reserved. TermsPrivacyAI policyAccessibilitySecurity
Not legal advice. Compliance packs are AI researched and operator reviewed.