Hi Base44 team and community,
Currently, apps built on Base44 using a custom domain (e.g., mydomain.com) face a significant limitation: backend functions are only accessible via Base44 system URLs, such as api.base44.com/... or app--.base44.app/....
While this works on a technical level, it creates a critical SEO and User Experience (UX) issue when trying to generate dynamic Open Graph (OG) tags for social media platforms (X/Twitter, Facebook, WhatsApp, etc.).
The issue in detail:
If we use a proxy function to generate metadata (title, image, description) when sharing a user's public profile or an event, the link displayed on social media and crawled by bots belongs to api.base44.com, not our custom domain.
This has two severe consequences for any builder:
Loss of SEO Authority (Backlinks): All external links shared on social networks pass the domain authority to Base44, rather than building authority for our own brand/domain.
User Distrust (UX): Seeing a generic API link instead of the app's official domain drastically lowers the Click-Through Rate (CTR), as it looks like a suspicious or unprofessional link.
Proposed Solution:
Enable native support for backend functions to be accessible via the app's associated custom domain. For example:
mydomain.com/api/functions/myFunction or mydomain.com/_functions/myFunction
This is an industry-standard feature (available on Netlify Functions, Vercel API Routes, Supabase Edge Functions, etc.) and is absolutely vital for any public web app that relies on organic traffic and social media virality.
If you are building a directory, a marketplace, a blog, or any app with public profiles on Base44, please upvote this request so the team can prioritize it. Thank you!
Please authenticate to join the conversation.
In Review
Feature Request
About 12 hours ago

Busca Bolos
Get notified by email when there are changes.
In Review
Feature Request
About 12 hours ago

Busca Bolos
Get notified by email when there are changes.