How lovely.link's Process Works: From Brief to Live Images

lovely.link turns your brand into a set of custom Open Graph (OG) image templates, then generates a unique share image for every page on your site automatically. The process runs in three steps — strategy, design, and an integration kit — and the site states the kit is usually ready within about 7 days. You don't need developers to set it up, though the integration itself is a URL-based API that works with any CMS, framework, or static site.

The three steps

1. Strategy

You start with a detailed consultation. In that conversation you share:

• Your brand assets (logos, colors, type, imagery)
• Your goals for the shared links
• The pages you want covered

This is the step that determines what the templates need to hold. If you skip it or give vague inputs, the design step has nothing concrete to work from.

2. Design time

lovely.link designs custom template concepts and iterates until they match your brand. The output is a template — a fixed layout with defined slots — not a finished image. You fill in the blanks with your content later, and the service automates the rest.

The site is explicit that this is 100% custom design: no stock photos, no generic layouts.

3. Your kit is ready

You receive an integration kit containing:

• A URL-based API
• Documentation
• Ready-to-use templates

The site says this usually happens within about 7 days of starting.

What happens after delivery

Once the kit is in hand, the ongoing flow is:

1. You fill in the content blanks for each page — the text, images, and data that should appear on that page's share image.
2. lovely.link generates the image dynamically from that content, every time a link is shared.
3. The image renders on the platform — the site lists Twitter, LinkedIn, Facebook, WhatsApp, Slack, and "every platform that renders Open Graph images."

The key shift is that you stop making images manually. There's no Photoshop step per page; the template plus your content produces the image on demand.

Integration and infrastructure

The "no developers required" claim applies to getting set up. The API is still URL-based, so whoever wires it into your site needs to be able to add a URL pattern to your page templates — a task most CMS or framework users can handle, and one lovely.link offers to help with.

What you get out of it

The site frames the payoff in three numbers:

• 60% brand awareness
• 20% click-through rate
• 80% cheaper than building your own

It also makes the argument directly: if you already get organic traffic on social media, fixing how those links look improves that channel's effectiveness. The comparison it draws is companies spending thousands on paid traffic while neglecting organic impressions.

When this process fits

The three-step flow suits you if:

• You have a site with many pages and want consistent, branded share images across all of them
• You want custom design rather than a generic template library
• You can supply brand assets and a list of pages to cover up front
• You want the images generated automatically rather than made by hand

It's less suited to a one-off image need, since the value comes from the template being reused across every page.

Common points to plan for

• Have your assets ready before the consultation. The strategy step is where the design gets its inputs; missing logos or unclear brand direction slows everything downstream.
• Decide which pages are covered. The consultation includes "the pages you want covered," so come with that list rather than discovering gaps after delivery.
• Know who will do the integration. No developers are required, but someone still has to place the URL-based API into your site. If that's not you, identify that person before the kit arrives.
• Expect about a week. The site says the kit is usually ready within 7 days — plan your launch around that, not around same-day turnaround.