Menu
Docs / Product / Draft generation

Draft generation

Campaigns that write their first drafts — from what the audits actually found. Your team edits instead of stares.

Meta tags

Titles and descriptions that never exceed SERP truncation — checked against pixel width, not character count. Three variants per page: the existing one kept as a baseline, two drafted for the target keyword, with optional tone refinement.

agent
you new title and description for /pricing, keyword “seo platform”
SiteTR // generate_meta — 3 variants, pixel-safe
  1. “SEO platform with evidence on every finding — SiteTR” // 512px ✓

Schema

Schema.org templates with labeled placeholders for the types that matter — Organization, LocalBusiness, FAQPage, and friends. Deprecated types are rejected outright, so the structured-data check stays green after you ship.

FAQs

FAQ blocks drafted from the page’s content and the questions the research says people ask — ready for the page and for FAQPage markup.

llms.txt

llms.txt and the full llms-full variant for the audited site — the AI-crawler companion files that make the site legible to the engines that answer questions. Generated from the real page inventory, not a template.

Ship it

Drafts attach to recommendations and ship through the loop: as a patch, as a GitHub pull request, or routed through customer approval first — then the engine verifies the live page took the change.