Listicle AI builds long, stand-out "list" posts the smart way: topic check, title, intro, categories, items, descriptions, conclusion, score, and export. Here's how to get going.

1. First-time setup (your AI key)

Listicle AI uses your own AI key (OpenAI, Anthropic, or Google Gemini). There's no subscription to us, and a whole post usually costs a few cents at your provider.

1. Click the extension icon to open the side panel and activate your licence key.
2. Open Settings (gear / "Settings" button).
3. Under AI provider, model & key, pick your provider + model and paste your API key. It's stored only on this device.

2. Build a list post

Open the assembler ("Open List Assembler") and work top to bottom:

1. Topic check — enter your topic, item type, and how many items. Run the 3-point check; use a suggested sharper angle if it flags one.
2. Title — generate options or type your own (it's an editable field).
3. Intro — generates a promise + item count + what-to-expect + call to action.
4. Categories — suggest or add sections (these become your sub-headings and jump links).
5. Items — generate toward your target; duplicates are removed automatically and the counter tracks live.
6. Descriptions — one short, useful line per item, in a single pass.
7. Conclusion — asks readers what you missed (and includes your CTA if you pick one).
8. Assemble & export — build the preview, then copy/download.

3. The content score

The right-hand panel shows four live scores:

• Overall — a blend of the three below (0.5 Optimization + 0.25 Naturalness + 0.25 Readability).
• Optimization — structural completeness (title, intro, items vs target, descriptions, categories, conclusion, jump links, odd count).
• Readability — Flesch reading ease. Aim ~50–60 for SEO content (green at 50+).
• Naturalness — flags repetition and marketing clichés ("powerful / seamless / comprehensive") so it reads human, not AI.

4. Export & save campaigns

• Copy Markdown / Copy HTML / Download HTML / Download Word — paste into any editor or CMS.
• Save campaign / Load campaign — store the whole post as a file and reload it later to refresh the list (great for "best X of [year]" posts you update).

5. Publish to WordPress (STUDIO upgrade)

1. In WordPress: Users → Profile → Application Passwords, create one, copy it.
2. In Listicle AI Settings → WordPress sites: add your site URL, username (your WordPress login name), and the application password.
3. In the assembler's publish step, pick the site, click Test connection, then Publish (draft is recommended first).
4. Refreshing later? Tick "Update the post I published before" to update the same URL instead of creating a new one.

6. WordPress won't connect? Common fixes

If Test connection fails, work down this list. The error message tells you which case you're in.

"Authenticated, but this user can't create posts" (403)

Your login works, but the account isn't allowed to publish. Use the application password of an Administrator, Editor, or Author account.

"Not authenticated" / "not logged in" (401)

WordPress isn't seeing your login. Two causes:

• Wrong username. Use your exact WordPress login username (Users list → Username column), not your display name or email.
• Your server strips the Authorization header. Very common. Fix depends on your host:
  • Apache / LiteSpeed: add to the top of your site's .htaccess:

    CGIPassAuth On

    or, if that's not allowed:

    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
    </IfModule>

  • nginx (no .htaccess): add to the PHP location block (or ask your host):

    fastcgi_param HTTP_AUTHORIZATION $http_authorization;

  • Can't edit server config? Upload the included wp-auth-header-fix.php to wp-content/mu-plugins/ (create that folder if needed). It auto-activates.

Test fails but publishing works

Some security plugins (e.g. user-enumeration / author-slug protection) block the /users/ endpoint. Listicle AI tests against the posts endpoint to avoid this, but if your test still errors oddly, just try Publish — it uses a different route.

Security plugins to check

• Make sure Application Passwords aren't disabled (e.g. Really Simple Security → Hardening → Advanced; "Admin and Site Enhancements" → Security / Disable Components).
• If a firewall (Wordfence etc.) is blocking the REST API, allow the /wp-json/wp/v2/posts route.

Confirm it's the server, not the extension

Run this in a terminal (replace the username + password):

curl -i -u "USERNAME:APP PASSWORD" "https://YOURSITE.com/wp-json/wp/v2/posts?context=edit"

Returns post data = it's working. Returns 401 = it's your server/credentials (apply the fixes above). Either way, the meantime workaround is to Download Word/HTML and paste in.

7. Upgrades

Add an upgrade key any time in the side panel under Add upgrade key.