Create HTML title, description, Open Graph, and social summary tags. Keep page identity consistent when sharing links or editing a page head.
How to use
Enter the page title and description in the fields, then put the full page URL in the input. Generate the tags and replace conflicting entries in your page head.
Example
For a recipe guide, use its actual title, a summary of the method, and the published URL rather than your site's homepage address.
FAQ
Does this publish the tags?
No. Copy them into your site and inspect the resulting HTML. It does not add an image tag or guarantee search rankings.
Related tools
A practical task
Inspect existing head tags before adding the generated block. Duplicate titles or descriptions can leave several conflicting candidates for a platform. Replace the relevant entries deliberately and check the final rendered HTML rather than only the source template.
Another useful question
Does an Open Graph tag change page content?
No. It describes a shareable page to a consumer. The visible article, its URL, and its metadata should still agree about what the link offers.
Settings and formats
| Field | Values |
|---|---|
| Page title | Starting value: My article |
| Meta description | Starting value: A useful guide for readers. |
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. |