ForHosting KIT · SEO

Write click-worthy titles

A title tag does two jobs at once — rank and get clicked — and most writers only optimize for the first one. This endpoint takes a page's topic and target keyword and returns several distinct title variants built to earn the click without resorting to bait.

● StablePer request + per variant$0.003

Run — $0.003 + $0.0135/variant How it works & API

Use it from WebAPIEmailApp soonTelegram soon

Run it online

Run this on our servers with your account. Free tools run in your browser; this one bills your KIT balance per the price above.

The problem with writing titles alone

Staring at one title for twenty minutes is a bad use of anyone's time, and it's also a bad way to find a good title — the first phrasing that comes to mind is rarely the sharpest one. This endpoint sidesteps the blank-cursor problem by generating several angles at once: a direct keyword-first version, a benefit-led version, a question version, a number-led version — so the choice becomes picking the best of several real options instead of defending the only one you wrote.

What 'earning the click' means here

Search results punish titles that overpromise: a page that doesn't deliver on its title's claim gets abandoned quickly, and that abandonment is itself a signal. Every variant this endpoint returns is grounded in the topic you provided — no invented statistics, no fabricated superlatives, no urgency that isn't real. The goal is titles that a searcher trusts enough to click and doesn't regret clicking.

Why length and clarity still decide the outcome

Search engines have truncated title tags at roughly 50 to 60 characters for well over a decade, and that constraint hasn't loosened even as interfaces have changed — it just gets less attention than it deserves. Variants are written with that limit in mind, front-loading the keyword and the value proposition so the part that matters survives truncation on any device.

Where it plugs in

Because results arrive asynchronously, this fits naturally into a bulk workflow: submit every underperforming page's target keyword in a batch job overnight, and wake up to a spreadsheet of ready-to-test title options for each one. It works just as well one page at a time, dropped into a CMS field before publishing.

What stays a judgment call

The endpoint proposes; it doesn't decide. Brand voice, legal claims and factual accuracy for anything sensitive still need a human pass before a title goes live. Results are delivered by signed webhook or a 24-hour signed link, and nothing you submit is retained past the storage window or used to train anything.

What you can do with it

A/B testing title tags

A publisher pulls five variants for an underperforming article and rotates them through a testing tool to see which lifts click-through rate.

Bulk rewrite after a migration

After a site migration flattens dozens of titles into generic templates, a team regenerates proper variants for each URL in one batch.

New article launch

A writer requests variants the moment a draft is finished, picking the sharpest option before the page goes live instead of shipping the working title.

E-commerce category pages

A store generates distinct title options for near-duplicate category pages to reduce the sameness that makes them blur together in results.

FAQ

How does the SEO title generator API avoid clickbait?

Every variant is grounded in the topic and keyword you submit — no invented numbers or claims — so titles stay accurate to what the page actually delivers.

How many title variants do I get per request?

You choose how many variants to request; pricing scales per variant, so you only pay for the options you actually ask for.

Is there a free trial?

There's no free tier — free tiers get abused and slow everyone down. Access runs on a prepaid ForHosting KIT balance: top up from $10.00 (it never expires) and each request is charged at its published price, so a call with no balance returns HTTP 402. No subscription, no tokens, no invented credits, and a failed task is never charged.

What's the pricing?

$0.003 per request plus $0.0135 per title variant generated.

Can I generate titles for many pages at once?

Yes, batch requests are the intended use — queue titles for an entire list of URLs and collect results asynchronously.

How do results come back?

By signed webhook (recommended for automation) or a signed link valid for 24 hours.

Are failed requests billed?

No. A task that fails after three retries is never charged, and you receive a clear error instead.

Does it account for character length limits?

Yes, variants are written with typical title-tag truncation limits in mind so the key message survives on most devices.

For developers — API access

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

API endpoint

POSThttps://api.kit.forhosting.com/seo/title-variants

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, and soon from our app, email and Telegram.

Call it from your stack

curl -X POST https://api.kit.forhosting.com/seo/title-variants \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d &#39;{"input":"…"}'

const res = await fetch("https://api.kit.forhosting.com/seo/title-variants", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "input": "…"
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/seo/title-variants",
    headers={"Authorization": f"Bearer {os.environ[&#39;KIT_KEY']}"},
    json={
    "input": "…"
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/seo/title-variants", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => &#39;{"input":"…"}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"input":"…"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/seo/title-variants", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)

Example request

{
  "input": "…"
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "seo.title_variants",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Pricing

Per request$0.003

Per variant$0.0135

Published price — no tokens, no invented credits. A failed task is never charged.

Errors

HTTP	Code	Meaning
`401`	`unauthorized`	Missing or invalid API key.
`402`	`insufficient_balance`	Your balance doesn't cover the task price.
`404`	`unknown_type`	That task type doesn't exist.
`429`	`rate_limited`	Too many requests. Use the webhook instead of polling.
`422`	`task_failed`	The task failed after 3 retries. You are never charged for it.

Read the full KIT documentation →