How Verand works

Verand is a content operations system, not a writing tool. You connect your site once, and from then on a set of routines runs on its own schedule, crawling your pages, tracking your rankings, watching your competitors, and surfacing what to do next. You spend your time reviewing and approving, not generating.

This page covers what runs automatically, what you drive yourself, and what counts against your plan.

The division of labour

You drive three things:

• Creating content: researching a topic, generating an article, editing and approving it
• Refreshing content: updating an existing page that's slipped or gone stale
• Deciding what publishes: nothing goes live without you

Verand runs everything else on a schedule. You don't turn these on, and you don't pick when they run.

What runs automatically

The deep full-site crawl is the big one. It reads your sitemap, follows what it finds, and scores every page it can fetch, up to 2,000 pages per run. There's no sampling of the main checks: every page that's fetched gets the full analysis, not a representative subset. If your site is larger than 2,000 pages, the run tells you how many discovered links it didn't reach.

It covers technical SEO, schema and indexability, E-E-A-T scoring, and a compliance re-check where you have a pack assigned. These aren't separate routines to find and run. They happen inside the crawl.

Core Web Vitals is the one exception to "every page." Speed measurement is slow and rate-limited at the source, so each crawl measures a small representative sample: your home page, up to three of your main sections, and a couple of articles, six pages at most. That's enough to show whether your site is broadly fast or broadly slow, which is what the Site Health score needs.

For any specific page, run it yourself. The Page Tracker has a speed check on every page, on demand, as often as you like. There's no allowance on it. So the crawl gives you the sitewide picture, and the Page Tracker answers "what about this page", which is usually the question you actually have.

Page previews are also capped per run, with the remainder captured on the next audit.

The run's headline reports the number of pages scored, which is the figure Site Health, the Page Tracker and your Home card all agree on. If pages dropped out along the way (redirects, errors, unreachable URLs) it shows the discovered count too, so the gap is visible rather than quietly absorbed.

📸 Screenshot slot: scheduled-tasks-overview.png
The Scheduled Tasks tab showing the full routine list with cadence bands. Use a site with real run history so the "last result" lines aren't empty.

Why you can't change the schedule

The Scheduled Tasks tab is deliberately read-only. You can see every routine, its cadence, when it last ran and what it found, and you can trigger a Run now, but you can't switch a routine off or change how often it runs.

That's a design decision, not a missing feature. The routines feed each other: the crawl produces the page data that Opportunities, the Topical Map, Issues and Page Tracker all read from. Switching one off silently breaks the others in ways that wouldn't be obvious until you wondered why your worklist had gone stale. Verand owns the rhythm so the data stays coherent.

Nothing on that schedule publishes anything. Every routine either gathers data or drafts a proposal for you to approve.

Routines above your plan still appear in the list, shown as locked. That's so you can see what's there, not to nag you.

📸 Screenshot slot: scheduled-tasks-run-now.png
The Run now control and the run-history modal on a single routine row.

What counts against your plan

Three separate meters, and the distinction matters because people routinely assume there's only one.

A tracked keyword slot is one SERP check per day, not one phrase. If you track the same phrase on both mobile and desktop, or in two locations, that's two slots. It's counted this way because each one is a separate daily lookup.

A new article and a Full Rewrite draw from the same pool. A full rewrite does the same research and generation work as a new article and costs about the same to produce, so it's metered the same way.

A Content Refresh is the cheaper, separate line. It loads your existing article and edits it in place rather than regenerating it, so it draws from its own larger allowance, not your article pool.

The small in-editor actions are free. Rewriting a title, regenerating a meta description, tightening a single paragraph. These aren't metered at all.

Reading is never metered. Your scores, issues, opportunities, rankings and competitor data are all yours to look at as often as you like.

📸 Screenshot slot: plan-usage-rings.png
Settings → Plan & Usage, showing the usage rings mid-period so the meters read as partially consumed rather than empty.

Your first week

Your trial runs 7 days. A card is required up front, and you trial the plan you picked rather than a cut-down tier, so every feature you're testing is the real one. It converts automatically on day 8 unless you cancel, and you can cancel in one click.

A few volumes are capped for the seven days, because a month's worth of generation can be spent in an afternoon: five articles, five content refreshes, and 25 AI-visibility prompts on every plan. Everything else runs at your plan's own limits. Plans, limits and your trial has the full list.

On your Home tab there's a getting-started checklist that tracks the setup worth doing early:

• Approve your first article
• Connect your CMS
• Connect Search Console
• Connect GA4
• Set your image style
• Add an experience fact
• Track your keywords

Items tick themselves off when the system detects you've done them: a checked box means the thing actually happened, not that you told us it did. You can dismiss the checklist once you're done with it, and nothing you've completed is undone by hiding it. If you want it back, it's under Settings → Sites.

📸 Screenshot slot: getting-started-checklist.png
The Home checklist part-completed, so both the ticked and unticked states are visible.

Your knowledge base is never capped

Experience facts (your credentials, client outcomes, strong opinions, the things only you know) are ungated on every plan. Add as many as you want. They're your data, and they're what makes generated content sound like you wrote it rather than like everyone else's AI output.