Answers to every question about installing, configuring, and operating Aedan Rose. For platform-wide incidents, see the System Status page.
<head> section.<head> section of your website's HTML, on every page where you want the widget to appear. The widget uses defer loading, so it never blocks page render. Full installation guide →data-restaurant-id (required) — your unique restaurant IDdata-position — bottom-right (default), bottom-left, top-right, or top-leftdata-primary-color — hex color for the launcher (overrides dashboard branding)data-api-url — alternate API endpoint (only for self-hosted enterprise deployments)header.phptheme.liquid before </head>Head on all pagesdefer, so it never blocks initial page render. For maximum performance, add <link rel="preconnect" href="https://aedanrose.ai"> to your <head> above the widget snippet — this starts the TLS handshake earlier.queued → processing → completed (usually 1–3 minutes per document).failed, the PDF was unreadable (usually image-only). Re-export as text PDF or run OCR first.widget.js loads with status 200.<head>, not <body>.data-restaurant-id matches what's shown in your dashboard Dev tab.completed on your documents.completed? Are the PDFs text-based (not scans)? Is your Restaurant Profile (Settings → Profile) fully filled out? See AI Training for the complete workflow.Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac). The widget script is cached aggressively. If you use a CDN like Cloudflare, also purge cache there. If your embed snippet has inline data-primary-color or data-position, those override the dashboard settings.
Check live platform health on our System Status page, browse the full Integration Guide, or reach out:
Email: help@aedanrose.ai
We typically respond within 24 hours on business days.