Verand
Pricing
Sign in Start for Free
Tracked AI models
ChatGPTGoogle AI OverviewsGoogle AI ModeGeminiPerplexityClaude
Integrations
WordPressGitHubSearch ConsoleAnalytics 4
MCP connector In betaAuthorise once. Then ask Verand about your own site, from wherever you already work.ClaudeChatGPTCursorVS CodeVerandOpen the connector →
Operator reviewed, not attorney verified. Every pack says which, and none of it is legal advice.How we review →
Insurance
Insurance agenciesState and provincial regulatorsLife insurance agentsSuitability and replacement rulesHealth insurance agentsMedicare and ACA marketing rulesCanadian life insuranceCLHIA G6, provincial regulators
Verand works for every industry
the list keeps going
Mortgage brokers

Rulebook if you have one. Truthfulness floor if you do not. Either way: no guaranteed outcomes, no implied endorsement, every claim substantiated.

See the 46 checks →
Rulebook loaded at onboarding
Financial advisor
SEC Marketing Rule 206(4)-1
CFP Board
Attorney
ABA Model Rules 7.1 to 7.3
state overlay
CPA
AICPA Code of Conduct
IRS Circular 230
Medical practice
HIPAA Privacy Rule
state boards
Syndicator
Reg D 506(c)
FINRA Rule 2210
Insurance brokerage
Suitability and replacement
CLHIA G6, FSRA, AMF
Pack active
Not on the list? The gate is about what you claim, not what you are licensed as.How the gate works →
Free tools
AI visibility checkerSoonSee which assistants already name your brand.Compliance auditSoonRun the gate over a page you have published.llms.txt generatorSoonWrite the file assistants read first.
Free tools are in build. The help centre is live now.Open the help centre →

The page is already published. The change lands in one spot.

Titles, answers, takeaways, citations and links are woven into a published page one occurrence at a time. You see the exact edit first, and a gate refuses rather than commit a page it can't verify.

Start for freeSee pricing

Settings

Manage your account, connections, and plan.

Integrations

Connect the tools Verand reads from: and, soon, publishes to.

Analytics & Search

Google Search Console
Query, impression & ranking data per page.
Checking…
Google Analytics (GA4)
Sessions & engagement per landing page.
Checking…

Publishing

WordPress
Publish drafts straight to WordPress.
Checking…
GitHub Static sites
willowdale/willowdale-site
Checking…
Webflow
Publish to Webflow CMS collections.
Coming soon

Developer

Webhooks
Get an HTTP callback when a run finishes or an article is ready.
Coming soon

Webhooks arrive with API access (Agency tier), after launch.

Before anything is written

You approve the edit
before it exists.

Every apply has a preview step, and the preview is the thing that gets written. A citation lands as a small superscript link straight after the claim sentence, once. Re-apply the same source to the same claim and nothing happens.

Find sources: Can You Do a 1031 Exchange From Residential to Commercial?

Verand can cite these for you. Apply to live adds a small superscript source link right after the claim on your live page. Prefer to do it yourself? Copy the URL and tick it off.

6 sourced · 1 to self-attribute · 7 claims

The replacement property must be identified within 45 days of the sale.
regulatory· needs a primary source
Primary sourceIRS✓ live
Like-Kind Exchanges, Real Estate Tax Tips | Internal Revenue Service
+2 more options

On your live page

A 1031 exchange runs two clocks at once. The replacement property must be identified within 45 days of the sale. The exchange itself has to close within 180 days, and the two windows overlap.

After you apply

A 1031 exchange runs two clocks at once. The replacement property must be identified within 45 days of the sale.IRS The exchange itself has to close within 180 days, and the two windows overlap.

On a git site

A page it can't verify
is never committed.

A static page is rebuilt from a recent article in your repo, then checked before anything is written: exactly one H1, the canonical pointing at this article, the head's scripts and stylesheets intact, the previous article's heading and hero gone, the site's own navigation byte-identical. Any one of those fails and you get an explanation instead of a pull request.

Publishing opens a PR on willowdale/willowdale-site. Merge it to go live. Your host rebuilds.

The generated page failed its safety checks, so nothing was committed:

  • • the previous article's heading (“Fannie Mae and Freddie Mac Guidelines: Updated…”) is still on the page
  • • this article's hero image didn't replace the previous article's in the page header

Other things it stops for

  • The donor page has fewer than two H2 headings, so the article body can't be located reliably.
  • Only part of the article body could be identified in the donor page, so publishing stopped.
  • The donor page has no canonical URL, so the new page's address couldn't be derived.
  • Couldn't locate the target text in the page's source file. It may have changed since the scan.
WordPress and page builders

Edits land inside
the editor that built the page.

On a block or classic post, Verand patches the post itself. On an Elementor page the visible text never lives in the post body, so a free companion plugin applies the change inside the builder's own model instead. A builder it doesn't handle yet says so rather than writing to the wrong place.

WordPress
millgardens.com

Connected as Jordan Reyes. Verand can create drafts for you to review and publish. Rank Math SEO detected.

Verand ConnectorActive
Applies fixes natively on Elementor + block pages.
Connected
Pending changes2
Answer block
What counts as a capital improvement on a rental?
A capital improvement adds value, extends the useful life of the property, or adapts it to a new use. It is depreciated over time rather than deducted in the year it is paid for, which is what separates it from a repair.
New meta description
Applied ✓
Repair or improvement? What the difference costs you at tax time, and how each one is treated on a rental property you hold long term.

Apply to live pushes each straight to your WordPress page, or Copy to paste it yourself.

Static sites on git

A new page opens a PR.
An approved edit is a commit.

Publishing a new article commits it on a branch and opens a pull request, so a person merges before anything is live. An edit you have already reviewed and approved goes straight to the production branch as its own commit, and your host rebuilds. A new page carries its images in the same commit, so a merged article never has a broken hero.

Publishing opens a PR on willowdale/willowdale-site. Merge it to go live. Your host rebuilds.
PR #5 open
Pushed Jul 26, 2:14 PM
Open PR on GitHub
The Difference Between Stagflation And Recession
/blog/difference-between-stagflation-and-recession/ · 82% related
Added ✓
Cap rates move with the cost of debt, so a stretch of rising interest rates changes what a stabilized asset is worth before a single lease turns over.

Anchor: rising interest rates → links to The Difference Between Stagflation And Recession

Added to your live page. Open change →

How it works

Four steps, and the last one is a refusal.

The same shape every time, whichever engine runs and whichever site it writes to.

Start for free
TitleCopy

Stagflation vs Recession - Willowdale Equity

Stagflation vs Recession: What Each Does to Rents
01

One scoped change

A title and meta, an answer block, key takeaways, a citation, an internal link or a year. Never the whole page.

a stretch of rising interest rates changes what a stabilized asset is worth

Anchor picked from the page's own words

02

Previewed in place

You see the sentence it will change, taken from the crawled page, before you approve it.

Applied ✓1 of 1 requested

Added to your live page. Open change →

03

Written once

The edit is placed at that occurrence only, and re-applying the same one is a no-op rather than a duplicate.

Couldn't locate the target text in the page's source file. It may have changed since the scan.

04

Or not written at all

If the page has moved on since the scan, or a derived page fails its checks, nothing is committed and you are told why.

Questions

What people ask before they connect a site.

What it can change, what it refuses, and the two places it can't write yet.

What can Verand change on a page that is already published?

A fixed set: the title and meta description, an SEO title where your SEO plugin exposes one, a snippet-shaped answer block, a Key Takeaways block, a source citation attached to one claim, an internal link, and a year rollover on the references you tick. Anything larger is a content refresh you do in the editor and publish as a whole page.

Does a model rewrite my page?

No. A model drafts the short new text (a title, a 40 to 50 word answer, three to five bullets) or picks a phrase already present in your page to use as a link anchor. The write itself is code: it locates that one claim, phrase or year in the current page and inserts at that offset. The apply step never sends your page to a model.

What happens if the page changed since the scan?

Nothing is written. The weave matches the claim, anchor or year against the page as it is right now, ignoring whitespace and markup, and refuses any match that would sit inside an existing link, a heading, the intro or a takeaways block. If it can't find a clean spot you are told the page may have changed, rather than getting an edit somewhere approximate.

Where can it not write yet?

Two places, and both say so in the product. Title and meta edits on a git-hosted site are not wired: they change tags in the head rather than weave content, so that button explains itself instead of failing. And live edits on a git repo work on pre-rendered HTML sites; a Markdown or SSG repo publishes new articles normally but can't take an in-place weave yet. On WordPress all six work.

Does anything apply on its own?

No. Every apply is a button a person clicks on a preview they can see. Scheduled routines find the work and draft the fix; none of them writes to your site. An article a compliance check has blocked can't be published to WordPress or committed to your repo either, because both publish paths check the same flag.

What does the pre-commit gate actually check?

It applies to static sites whose pages are baked HTML, where a new page is rebuilt from a recent article in your repo. Before the commit: exactly one H1, the canonical and og:url pointing at the new article rather than the one it was derived from, no scripts or stylesheets lost from the head, balanced structural tags, the surrounding layout still there, the previous article's heading and opening paragraph gone, this article's hero in the header, and the site's own navigation unchanged. Any failure returns the list instead of a pull request.

Apply-to-live edits

Approve it once. It lands once.

Connect WordPress or your repo and the fixes you have already reviewed stop being a list you copy by hand.

Start for freeSee pricing
Verand

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

support@verand.ai

Platform
All featuresAI Article GeneratorContent EditorBrand HubSite IntelligenceOpportunitiesKeyword TrackingSEO & AI AnalyticsRoutines
Compliance
Compliance gateValidation engineReport CardSEC Marketing RuleFINRA Rule 2210Reg D 506(b)/(c)HIPAA marketingState bar advertisingAICPA and Circular 230
AI Search
AI VisibilityShare of VoiceMentions and CitationsBrand SentimentPromptsCompetitor Monitoring
Solutions
Financial advisorsAttorneysCPAsMedical and dentalReal estate syndicatorsInsurance agenciesMultifamily and local
Verand works for every industry
the list keeps going
Mortgage brokers
Company
AboutBlogDocsPricingIntegrationsMCP connectorAuthor Bio ProEditorial standardsCompliance standardsAI instructionsContact
AI Trackers
ChatGPTGoogle AI OverviewsGoogle AI ModeGeminiPerplexityClaude
© 2026 Verand. All rights reserved. TermsPrivacyAI policyAccessibilitySecurity
Not legal advice. Compliance packs are AI researched and operator reviewed.