Phoenix Downtown Core SEO Strategy

Your search data already reads like a ticket rail

Search Console lists the words people typed before your catering pages showed up, so you can read it the way a kitchen reads the morning's order tickets.

It's 6 a.m. and the kitchen smells like coffee and roasting peppers. Yesterday's order spike sits on a clipboard: eleven lunch requests where you'd usually see four. Search Console is open on the laptop beside the prep list. Somewhere in last week's search words is the reason those requests came in, and the trick is finding it before the ovens get hot.

Search Console is where those buyers' searches leave a trace. It shows the queries that put your pages in front of people, how often you appeared and how often someone tapped through. Most owners open it once, see a wiggly line and close the tab. We'd rather you read it like a ticket rail, one query at a time, asking what that person needed by lunch.

None of this needs a paid tool. Search Console is free, it comes straight from Google, and it's the closest thing you'll get to reading over a customer's shoulder. The catch is that it hands you raw words with no story attached. The story is your job, and your kitchen already knows most of it.

A good first habit is ten minutes every Monday. Open the report, scan the new queries from the past week and circle anything that surprises you. Bring the surprises to your next staff meeting. Your delivery drivers and phone staff will often explain them in one sentence.

1. Pick your catering site Sign in to Search Console and choose the site. If nobody on your team has access yet, that's job one, and it's a quick thing to sort out together.
2. Open the search results report Go to Performance, then Search results. Tick all four boxes above the chart so clicks, impressions, click rate and average position all show at once.
3. Stretch the dates as far as they go Pick the longest range in the date menu. That lets you hold this spring against last spring instead of guessing from one busy week.
4. Sort the queries by impressions Open the Queries tab and sort by impressions. The top of that list shows what Google thinks your pages are about, which isn't always what you think.
5. Save a copy every month Export the table to a spreadsheet on the first of each month. Old rows fall off the report as time rolls on, and a saved file keeps them.

• Queries with a number in them, since a number usually means someone is sizing a real order.
• Queries that name a building, a street or a landmark near you, which show people planning a delivery.
• Queries with a question word, like how, can or who, which point to an answer your page should give.
• Queries you'd never want, such as jobs or recipes, which tell you a page is attracting the wrong crowd.

Four filters that sort lunch searches from party searches

Regex filters group your queries by the words inside them, so headcount questions, rush orders, diet questions and event planning each land in a pile you can read.

Treat each pile as a question your site either answers or dodges. If the rush pile is fat and your cutoff lives on page three of a PDF, you've found this month's job. If the event pile is tiny, don't panic. Plenty of event work arrives by referral, and your own order log will tell you whether that's your story.

Now pair a pile with the Pages tab. Filter the queries with the rush pattern, then click over to Pages and see which address catches those searches. If rush searchers keep landing on your About page, they're reading your origin story while the clock runs out. That's a page problem, and a fixable one.

One warning from our own bad habits: a pile with five impressions is gossip. We wait until a pattern holds for a couple of months before rebuilding a page around it, and we'd ask the same patience from you.

Title lines an office manager can scan in one glance

Every catering page deserves a title line that names the kind of order it handles, since Google asks for distinct, descriptive titles and warns against boilerplate ones.

Look at what the after versions do. Each tells a busy reader what happens on the page before they tap, and none repeats a phrase for the robot's sake. The cutoff and guest range are there because those are the facts that make someone keep reading or bail. Swap in your own real numbers, and change the title the same week they change.

Google assembles the title it shows from a few ingredients. It looks at your title tag, the big heading on the page and the words on links pointing your way. That's less scary than it sounds. When your title tag and your top heading say the same plain thing, whatever Google picks will still steer people right.

• Lead with the kind of order, since that's the word a buyer is scanning for.
• Add one fact that filters people, like a cutoff time or a guest range.
• Put your business name at the end, once, and keep it short.
• Read the title aloud. If it sounds like a chant, cut the repeats.

Keep the PDF menu, but give the click to a real page

Google can read the text inside most PDFs, so your old menu file may be where strangers land. A menu built as a web page does that job far better on a phone.

1. Build the menu as page text Put every dish, portion format and diet label on a normal web page. Group it the way people order, such as boxed lunches, buffet trays, breakfast spreads and dessert add-ons.
2. Link the PDF from that page Keep a download button for the people who print menus for the break room. It's a courtesy, and it costs you nothing.
3. Ask Google to skip the PDF Once the web page is live and linked from your site, a developer can add an X-Robots-Tag noindex header to the PDF. Google honors that header on PDFs, so the file stays downloadable without competing in search.
4. Check that the swap took A few weeks later, open the Pages tab in the Performance report. The PDF's impressions should fade while the menu page picks up the same queries.
5. Keep one copy of the truth When prices change, update the web page first and make a fresh PDF from it that same day. Two menus with two prices is how a caterer ends up eating a discount.

A menu that's really a photo saved as a PDF is the worst of both worlds. Google may try to read the words out of the picture, but a phone user still has to pinch and zoom. If your menu started life as a design file, ask your designer for the plain text too. Typing it into a web page once is cheaper than losing a single twelve-person order.

Prices deserve a small warning of their own. If you'd rather not publish per-person prices, say how pricing works instead, such as a per-head range or a minimum order. A buyer who knows the rough shape of the bill is far more likely to send a request than one left guessing.

Which catering happenings count as events to Google

Event markup can put a dated listing in search results. Google keeps it for real gatherings, and marking a deal or your opening hours as an event can bring a manual action.

If you do run public tastings, give each one its own short page with the date, the address, the price and a way to book. That page earns the markup honestly. Your office lunch pages don't need event markup at all, and clear, accurate text will do more for them than any code we could add.

The temptation shows up every holiday season. Somebody suggests marking the party tray deadline as an event so it stands out. Please don't. The downside is losing rich results across the whole site for a stunt that was never going to sell an extra tray.

A cleaner win for the season is a plain holiday ordering page. Put the last booking day, the tray sizes and the delivery windows at the top, then link it from your home page in late fall. It's boring, and boring pages that answer questions tend to get the orders.

Reading your slow months and busy months without panicking

Your own busy and slow stretches show up in the chart. Compare each month with its twin from last year, and pin a note whenever the menu or cutoff changes.

• Switch the chart to monthly and hold this March against last March, never against February.
• Use the compare option to put two date ranges side by side, so a quiet month is judged against its own twin.
• Pin an annotation on the day your menu, prices or order cutoff change, so nobody has to remember it later.
• Note outside events too, like a new caterer opening nearby or a week your site went down.
• Read clicks and impressions on their own. Rising impressions with flat clicks often means the title line isn't earning the tap.

We love annotations for a dull reason. Six months from now, nobody will remember that the lunch cutoff moved from 3 p.m. to 1 p.m. in April. When clicks dip in May, the note is sitting right there on the chart, and a scary mystery turns into a two-minute conversation over coffee.

Annotations also keep us honest. When we change a title line or rebuild the menu page, we pin a note that day. If orders rise a month later, you can see what we touched and when, instead of taking our word for it. If nothing moves, you can see that too.

The first lines on each page usually become the snippet

Google builds most search snippets from the page's own text and only sometimes uses the meta description, so the opening lines of an order page matter more than hidden tags.

The after version reads like a counter clerk who's heard the same question a thousand times. It covers headcount, deadline and diet range before anyone scrolls. Whether Google quotes it or not, the office manager reading on a phone gets the same answers in the same spot, and she's the one you're writing for.

Your chef's story still belongs on the site. Move it to the about page, or tuck it below the order details, where the people who care about it will happily read every word.

We run the same test on our own pages, by the way. If a first screen can't tell a stranger what we do and who it's for, we rewrite it before touching anything fancier. It's humbling, and it works.

1. Pull up your top three order pages Use the Pages tab to find the three addresses that earn the most impressions. Those openings get read most, so they get fixed first.
2. Write down the three facts buyers ask for Ask whoever answers the phone. Nine times out of ten it's headcount, the latest time to order and whether you can handle a diet.
3. Put those facts in the first two sentences Use plain numbers and a clock time. Cut the welcome, the passion and anything a rival could paste onto their own site.
4. Check it on a phone Open the page on your own phone and read the first screen only. If the three facts aren't there, keep trimming.

How long Google takes to notice, in its own words

Google's starter guide says some changes show up within hours and others take months, and it recommends giving an edit a few weeks before you decide it worked.

Should we blog about downtown events to pull in more traffic?

Only when the post helps someone order from you. A recap of a festival you didn't cater brings visitors who were never buying lunch. A post on planning food for an all-day offsite, written from your kitchen's own experience, suits your buyers far better.

Can we reuse our supplier's descriptions for the menu?

You can, but you'll sound like everyone else who buys from them. Write two lines per dish in the words your staff use when someone asks at pickup. That's copy only your kitchen could have written.

Should every diet get its own page on our site?

Usually not. One menu page with clear labels and a short section on how you handle allergies covers most buyers. A separate page makes sense when you run a real specialty line and can describe it honestly.

Will moving to a new website platform hurt us in search?

It can wobble for a while if page addresses change. Keep the same addresses where you can, point each retired address at its replacement using a permanent redirect, and watch Search Console for pages that drop away.

What should we do while we wait for results?

Keep taking orders and keep the log honest. Mark which requests came through the website and whether each one fit. That log is how we'll judge the pages later, far more than any ranking screenshot.

The waiting weeks aren't wasted. They're when you learn whether the people who do arrive are the right people. A page that brings four good office orders a month beats one that brings forty clicks from folks hunting for a dinner reservation. Only your order log can tell those two apart.

• Log every web request with the date, headcount and whether you could take it.
• Ask new office buyers how they found you, and write down their exact words.
• Fix typos, dead links and stale prices as you spot them, and jot each fix in the log so it can't muddy the picture.
• Leave the new pages alone for a few weeks so you can tell what they did on their own.

Six questions that separate a real SEO plan from a pitch deck

Before you pay anyone for catering SEO, us included, ask these and listen for plain answers tied to your own orders, menu and Search Console data.

• Which of our current pages would you change first, and what should that change fix?
• How will you tell a good-fit order request apart from traffic that never orders?
• Do we keep full access to Search Console, analytics and the site if we part ways?
• What won't you do? Listen for fake reviews or a page for every office tower.
• Who writes the menu wording, and who in our kitchen signs off before it's live?
• What would make you tell us search work isn't worth our money this year?

That last question matters most. Say nearly all your orders come from repeat offices and a few event planners. Then a cleaner order page and a Google profile that answers the basics may be all the search work that pays. We'd rather say so on the first call than sell you a monthly plan that can't earn its keep.

Listen for how people talk about access, too. Search Console lets an owner add other users and choose what each one can do, so there's never a reason to hand anyone your password. If a vendor asks for it anyway, that tells you plenty about how they'll treat the rest of your accounts.

Watch for vague answers about results, too. Anyone who promises a spot on page one by a date is guessing, because Google doesn't sell those spots and doesn't tell anyone its schedule. We'll talk about what we'll change and how we'll read the order log afterward. That's a promise we can actually keep.

How the work runs from our desk in Indianapolis

We work remotely from Indianapolis, so the job runs on shared access, video calls and your kitchen's knowledge of every loading dock and front desk downtown.

Here's the honest part. We've never wheeled a hotel pan through a Phoenix lobby, and we won't pretend we have. You know your own building quirks, such as where drivers check in and who signs for the trays. We know how search tools read pages, and Jeff Clerisier has been building and fixing websites since 2016.

So the split is simple. You bring menus, cutoffs and the week-by-week rhythm of your orders. We bring the Search Console reading, the page structure and the rewrites, and we check each change against your records. Jeff reads the order log next to the query piles with you, so the first rewrite goes to the page that cost you real orders.

On that first call we'd rather look than talk. Share your screen, open Search Console and the order page, and we'll read them together. Our team looks after more than 1,400 live sites, so a menu stuck in a PDF is old news to us. Old news is good news here, because a problem we've met before comes with fixes we've already tested.