> For the complete documentation index, see [llms.txt](https://www.oddle.me/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.oddle.me/docs/new-guests/site/setting-up-your-site.md). # Setting Up Your Site Getting your site live is a guided process — Oddle builds the first version with you, then you keep it current by describing the changes you want. *** ## How your site gets built Your account manager walks you through: 1. **Brief** — A short call to understand your restaurant's brand, story, signature dishes, and what diners are searching for when they look for you. Your Brand Knowledge Base in Oddle feeds this directly. 2. **Build** — Oddle's team puts together your initial site using your menu data, brand assets, and the brief. You get a preview link before anything goes live. 3. **Review and iterate** — You walk through the preview, flag what to change, and Oddle edits — fast. 4. **Launch** — Site goes live on your own custom domain (apex, `www`, or any subdomain), or on an `oddle.restaurant` address if your domain isn't ready yet. Oddle can even help you purchase a domain if you don't have one. You don't need a developer, an agency, or a designer. The brief is the briefing — everything else is handled. *** ## The AI-edit model After launch, you don't open a traditional CMS to update your site. You describe the change you want in a chat-based editor, and Oddle makes it: * "Add a Mother's Day brunch promo for May 12, photo from the menu library, 'Book Now' button to the brunch booking page." * "Swap the hero photo to the new chef portrait." * "Add a press-and-awards section to the About page." * "Update Wednesday hours — we're closed for kitchen maintenance May 14." Changes land as a **draft** first — you review them in a live preview, then **publish** when you're happy. Nothing goes live until you say so. The whole loop takes minutes, not the days an agency or WordPress cycle would. *** ## Where Oddle Site lives in Merchant Admin Once your site is provisioned, the **Site** tab appears in your Merchant Admin sidebar. Selecting it opens your site management surface embedded in the dashboard, so you can edit content (via the chat editor), manage your custom domain, and check your visitor analytics without leaving Oddle. A few things you manage from here: * **Content** — Pages and sections, edited through the chat-based AI editor with draft → publish. * **Custom domain** — Connect your own domain and follow the DNS instructions; status is polled live. * **Visitor analytics** — A traffic dashboard (visits, sessions, realtime) for your site, embedded right in the admin. If you don't see the Site tab, Oddle Site isn't switched on for your account yet. Your account manager can turn it on. *** ## Editing your site with an AI assistant Beyond the chat editor inside Merchant Admin, you can connect Oddle Site to an AI assistant like Claude and make changes from there — useful when you're already working with your assistant on menus or campaigns. See **Oddle AI** for setup. *** ## Related * [Virtual Lounge](/docs/returning-guests/virtual-lounge.md) — A single branded landing page for link-in-bio uses. Lighter than Oddle Site; doesn't replace a full website. * [Reserve with Google](/docs/new-guests/reserve/setting-up-reservations/reserve-with-google.md) — How Google's booking integration works. Oddle Site reinforces the same signals. * [Google Business Integration](/docs/returning-guests/google-business-integration.md) — Review attribution and review reply, complementary to Oddle Site's review surfaces. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.oddle.me/docs/new-guests/site/setting-up-your-site.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.