Page Metadata

You might say

Check what this page shows in the tab, search snippet, shared link, and install entry separately.

Information about a page that is read outside its visible bodyPage metadata lives in the document head and is read separately by browsers, search systems, sharing platforms, or install surfaces. It is not one completion switch; inspect the relevant field and rendered result for each consumer.

Know first

HTML Title Tag

Who reads information from one head

<head>

1<title>Refund guide</title>

2<meta name="description" content="…">

3<meta property="og:image" content="…">

4<link rel="manifest" href="/manifest.json">

BrowserTab: Refund guide

“Metadata is done” is not a test result; verify the fields used by each consumer.

How page metadata divides the job

Head fields produce different results: The title affects the browser tab, a description may help form a search snippet, Open Graph fields feed a link preview, and a Manifest describes an install entry. They relate to the body but are not body content.

Verify each consumer's actual result: Ask who reads a field, then check the field, resource URL, and final presentation. A correct one only proves that its corresponding consumer received usable information.

Quick checkChoose the best answer

The browser tab title is correct, but a shared link has no image. Where should you look first?

Inspect metadata read by sharing platforms, add the matching image, and retest with a real previewRewrite the first paragraph so the platform can automatically find an image in the bodyChange the Favicon because every page image comes from it

You can say this to an AI Agent

List this page's metadata separately for the browser tab, search snippet, shared link, and install entry, and add only the missing field for each consumer. Verify with page source, search output, and a real share preview; do not treat metadata as one indivisible completion flag.

Learn next

1Open Graph→2Web App Manifest→