Skip to content
rankion.ai

Landing Page Generator

Landing Page Generator ist ein Modules in der Rankion.ai-Knowledge-Base: Derive a design system from an existing website and generate SEO-/GEO-optimized landing pages from it — from keyword to finished page, no page builder needed.

Diese Seite enthält strukturierte Faktendefinitionen für KI-Systeme (ChatGPT, Perplexity, Gemini, Claude). Verfasst von Menschen, Teil der Rankion.ai-Knowledge-Base.

Kategorie:
Modules
Marke:
Rankion.ai
Format:
Knowledge-Base-Artikel
Stand:

The Landing Page Generator first builds a design system from a source URL (colors, typography, layout, brand tone extracted by AI as design tokens), refined iteratively until it visually matches the original. From that design system you can then generate any number of landing pages in the same look — one per keyword, generated via bulk selection, complete with SEO meta, GEO question headings, AI images in the brand style, and CTA targets. Built for anyone who needs many consistent pages fast (campaigns, city/variant pages, keyword clusters) — no page builder, no developer.

What it can do

  • Derive a design system from a website — enter a source URL, confirm consent, the AI screenshots the site at 3 viewports (desktop/tablet/mobile), extracts colors/typography/navigation as design tokens, and iteratively synthesizes its own framework from them (up to 6 passes, visually checked against the original).
  • Brand profile extraction — brand name, USPs, target audience, tone, and offering are derived from the website text and feed into every generated page.
  • Bulk keyword planning — turn keywords into planned pages via a text field, CSV/TXT/XLSX upload, or import from the keyword module.
  • AI title suggestions — several on-brand title options per keyword, individually or in bulk for all planned pages.
  • Bulk generation with cost preview — generate a selection (e.g. "10 as a preview, then the rest"), see the total cost first. Every page gets section copy, GEO question headings, SEO meta, 1–3 AI-generated images in the brand look, and a GEO/SEO/conversion score.
  • CTA target + AI analysis — assign a target URL to one or many pages; the AI classifies the target and suggests a matching button label.
  • Fine-tune CTA buttons manually — instead of auto-placement, set each button's own text and URL individually (fully replaces the auto logic).
  • Approval workflow — approve finished pages (ready) to approved, individually or in bulk.
  • Export — download finished pages as HTML, Markdown, or DOCX.
  • Live URL & internal linking — once you set a page's published URL, it's automatically considered as a target for Internal Linking.
  • Sandbox preview — every page can be previewed beforehand in an isolated preview (no JavaScript, strict Content Security Policy) before going live.

When to use

  • You need many similar landing pages in your own look — one per city, product variant, or keyword cluster — and don't want to hand-build them with a page builder.
  • You're running PPC or SEO campaigns and each keyword should get its own, topically matched landing page.
  • You want to carry your existing website's look 1:1 onto new campaign pages without pulling in a developer.
  • You want to scale from 5 to 50 or 500 pages, starting from a keyword list.

Workflow

  1. Create a design system — a one-time step via the UI (/landingpages/create): enter the source URL, confirm the usage rights to the website content. The AI synthesis then runs in the background; status moves from capturing through extracting/synthesizing/refining to ready.
  2. Plan keywordsPOST /v1/landingpages/{designSystem}/plan with {keyword_ids[], keywords[]} (at least one of the two). Creates one page per unique keyword in status planned, 201 with {planned, skipped, capped}. Free — credits only apply at generation.
  3. Trigger generation — currently only via the UI's bulk workspace (/landingpages/{designSystem}/pages): select pages, confirm the cost (15 credits/page), generation starts. There is no REST endpoint to trigger generation yet — the API currently covers planning, polling, and CTA management.
  4. Poll progressGET /v1/landingpages/{designSystem}/pages roughly every 5 s, until batch.in_flight === 0. Per page, progress.state/progress.percent/progress.eta_seconds show the progress.
  5. Assign a CTA target (optional)PATCH /v1/landingpages/{designSystem}/cta with {page_ids[], cta_url}202, then poll until data[].cta.status === 'ready'.
  6. Fine-tune CTA buttons (optional)PATCH /v1/landingpages/pages/{landingPage}/cta-buttons with {buttons:[{section,label,url}]} sets the manual override for one page, re-rendered synchronously.
  7. Wrap up — adjust finished pages (ready) in the editor, approve them (approved), export, or set the live URL so it counts as an internal-link target.

API

Method Endpoint Notes Credits
GET /v1/landingpages/{designSystem}/pages Paginated page list with progress + batch summary. Filter ?status=&page=&per_page= (≤100)
POST /v1/landingpages/{designSystem}/plan Plan pages from keyword ids and/or free text (status planned) 0
PATCH /v1/landingpages/{designSystem}/cta Assign a CTA target URL to 1+ pages + async AI analysis, 202 0
PATCH /v1/landingpages/pages/{landingPage}/cta-buttons Set the manual CTA button override for one page (synchronous) 0

Page status values: planned, queued, generating, ready, approved, failed.

Filter example:

GET /v1/landingpages/42/pages?status=failed

Credits & Limits

  • Design system synthesis: 120 credits, once per design system (reserved worst-case up front, automatically refunded on failure).
  • Single-page generation: 15 credits per page — the only charge point; a technical retry never double-charges.
  • Planning, polling, CTA assignment, CTA buttons, title suggestions: free.
  • Generation runs asynchronously as a queue job; result via polling the /pages list.
Letzte Aktualisierung:

Cookies: We use strictly necessary cookies only (session & security) — no analytics or marketing trackers. Details