Connect WordPress or your
GitHub repo and Verand publishes the way your site already builds.
Vercel,
Netlify,
Cloudflare Pages and
GitHub Pages need nothing extra. Everything that is not built yet carries a chip on this page, because the alternative is you finding out later.
Each card carries the same three rows. What it does, what it needs from you, and what it will not do. The last row is the one worth reading.
The GitHub path integrates with your repository, not with your host. Verand opens a pull request for a new article, or commits an approved fix straight to your production branch, and whatever already builds that repo builds the new commit the way it always does. Verand never asks for a host account, never holds a host credential and never triggers a build, which is why there is no separate Vercel, Netlify or Cloudflare integration to wait for.
One exception worth saying out loud: this reaches content that lives in the repo. If your front end pulls its posts from a headless CMS instead, the GitHub path does not reach them, and that is a separate integration that is not built.
Justia Elevate, WebToMed, Apartment Investor Pro and a good number of the other platforms sold into law, medicine, accounting and real estate are WordPress underneath. They reach Verand through the WordPress integration, with the capability probe deciding what each site will accept before anything is written. The walled gardens that are not WordPress, FMG Suite and Scorpion among them, publish no API at all, and no integration can be built against nothing.
Second in line. The CMS API sandbox sits behind a paid tier, so that check comes before the build.
Third in line, on the published CMS API.
Fourth in line, for the mid market marketing teams already on the hub.
Fifth in line. It self hosts cleanly, and the buyers Verand serves are mostly elsewhere.
Takes the fifth slot instead of Ghost only if commerce adjacent demand shows up.
The sequence does not shorten for a plan, a routine or a schedule, and there is no setting that removes step two.
Research, brief, draft, hero image, 46 deterministic checks. One run, and it ends in your dashboard.
The Report Card and the compliance gate. Pass or Blocked, never a score, and the hard tier has no override.
A draft post in WordPress, or a pull request on your repo with content, frontmatter and images in one commit.
For a page that already exists, the change is woven back per occurrence rather than the page rewritten.
These are read only. They are how Verand knows which pages are worth touching, rather than guessing from the draft in front of it.
Queries, impressions, clicks and average position, joined onto every page in the Page Tracker. It is the market signal underneath the Opportunities worklist, the decay checks and the striking distance list.
Sessions, engagement and conversions per landing page, so a single row carries the whole funnel from the query someone typed through to what they did after they arrived.
The name, address and phone as your listing states them, checked against every page the crawl saw, plus the local checks that sit on top of that comparison.
| Page | Clicks | Impr. | Pos. | Sessions | Conv. |
|---|---|---|---|---|---|
| /blog/sec-marketing-rule-testimonials | 412 | 9,180 | 4.2 | 468 | 11 |
| /blog/reg-d-506b-vs-506c | 286 | 7,441 | 6.8 | 301 | 7 |
| /blog/depreciation-recapture | 193 | 11,027 | 11.4 | 204 | 3 |
| /services/fee-only-planning | 88 | 2,310 | 7.1 | 96 | 9 |
Draft an article or refresh a page from Claude, ChatGPT, Cursor, VS Code or anything else that speaks MCP.
Both come up in sales calls. Neither is coming, and a roadmap chip would be the dishonest way to answer.
There is no content API. No supported way exists to write a post, so Verand does not claim one and will not screen scrape your admin.
A data store rather than a publishing target, with very little adoption among the regulated businesses Verand serves. Not planned.
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.