The page has no <title> tag
Your page has no <title>. That breaks browser tabs, bookmarks, search results and the fallback path for social previews all at once.
What you are seeing: Browser tabs show the URL instead of a name, bookmarks save with no label, and search results display a title Google invented.
More things depend on this than you would expect
The <title> tag names the page for the browser tab, the bookmark, the browsing history entry, the search result, and — when og:title is absent — the social card headline. It is one of the few pieces of metadata with no reasonable fallback anywhere in the stack.
Without it Google generates a title from the page content, usually by taking the H1 or an anchor's text. Sometimes that is fine. Often it is a nav label or a fragment, and you have no way to influence it.
How this usually happens
Almost always a single-page app that sets the title with JavaScript after mount. The browser shows the right thing, so it looks correct in testing, but crawlers read the raw HTML response and never run your JavaScript. They see an empty head.
The fix is to render the title server-side. Every modern framework has a metadata API that does this — the point is that the tag must be present in the initial HTML response, not applied afterwards.
What to write
Put the page-specific part first and the site name last, separated by a pipe or a dash. Someone scanning a row of browser tabs sees only the first twenty characters or so, and 'Acme Inc | Pricing' is useless in that context where 'Pricing | Acme' is not.
Keep it under 60 characters so Google displays it in full.
Server-rendered, page-specific first
<head>
<title>Pricing | Acme</title>
<meta name="description" content="Simple per-seat pricing. Start free." />
</head>Frequently asked
I set the title with JavaScript. Why does the checker not see it?
Because crawlers read the raw HTML response and do not execute JavaScript. document.title updates the tab for real users and is invisible to Google, Facebook and every other crawler. The tag has to be in the server response.
Does the <title> affect my social preview?
Only as a fallback. Most platforms use it as the card headline when og:title is missing. Setting og:title explicitly is better, but a page with neither has nothing to show.
Check your page
Run your URL through the checker to confirm the fix is live and see how the card renders on every platform.
Test a URL