Every feature of a KitchenWebStudio website for ghost kitchens, commissary kitchens, catering kitchens and multi-brand operators, and which of the three plans carries it.
Jump to a feature
Custom-coded pages served from the edge, 90+ PageSpeed on every tier.
A customer deciding between your brand and the next one in a delivery app is not going to wait for a slow page. Every page on your site is custom coded, ships almost no JavaScript, and is served from Cloudflare's global edge network, so it opens the same instant whether someone finds you through a Google search, a QR code on packaging, or a link from a delivery platform. There is no plugin stack to slow down over time and no theme update that quietly breaks the checkout link.
If you run Google Ads or boosted posts, you are paying for every click that lands on your page, and a page that loads slowly loses a share of them before anything renders. Google Ads assesses ad quality partly on landing page experience, which covers how relevant and useful the page is and how easily people can move around it, and a better landing page experience can lower what you pay for a click. We do not promise a number, and nobody honestly can. What we can say is the mechanism: faster, more relevant pages keep more of the clicks you already bought and give the auction less reason to charge you a premium. Source: Google Ads Help, About ad quality, read 21 September 2026.
A ghost kitchen or catering operation gets traffic in bursts, around meal periods, around an event date, around a marketing push. The site is built to hold up under that kind of spike without you doing anything, because it is not running a database query per visitor the way a page-builder site does. If a station is running behind and you need to update a cutoff time or pause online ordering for a brand, that page still loads instantly for everyone checking it.
A page for each virtual brand operating out of your facility, all under one domain.
Each virtual brand you run out of your kitchen gets its own page with its own name, its own menu, its own photos, and its own delivery links, while the whole set lives under one domain you control instead of scattered across marketplace listings. A visitor lands on the brand they searched for, not a generic facility homepage, and search engines can index each brand separately instead of treating your operation as one blurry entity.
Launching a new concept or shutting one down is common in this business, and the site is built so that is a revision, not a rebuild. A new brand page goes up with its own menu and delivery links inside your standard turnaround. A retired brand comes down cleanly, with its links redirected so nothing on a delivery platform points at a dead page. You are never locked into the brand lineup you had on day one.
DoorDash, Uber Eats, Grubhub and more, linked correctly under each brand.
Most ghost kitchen orders complete on a third-party platform, not on your own site, and the job of this page is to get the right customer to the right platform link for the right brand without confusion. Each brand section lists its live delivery platform links, so a customer who wants your food through DoorDash, Uber Eats or Grubhub gets there in one tap instead of searching the platform themselves and possibly landing on a competitor.
Delivery platform links change more often than most site content: a brand goes live on a new platform, an old listing gets deprecated, a promo link needs swapping in for a season. Any of that is a standard revision through your client portal, turned around in your plan's turnaround window. You send the new link and which brand it belongs to, and it is live without you touching a website builder.
A form built around event date, guest count and menu, not a generic contact box.
A catering inquiry needs an event date, a guest count, a menu direction and a delivery or pickup preference before anyone on your team can quote it, so that is what the form collects instead of a generic name-email-message box. The inquiry lands wherever you tell us to send it, whether that is an inbox, a shared calendar, or your CRM, formatted so your team can see at a glance whether the date and headcount are even feasible before picking up the phone.
If your catering page shows a starting range or a per-person estimate to help a prospect self-qualify, it is clearly labeled as an illustrative starting point, not a binding quote, and the form itself makes clear that final pricing comes from your team after the details are confirmed. We never build a page that commits you to a number before you have reviewed the order, and we never advise on what to charge, that is entirely your call.
A page built to fill open stations, with tour requests routed to you.
A prospective tenant looking for kitchen space wants to know what is available, what it costs to find out more, and how to see the facility before committing. This page presents your available stations, storage and equipment in plain operational language, states your general terms without locking you into a rigid rate table that goes stale, and puts a tour-request path front and center so a serious lead reaches you rather than bouncing to the next listing they find.
Station availability shifts as tenants sign and leave, so this page is built to be updated as a revision: mark a station as taken, add a new one when you expand, adjust the equipment list, all inside your plan's standard turnaround. On tier two and three, an inquiry about touring the space can be picked up automatically by the AI Engine and routed to your calendar, so a lead that comes in overnight is not sitting untouched until morning.
Clear pages for your facility address, service radius and pickup details.
A location page states where your facility operates from, what delivery radius or service area each brand covers, and whether pickup is available, so a customer or a search engine does not have to guess. This matters for both people and platforms: search engines use this page to understand where you actually serve, and customers use it to check before they place an order that will only get canceled for being out of range.
If you operate from more than one facility, or expand a delivery radius as you add drivers or platforms, each location gets its own page rather than one page trying to describe several addresses at once. Updating a delivery radius, adding a new facility, or narrowing a service area during a slow season is a standard revision, turned around within your plan's window.
Hosting, SSL, backups and uptime handled, with nothing billed separately.
Hosting, SSL, backups and day-to-day security monitoring are handled as part of your plan, included in the one monthly fee with nothing billed separately later. The site runs on Cloudflare's global network, which means DDoS protection and unmetered bandwidth are built in rather than sold as an upgrade. You are not the one renewing a certificate, patching a plugin, or fielding a hosting company's upsell email between shifts.
If anything about the site needs a look, you raise it in your client portal and it is handled by the team that built the site, not a ticket queue at a hosting company that has never seen your brand. You never need your own login to a server or a website admin panel. That separation is deliberate: you run the kitchen, we keep the site up.
Request changes, track them and message the team, all in one place after launch.
The client portal is your account with us, and you get access the day your site goes live. Every request after that runs through it: a new brand page, an updated menu, a changed delivery link, a swapped photo. You describe the change, attach whatever we need, and it becomes a tracked request instead of a message that gets buried in an inbox during a busy shift. Revisions included in your plan are turned around within your plan's standard window, and you can see exactly where each one stands.
Every plan includes a set number of revisions each month, and there is no limit on the size of a single revision, so a request covering several changes at once still counts as one. Once you go past the included amount for the month, each additional revision is billed at a flat rate rather than by the hour, so there is never a guessing game about what a change will cost before you ask for it.
Automated inquiry intake, messaging and tour booking, handed to a person for anything sensitive.
On The Pass and Head Chef, the AI Engine picks up incoming inquiries the moment they arrive, whether that is a catering request, a commissary tour inquiry, or a general question about a brand, and responds immediately instead of leaving a lead waiting until someone checks email. It can answer questions about your menus, delivery areas and availability, hold a conversation with a prospect, and book a tour of your facility directly onto your calendar, all while you are running the line.
The AI Engine never gives food safety, allergen or nutrition advice, and it never makes a licensing or compliance claim on your behalf. The moment a conversation touches any of that, it hands the customer to a person on your team rather than guessing at an answer. We build and manage the website and its automation, we are not a food safety consultant or a licensing authority, and the AI Engine is built to respect that line every time, not just when it is convenient.
Researched articles published every week, written for your kitchen operation.
On Head Chef, researched articles are written and published to your site every week, each one running 2,500 to 3,200 words and grounded in real research rather than filler generated to hit a word count. Topics are pulled from what people running or ordering from kitchens like yours actually search for: how a virtual brand model works, what a commissary tenant should know before signing, how catering minimums typically get structured. Nothing gets invented to sound impressive; a claim either has a real source or it does not appear.
Most kitchen operators do not have a spare hour between prep and service to write search-optimized articles, and content that never gets published cannot bring in search traffic. The Content Engine removes that bottleneck entirely: articles are researched, written, checked and published on a standing weekly cadence without you drafting anything, so your site keeps growing its footprint in search results while you stay focused on the kitchen.
Calls, site chat and text messages answered the moment they arrive, with appointments booked straight onto your calendar.
On The Pass and Head Chef the AI receptionist and the chat and messaging agents answer for your business the moment someone reaches out, on the channels a kitchen actually gets contacted on: the chat widget on your own site, text messages, and the inquiry forms feeding it. They answer questions about your brands, menus, delivery areas and availability, take the details of an inquiry, and book an appointment or a facility tour directly onto your calendar. Nothing waits for someone to finish a service and check a phone.
Business text messaging in the United States requires carrier registration, A2P 10DLC, and we file that for you rather than leaving you to work out a carrier portal between shifts. Carrier fees are passed through at what the carriers charge us, and AI usage is billed monthly in arrears at our providers’ cost, which is why The Pass is priced as a monthly fee plus usage. You review every script before launch, so the wording that represents your kitchen is wording you approved.
The agents are configured never to give professional advice on your behalf. For a kitchen that means no food safety guidance, no allergen or nutrition answers, and no claim about licensing or inspection status. The moment a conversation moves in that direction the agent hands the person to someone on your team. You stay responsible for consent, opt-out and record-keeping on your own messaging, and we build the forms and footers that make that straightforward. The full position is in the terms.
Every form and inquiry lands where your team already works, by direct API, Zapier or Make.
At onboarding you tell us where inquiries should land, whether that is a CRM, a shared inbox or both, and who should be notified when one arrives. We connect it by direct API, Zapier or Make, and every form on the site, catering quote requests, commissary tour requests, general contact, lands there with its fields intact rather than as a block of text somebody has to retype. A lead that arrives at 11pm is already in the system your team opens in the morning.
Kitchen inquiries cluster around the worst possible times: the lunch rush, the middle of an event build, the hour before service. If the only place they land is a phone in somebody’s apron pocket, the ones that arrive during a rush are the ones that get lost, and those are usually the biggest jobs. Routing them automatically means the record exists whether or not anyone had a free hand, and on The Pass and Head Chef the AI Engine starts the reply while the lead is still reading your page.
Technical and on-page SEO, service-area pages for your own cities, answer-first content and structured data.
Search work starts with the build itself, because most of what holds a kitchen site back is structural: slow pages, no page per brand, no page stating where you deliver, and markup a search engine cannot read. At onboarding you list the towns, cities or counties you serve and we build a page for each one, so searches in the areas you actually cover have something of yours to find instead of a platform listing you do not control. Every service you offer gets its own page for the same reason. Titles, descriptions, headings, internal links and clean URLs are set as each page is written, not bolted on afterwards.
Answer engine optimisation is about the shape of the content. Every section on your site opens with a direct answer to the heading above it, questions are phrased the way a person would actually ask them, and each significant page carries its own FAQ block, visible on the page and marked up so it can be lifted into a featured snippet or read aloud by a voice assistant. Comparison tables and short definition blocks are written to be extractable whole. None of that requires you to write anything.
Assistants like ChatGPT, Claude, Perplexity and Google’s AI Overviews summarise from pages that state facts plainly and are easy to parse. Your site ships an llms.txt and a full-content file describing what your operation is and where it works, uses the same entity names everywhere, keeps facts specific and dated, and stays crawlable without JavaScript. No one can guarantee an appearance in an AI answer, and we will not pretend otherwise. What we do is remove every reason for an assistant to skip you.
Structured data is a block of machine-readable facts attached to each page: what kind of business you are, where you operate, what you sell, what the questions and answers on the page are, and how the page sits in the site. Your site carries Organization or LocalBusiness markup, Service markup on service pages, FAQPage on pages with questions, and BreadcrumbList throughout, all generated from the same data the page displays so the two can never drift apart. Review markup is only ever added from reviews that are genuinely yours.
Privacy, terms, cookie policy with consent that really gates scripts, and an accessibility statement, written into the build.
Every site we build carries the same policy set this one does: a privacy policy covering what the forms collect and where it goes, terms, a cookie policy that lists the cookies the site actually sets, and an accessibility statement naming the standard the build was made against and how to report a problem. They are written for your operation rather than pasted from a generator, they read like part of the site, and they carry a last-updated date. This helps you meet the obligations that come with running a public website; it is not legal advice, and a lawyer should review anything specific to your business.
The cookie banner on your site is wired to the scripts, not decorative. Analytics and marketing tags do not fire before consent is given, and the choice is remembered. That is the difference between a banner that satisfies a checkbox and one that does what it claims, and it matters because the second kind is what privacy rules in several states are written around.
Forms carry real labels, every control can be reached and operated from a keyboard, focus is always visible, contrast is checked in both light and dark, tap targets are large enough for a thumb, and motion respects a reduced-motion preference. For a kitchen site the practical version of that is simple: a catering quote form that a screen reader user can complete, and an order button a tired person can hit first time on a phone. We build with WCAG in mind and state the target in your accessibility page; we do not certify conformance for you.
We build and run the website. We are not a food safety consultant, a health inspector or a licensing authority, and nothing on a site we build, including the AI agents, gives food safety, allergen, nutrition or licensing advice. Where a page states something about your certifications, permits or insurance, it states what you told us, and it stays your responsibility to keep that accurate.
Your existing content brought across, old URLs redirected, a domain included and registered in your name.
Send us what exists today, a page-builder site, a set of menu PDFs, photos, a marketplace-only profile, and we rebuild what is worth keeping into the new structure rather than starting from a blank page. Old URLs that are moving get redirected to their closest equivalent, so a link on a delivery platform, in a social bio or in someone’s bookmarks still lands somewhere useful instead of a dead page. Anything outdated, a discontinued item or an old price, gets flagged back to you rather than carried across quietly.
One domain is included free for as long as your plan is active, registered in your name through Cloudflare Registrar or Spaceship, so you own it outright. If you already have a domain we point it at the new site instead and nothing changes for people who know your current address. If you ever leave, tell us where to send it and we transfer it at no charge. Content you supply stays yours throughout, and on cancellation we export your content and articles within 14 days.
Kitchen teams naming the part of the build that made the difference for them.
Order noteNo. 201
“Converting our commissary kitchen tours attachment into proper pages was overdue. The content is the same material, reorganized into headed sections that work on any screen. Nothing was taken away from the people who like paper.”
Huda Shalhoub, Intake coordinator
Farm shop production kitchen hire, Manchester, NH
Structured reference pages for commissary kitchen tours
Order noteNo. 202
“The audit found our commissary kitchen tours details repeated across several pages, each worded slightly differently. The facts have one home, and every change request names the reference page and its reviewer. It is the least glamorous work they did, and possibly the most valuable.”
Isaac Butterfield, Operations manager
Hot food production commissary, Fargo, ND
Content audit and update process for commissary kitchen tours
Order noteNo. 203
“The guided contact options looked like a small feature; they changed the inbox. New business and existing conversations now arrive under different subjects. Returning customers no longer repeat the whole form to ask one question.”
Beatrice Dalrymple, Customer care coordinator
Recipe development kitchen rental, Baton Rouge, LA
Inquiry categories and guided navigation for commissary kitchen tours
| Feature | The Line | The Pass | Head Chef |
|---|---|---|---|
| Pages that open instantly | |||
| One site, every brand you run | |||
| Delivery platform links, organized by brand | |||
| Catering inquiry and quote-request forms | |||
| Commissary and shared-kitchen listing page | |||
| Location and delivery-area pages | |||
| Managed hosting and security | |||
| Client portal and revisions | |||
| The AI Engine | |||
| The Content Engine | |||
| AI receptionist, chat and text agents | |||
| Inquiries routed into your CRM | |||
| Search, answer engines and AI citations | |||
| Policy pages and an accessible build | |||
| Migration, domain and a launch that keeps your links alive |
Choose a plan, pay the first invoice.
Form plus one call, about 15 minutes total.
Live in 7 to 15 days.
Updates, revisions and articles keep moving.
A revision is any change request you send, and there is no limit on how much goes into one. A new brand page, an updated menu, a changed delivery link, a different photo: each is one revision. So is something much larger. "Build pages for our two new virtual brands, here is the menu copy and photos for both" is one revision, not four. 5 are included every month. After the fifth, each additional revision is a flat $20, with no cap on how many you can buy and no hourly billing anywhere. Every revision is completed within 2 to 5 working days of you sending it, whatever the size.
Raise it in your client portal. You describe the change, attach anything we need like an updated menu or a new delivery link, and it lands with the team as a tracked request so you can see where it stands. You can also email us or reply to any thread with our team, and we log it for you. Unused revisions do not roll over to the next month.
No, and that is deliberate: every delivery link change goes through the portal so we can confirm it points at the right brand and the right platform before it goes live, rather than risking a broken link during service. Because it is a standard revision, it is still turned around inside your plan's normal window, not treated as a special request.
2 researched articles a week on The Line and The Pass, and 3 a week on Head Chef, each one 2,500 to 3,200 words. They are written for people actually searching around your kind of operation, virtual brand models, commissary tenancy, catering logistics, not filler generated to hit a word count.
No, they publish on the standing weekly schedule without you drafting or approving each one first, since most kitchen operators do not have spare time between prep and service for a review cycle. If an article needs a change after it is live, whether that is a correction or a different angle, that is a standard revision through your portal.
No. Articles are researched and written around topics like operations, delivery logistics and the business side of running a kitchen, never food safety, allergen or licensing guidance. We are not a food safety consultant or a licensing authority, and every claim in an article either has a real cited source or does not appear at all.
On The Pass and Head Chef, the AI Engine picks up incoming inquiries the moment they arrive, whether that is a catering request, a commissary tour request, or a general question about one of your brands, and responds immediately. It can answer questions about menus, delivery areas and availability, hold a conversation with a prospect, and book a facility tour directly onto your calendar, all without someone on your team stopping mid-shift to reply.
No. It never gives food safety, allergen or nutrition advice under any circumstance. The moment a conversation touches any of that, it hands the customer to a person on your team rather than guessing at an answer. We build and manage the website and its automation; we are not a food safety consultant, and the AI Engine is built to respect that boundary every time.
Yes. It is trained on every brand, menu and facility detail you provide at onboarding, so it can answer a question about any of your virtual brands or units without you configuring a separate assistant for each one. When you add a new brand, its menu and details are added to what the AI Engine already knows as part of that revision.
On The Pass and Head Chef it answers the chat widget on your own site, inbound inquiries from your forms, and text messages. Business text messaging in the United States needs carrier registration, A2P 10DLC, which we file for you, with carrier fees passed through at cost. You review every script before launch, and AI usage is billed monthly in arrears at what our providers charge us, which is why The Pass is priced as a monthly fee plus usage.
Ten comparison pages set this feature list against the builders, the platforms and the people you could hire instead, including the situations where they are the better answer.
Everything on the pass
Book a demoSearch this site
Type to search every page and article. Press Enter for the full results page.
Appearance
Colour scheme
Accent
5 accents, all drawn from the same kitchen. Saved on this device only.
KitchenWebStudio uses the cookies below. Necessary cookies keep the site working and cannot be turned off.
Saved on this device only. Press Esc to close.