Why doesn't Google show the title I wrote?

Because the element is one of nine sources Google uses for the title link, not the only one. Its documentation says it may generate an improved title link from anchors, on-page text or other sources when it detects an issue on the page. The usual issues are titles that repeat across pages, boilerplate, or keyword stuffing such as "Cakes, cake, cakes Leeds, Leeds cake", which Google explicitly warns makes results look spammy. Fix the cause and the rewrite usually stops.

Does the title have to match the H1 exactly?

No, and it usually shouldn't. The title element is read by someone deciding whether to click, so it carries the site name and the navigational words. The is read by someone who has already arrived and can be shorter and more natural. They should make the same promise, not use the same characters.

What happens if a page has no title element?

The browser tab falls back to the URL, screen-reader users lose the fastest way to identify the page, and Google is left to assemble a title link entirely from other signals. Its guidance is plain: make sure every page on your site has a title specified.

How do I find the title of a website that isn't mine?

Open the page and read the browser tab, which shows the element. If you need the exact text, view the page source and look for the line inside .

Website title: which of the four you mean, and what to write in it

Q: How long should a website title be?

Google says there's no limit on the element itself, and that the title link is truncated in search results as needed, typically to fit the device width. So there's no number to hit. Put the words that identify the page at the front and let the tail get cut if it has to.

Somebody tells you to fix the website title. Before you can, you have to work out which one they mean, because four separate things go by that name: the <title> element in the page's head, the big heading you can actually see on the page, the name of the site as a whole, and the title that fills the card when someone pastes your link into a chat.

They are not synonyms. Different places, different edits, different consequences. This is why "I changed the title and nothing changed" is such a common complaint.

So the useful question isn't what a website title is. It's this: where did you see the text you want to change?

Four surfaces, four titles

The browser tab is fed by the <title> element, which sits in the page's <head>. The heading you see on the page is the <h1>, a completely different element in a completely different part of the document. The Google result actually shows two names, not one: a small grey site name on top, and the blue clickable line underneath. And the card in a chat window is usually built from og:title.

Four surfaces. Four elements. One phrase covering all of them, which is where the confusion starts.

Which one are you actually editing

You almost never know which element you need by name. You know where you saw the text. So route from there.

Where you saw it	What you edit
The browser tab, or the window title	The `<title>` element
The big heading on the page itself	The `<h1>`
The blue clickable line in a Google result	The `<title>` element, usually
The small grey name above that line	Your site name
The card that appears when you paste the link into a chat	`og:title`

That third row has a hedge in it, and the hedge is the honest part. Google lists the sources it uses to build a title link, and the <title> element is only the first of nine. The others include the main visual title on the page, heading elements such as <h1>, og:title, prominent styled text, other text on the page, anchor text, links pointing at the page, and WebSite structured data. If Google detects a problem, it says it "may try to generate an improved title link from anchors, on-page text, or other sources."

Which means the four elements aren't independent after all. They're four inputs that partly feed each other. Set them consistently and they reinforce; set them carelessly and Google picks whichever one it likes.

What goes in each one

The title element

It goes in the <head>, there is exactly one per document, and MDN notes it contains text only: any HTML tags inside it are treated as plain text. This is the one that fills the browser tab, and it is the default candidate for the search result's clickable line.

Write the page's own promise first, then the site name. Google's guidance is to keep branding concise and put the site name at the beginning or end, separated by a delimiter. Its other rule matters more: "It's important to have distinct text that describes the content of the page in the <title> element for each page on your site." Ten pages sharing one title is the most common real problem, and it is invisible if you only ever look at one page.

On length, the folklore says 60 characters. What Google actually says is that there's no limit on the element, and that the title link "is truncated in Google Search results as needed, typically to fit the device width." So the rule isn't a character count. It's ordering: put the words that identify the page at the front, where nothing can cut them off.

The visible heading

The <h1> is what a reader sees once they've already arrived. It usually sits in the hero block, whatever layout the page uses. It doesn't need the site name, because the person is already looking at your site, and it can drop the keywords that were doing navigational work in the search results.

It should still say the same thing. A page whose tab says one thing and whose heading says another feels like a redirect went wrong.

Your site name

This one surprises people, because it's a real feature with its own documentation. Google describes the site name as "the name of the site the page comes from", shown above the title link, and it draws that from WebSite structured data, og:site_name, the home page's <title>, heading elements, and other home page text. Generation is automated, so structured data is a strong signal rather than a switch you flip. Site names also work at the domain or subdomain level only, never per subdirectory.

Worth knowing on a free Birta project: the address a searcher sees is your Birta subdomain, something like cake-shop.birta.link, until you connect a domain of your own on a paid plan.

og:title comes from the Open Graph protocol, which defines it as "the title of your object as it should appear within the graph" and lists it as one of four required properties alongside og:type, og:image and og:url.

Chat apps, social platforms and preview bots read it to build the card. Each of them decides for itself what to do when the property is missing, so leaving it out means handing that decision to whichever app your link lands in. Setting it is cheap.

The formula

Purpose first, site name second. Not because marketers agree on it, but because MDN gives the accessibility reason: a common navigation technique for assistive technology users is to read the page title and infer what the page contains, so titles should surface "the primary purpose of the page first, followed by the name of the website."

Page	Formula
Home page	What you do, where, then the site name
Inner page	What this page is, then the site name
Article	The article's own promise; the site name is optional
One-page site	The home page formula, because there is only one page

Written out for a cake business in Leeds:

Home page      Wedding Cakes in Leeds | Vale Cakes
Inner page     Delivery and Setup | Vale Cakes
Article        What a three-tier wedding cake costs
One-page site  Wedding Cakes in Leeds | Vale Cakes

Whatever separator you pick, use the same one everywhere. A site where three pages use a pipe, two use a dash and one uses a colon reads as unmaintained before anyone has read a word of it.

One prompt that sets all four

There's no title box to fill in anywhere. On Birta the site is files, so all four of these live in the HTML your agent writes, which makes a prompt the right tool rather than a workaround. Paste this one, and adjust it the way you would any other brief you hand an agent:

Set the four title elements on every page of this site, consistently.

1. <title> in <head>: this page's own promise first, then " | " and the site
   name. Plain text, one per page, and no two pages get the same one.
2. <h1>: the visible heading. Same promise as the title, phrased for someone
   who has already arrived. Exactly one per page.
3. og:title in <head>: the same text as <title> without the site-name suffix.
4. On the home page only: WebSite structured data with "name" set to the site
   name and "url" set to the home page URL. Also set og:site_name to match.

Before you change anything, list every page with the title you plan to give it
so I can check that none of them repeat.

The last instruction is the one that earns its place. Uniqueness is the rule you cannot verify by looking at a single page, and it's the rule most sites break.

Once the titles are set, they're one line in a broader pre-launch pass. The website audit template covers what else to check before the site goes out.

Hand the prompt to your agent

Your titles live in the site's files, so the change happens where your agent already works.

Connect your agent to Birta