> 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.md). # Oddle Site Oddle Site is your restaurant's full website — the front door diners hit when they search for you, click a link from social, or arrive from Google Maps. Built specifically for restaurants, it's set up to be found, designed to convert visitors into known guests, and edited just by telling Oddle what to change. This isn't a website-building tool. It's the front door of your funnel — the first thing diners see, the first thing they search for, and the surface every other Oddle product plugs into. *** ## What Oddle Site does Oddle Site does three jobs: **Get Found.** Pre-tuned for Google from day one. Restaurant-specific SEO, structured menu data, and Google Places location all built in — so your menu, hours, and bookings show up where guests search. You outrank the aggregators (Tripadvisor, OpenRice, Wikipedia) that have been leaking your brand equity. The site is also built to serve the languages your guests search in. **Convert.** Turn visitors into known guests. Bookings, orders, and signups are built into the site — and every guest you win is saved across Oddle, tied to a profile in Reserve, Shop, Check-in, and Marketing. No broken third-party integrations, no lost data. **Always Current.** Update just by asking. Swap a photo, change tonight's menu, push a promo — tell Oddle through a chat-based editor and it happens. Changes land as a draft you review, then publish when you're ready. No agency, no tickets, no WordPress, no going stale six months after launch. *** ## Two stories Oddle Site solves **New restaurants.** Go live fast and properly. Most new restaurants either ship without a site or stand up a half-finished one that rots over time. Oddle Site gives you a complete, well-structured website on day one — built to be found, set up to convert. **Established brands.** Protect decades of reputation. If your restaurant has 30+ years of history but a 5-year-old website, you're leaking customers to aggregators that show up above you in search. Oddle Site reclaims the front door and keeps it current as your menu and offers change. *** ## How Oddle Site connects to the rest of Oddle Oddle Site is the top of your funnel. Everything else plugs into it: | Connection | What happens | | ------------------------- | --------------------------------------------------------------------------------------- | | **Oddle Reserve** | Bookings on your site land in your Host App | | **Oddle Shop** | Orders flow to your webstore; your live menu data is shared with the site | | **Oddle Check-in** | Signups build your guest database from visitors who aren't ready to book | | **Marketing** | Captured guests become a marketing audience for follow-ups, automations, and broadcasts | | **Customer Intelligence** | Every guest you win on the site is saved to one profile, across every Oddle product | The result: every visitor is potentially a known guest, every guest plugs into the marketing loop, and the front door no longer leaks demand to platforms you don't control. *** ## One platform, not five subscriptions Oddle Site replaces the patchwork most restaurants stitch together — a website builder, an ordering platform, a reservations tool, an email tool, and an agency to keep it all current: | What you'd normally pay for | Oddle Site | | ------------------------------------------ | ------------------------------------ | | Squarespace / Wix (website) | Built in | | GrabFood / a delivery platform (ordering) | Oddle Shop, connected | | SevenRooms / a booking tool (reservations) | Oddle Reserve, connected | | Mailchimp (email marketing) | Oddle Marketing, connected | | An agency (keeping it current) | AI chat editor — you ask, it updates | And because it's one platform, every guest who books, orders, or signs up is saved to a single profile — not scattered across five tools that don't talk to each other. *** ## Where to Manage What | What | Where | | ------------------------ | ------------------------------------------------------------------------------- | | Your live Oddle Site | Merchant Admin > **Site** (opens an embedded view of `sites.oddle.me`) | | Site content edits | Through the AI agent inside the Site view — describe what to change, it happens | | Getting your site set up | Talk to your account manager | *** ## In This Section * [**What Your Customers See**](/docs/new-guests/site/what-your-customers-see.md) — The visitor experience: pages, search ranking, conversion paths * [**Setting Up Your Site**](/docs/new-guests/site/setting-up-your-site.md) — How your site gets built, the AI-edit model, and where it lives in Merchant Admin *** ## What Oddle Site is not * Not a freeform site builder, CMS, or blog platform — restaurants that want WordPress or Squarespace are wrong-fit * Not the same as **Virtual Lounge** — Virtual Lounge is a single branded landing page (link-in-bio style); Oddle Site is the full restaurant website * Not "just a website" — the job is being found and converting demand into known guests, not winning design awards --- # 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.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.