Preview a title, description, and URL as a search snippet or social card. Check clarity and consistency before publishing your page metadata.
How to use
Enter the fields and select Search snippet, Open Graph, or Social summary. You can also import pasted HTML meta tags and add a local preview image.
Example
Compare “Guide” with “How to freeze basil” above the same description. The second title gives the reader a clearer topic.
FAQ
Is this the exact Google result?
No. Search and social platforms change layouts, snippets, and truncation. The preview is illustrative and does not fetch a live result.
Related tools
A practical task
Use the preview to compare wording choices, not forecast clicks. A reader should understand the topic from the title and the useful detail from the description. Check that both still make sense when the description is shortened by a platform.
Another useful question
Does importing metadata contact the page?
No. Paste the HTML source you want to inspect. The tool reads those supplied tags instead of crawling a URL to discover them.
Details for interpreting the result
| Detail | Explanation |
|---|---|
| Metadata and page content | A title and description should summarize the page a visitor will actually find. Search engines can choose other wording for a query. Clear, distinct summaries are more useful than repeating a keyword in every available field. |
| Canonical signals | A canonical tag indicates a preferred URL among duplicate or similar pages. It is a signal rather than a command. Internal links, redirects, sitemaps, and actual content should agree about the preferred address. |
| URL components | A URL contains structure such as scheme, host, path, query, and fragment. Characters that separate those parts differ from characters inside a value. Encode the right component rather than transforming the full address blindly. |
| Query values | Query separators connect parameter names and values. An ampersand inside a value must not be confused with the separator between parameters. Build the URL with correct component encoding before sharing it. |
| URL fragments | A fragment points to a location within a resource and is normally not sent as part of the server request. It differs from a query parameter. Changing it does not necessarily create a different document for canonical selection. |
| Structured data | Structured data describes entities and facts in a machine readable format. It must match visible page content. A valid JSON document is not proof of eligibility for a search feature or a promise of richer display. |
| Source boundaries | A summary or rewrite works from the material you provide. A URL alone does not supply the full article in this interface. Include the relevant passage and keep citations attached to the claims they support. |