why most ottawa restaurant sites lose to their google business profile

Search for "brunch near me" in Ottawa and look at what comes first. A map, then three business listings, then the websites. That block of three is the local pack, and for a restaurant it is where most of the decisions happen. Photos, star rating, hours, a call button and directions are all there before anyone clicks a website.

This changes what your website is for. It will rarely outrank your own Google Business Profile, and it does not need to. Its job is to back that profile up. Google wants to confirm that the business exists, where it is, what it serves and whether it is open. Your site is the strongest place to confirm all of that.

So the useful question is not "how do we get the website to number one?" It is "does the website agree with, and add to, what the profile says?" Most local restaurant sites we see fail on the second half. They have a nice hero photo and nothing else a search engine or a hungry person can use.

If you do only one thing this month, claim and complete your profile: correct categories, real hours, holiday hours kept current, a menu link, and photos taken in the last year. Everything else in this article assumes that is done.

menu pages google can actually read

The most common restaurant site problem is a menu that exists only as a PDF or as a photo of a printed menu. People can read it. Google can only partly read it, and phones handle it badly: pinch, zoom, scroll sideways, give up.

A menu that ranks and converts has three parts:

Plain text on a normal web page. Dish names, descriptions and prices as real text. Not an image, not text baked into a graphic.
Clear structure. Sections like starters, mains and drinks, each with its own heading, so the page has an outline.
Structured data. schema.org has Menu, MenuSection and MenuItem types, and a Restaurant type can point to its menu with hasMenu. This is JSON-LD in the page that describes the same content in a machine-readable form.

A few cautions. Structured data does not guarantee any special display in search; it removes ambiguity. It must match what is visible on the page, so don't mark up items that aren't there. And if your menu changes weekly, the markup needs to change with it, which is a good reason to generate it from the same data as the page rather than maintaining two copies.

Keep the PDF if staff print from it, but link to it from the menu page, not instead of it. Give the menu its own short URL such as /menu, so your Business Profile has a clean place to point.

tip: open your menu on your own phone, on mobile data, standing outside. If you can't read it in ten seconds, neither can a customer deciding where to go.

speed and mobile rendering for a restaurant site

Restaurant sites are image-heavy by nature, and that is where the trouble starts. A gallery of twenty full-resolution photos from a camera or phone can be tens of megabytes. On a phone with a weak signal in a parking lot, that is a blank screen.

Google measures real-user loading and interaction under Core Web Vitals, and speed is a ranking input, though a modest one next to relevance and proximity. The larger effect is simpler: people leave slow pages. A visitor who bounces to the next result is a lost table.

The fixes are mostly unglamorous:

Resize before upload. A photo shown at 800 pixels wide does not need to be 4,000 pixels wide.
Use modern formats. WebP or AVIF are much smaller than JPEG at similar quality. Most current frameworks, including Next.js, convert and size images automatically.
Lazy-load below the fold. The gallery should not load before the opening hours do.
Set image dimensions. This stops the page jumping around as photos arrive, which is what the layout shift metric measures.
Limit what you embed. Every third-party widget, such as a reservation plugin, chat bubble or social feed, adds weight. Keep the ones that earn their place.
Pick hosting that serves from a CDN. A page served from a nearby edge location is faster than one built from a database on every request.

You can check all of this for free with PageSpeed Insights and the Core Web Vitals report in Search Console. Test the menu page and the home page on mobile first. That is where your customers are.

getting listed once and consistently, not five times differently

Search engines build confidence by cross-checking. Your name, address and phone number, called NAP, appear on your website, your Google Business Profile, Apple Maps, Yelp, delivery apps, reservation tools and local directories. When they agree, you look like one real business. When they don't, you look like several uncertain ones.

Typical drift looks like this: "Bistro 22" on the website, "Bistro Twenty-Two" on Google, "Bistro 22 Restaurant" on a delivery app. Or a suite number on one listing and not another. Or an old phone number that still rings the previous owner's landline.

The fix is dull and worth doing once:

Pick one exact format for name, address and phone. Write it down.
Put it in the footer of every page on your site, as text, not in an image.
Audit your listings against it and correct each one. Start with Google, Apple, Bing and Yelp, then delivery and booking platforms.
Use the same name as your signage. Don't add keywords to your business name on Google; it breaks the guidelines and can get your profile suspended.

When you move, change hours seasonally or swap a phone number, treat it as a checklist item across every listing, not an edit in one place.

turning one storefront link into your seo hub

Restaurants tend to accumulate pages that compete with each other. One for online ordering, one for a loyalty card, one for reservations, one for catering, plus a delivery platform page and an old page from a previous system. Each has its own URL, its own half-written description, and its own set of links pointing to it from somewhere.

That splits attention in two ways. Search engines see several thin pages about the same business instead of one strong one. And customers hit different front doors depending on where they came from.

A cleaner pattern is one hub. Choose one canonical address for the restaurant, usually the home page, and make it the place everything hangs from: order, book, join the loyalty list, see the menu. The links from your Business Profile, Instagram bio and printed materials all point to that one hub. Old or duplicate pages either redirect to it or are removed.

A few practical rules:

One URL per purpose. If two pages answer the same question, merge them and 301-redirect the old one.
Link to your third-party ordering or booking tool from the hub, rather than letting that tool's page stand in as your public face.
Keep the Business Profile "website", "order" and "reservation" links pointing to specific, working pages on your domain.

None of this needs new software. It needs someone to decide which page is the hub and tidy up around it.

reviews: asking for them without gaming them

Reviews affect both ranking and conversion. They are also the area where well-meaning restaurants break the rules most often.

What Google's policies prohibit is straightforward: paying or rewarding people for reviews, writing your own, and filtering who you ask so that only likely-happy customers are invited. What is fine is asking every customer, honestly, at a moment when they have something to say.

Timing matters more than wording. Some points where the ask fits naturally:

After a completed online order. The confirmation or pickup message can include a short line and the link to your review page.
After a booking is fulfilled. A message the next morning, not during the meal.
At the till. A small card with a QR code that opens your Google review page directly.

Use the direct review link from your Business Profile dashboard so people don't have to search for you. Keep the ask short: one sentence, one link. Don't script what they should say.

Then reply to reviews, including the unkind ones. A calm, specific reply to a bad review reads well to the next person deciding, and it shows the profile is actively managed. Don't argue, and don't put private details of a visit in public.

a 90-day checklist for an ottawa restaurant owner

Sequenced by effort against impact. Do them in this order.

Days 1–14: foundations (low effort, high impact)

Claim and complete your Google Business Profile: categories, hours, holiday hours, photos, menu and website links.
Write down your exact NAP and fix it on Google, Apple Maps, Bing and Yelp.
Test your site on a phone. Note what is slow or hard to read.

Days 15–45: the site itself (medium effort, high impact)

Put the full menu on a /menu page as plain text with clear sections.
Compress and resize images; lazy-load the gallery.
Put NAP, hours and a map in the footer as text.
Add Restaurant and Menu structured data that matches the visible content.

Days 46–75: tidy-up (medium effort, medium impact)

List every page that does ordering, booking or loyalty. Merge duplicates, redirect old URLs, and pick your hub.
Correct NAP on delivery and booking platforms and any local directories.
Add a French menu page if a meaningful share of your customers use French.

Days 76–90: the ongoing habit (low effort, compounding)

Add the review ask to order and booking confirmations, using the direct review link.
Reply to every new review within a few days.
Check Search Console for crawl errors and Core Web Vitals once a month.

Expect the Business Profile and listing fixes to show first, and the website work to take longer. Be sceptical of anyone selling guaranteed rankings.

If you'd rather hand the site work to someone who will talk to you directly, our services page lists what we build, and how we scope and price projects explains how quotes are structured. You can also read about us first.

seo for ottawa restaurants: what actually ranks