← All guides

GUIDE 03 / FIRST IMPRESSIONS

Make your links look like your site.

A shared link often arrives before your page does. Give it enough context to help someone decide whether to open it.

Start with a useful title.

A page title should explain the subject clearly, even when separated from the rest of the site. “A practical guide to repotting ferns” says more than “Article 17.” Add a short site name when it gives helpful context.

<title>Repotting ferns: a practical guide | Greenhouse Notes</title>
<meta name="description"
      content="Learn when a fern needs a larger pot, which soil to use,
               and how to move it without damaging the roots.">

The title and description in this example describe a fictional page. Write your own around the actual content. Search engines can choose different title links or snippets, so a metadata preview is not a promise of how a search result will appear. Google’s title-link guidance explains how titles may be generated.

Give social platforms explicit metadata.

Open Graph metadata describes a page for services that support the protocol. The basic properties include a title, type, image, and URL. A description adds useful context. See the Open Graph protocol for the property definitions.

<meta property="og:type" content="article">
<meta property="og:title" content="A practical guide to repotting ferns">
<meta property="og:description" content="A calmer move for a growing plant.">
<meta property="og:url" content="https://example.com/repotting-ferns/">
<meta property="og:image" content="https://example.com/images/fern-guide.jpg">
<meta property="og:image:alt" content="A fern beside its new terracotta pot">

Use an absolute public URL for the image. Make sure the image belongs to the page, is available to the intended platform, and still makes sense when cropped. The best crop depends on the service and card format.

Check the served source.

It is easy to edit a template and still serve old metadata from a cache, a duplicate page, or a different language version. Inspect the public URL after publishing, then compare the returned values with what you intended.

Metadata inserted only after JavaScript runs may not be present in the initial HTML response. Our URL checks inspect that source response and do not execute scripts. The result can therefore differ from what you see in a browser’s live document inspector.

Read previews as approximations.

The same link can look different across platforms, screen sizes, and versions of an application. Titles may be truncated, images cropped, or descriptions omitted. Platforms can also cache older values.

The preview is illustrative. Imagiware does not connect to social networks or guarantee their final card layout. Image URLs are shown as text with a placeholder, so checking a page does not silently load its remote preview image.

A compact publishing checklist.

  1. Write a specific title that matches the page.
  2. Summarize what someone will actually find there.
  3. Check that Open Graph values use the intended page and image URLs.
  4. Inspect the live response after publishing.
  5. Test the link on the platform that matters to you, accounting for cached previews.

Length guidance is a reminder to edit, not a universal character limit. Focus on the most useful information first, and review the whole card in context.