Cookbook

    Complete guide for submitting web apps to Urabin.

    When submitting a web app to Urabin, we verify domain ownership and auto-generate the web app card data using metadata from the submitted URL.

    Domain Verification (Required)

    To verify ownership of your domain, you must add a specific TXT record to your DNS settings.

    Type
    Name
    Value
    TXT
    @
    urabin-verify-abc
    • Why required: Ensures only domain owners can submit web apps
    • Where to add: Your domain registrar's DNS management panel
    • Propagation time: Usually 5-60 minutes, can take up to 24 hours
    • Verification: System automatically checks for this TXT record during validation
    • Troubleshooting: If verification fails, check your DNS settings and wait for propagation

    Favicon (Logo/Icon)

    Appears as the icon on the left of the web app title in the card.

    • Use .ico, .png, or .svg
    • Recommended size: 32×32 or 48×48 pixels
    • Linked in HTML head:
      <link rel="icon" href="/favicon.ico" />
    • Should be publicly accessible from the root or specified path

    OG Image (Thumbnail)

    Displays as the main image of the card (like a banner/thumbnail).

    • Tag format:
      <meta property="og:image" content="https://example.com/image.jpg" />
    • Recommended size: 1200×630px (aspect ratio ~1.91:1)
    • Use JPG or PNG (avoid WebP for broader compatibility)
    • Ensure image is publicly accessible and served over HTTPS

    Title & Description

    Pulled from your site's metadata and used in the card.

    • Set in:
      <title>Your App Name</title><meta name="description" content="Short description of your app." />
    • Title: Keep it under 60 characters
    • Description: 150–160 characters

    Submission & Validation Flow

    Here's what happens when you click Validate on the submit page:

    1. Domain Verification: System checks for the required TXT record in your DNS
    2. Duplicate Check: Ensures the web app isn't already listed
    3. User Limit Check: Verifies you haven't already submitted a web app
    4. Metadata Fetch: Retrieves title, description, favicon, and og:image
    5. Preview Generation: Creates a preview card with the extracted data

    Important Notes:

    • Domain must have the verification TXT record added
    • Site must be publicly accessible
    • Metadata should be present in the initial HTML (not rendered via JS after load)
    • If verification fails, you can re-verify after adding the TXT record

    Common DNS Providers

    Where to find DNS settings for popular providers:

    • Cloudflare: DNS → Records → Add Record
    • GoDaddy: My Products → DNS → Records → Add
    • Namecheap: Domain List → Manage → Advanced DNS → Add New Record
    • Google Domains: DNS → Custom records → Create new record
    • Vercel: Domains → [Your Domain] → DNS Records
    • Netlify: Domain Management → DNS → Add DNS record

    Quick Reference

    FieldTag/TypeRequiredRecommendedNotes
    Domain VerificationTXT RecordYes@ → urabin-verify-abcDNS propagation required
    Favicon<link rel="icon">Yes32×32pxPublicly accessible
    OG Image<meta property="og:image">No1200×630pxNo WebP
    Title<title>Yes≤ 60 charsShort & clear
    Description<meta name="description">No150–160 charsNo filler

    Troubleshooting

    Domain Verification Failed

    • Ensure TXT record is exactly: urabin-verify-abc
    • Check that the record is set for the root domain (@)
    • Wait for DNS propagation (can take up to 24 hours)
    • Use online DNS lookup tools to verify the record is visible

    Metadata Not Found

    • Ensure your site is publicly accessible
    • Check that metadata is in the initial HTML response
    • Verify URLs in meta tags are absolute (include https://)
    • Test with online meta tag checkers