Module 2 · Lesson 5b of 16 · ~30 minRebuild track

Before you replace it. Name what's broken.

Open your current restaurant site in another tab. Walk through ten common audit items, rank them by how much they're hurting you, and write notes on the top three. You leave this lesson with a punch list — not a vague unease — and a clear sense of what to prioritize in the rebuild.

2 of 4 lessons in Module 2

A vague feeling that "my site is bad" is the worst possible briefing for a rebuild. By the end of this lesson, you trade the feeling for a sorted list of specific problems, ordered by what they're costing you.

What you'll be able to do by the end
  • Walk through 10 common audit items against your current restaurant site.
  • Rank the 10 items by severity for YOUR site (top 3 become rebuild priorities).
  • Write one-sentence notes on the top 3 issues that justify the ranking.
Plain language version — the fast read

Open your current site in another tab. Look at it like a stranger would. Rank ten common problems from worst to least bad. The top three are what to fix in the rebuild. Write a short note about each top problem.

Open your current site in another browser tab. Pull it up on your phone too. Look at it the way a stranger would — as someone who has never been to your restaurant, who has thirty seconds to decide whether to walk in tonight. That's the audit perspective. Don't grade the site against your taste; grade it against that stranger's needs.

The ten leaks

Below are the ten most common things that hurt restaurant websites. Walk through each one against your real site. Use the up/down buttons to rank them in order of severity — the worst at the top.

The top three turn red as you rank them, because the top three are where you'll spend your rebuild time. The bottom four can wait. The middle three are the ones you'll write notes about after — issues you know about but haven't decided how to handle yet.

The colors reflect your ranking, not ours. Red means "you said this hurts most" — not "the bootcamp grades this as bad."

Your top three are now red. Those are what the rest of the bootcamp will help you fix first. The middle and bottom items still matter, but if you only had time to address three things this month, those are the ones.

Notes on your top three

For each of the top three you just ranked, take two minutes to write what specifically is wrong — not just "the menu is buried" but "the menu is a 2019 PDF and prices have changed twice since," or "the hours show 5pm but I actually open at 4 on Fridays." Specificity now saves you from re-discovering the same problem in Module 3.

One free tool to ground-truth the audit

You just graded your site by eye. That's the right place to start — the human's read is what diners actually do. But there are a few free tools that will catch things eyes miss, especially around performance and how Google sees your page.

  • Muntin Restaurant AuditFree, no signup. Scores your site on the ten leaks above plus a few more, in plain language.Open the audit →
  • PageSpeed InsightsGoogle's free performance test. Run your site URL through it; look at the mobile score.PageSpeed →
  • Muntin SEO GraderChecks how a restaurant site shows up in local search, including Google Business Profile parity.Open SEO Grader →

If any of these surfaces something your audit missed, add it to your notes above. Then close those tabs and stop looking. You have enough to design from.

What this changes downstream

From Lesson 7 forward, every lesson in this bootcamp is designed to fix one or more of the items in your ranking. Lesson 8 (menu) addresses "menu buried" and "outdated copy"; Lesson 9 (photos) addresses "photos bad"; Lesson 10 (hours) addresses "hours stale"; Lesson 12 (local SEO) addresses "address vague." The rebuild track doesn't waste your time on things you don't need to fix.

Your top three are also load-bearing for the L14 generator: when you download your finished site at the end of the bootcamp, those three will be the ones the generator made sure to handle differently than your old site did.

You traded vague unease for a punch list.

A ranked list of ten common restaurant-site failures, your top three turned red, and notes on what's specifically broken about each — saved in your browser. The rest of the bootcamp reads this and prioritizes the fixes you actually need.

The discipline of naming what's broken is the half of rebuilding most operators skip. You didn't.

Print the Lesson 5 tear-sheet →

L6b uses the audit ranking you just set as the starting point for a deeper diagnostic of the top issues. The rest of the bootcamp reads both lessons' outputs directly.