Set your AI key (required), and create reusable brand voices, CTA voices, CTAs and brand styles once. Everything is stored on this browser profile only — use Export to move it to a new build or another machine.
Niche starter templates
Pick a niche and click Add — it drops a pre-filled brand voice and brand style into the lists below that you can tweak and save.
Brand voices (for the post body)
How the brand writes. Used by the Assembler when it generates your intro, items and descriptions.
CTA voices
A separate, usually punchier voice used only for the call-to-action (urgency is OK here, while the article voice stays calm).
CTAs
Your offers in your own words. The AI rewrites them with stronger copy and a natural transition into the close.
Brand styles Visuals OTO
Design identity (colours, fonts, look) and an optional ChatGPT/Claude Project URL. Used by the visuals & branded export in the Visuals & White-Label upgrade.
White-label Visuals OTO
Rebrand the tool to your own name across the popup, optimizer and this page. Applies on the next time each page is opened.
WordPress sites Visuals OTO
Publish finished articles straight to WordPress. In WordPress go to Users → Profile → Application Passwords, create one, and paste it below (not your login password). Add as many sites as you like.
AI provider, model & key required
Listicle AI uses your own AI key to generate your list. Set your provider, model and key here once — stored only on this device and used only to call your chosen provider (OpenAI / Anthropic / Gemini).
My Take — your voice, experience & expertise
Add your own background, opinions, real results and client examples once. Every prompt this tool builds will weave them in as your first-hand experience and original commentary, so the content reads like you, not generic AI. This is what makes a piece pass the experience test (the first E in E-E-A-T). Use your own insights only, and never invent numbers.
Backup & restore
Loading a fresh unzipped build starts empty. Export your settings to a file, then Import it into any future build (or another machine) to get everything back in one click.
Stored in chrome.storage.local on this browser profile only — never committed to a repo or sent anywhere except the AI services you point it at.