haplo.

the one-click platform for keyword research, competitor analysis & content generation

Choose the platform where the content will be published.
Automated uses keyword intent and SERP competitor analysis to choose the format and article length.
topic mode researches the best primary and secondary keywords. keyword mode writes directly from the supplied keyword.
Currently only available for UK, US, AU, and CA.
search market

These settings control Google Ads keyword-volume targeting and SERP localisation.

Blank means global, no geo target.
example: sound effects libraries for video editors; how to edit audio in DaVinci Resolve
example: sound effects libraries for video editors; audio editing in DaVinci Resolve
CMS details

Only the selected CMS section is used. Secret fields are accepted for the current request but should not be rendered back into the page after submission.

WordPress setup

Connect with a WordPress Application Password. Do not use the normal wp-admin password.

1 Add the site and user

Use the final HTTPS WordPress domain and the username that should create the post.

2 Create the password

Open WordPress' Application Password screen, approve access, then copy the generated password.

3 Paste and test

Paste the generated password below and run the REST access test before generating content.

4 Choose publish settings

Start with Draft, then add optional author, category, tag or SEO meta settings if required.

1. Site and WordPress user

2. Application Password

This is the label WordPress shows in the user's aapplication passwords list.
Do not paste the WordPress username password.
  1. Generate the password in WordPress.
  2. Paste it into the field above.
  3. Click test connection. Only run content generation after the test passes.

3. Publishing settings

recommended: Draft
Use Draft until the connection and formatting have been checked on the WordPress site.
Use posts for normal blog posts or pages for pages. Custom post types must be available in the REST API.
Optional WordPress settings
Leave blank to use the authenticated WordPress user.
Comma-separated numeric IDs.
Comma-separated numeric IDs.
Leave as Auto unless the access test says a specific route style is required.
Leave blank for manual copy/paste. Only use an HTTPS callback URL when one has been configured.
Only use this when the SEO plugin or theme exposes the meta key through the REST API.
Leave blank unless the key is registered for REST writes.

Webflow setup

Connect to a Webflow CMS Collection with an API token, then map the fields used for the generated draft.

1 Add the API token

Use a Webflow API token with permission to create CMS Collection items for the selected site.

2 Identify the collection

Add the Collection ID for the CMS collection that should receive the generated article.

3 Map the fields

Match each field slug to the fields in the Webflow collection, especially title and article body.

4 Create as draft

Keep draft mode enabled until the field mapping and formatting have been checked in Webflow.

1. API access and collection

Use a token intended for API publishing. Do not share or store it outside the current request.
This should be the collection that stores blog posts or article pages.
Add the Site ID when the backend needs it to resolve collection context or publishing behaviour.

2. Collection context

helps with labels and diagnostics
Human-readable collection name, used to make the setup easier to understand.
The collection slug used in Webflow URLs or collection settings.
Recommended while testing. Review the CMS item before publishing to the live site.

3. Required field mapping

match Webflow field slugs exactly
The field that receives the generated article headline.
The rich text or HTML field that receives the article body.
Optional fallback field if the collection stores Markdown.
Optional Webflow field mappings

Use these only when the Webflow collection has matching fields. Field names should match the Webflow field slugs, not the display labels.

  1. Paste the API token and Collection ID.
  2. Check the title and body field slugs against the Webflow collection.
  3. Keep draft mode enabled for test runs.
  4. Run the tool, then review the item in Webflow before publishing.

Sanity setup

Connect to a Sanity project and dataset with a token that can create documents for the chosen document type.

1 Add project details

Enter the Sanity project ID and dataset that should receive the generated document.

2 Add an API token

Use a token with write access for the selected project and dataset.

3 Choose the schema type

Set the document type used by the Sanity schema, such as post or article.

4 Run and review

Create the document, then review it in Sanity Studio before using it on the live site.

1. Project and dataset

The project ID from the Sanity project settings.
Use the dataset that powers the target website or preview environment.

2. API token

Use a token that is allowed to create documents in the selected dataset.

3. Schema and API settings

This must match the document type in the Sanity schema.
Use the version configured for the backend integration. Keep the existing value unless the backend has been updated.
  1. Enter the project ID, dataset and API token.
  2. Confirm the document type matches the Sanity schema.
  3. Run a test item and review the generated document in Sanity Studio.
  4. Check portable text, slug, title and metadata fields before publishing from the website workflow.

keyword research

This researches a seed topic or keyword, gathers related Google Ads keyword ideas, checks SERP intent when enabled, and ranks the best primary keyword using topical fit, SERP/PASF alignment and search-volume evidence. It does not create a CMS item.

research summary

No keyword researched yet.

keyword ideas

—