Title Tag Generator
Give it a URL or a topic and the keyword you want to rank for. It writes 12 candidate title tags, appends your brand by code, then measures every one in your browser at Google's desktop and mobile widths, so the ones it shows you first are the ones that will not be cut.
Short answer
A title tag generator writes candidate <title> text from what a page is about and the phrase it targets. This one measures every candidate in real pixels at Google's desktop and mobile widths, because Google cuts by width, not by character count. The words are a model's and are marked as such; the widths, counts and keyword placement are measured.
The words are generated. The numbers are not.
A model is good at writing twelve ways to say what a page is about, and bad at knowing how wide any of them will be. So the tool splits the job: the model gets a character budget, a list of angles, and the page's own title, H1, description and opening paragraph. Then code takes over.
| What | Who does it | How |
|---|---|---|
| The twelve candidates | Model | One call, JSON out, model named on the page |
| Brand suffix | Code | Typed, or read from the current title, appended identically to every candidate |
| Width on desktop and mobile | Your browser | Canvas measurement at 20px and 18px Arial, the same code as the SERP preview |
| Cut point | Your browser | Where Google stops, shown in grey on any candidate that overflows |
| Keyword placement | Code | Up front, later, or absent, on every candidate and on the current title |
| Character count | Code | Reported next to the width, never instead of it |
That split is why the generated block is drawn in its own colour with the model named at the top. A generated title and a measured width are different kinds of claim, and the page keeps them apart so you always know which one you are reading.
Why the budget is an estimate and the width is the rule
A desktop result gives a title one line of 600px in 20px Arial. Mixed-case English averages just under ten pixels a character, which is where the 60-character rule comes from, and why it fails: capitals run out of room near 50 characters, narrow lowercase fits past 65. A model gets a budget because it cannot measure; the tool measures anyway.
Candidates that fit are listed first. Candidates that overflow are kept in a second group with the cut point marked rather than dropped, because a title four pixels over is one you can fix with one word. Mobile gets two lines at 400px, so a title can fit mobile and cut on desktop, and each candidate says which.
The container moves
Google changes the result layout without announcing it, so the widths are a working approximation and not a specification. Treat a title measuring 590px as at risk. The SERP snippet preview and the bulk title checker use the same measurement, so the three tools cannot disagree about where a title is cut.
What this generator cannot know
The tool reads one page and writes for it. It can tell you which of twelve titles fit and carry the keyword, and it cannot tell you whether this is the page whose title is worth rewriting. That takes data it does not have:
- Which titles to fix. High impressions with a low click-through rate is the clearest sign a title is underperforming, and it is a Search Console signal. A free tool with no OAuth cannot see it.
- What people actually type. The keyword you give it is the one it checks. The queries a page already earns impressions for, which are often not the one you had in mind, are in Search Console too.
- Whether the same title repeats. One generated title is unique by construction. Whether it collides with 40 other pages on the site is a bulk question, which the bulk title checker answers.
That ranked view, this page has 2,000 impressions, a 1% CTR and a cut title, fix it first, is what CrawlRaven builds by joining your Search Console and GA4 data with a technical crawl. The generator is the last step of that, run by hand on one page. Nothing here implies a free tool knows which title matters.
Using the generator on a real page
Start from a page whose title is cut or duplicated: the bulk title checker links every such row straight here with the URL filled in. Then:
- Add the keyword, leave the brand blank. The tool checks the phrase on every candidate and reads the suffix the site already uses.
- Read the current title first. Its width and cut point are the baseline. Then click any candidate that fits to see it in the preview at either width.
- Pick on two things. The keyword sits up front, and the title says what the page contains. A candidate promising a comparison the page does not make gets rewritten by Google and disappoints the reader who clicked.
- Ship it and check the rest. Copy the winner into your title tag, keep the H1 in agreement with it, and check the description with the meta tag checker.
Re-running the same page with the same keyword and brand is served from cache and does not spend an AI run. For the H1 and blog title rather than the tag, the headline generator writes to the editorial rules instead of the pixel box.
What the generator reports
Twelve candidates, ten angles
How-to, list, question, benefit, comparison and more, so it is not one idea reworded twelve times
Width in real pixels
Every candidate measured in your browser at 600px desktop and 400px mobile, the way Google cuts
Cut point shown, never hidden
Candidates that overflow are kept with the dropped part in grey, so a near miss is a one-word fix
Brand appended by code
Typed or read from the current title, identical on every candidate, subtracted from the budget first
Keyword placement checked
Up front, later or absent, on every candidate and on the title the page has now
Before against after
The current title, H1 and description measured the same way, so you can see what changed
Live preview at both widths
Click a candidate to see it in a result box pinned to Google's container, not rewrapped
Generated kept apart
The model is named and its block drawn in its own colour; the measurement stands without it
What this reads, and what it cannot
Frequently asked questions
What is a title tag generator?
A tool that writes candidate title tags for a page from what it is about and the keyword it targets. Given a URL, this one reads the current title, H1, description and opening content, asks a model for 12 candidates under a character budget, then measures every one in your browser at Google's desktop and mobile widths.
Why measure in pixels rather than characters?
Because Google cuts a title by width, not length. A desktop result gives a title one line of about 600px at 20px Arial: sixty characters of narrow lowercase fit, fifty-five of wide capitals do not. Every generator that promises a length in characters is guessing at the width. This one measures it with the browser's own canvas layout engine.
What happens to candidates that are too wide?
They are shown, not dropped, in their own group under the ones that fit, with the cut point marked in grey. The character budget the model is given is an estimate and the width is the rule, so a candidate can come back a few pixels over. Trim the grey part and it fits.
Where does the brand suffix come from?
You can type one, and if you leave it blank in URL mode the tool reads the suffix the current title already carries, separator included, and says it was detected. The suffix is appended by code, not requested from the model, so every candidate carries it identically and its length is subtracted from the model's budget before writing starts.
Does it check that my keyword is in the title?
Yes, on every candidate and on the current title. Each is labelled with the keyword up front, meaning it begins within the first three words, present later, or absent. Front matters because a scanning eye and a truncating result read from the left. The model is asked to use the phrase verbatim in most candidates and never twice in one.
Can I use it without a URL?
Yes. Describe the page in a sentence or two, add the keyword and an optional brand, and nothing is fetched. You lose the before-and-after comparison and the detected brand suffix, and the model writes from your description alone, so say what the page actually contains rather than what you wish it did.
How is the AI part labelled?
Everything the model wrote sits in its own block with the model named at the top, in a colour nothing measured uses. The current title's measurement sits above it in the ordinary style. If the model is unavailable or you are over the daily AI allowance, the measurement still runs and the block says why the candidates did not.
Why is there a separate daily limit for this tool?
Because every run bills a model call, which none of the fetch-only tools on this site do. AI runs are limited per day on top of the ordinary tool limit. An identical run, same page, keyword and brand, is served from a cache and does not spend an AI run.
Will a new title improve my ranking?
Not by itself, and nothing here claims to. A title that is cut, or omits the phrase people search for, loses clicks on impressions you have already earned: a click-through problem, not a ranking one. The pages where a rewrite pays have high impressions and low CTR in Search Console, which is data this free tool does not have.
Should the title match my H1?
They should agree, not repeat. The title is written for the results page, where it competes with nine others and gets cut at 600px; the H1 is written for a reader who has already arrived. Google rewrites titles it considers a poor match for the page, and a title that contradicts the H1 is one of the clearest triggers.
Which pages should I run through this?
Start with the ones the bulk title checker flagged as cut or duplicated, which link straight here with the URL filled in. Then the pages Search Console shows with impressions at positions 8 to 20 and a click-through rate below their neighbours: those are the titles doing the least with the most.
Can I export the candidates?
Yes, as CSV: every candidate with its character count, desktop width, cut point if any, whether it fits mobile, keyword placement, the angle the model took, and a source column that says which rows were generated and which was measured from the page.
Other on-page SEO tools
Canonical Tag Checker
Validate canonical tags for self-referencing, protocol mismatches, trailing slash conflicts, noindex conflicts, and og:url consistency.
Use toolHreflang Validator
Validate hreflang tags for international SEO: self-referencing, return tags, x-default, language codes, and duplicate detection.
Use toolSchema & JSON-LD Validator
Validate structured data markup: required properties, date formats, nested entities, and JSON syntax. Supports all major schema types.
Use toolMeta Tag Checker
Check title tags, meta descriptions, Open Graph tags, Twitter cards, canonical URLs, robots directives, and viewport settings.
Use toolMeta Tags Generator
Write the title, description, and social share tags every page needs. Live character counts plus previews of how it will look in Google and on social.
Use toolKeyword Density Checker
See which words and phrases your copy actually leans on. Single word, two word and three word counts with density and first-mention position.
Use toolSERP Snippet Preview
See your title and meta description the way Google renders them, measured in pixels. Desktop and mobile, with the exact character your snippet is cut at.
Use toolURL Slug Generator
Turn a list of page titles into clean, readable URL slugs. Accents transliterated, filler words optional, and duplicates caught across the whole list.
Use toolAnchor Text Generator
Build branded, partial, long tail and naked URL anchor variations for any page, then audit the anchors you already have against a natural distribution.
Use toolReadability Checker
Score any text on six readability formulas at once, then see which sentences are dragging the grade up. Passive voice and long sentences broken out separately.
Use toolPage Word Counter
Count the words on any URL, with the body copy separated from the nav, header and footer. Unique words, reading time, paragraphs and the heading outline.
Use toolImage Alt Checker
Audit the alt text on every image on a page. Missing attributes kept apart from decorative alt="", plus image links with no name, filenames used as descriptions and duplicates.
Use toolOpen Graph Preview
Paste your meta tags and draw the card each platform renders, cut where it really cuts. Works on staging and on tags you have not deployed yet.
Use toolTwitter Card Validator
X retired its own validator in 2022. Check twitter:card on a live URL, see which tags X reads through the Open Graph fallback, and prove the image loads.
Use toolOpen Graph Checker
Fetch a live URL and read its og: tags the way a scraper does, then check the card image actually loads rather than only that the tag exists.
Use toolHeading Analyzer
Read the H1 to H6 outline of any URL and find the skipped levels, empty headings and duplicate labels, with the page's own headings separated from its template.
Use toolBulk Title Tag Checker
Check up to 100 title tags at once, measured in pixels rather than characters, and find the duplicates across a set that no single-URL checker can see.
Use toolBulk Meta Description Checker
Check up to 100 meta descriptions at once, measured in pixels, and find the duplicates, empty tags and descriptions that just repeat the title.
Use toolSEO Content Grader
Grade a page or draft against 20 weighted signals plus an AI judgement kept clearly apart. The score shows its own arithmetic, and every row prints its method.
Use toolHeadline Generator
Write 12 H1 and blog headlines from a URL or a topic, each checked against the house style: length band, keyword present, and none of the template tells or bait an editor would cut.
Use toolBulk Alt Text Generator
Write alt text for every image on a page that has none or sits in an unnamed link, never for decorative ones, with each description checked against the alt checker's own rules.
Use toolHelpful Content Checker
Check which of Google's helpful content signals a page actually shows: author, dates, sourcing, content ratio and ad load. No invented score.
Use toolRead up on on-page content
A tool tells you what is wrong. These explain what to do about it.
SaaS SEO: The Complete Guide to Ranking Your Product in 2026
Read guideSEOquake Review: Free, Still Shipping, and Built to Upsell Semrush
Read guideAIOSEO Review: The Search Console Reports Cost $599 a Year
Read guideTerms this tool checks
- Title Tag
A title tag is an HTML element (<title>) that specifies the title of a web page.
- CTR (Click-Through Rate)
Click-Through Rate (CTR) is the percentage of people who click on your search result after seeing it.
- H1 Tag
An H1 tag is the primary heading element on a web page, indicating the main topic of the page's content.
- Meta Description
A meta description is an HTML meta tag that provides a brief summary of a web page's content.
Twelve titles for one page, or the titles worth fixing across all of them
The generator writes and measures titles for one page. It cannot tell you which of your 400 pages has the title losing the most clicks, because that takes the click-through rates in Search Console. CrawlRaven joins GSC, GA4 and a technical crawl into one plan: what to write, update and fix first, ranked by the traffic behind it.