Launching a Virtual Brand: The Website Checklist for the First Week

A virtual brand can be live on the web in about a week, but only if the decisions that cannot be made by a web team are made first. The build is fast. The name, the concept sentence, the menu list, the platform storefronts and the photography are what set the pace, and every one of those belongs to the kitchen rather than to whoever is writing the pages. This checklist runs the launch as seven working days with a gate at the end of each one, so that a brand that is genuinely ready moves in a week and a brand that is not stalls visibly on the day it stalls, instead of drifting for a month while everyone assumes someone else is blocked.

Five decisions that have to land before anything gets built

Nothing on a brand page can be written until five questions have real answers, and a launch week that starts without them is a launch week that ends on day eleven. Get these settled before the build calendar starts, not during it.

The brand name, and whether it is actually free to use

Check the name against the delivery platforms first, then the domain, then the social handles, in that order. A virtual brand lives or dies inside a marketplace search box, so a name that already belongs to an active storefront in the same metro is a problem long before it is a trademark question. Search each platform the brand intends to sell on, check the obvious domain spellings, and check the handles on the one or two social channels the brand will actually use.

Write the result down as a short note next to the name: where it is clear, where it collides, and what the fallback spelling is. A name that survives that check can be built on. A name that does not should be replaced on day one rather than on day five, because every asset produced after the name is settled carries the name inside it.

The concept sentence

Write one sentence that a guest could repeat to someone else, and stop there. Not a paragraph, not a mission, one sentence that names the food and the angle. Smash burgers built for delivery, cooked to order and boxed to stay crisp. Birria and consomme from a family recipe, portioned for one. Late night wings with a sauce list that changes monthly.

That sentence is the single most reused piece of copy in the whole launch. It becomes the page headline, the meta description, the platform storefront blurb, the social bio and the first line of any ad. Writing it once, well, on day one saves rewriting five versions of the same idea that slowly drift apart.

Which platforms the brand sells on

List them explicitly, and list them per kitchen. A brand that will be on two marketplaces from one facility is a different build from a brand that will be on three marketplaces from two facilities with direct ordering on top. The page layout, the number of buttons and the way locations are presented all follow from this list, so an answer of “all of them, probably” is not an answer yet.

Include the direct ordering question here too. If the brand intends to take orders on its own site rather than only linking out, that decision affects the page set, the checkout path and what has to be tested before launch. Delivery platforms publish merchant tooling for exactly this in their own help centers, and running a checkout on your own site is a different wiring job from a plain outbound link.

Which kitchen actually produces it

Name the facility, the station and the shift. This sounds like an operations detail rather than a website detail, but it determines the service area on the page, which ordering links are valid, what hours the page should show and where a catering inquiry routes. A brand that is produced on the same line as three others during the same shift has a different capacity story than a brand with its own station, and the page should not promise a lead time the line cannot hold.

Who owns the brand inbox and phone

Decide where a contact form submission and a phone call land before the form exists. A new virtual brand inside a multi-brand facility usually generates three kinds of inbound messages: a guest with an order problem, a catering or large order inquiry, and a wholesale or partnership question. Those rarely belong to the same person. If the routing is not decided during the build, every message lands in one general inbox and the catering inquiries are the ones that get lost.

Operators running several concepts from one facility can see how this scales on the multi-brand operators page, where the brand count changes the page architecture more than it changes the build effort.

The assets the kitchen has to supply, and the realistic minimum

Three asset categories block a launch: photography, the logo, and menu copy. Everything else can be drafted by the build team and corrected later.

Photography, and what is genuinely enough

A handful of clean photographs of the dishes the brand actually wants to sell is enough for launch. Not a full shoot, not a stylist, not a studio. Shoot on the pass, against a neutral surface, in the best available light, with the dish plated the way it will actually leave the kitchen. Shoot the hero dish, the two or three items the brand expects to carry the ticket average, and one wider shot that shows the food as a guest would receive it.

What does not work is an empty page, a stock photograph of a dish the kitchen does not make, or a photograph of a dish plated for a dining room when the brand ships in a clamshell. A guest comparing a marketplace listing to a brand page notices the mismatch immediately, and the page loses the credibility the listing already had.

Schedule the full shoot as a post-launch revision. It is a better use of a shoot day to photograph a menu that has already survived two weeks of real orders than to photograph a menu that might change once tickets start landing.

The logo

A vector file is ideal, a large transparent raster file is workable, and a screenshot of a logo lifted from a delivery app is not. The logo appears at several sizes across a brand page, a favicon, an open graph card and the platform storefronts, and a low resolution file is visible at every one of them.

If a logo does not exist yet, launch with a clean wordmark set in the brand typeface rather than waiting. A wordmark that is legible at small sizes outperforms a rushed mark that has to be redrawn in month two.

Menu copy

Supply the final item list with prices and a short description per item, as text rather than as a photograph of a printed sheet or a design file. Prices and item names change more often than anything else on a brand page, and text that can be edited in place is the difference between a five minute correction and a rebuild.

Write descriptions the way the brand talks, not the way a facility talks about itself. An item description does two jobs: it tells a guest what arrives, and it answers the question that would otherwise become a support message. Name the protein, the heat level, the format and anything a guest would want to know before committing.

The page set a virtual brand needs at launch

A new virtual brand needs a small, complete page set rather than a full website, and adding pages later is easier than pruning a bloated launch.

At minimum:

1. A brand page carrying the name, the concept sentence, the identity and the primary ordering path.
2. A menu and ordering page listing every item with its description and price, plus the ordering links for every platform and kitchen combination that is live.
3. A service area statement, either its own page or a clearly marked block, that says which neighborhoods or postal codes the brand delivers to from which kitchen.
4. A contact path routed to the inbox decided on day one, with a separate route for catering or large orders if the brand takes them.
5. A short about block explaining that the brand is produced by the facility, for guests who arrive curious about who is behind it.

What is not needed at launch: a blog, a careers page, a gallery, a team page or a locations page for a single kitchen. Those are all reasonable additions later. None of them helps a guest order on day one, and each of them is a page that has to be written, reviewed and kept current.

The virtual restaurant brand website page covers what that page set looks like in practice when a brand is the second or fourth concept in a facility rather than the first.

The day by day sequence

Here is the week as a working schedule, with the gate that has to close before the next day starts.

Day	Work	Kitchen supplies	Gate before moving on
Day 1	Name check, concept sentence, platform and kitchen list, inbox routing	Decisions, not files	Name cleared, concept sentence signed off in writing
Day 2	Page set agreed, brand page drafted, menu copy imported	Final menu list with prices and descriptions	Menu list is final enough to publish
Day 3	Identity applied, photography placed, mobile layout built	Logo file, photographs from the pass	Page reads as the brand on a phone, not a template
Day 4	Ordering links wired per platform and per kitchen, service area written	Confirmed storefront links, delivery radius per kitchen	Every link opens the correct storefront from a fresh session
Day 5	Contact routing, analytics, Search Console, sitemap and schema	Destination inbox and phone line	A test submission arrives at the right person
Day 6	Copy review, speed pass, dark and light check, accessibility check	Final read from whoever owns the brand voice	No placeholder text, no broken link, no unreviewed price
Day 7	Launch, profile updates, platform blurbs, link handover	Someone available to answer a first ticket	Page live, links tested again after launch, owner has the list

The gates matter more than the day numbers. A kitchen that supplies photographs on day six rather than day three has not lost the week, it has moved day three to day six and everything behind it.

Wiring ordering links per platform and per kitchen

An ordering link belongs to one brand, on one platform, produced by one kitchen, and that combination is the unit of work. A brand on two marketplaces from one facility has two links. The same brand added to a second facility has four.

The procedure:

1. Build the grid before building the page. Rows are brands, columns are kitchens, cells list the platforms live in that combination.
2. Collect the link for each live cell from that platform merchant tools, using the storefront for that specific kitchen rather than copying a link from a sibling location.
3. Confirm each storefront is actually open and accepting orders, not still in onboarding or paused from a previous week.
4. Place the links on the page grouped by kitchen when the brand runs in more than one facility, so a guest is never choosing between two identical buttons with no way to tell them apart.
5. Open every link in a fresh browser session, ideally on a phone, and confirm it lands on the brand storefront rather than a marketplace search result or a generic city page.
6. Note the date of the test next to the grid. Links go stale quietly when a platform reorganizes its storefront URLs, and a dated grid tells you when to re-test.

Direct ordering, where it is used, is wired the same way but tested further: place a real order through the flow, confirm the ticket prints or appears on the station display, and confirm the confirmation email reaches the guest and the kitchen. A link that opens is not the same as an order that lands.

Analytics and Search Console, set up before launch

Set up measurement on day five, before traffic arrives, because the first week of a brand is the only clean baseline it will ever have. Retrofitting analytics in week three means the launch itself is unmeasured.

Three things get configured:

1. An analytics property for the site, with the brand page and ordering clicks visible as distinct events rather than lost inside a site wide pageview count. Google documents the setup path for a web property in its Analytics Help center, and the important part for a kitchen is that outbound ordering clicks are tracked as events, since those clicks are the conversion for a brand that sells through marketplaces.
2. Search Console verified for the property, with the sitemap submitted, so that indexing problems surface as messages rather than as a brand that quietly never appears in search.
3. A speed baseline. The Web Vitals metrics documented on web.dev describe loading, interaction responsiveness and visual stability, and a brand page that is heavy with unoptimized photography fails the loading metric first. Check it on a phone on a normal connection, because that is the device a guest is holding.

None of this takes a full day. All of it takes considerably more than a day to reconstruct later.

Domains, redirects and the brand that gets renamed

A virtual brand should launch as a page on the facility site unless it already has an audience of its own, because a page on an established site inherits speed, links and analytics that a fresh domain has to earn from nothing.

That decision becomes important later, because virtual brands get renamed more often than restaurants do. A concept that tests well under one name and is repositioned under another is a normal outcome, not a failure. What matters is that the change is handled as a move rather than a delete.

When a brand moves to its own domain

Treat it as a documented migration. Google Search Central covers site moves with URL changes and describes permanent redirects as the mechanism that carries signals from the old location to the new one. In practice that means every old page redirects to its specific counterpart rather than all of them collapsing onto a home page, the internal links across the facility site are updated to point at the new location directly, and the platform storefronts, profiles and social bios are updated to the new address in the same week rather than over the following months.

When a brand is renamed in place

The page usually keeps its structure and changes its name, its wording and its identity. The old address should redirect to the new one permanently rather than being left to return a not found error, and any link the kitchen has already printed, posted or handed to a platform should be re-checked. The riskiest links are the ones outside the website: a storefront blurb, a business profile, a printed insert in a delivery bag.

When a brand is retired

Redirect the page to the facility page or to the nearest surviving brand, and remove the ordering links immediately. A retired brand page that still shows working ordering buttons produces tickets for a concept the line no longer runs, which is worse than a page that is simply gone.

Launch day checks

Launch day is a list, not an announcement. Work through it on a phone, because that is where most of the traffic will arrive.

1. Every ordering link opens the correct storefront, tested again after the page went live and not only before.
2. The contact form submits and the message reaches the person who owns the brand inbox, confirmed by that person rather than assumed.
3. The phone number, if one is shown, is tappable and rings the right line.
4. Prices on the page match prices on every platform storefront, item for item.
5. The page renders correctly in both light and dark, with no unreadable text over a photograph.
6. Photographs are compressed and sized for a phone rather than uploaded at camera resolution.
7. The service area on the page matches the radius the kitchen actually delivers to on each platform. If the facility is a delivery only operation, the Google Business Profile guidance on service-area businesses is the reference for whether the street address should be shown at all.
8. Nothing on the page is placeholder text, a draft price, or a description nobody has read aloud.
9. The sitemap includes the new page and Search Console has it submitted.
10. Somebody in the building knows the brand went live today and is watching for the first ticket.

What the first two weeks should actually change

The first two weeks change wording, photography and link order, and they should not change the page structure. Two weeks of traffic is enough to see friction and not enough to judge architecture.

Rewrite the descriptions that generate questions

Every question that arrives through the contact form or a platform message is a sentence the menu did not write clearly enough. Collect them for two weeks, then fix the descriptions. Heat level, portion size, what a combo actually includes and whether an item travels well are the four that come up most often in delivery only formats.

Replace the weakest photographs first

By week two it is obvious which items are selling and which photograph is underselling its dish. Reshoot those, not the whole menu. This is also the point at which a proper shoot is worth scheduling, because the menu has now been tested against real orders rather than against a planning spreadsheet.

Reorder the ordering links

If the analytics event setup from day five is in place, the ordering clicks show which path guests prefer. Move that link to the top of the stack, and consider whether a platform that gets almost no clicks deserves the visual weight it currently has on the page. This is a layout adjustment, not a redesign.

Leave the structure alone

Resist adding pages, sections and modules in week two. A brand that is two weeks old does not need a blog, a press page or a rewritten navigation. It needs accurate wording and working links. Structural questions are worth revisiting once there is a quarter of data behind them, and how often that kind of change is practical depends on the revision capacity on the plan the facility runs on.

Operators who want the launch sequence run against their own brand list rather than a generic template can start from the onboarding page, which collects the day one decisions and the asset list in the order this checklist uses them.

What a website launch does not cover

This checklist covers getting a brand live on the web and nothing beyond that. It does not cover whether a new concept may legally be produced in a given facility, what a menu must disclose about allergens or nutrition, how a second or third brand affects permitting, or any question that belongs to a health inspector or a licensed professional. Where a step here touches that territory, such as writing a menu description or adding an allergen note, treat the text as a draft to confirm with the relevant authority before it goes live.

A launch week works because it front loads the decisions the kitchen owns and leaves the mechanical work to the days where it belongs. The brands that go live in seven days are not the ones with the fastest build. They are the ones where somebody settled the name, wrote the concept sentence, finalized the menu and took a few minutes on the pass to photograph the food before anyone asked for a page.