How to Write Title Tags and Meta Descriptions That Get Clicks

SERP Snippet Preview is a width check while you write. Meta Tag Extractor is how you confirm those strings actually shipped (a live URL is fetched). This is copy for the page in front of you, not a plan to rank this article.

Intent first, then the character budget

Ask what the searcher is trying to do on this URL. Format JSON. Check a certificate. Preview an OG card. The title should sound like that task. The description should say what happens after they click (paste, run, download) and any constraint that matters (no account, public lookup, browser-local file).

Only then worry about length. A perfect 55-character title that names the wrong job loses to a slightly long title that names the right one.

Queries that mean “do the thing now” want a tool name plus a concrete verb. Queries that mean “how does X work” want a how-to title on the article, and a shorter job name on the tool. Do not copy the blog title onto the form page.

Titles that name the job

Patterns that hold up:

• Tool: JSON Formatter - Validate and Pretty-Print
• Checker: SSL Certificate Checker - Expiry and SAN
• Guide: How DNS Records Work: A, AAAA, MX, CNAME, TXT

Patterns that fail:

• Best Free Online Ultimate JSON Tool 2026 | Brand | Home
• Brand first, job last, truncated to Brand | Best Fr…
• The same title on twenty routes.

Put the unique noun early. Put the brand after an em dash or pipe if it still fits in SERP Snippet Preview. If the brand forces a cut, drop the brand; the tab already shows your favicon.

Match the <h1> closely. A title that says “Invoice Generator” and an H1 that says “Welcome” is how rewrites get invited.

Descriptions that finish the sentence

Write one or two sentences a person would say out loud:

Pretty-print, validate, and minify JSON in the browser. No account. The file never needs to be uploaded to run the formatter.

Avoid:

• Keyword lists (json, formatter, beautify, validate, online, free).
• Claims you cannot see on the page (“#1 ranked”).
• Cutting off at “Learn more about our…” with no object.

Front-load the outcome. If mobile width keeps only the first 100 pixels of text, that fragment should still be true.

You do not need a call-to-action on every description. On a tool page, “paste and run” is enough. On an article, say what the reader will understand by the end.

Pixel width versus character counts

Google measures pixels, and fonts are not monospaced. “W” and “i” do not cost the same. Character guidelines (title ~60, description ~150–160) are a draft. The preview is the check.

SERP Snippet Preview shows a typical desktop result and a narrower mobile line. If the last word of the title is the verb, shorten the noun phrase. If the description ends on “and”, cut a clause.

URL crumbs (site name, path) also take space. A deep path /blog/2026/08/how-to-… can crowd the line. That is a URL-design issue, not a reason to write a 20-character title.

How to preview, then verify

1. Write title and description next to the H1 in a doc.
2. Paste them into SERP Snippet Preview. Edit until both breakpoints read as complete.
3. Put the strings in the template. Deploy.
4. Confirm with Meta Tag Extractor on the public URL - that request leaves the browser.
5. If you also share the URL in chat, write og:title / og:description separately when the SERP title is too cramped for a card. See How Open Graph Tags Control Link Previews.

No account. No keyword spreadsheet upload.

What you cannot control after a rewrite

Google may pull a heading, a branded sitelink name, or a sentence from the body. That happens more when:

• the title is stuffed or repeated across the site,
• the query is very specific and your title is generic,
• the page is new and the index is still guessing.

You cannot “lock” a snippet with a tag. You can make the official title the best available sentence so a rewrite is optional, not a rescue.

This is still not a ranking playbook. Clicks on an accurate snippet are a side effect of saying what the page does.

Draft the snippet, then audit the shipped head

Draft in SERP Snippet Preview. After deploy, audit the head with Meta Tag Extractor. If the URL is a form, continue with On-Page SEO for Tool Pages so the H1, canonical, and title stay one story.