← All optimization drafts

Daydream × Beautiful.ai · Page Template Spec · July 2026

Net-New Tool Page: the template for every "[x] maker / converter" page

Five sections, fixed order, fixed anatomy. Two pages already run on this contract (/pdf-to-ppt and /flowchart-maker), and every future tool-keyword page ships on the same skeleton. This sheet is the source of truth for the Figma build: what is locked on every page, and what flexes per keyword.

Derived from the live feature-landing family (modeled on beautiful.ai/integrations/powerpoint, re-verified 2026-07-17) and the two shipped net-new drafts. Each section below shows the layout, the copy formula, and both real instantiations.

1
Hero
Keyword claim + trial CTAs
2
Features
3 positioning cards
3
How-to
3 numbered steps
4
FAQ
5–10 Qs + JSON-LD
5
CTA banner
Imperative close

The canonical order is features before how-to. The two drafts differed here (pdf-to-ppt ran steps-first per its converter SERP). We standardize on the live sibling /integrations/powerpoint as re-verified in-browser 7/17 (hero → features → how-to → FAQ → banner). One order, one Figma file.

Fixed identical on every page Variable flexes per keyword / SERP Needs customer input media & unverified-claim convention
1

Hero

Job: claim the keyword in the H1, name the category's weakness, convert to trial. Two-column: copy left, product media right.
H1 · keyword first
Try for freeGet started
Hero product media
(swappable slot; see widget note below)

Fixed Anatomy

H1 = [primary keyword] + "for" + [benefit clause]
  • Intro: 3–4 sentences. Sentence 1 names the category's weakness, then the Beautiful.ai alternative in real product verbs. No invented behavior.
  • Buttons, verbatim: Try for free (primary) + Get started (secondary). No other labels.
  • Media right: real product visual of the flow (screenshot or short loop), briefed as Needs customer input until supplied.

Variable Per page

  • Keyword, benefit clause, and which weakness the intro names.

Both instantiations

/pdf-to-ppt: "PDF to PPT Converter for Fully Editable Presentations"
/flowchart-maker: "Flowchart Maker for Slides That Design Themselves"

2

Feature block

Job: carry the whole positioning in exactly three cards. Centered H2; cards alternate copy + media.
H2 · positioning statement
Media
Media
Media

Fixed Anatomy

  • H2 states the positioning; optional one-sentence lead-in below it.
  • Exactly 3 cards: H3 + ~60-word paragraph + media slot each.
  • The block carries 3–5 internal links across its three cards (/presentation-maker, /smart-slides, relevant /templates/… page); link where the copy makes it natural.
  • Product properties use the product's own naming, verbatim from support docs; every claim is register-verified.

Variable Per page

  • The three angles (chosen to carry that keyword's wedge) and which links each card gets.

Both instantiations

/pdf-to-ppt: "Why convert your PDF with AI instead of a file converter" · rebuild vs trace / editability / outline control
/flowchart-maker: "A flowchart maker built for presentations" · slide-native chart / on-brand design / AI + 300 layouts

3

How-to in three steps

Job: the numbered how-to every SERP rewards, in the product's real click-path. H2 carries a supporting keyword.
H2 · supporting keyword
Try for free
1
Screenshot
2
Screenshot
3
Screenshot

Fixed Anatomy

  • Exactly 3 steps, matching the family's own how-to on the live siblings. Always three.
  • Lead-in sentence + a mid-page "Try for free" CTA in the section header (standard slot; flowchart-maker shipped it, pdf-to-ppt adopts it).
  • Step card = number + H3 + paragraph + per-step screenshot Needs customer input until marketing-grade assets exist.
  • Every step is a documented product behavior; no invented click-paths.

Variable Per page

  • H2 phrasing (built from a supporting keyword) and the three steps themselves.

Both instantiations

/pdf-to-ppt: "Convert a PDF to PPT in three steps" · upload → shape the outline → export
/flowchart-maker: "How to make a flowchart in Beautiful.ai" · template → map steps → style & export

4

FAQ

Job: the page's depth layer. SERP consensus questions, honest answers, FAQPage schema. Single column, max-width ~820px.
H2 · Frequently asked questions
NEEDS CUSTOMER INPUT: unverified Q rendered as a flag, excluded from schema

Fixed Required questions, every page

  • How-to recap ("How do I [task] with Beautiful.ai?")
  • "Is it free?" answered with the honest 14-day trial framing.
  • Export / editability ("Can I use it in PowerPoint / edit the result?")
  • One honest concession question that names the job a competitor tool does better, then reframes to the presenting use case.

Fixed Rules

  • Link-dense answers (pricing, templates, comparison pages).
  • FAQPage JSON-LD mirrors only answerable questions; NEEDS-INPUT questions render as amber flag blocks and stay out of schema until answered.

Variable Per page

  • Count: 5–10 within the band. Education questions (what-is / symbols / types) only when the SERP demands them.

Both instantiations

/pdf-to-ppt: 7 Qs (2 flagged: OCR, upload security)
/flowchart-maker: 8 Qs + education layer (2 flagged: AI structure gen, Visio import)

5

Closing CTA banner

Job: the family's imperative close. Centered, short, single action.
H2 · imperative
Get started

Fixed Anatomy

H2 = "Turn your next [x] into a presentation"
  • One-line subhead ending "Try Beautiful.ai free for 14 days."
  • Single button: Get started. Nothing else in the section.

Both instantiations

/pdf-to-ppt: "Turn your next PDF into a presentation"
/flowchart-maker: "Turn your next process into a presentation."

What flexes per page

  • Body word count, matched to the keyword's competitive SERP band (pdf-to-ppt ~950 in an 800–1,200 band; flowchart-maker ~1,300 in 1,200–1,600).
  • FAQ count: 5–10; education questions are SERP-dependent.
  • Internal links: which sibling pages each feature card and answer points to.
  • All copy. Every customer claim must trace to a customer-owned source (site, support center, blog, pricing) in the page's claims register. Competitor pages inform structure only; zero facts cross over.
  • Keyword scope (fixed rule): a maker page targets tool intent only ("[x] maker / creator / generator", "free [x] maker"). Template-intent keywords ("[x] template") stay with the /templates/ spoke the page links down to. The maker page helps you make the [x]; the template page holds the ready-made template. Two intents, two pages, kept separate.

One structural gap to design for

Nearly every ranking competitor opens with an in-page tool entry: an upload widget (7/8 converter SERPs) or an open-the-editor button (6/6 flowchart SERPs). Beautiful.ai has no embedded tool on its marketing pages, so this template substitutes the trial CTA. Design the hero's media slot so a live tool entry point can swap in later without re-laying-out the section. It's the one product build that would close the gap, and it's flagged to the Beautiful.ai team as an open option.

Sources: net-new drafts #13 (/pdf-to-ppt, July 2026) and #14 (/flowchart-maker, July 2026) in the Beautiful.ai on-page optimizations workspace; template family evidence from beautiful.ai/integrations/powerpoint and /presentation-maker, re-verified live 2026-07-17. Full drafts, claims registers, and SERP appendices live on the optimization drafts site. Prepared by Daydream for the Beautiful.ai Figma template build.