Page AI gives you dramatically better output when you do the planning work before you open Vev. If you're coming from a document-based or long-form publishing workflow — reports, articles, playbooks, internal decks — this is the single biggest behavior change to make, and the one that unlocks everything else. Here's the approach.
The principle
Page AI isn't a magic translator. It's a designer that needs a brief. A wall of copy isn't a brief — it's raw material. Your job is to turn it into something a designer (or in this case, an AI playing designer) can actually build from.
If you give Page AI a 4,000-word document and say "build this," it has to guess at structure, hierarchy, and pacing. Give it the same content broken into clearly tagged sections with descriptions, and it builds what you envisioned the first time.
The workflow
1. Start outside Vev. Use a general-purpose tool such as Claude or Gemini as your planning partner — not Vev's built-in AI. External tools are strongest at the structural thinking phase. Vev's AI is strongest at building once the structure is decided.
2. Feed your full long-form copy to Claude or Gemini.
Ask it to:
Break the content into logical sections
Identify "stoppable moments" — quotes, stats, data points, and key insights that deserve visual treatment
Suggest where text-heavy passages should stay (for context) versus where information should be pulled out into interactive or visual elements
Flag candidates for charts, callout boxes, animated stats, or pull quotes
3. Get internal approval on the structure before building.
Show the breakdown to your team. "We're presenting this section as a scrollytelling moment with a pulled quote instead of three paragraphs — is that aligned with the intent?" This step prevents rework and gets everyone used to the new format.
4. Tag the structure clearly
In a Notion doc, Google Doc, or wherever you draft, label sections explicitly:
Label the sections, and tag the text elements inside them — H1, H2, Paragraph, Quote, and so on. The section names tell Page AI how to break up the page; the element tags tell it how to treat each line: what becomes a headline, what's a subhead, what's body copy, and what should stand alone as a pulled quote.
HERO SECTION
H1: [headline]
H2: [supporting line]
CTA: Learn more
CARD GRID 4 cards linking to the deep-dive sections below.
Card 1: [topic + 1-line description]
Card 2: ...
SECTION 1 — [topic name]
H2: [section heading]
Paragraph: [body copy, broken into paragraphs]
Include an Element AI graph showing [describe the data].
PULL QUOTE Quote: [quote text] — [attribution]
SECTION 2 — [topic name]
...
The tagging matters. Page AI reads the structure and the element roles, not just the words — and the clearer you are about each line, the closer the first draft lands to what you had in mind.
4. Tag the structure clearly.
5. Inline-tag your Element AI moments.
Where you want an interactive element, write it directly into the brief. You have two options depending on how much you want Page AI to do for you:
Option A — Scaffold the slot. Drop in a placeholder so Page AI leaves space for you to build the element afterwards:
"I will add an Element AI graph here showing [topic].""Scrollytelling moment: image of [subject] revealing as the user scrolls."
Use this when you want full creative control over the element and plan to build it yourself in a separate Element AI prompt.
Option B — Let Page AI generate the element for you. With a detailed enough description inline, Page AI will build the element itself as part of the page generation. The quality of what you get back is directly proportional to the quality of the description. Vague prompt → generic output. Specific prompt → something usable on the first try.
A weak inline prompt:
"Add a chart here."
A strong inline prompt:
"Add an interactive bar chart comparing sales across five regions (North, South, East, West, Central). Use the page's theme colors. On hover, show the exact figure. Include a brief caption explaining the data source."
The same principle applies to scrollytelling, calculators, animated stats, quizzes, and any other Element AI component. Describe what it does, what it looks like, what data it uses, and how the user interacts with it.
Rule of thumb: if you can describe the element to a designer in two sentences, you can prompt Page AI to build it inline.
6. Paste the tagged document into Page AI and select your theme. Review the plan it generates before hitting generate — you can edit section names, delete sections, and refine layout instructions at this stage by prompting. This is the cheapest moment to fix things.
7. Generate, then refine in the editor.
Page AI gives you a working draft. Use Vev's editor for fine-tuning rather than re-prompting from scratch.
Two prompts to keep in your toolkit
For section planning (paste into Claude or Gemini):
"Here is a [document type] for an audience that tends to skim rather than read long blocks of text. Break this into web-friendly sections. For each section, give me: a section name, a one-sentence description of what it covers, the body copy that belongs in it, any pulled quotes or stats worth highlighting, and a suggestion for an interactive or visual element (chart, scrollytelling moment, animated stat, callout) where it makes sense. Aim for a balance of text-heavy context and stoppable moments — every two to three sections should have something visual."
For briefing your content team:
"When writing the next piece, structure the copy with the web format in mind: short section headers, a clear lead, key stats or quotes that can stand alone as pulled elements, and natural breaks every few paragraphs where we can introduce a visual moment. Mark any data points that should become charts or interactive elements."
What "good" looks like
You'll know the workflow is working when:
Page AI's first output is recognizably what you envisioned, not a generic interpretation
You're spending more time on planning than on rebuilding inside Vev
Your content team starts delivering copy that's already in section-friendly format, before you even ask
Element AI moments are scaffolded into the page from the start, not bolted on at the end
The mindset shift
The biggest unlock isn't a feature — it's recognizing that planning is the work. The AI builds fast; the human decides what to build. Spend 30 minutes planning to save three hours building.