Aurify grows when people share their Auras. But every URL on aurify.com sends the same HTML shell, so a link to a scene or a result shows the same "Aurify — AI image platform" banner on WhatsApp, iMessage, X and Facebook. Those previews don't run the page's scripts. A friend sees a logo card instead of the person in a first-class cabin or in Tokyo after dark, which is the one picture that would make them tap. For a growth hire, this is the share loop leaking at its first step.
First action
Write per-template title, description and image tags for the 20 most-used scenes.
How to measure it
Click-through on shared links
- Now
- –
- Target
- 2x
- By
- 30 days
Steps
Check previews
Paste five scene links into WhatsApp and iMessage and record what shows.
Growth Lead 1 hour
Edge function
Write per-page tags for templates and shared results.
Frontend Engineer 3 days
Preview images
Generate 1200x630 crops with a small corner mark.
Frontend Engineer 2 days
Privacy rule
Only results the owner has chosen to share get a personal preview.
Trust and Safety Lead 1 day
Referral tag
Add the sharer's ?ref= code to every share link.
Frontend Engineer 1 day
Validate
Facebook, X and LinkedIn preview debuggers.
Frontend Engineer 2 hours
Measure
Shared-link visits and generations started from them.
Growth Lead weekly
Why it works
Add an edge function that, for /templates/<slug> and shared result links, writes the page's own title, description and image tags (the scene's example image, or the user's result with a "Made with Aurify" corner mark) into the HTML before it is sent. Use the 1.91:1 crop for link cards and keep 9:16 for stories. Then tag shared links with the sharer's ?ref= code so each visit counts toward their invite slots.
Rich previews raise click-through on shared links many times over a plain logo card, and each click starts at the exact scene the friend wants to try.
Ready to use
ChecklistShare preview checklist
[ ] /templates/<slug> returns its own title and description [ ] og:image is the scene example at 1200x630 [ ] Shared results use the user's image only when they shared it [ ] Corner mark "Made with Aurify" [ ] ?ref= code on every share link [ ] Twitter card summary_large_image per page [ ] Tested in WhatsApp, iMessage, X, Facebook, LinkedIn
Risks and how to handle them
Private images in previews
Use the scene's example image unless the owner shares a result.
Cached old previews
Refresh with each platform's debugger after launch.
Evidence
- Your websiteChecked November 4, 2026: every URL on aurify.com (the homepage, /gallery and each /templates/<scene> page alike) returns the same HTML shell with the same title, description and share image ("Aurify — AI image platform", og-image.jpg). Link previews on WhatsApp, iMessage, X and Facebook do not run the page's scripts, so a shared scene or result shows the generic banner, not the scene or the person's image. The result page shares with "Made with Aurify ✨" and opens the device share sheet; shared links open without sign-in.Source
- Your websiteGrowth features already built: an invite link ("Share your invite link — when a friend joins, a slot fills in") using ?ref= codes; "Caption for social" with "Copy caption + tags"; batch "Aurify them all at once" for up to 20 templates; an avatar built from four photos; pet scenes; and an "Aura Creator Payout" opt-in: "if Aurify selects my Aura to feature, I may be eligible for a payout of up to $1,000".Source
- Your websiteHomepage: "One selfie is all it takes. Drop into iconic, cinematic worlds looking unmistakably, magically you."; button "Aurify yourself — it's free"; "12,000+ already created Auras · Yours takes one photo"; "No studio. No photographer. Just pick a scene, upload one photo, and watch your aura come to life." Title "Aurify — AI image platform".Source