Restaurants
Reservations and ordering both arrive from outside the site, which makes the menu and the telephone number the parts you have to keep.
Restaurants hostingIn a town that sells tours, tables and freight, the page where money changes hands is usually not a page at all. It is a hole in your page, filled at load time by another company's server: a booking calendar, an ordering window, a rate request, a seat map. It works well until that company changes something. Then the site is still up, still fast, still paid for, and taking nothing. That is the failure web hosting in Savannah, GA cannot fix, and the one worth planning for.
AldoMedia is not in Savannah. The work is done from Buffalo, New York. There is no Georgia office, no local number, and nobody who will drive over and look at a screen with you. Registering a domain, setting hosting up, moving a site and answering questions afterwards all happen remotely, because that is where this work has always happened.
A port and visitor economy ends up running on other people's software. A restaurant takes reservations through a booking company. A tour operator sells dates through a ticketing platform. A crew services firm publishes a calendar of what is free next month. A freight broker puts a rate request behind a form belonging to a logistics platform. In each case the customer believes they are on your website, and in each case they are only half right.
It is worth being exact about what one of those boxes is. You paste a short piece of code into your page. Somebody two states away opens the page on a phone while planning a trip, their browser reads your code, then goes off to a supplier's servers for the rest. Whether ten o'clock on Saturday still has four places, and the confirmation that lands in their inbox, both arrive from there. Your hosting served an empty box and instructions for filling it, and saw none of the rest. That is no argument against embeds, since building bookings and card payments from nothing is a poor idea for any business selling dates to people who have not arrived yet.
So a site like this has two halves with two owners. The half you control holds the words, the photographs of the dining room or the deck, the telephone number and the hours somebody answers. The half you do not control is the box taking a deposit for a date three months out. Almost all the usual advice about hosting concerns the first half. Almost every failure that loses a booking, or a load, happens in the second.
Send us the address. We will list every piece of code the page pulls in from elsewhere, say which ones are doing real work, and tell you what a customer would still be able to do if each of them went quiet.
Nothing about an embed announces itself when it stops working. There is no error page and no alert. The page loads, the layout holds, and where the calendar used to be there is white space or a spinner that never resolves. The people it fails are strangers choosing between you and two others they found that morning, and a stranger does not ring to report a broken booking form. They book the next name on the list, and since they are only in town a few days, you never learn it happened.
The ways it happens are dull, and much the same whether the box sells a table, a tour or a truckload.
Which brings the useful half, namely what stays on your own side. Everything a customer needs in order to reach you anyway belongs in your page as ordinary text, above or beside the box rather than inside it. A telephone number as text and not part of a picture, because somebody reading it on a pavement wants to tap it, not copy it. An email address. The hours somebody genuinely answers. One line saying what to do if the form will not load. None of that depends on a supplier being awake.
Keep your own copy of the substance as well. If the rates, the sailing times or the menu exist only inside a supplier's account, losing the supplier loses the information along with the form. A plain page setting out what you do is worth writing even when the panel presents it more attractively, because that page is yours and it still reads when everything else has gone silent.
The last piece is being able to publish a short notice within the hour. When the booking tool is dark in a busy week, the useful action is a line at the top of the page saying bookings are by telephone today. That needs somebody in the building who can edit the site without raising a ticket. Without it, the outage lasts as long as the supplier's plus however long your web person takes to answer.
Ask an owner here who controls their website and the reply is normally a person's name. That is the wrong shape of answer, because control is not one object. It is a domain registration, a hosting account, whatever tool edits the pages, and on a site like this the booking account too. Separate logins, often held by separate people, none of whom think of themselves as holding anything important.
Check the registration first. It is the only item that cannot be rebuilt from what is already public, a domain in somebody else's name can stop a Georgia business trading rather than merely annoy it, and it is far easier to sort out while everyone is still friendly. Where the person who set it up has stopped replying, taking over a website covers recovering each piece in turn.
The booking account deserves the same attention and hardly ever gets it. It holds customer names, dates, deposits and a record of who came and when. If it was opened on a manager's personal address during a busy season three years ago, it will quietly leave with them. Move it onto a company address and make certain two people can get in.
The test takes an afternoon and needs nobody technical. Can you sign in at the registrar and see your own company name against the domain? Can you reach the hosting account without asking a favour? Can you change a sentence on a page today? Can you open the booking system and export what is inside it? A single no is worth fixing before anything else matters.
Copy, test on a temporary address, check every embedded tool against the real domain before the switch, keep the mail records intact. You keep trading while it happens.
Most businesses asking for help are leaving something rather than starting something. The order of operations is the entire job: copy the site, put it on the new hosting, test it on a temporary address, and point the domain at it last, so your address never leads nowhere. Website migration sets that sequence out in full.
Embedded tools add two traps. The first is the rehearsal: many suppliers tie their code to the domain registered with them, so on a temporary address the panel refuses to load and looks broken when it is not. Ask each supplier what is recorded against your account before the switch, so the test tells you something.
The second is that these tools frequently need a verification record in your domain settings, and those records live where people rebuild from memory during a move. Mail is the same story and worse, because for a business taking enquiries the inbox is the business. Write down every record before anything is touched. Email migration covers keeping mail running through the change.
Old links are the last thing. A site up for years is linked from listing sites, from suppliers, and from a repeat customer's bookmark. Keep the addresses you can and redirect the ones you cannot. A move is judged a week later on whether those still work.
The hosting line is rarely the largest number on the bill. Around it sit a domain renewal, a certificate that may already be included, a subscription to whatever builds the pages, a backup add on, a security add on, and a monthly fee for every outside tool the site leans on.
That last group multiplies without anyone noticing. A booking tool, a second ordering tool taken on during a quiet spell, a review feed, a chat box and a mailing list all bill separately and all load on the same page. It is common to find two of them doing the same job because different people signed up in different years.
Worth keeping: the domain, a working certificate, backups somebody has actually tested restoring, and the one panel you genuinely use. Worth questioning: anything duplicating what the plan already includes, and any tool whose only visible output is a box nobody clicks. What a website costs to run puts the whole picture in one place.
Three kinds of business here that lean hardest on somebody else's software, each with a page of its own.
Reservations and ordering both arrive from outside the site, which makes the menu and the telephone number the parts you have to keep.
Restaurants hostingA rate request form owned by a logistics platform, and a customer who moves along quickly when it fails to appear.
Trucking companies hostingGalleries, availability and proofing all held elsewhere, so a portfolio can vanish with an account nobody remembered to renew.
Photographers hostingEvery trade we cover is on hosting by industry, and every city on our locations page.
You would not, unless something is watching for it. An uptime check asks whether your page responds, and it responded perfectly. The box inside it was empty. The cheap answer is a habit rather than a product: somebody opens the site on their own phone at the start of each shift, on mobile data rather than the office network, because an office network will sometimes hand back a cached copy of yesterday. The other half is having a number and an address printed as plain text, so an empty box still leaves the customer somewhere to go.
Probably not, and not for the reason you expect. If bookings run through an outside panel, that traffic never reaches your hosting at all. The requests go straight to the booking company. What your hosting serves is a handful of pages of text and photographs, and a few hundred extra people reading those is nothing to a server. Put the money into making those pages lighter and into having your hours and telephone number as plain text, because that is what people fall back on when the panel is slow.
Almost certainly not. Taking payments, holding availability and stopping two people claiming the same slot is genuinely hard, and a small custom build will be worse than the thing you are renting and dearer to keep alive. Leave it alone. The work worth doing is much smaller: get the account into a company name, keep your own export of the bookings, publish the substance as ordinary text on pages you own, and make sure somebody can edit the site on the day the panel misbehaves.
It matters less than owners fear and more than suppliers admit. Customers barely notice the address changing under them. What you lose is the record. The visit, the order abandoned halfway and the search that brought the person to you are all counted on their side, not yours, and you cannot ask for that history back later. Keep a page of your own that explains the offer, links across plainly, and carries your contact details, so the part of the journey you can see stays yours.
Tell us what the site runs on, who can edit it, and which parts of it belong to another company. We will say what to fix, what to leave alone, and what is already fine as it is.
See hosting plans Get help choosing
Or call 716-771-2536. We are in Buffalo, New York, so we answer Eastern time.