← All optimization drafts

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

Existing Template Pages: the optimization spec for every "[x] template" page

One CMS template drives all 236 template pages, so this sheet is written the way that system works: section by section, what is locked on every page, and what fills in per page. It optimizes the existing pages (no net-new landing pages), and every video stays intact. Two pages are already instantiated on this contract (/templates/pie-chart and /templates/swot-analysis), and Batch 1 applies it to 10 chart pages carrying 82,330 monthly searches on their "[x] template" head terms.

Derived from live scrapes of the template family (re-verified 2026-07-24/25), Search Console evidence across all ten Batch 1 pages, and the winning-SERP pattern (Canva, Adobe Express, Venngage). Each section shows the layout, the fill rule, and both real instantiations. Before/after annotated mockups: pie chart · SWOT analysis.

0
Metadata
Title + description formulas
1
Hero
H1 head term + video kept
2
Style gallery
Static previews join the video
3
How-to
4 numbered steps
4
Overview
Kept copy, question H2
5
Pro tips + AI
Kept, untabbed
6
Related
Crawlable video cards
7
FAQ + links
5 Qs + programmatic links

The page leads with the template layer. Hero, style gallery, and how-to come first, because that is what the "[x] template" searcher came for. The educational overview, pro tips, and FAQ follow as the depth layer. Every section that exists on the live pages is kept; the spec re-orders, retitles, and adds around them.

Fixed identical on every page (structure & product facts) Variable fills per page, with a named source CMS constraint propagation & video requirements
0

Metadata

Optimized Job: make the snippet say what the page is (a presentation template) and fix the doubled title suffix every page currently carries.
Browser snippet
SITE-WIDE FIX: every live title ends "| Beautiful.ai | Beautiful.ai". One Webflow template edit corrects all 236 pages at once, ahead of Batch 1

Fixed Formulas

Title (chart/slide) = [Name] Template for Presentations | Beautiful.ai
Title (presentation) = [Name] Presentation Template | Beautiful.ai
Meta = Start from a designer-made [x] template, add your data by hand or let AI fill it in, then take the finished slide to PowerPoint or Google Slides.
  • "For Presentations" states the use case that separates Beautiful.ai from printable/vector template sites on the same SERP, and matches long-tail queries the pages already earn impressions for.
  • The description leads with the template, then the two things template searchers check before clicking: own data in, PowerPoint / Google Slides out. The live boilerplate is identical on every page.

Variable Per page

  • The [Name] and [x] nouns, pluralized and cased by the grammar gate ("SWOT analysis," "Venn diagram").

Both instantiations

/templates/pie-chart: "Pie Chart Template for Presentations | Beautiful.ai" (52 chars)
/templates/swot-analysis: "SWOT Analysis Template for Presentations | Beautiful.ai"

1

Hero

Optimized Job: say the word the searcher typed. The live H1 is just "Pie Chart"; adding "Template" makes it the exact head term. The video hero stays: it demos the template's built-in Smart Slide animations, which is the differentiator.
Templates › [Category] › [Name]
H1 · exact head term
Use this templateFill it in with AI
▶ Video hero (KEPT)
(template animation; VideoObject schema + thumbnail added)

Fixed Anatomy

H1 = [Name] Template
Subhead = A designer-made [x] template that's fully editable. Add your [data/content] by hand or let AI fill it in…
  • Primary CTA: Use this template (the existing copydeck link, kept). It matches the intent the page targets.
  • Secondary CTA: Fill it in with AI → /presentation-maker. AI fill is the wedge no printable/vector template site offers, so it gets the subhead and second button while the headline stays on the head term.
  • CMS constraint The hero video is kept on every page because it shows the template's built-in animations (also used in the slider carousel). The Beautiful.ai team adds video indexing in code; this spec mirrors it with VideoObject schema and a descriptive thumbnail per page (see Schema package below).
  • Honesty rule: no hero claims the template is free. Beautiful.ai is trial-based; the copy competes on design quality and AI fill.

Variable Per page

  • The subhead's nouns describe what this template actually holds: slices and values for a pie chart, four quadrants for a SWOT analysis.

Both instantiations

/templates/pie-chart: "Pie Chart Template" · "…add your data by hand or let AI fill it in, and Smart Slides keep the design aligned as you edit."
/templates/swot-analysis: "SWOT Analysis Template" · "…Smart Slides keep the four quadrants aligned as you edit." (removes the live "free" claim)

2

Template style gallery

New Job: give template searchers a gallery to evaluate, the one thing every winning SERP result has. Static previews join the video; nothing replaces it.
[Name] template styles
Theme 1
Theme 2
Theme 3
▶ Walkthrough video (kept)

Fixed Anatomy

  • A band of static previews of this page's own template in multiple slide themes where variants exist, each opening the editor.
  • The existing walkthrough video keeps its tile; the gallery adds crawlable image content alongside it. Videos keep their placement and stay visible on page load.
  • Every SERP winner (Canva, Adobe Express, Venngage) opens onto a gallery of editable variants; the live pages show a single template. This closes that gap without touching the video layer.

Variable Per page

  • Which theme variants exist, and the preview assets themselves (the page's own template renders rather than stock imagery).

Both instantiations

/templates/pie-chart: pie chart template in three slide themes + the existing walkthrough video
/templates/swot-analysis: SWOT matrix in three slide themes + the existing walkthrough video

3

How-to in four steps

New Job: the numbered how-to every template SERP rewards, in the product's real click-path. Marked up with HowTo schema.
H2 · How to use the [x] template
1
2
3
4

Fixed Four steps, every page

  • 1. Open the template. "Use this template" opens it in the Beautiful.ai editor.
  • 2. Add your [data/content]. Type it in, upload a document or data file, or describe it and let AI fill the template.
  • 3. Make it yours. Adjust colors and labels; Smart Slides keep the layout aligned as you edit.
  • 4. Present or export. Live link, present in Beautiful.ai, or export to PowerPoint, Google Slides, or PDF.
  • Every step is a documented product behavior; no invented click-paths.

Variable Per page

  • Step 2's nouns: what "your data" means on this template, in its own vocabulary.

Both instantiations

/templates/pie-chart: "Add your data": values, labels, and legend
/templates/swot-analysis: "Add your analysis": strengths, weaknesses, opportunities, and threats into the four quadrants

4

Educational overview

Optimized Job: keep the real educational copy the pages already have, retitle it as the question searchers ask, and move it below the template layer.
H2 · question form

Fixed Anatomy

H2 = What is a [x], and when should you use one?
  • The existing overview copy is kept in full; it is real, useful content. Only the "Overview" heading changes, and the block moves below the template layer.
  • One sentence appended naming the page's supporting terms where natural (skipped when the kept copy already names the head term).

Variable Per page

  • The kept copy itself, and whether the supporting-term sentence is appended.

Both instantiations

/templates/pie-chart: appends "…an editable pie chart template for presentations: the design is done, so you only add your data."
/templates/swot-analysis: no appended sentence (kept copy already natural); quadrant sub-heads normalized by the grammar gate

5

Pro tips + AI capabilities

Kept Job: preserve the genuinely differentiated content most chart-widget competitors lack, and make it crawlable by un-tabbing it.
Stacked sections (was: tab component)

Fixed Rules

  • "Pro Tips" and "Discover AI capabilities" content kept in full, laid out as stacked sections instead of the current tab component, since tabbed content that requires a click is easy for crawlers to miss.
  • Kept headings pass through the grammar gate ("Discover AI capabilities for pie chart" → "…for pie charts").

Variable Per page

  • Which blocks exist: not every live page has the AI-capabilities tab. Where it's absent, the batch fill adds the pane with the page's own nouns so the library stays uniform, and the how-to and FAQ still carry the AI fill copy.

Both instantiations

/templates/pie-chart: both blocks kept, untabbed; one grammar fix
/templates/swot-analysis: pro tips kept; the live page has no AI tab, so the fill adds the pane with SWOT nouns

6

Related templates band

Optimized Job: keep the sibling-template video previews, and give Google what the carousel currently hides: descriptive anchor text and an indexable thumbnail per card.
H2 · [Name] templates and related slides
▶ Sibling video (kept)
▶ Sibling video (kept)
▶ Sibling video (kept)

Fixed Rules

  • Sibling template videos stay; the animations are the product showcase. Each card gains a poster thumbnail (descriptive filename + alt text) and a descriptive text link ("Bar graph template"), replacing the bare "View template" labels that carry no keyword signal.
  • Videos load lazily against the poster frame, which addresses page weight without removing a single embed.
  • Self-referencing cards are dropped (the live SWOT carousel links back to its own page).

Variable Per page

  • Which siblings appear: same-category templates per the internal-link rule below.

Both instantiations

/templates/pie-chart: donut chart, bar graph, line chart, area chart, waterfall chart, data dashboard
/templates/swot-analysis: Venn diagram, XY plot, and comparison-category siblings (self-link dropped)

7

FAQ + programmatic links

New Job: answer the long-tail questions Search Console already records ("editable pie chart template"), power FAQPage schema, and make the 236-page library crawl like a connected system.
H2 · [x] template FAQ
H2 · More [category] templates

Fixed Five questions, every page

  • Is the [x] template editable? · How do I add my own [data/content]? · Can AI fill it in for me? · Can I export to PowerPoint or Google Slides? · When should I use a [x]?
  • Answers are 2–3 sentences of product facts only; the "when should you use" answer derives from the page's kept overview copy, so it is unique by construction.
  • Pricing questions answer honestly with the 14-day trial framing; no answer calls the template or the product free.
  • Below the FAQ, a rule-generated "More [category] templates" text module: every same-category sibling with its "[x] template" head term as anchor text, plus the category hub and one product page. Visible breadcrumbs on every page.

Variable Per page

  • The nouns in every question and answer, and the sibling-link set (category-driven).

Both instantiations

/templates/pie-chart: 5 Qs · links to 10 data & chart siblings + hub
/templates/swot-analysis: 5 Qs · comparison-category siblings + hub

Schema package (generated per page from the same slots)

  • Keep: Organization (site-wide).
  • Add: BreadcrumbList · HowTo (mirrors the four steps) · FAQPage (mirrors the five answers verbatim) · VideoObject for the kept hero and walkthrough videos, with name, description, thumbnail, and upload date per video, mirroring the video-indexing work the Beautiful.ai team is adding in code.
  • Revise: the existing WebPage/CreativeWork block's url host (beautiful.ai vs the www canonical); one Webflow template edit, shipped with the title-suffix fix.

Two CMS realities this spec is built around

  • Sections propagate. These pages are CMS templates: a section added to one page appears on all of them. So no section ships until its content exists for every affected page. The weekly batches fill content page by page, but structural changes wait for full coverage (or for a parallel-template setup, which the Beautiful.ai dev team is checking on).
  • Videos stay intact on every page. The hero and carousel videos demo the templates' built-in animations and are kept everywhere. The optimization layer adds around them: poster thumbnails with metadata, VideoObject schema, descriptive anchors, lazy loading.

Rules that hold on every batch

  • Grammar gate: every filled slot reads as natural English; grammar wins over exact-match phrasing, including on kept headings.
  • Unique-content floor: the 10 fills in a batch are diffed against each other; any sentence repeated across pages must be a fixed product fact.
  • Intent gate: supporting terms need ≥30% SERP overlap with the "[x] template" head term. "Maker" and "generator" terms are excluded whatever their volume, because their SERPs are won by in-page tools.
  • Honesty rule: competitors lead with "free"; Beautiful.ai is trial-based and the copy never claims free.

Weekly batch cycle

  • Monday: scrape each live page, fill the spec for the week's 10 pages, run the grammar gate and unique-content diff, publish to the review hub.
  • By Wednesday: Beautiful.ai reviews; rejections carry a reason and are revised in-cycle.
  • Thursday/Friday: approved copy into Webflow (direct entry with editor access, or a paste-ready sheet per page).
  • Batch 1 (10 chart pages, 82,330 searches/mo): pie chart, flow chart, timeline, word cloud, Venn diagram, bar graph, infographic, Gantt chart, SWOT analysis, org chart. Batches 2–12 re-ranked by head-term volume. Position + click checks at 4 and 8 weeks against the captured Search Console baseline.

Sources: live scrapes of /templates/pie-chart and /templates/swot-analysis (2026-07-24/25), Search Console evidence across all ten Batch 1 pages (Apr 26 – Jul 24), and the winning-SERP pattern documented in the research appendix. The full working bundle holds the complete filled drafts for both instantiations, the module-by-module review version, and the nine-slide analysis behind each decision. Annotated before/after mockups: pie chart · SWOT analysis. Prepared by Daydream for the Beautiful.ai web team.