Who actually reads the lodging page
The natural assumption is that the lodging page exists for people who want the room block. That is a small part of the readership. The block captures the attendees who decide first: the ones who register early, know their dates, and are happy in a standard hotel room at a group rate. Everyone else arrives at the page with a different problem. A family of five needs two rooms or a house. A crew of six wants a kitchen. A fan driving in from the opposite direction wants something on their side of town. A late registrant finds the block sold out or closed. A conference attendee is choosing between the headquarters hotel and something cheaper ten minutes away.
Timing matters as much as audience. In the mid-size events market Bookend instruments directly, a single peak event weekend produced about 550 room-nights, roughly 31% of that demand sat in room blocks that had sold out early, and about 70% of the lodging dollars landed in the final 30 days before the event. Read that against a typical lodging page and the problem is obvious: the page is written for the first month of sales, and most of its readers show up in the last one. A page that stops being useful at the cutoff date stops being useful right before most of the money moves.
So the design brief is not "list the block". It is "answer the where-to-stay question for every person who asks it, at any point in the cycle, in a form they can act on". The block is one answer among several, and it is the one with the shortest shelf life.
What a working lodging page contains
Start with the question the reader has and order the page by decision, not by which hotel signed first. The first thing on the page should be a one-line answer to "where is the event and how far is too far?" A distance or drive-time note, even a rough one, lets people rule options in or out before they read anything else. Below that, give the room block its own section with the rate, the booking link, the cutoff date, and a plain sentence about what happens after that date. Then give the open market: the hotels, rentals, and houses that are not in the block but are close, with a way to search and book them that stays live after the cutoff. Then the group option, houses and multi-room bookings for families and teams. Then the logistics: parking, shuttles, and anything about arrival that shapes where someone chooses to sleep.
Every option on the page should end in something bookable. A hotel name with a phone number is a task. A hotel name with a button that opens the right dates is an answer. The difference sounds cosmetic, but it decides whether the attendee finishes on your page or opens a new tab and finishes on a booking site that neither knows about your event nor sends anything back. The post on writing a lodging page for your event walks through this section by section, and the short version is that the page should read like a decision aid rather than a directory.
Keep the page short enough to maintain. The reason most lodging pages rot is that they were built as a one-off before sales opened and nobody owns them afterwards. A page with four clear sections and dated statements is easier to keep true than a page with fourteen hotel cards, half of which have stale rates.
The block section: honest, dated, and not the whole page
The room block deserves a clear section because for the attendees it suits, it is the best answer on the page. Write it plainly. Name the hotel, give the rate, give the booking link or code, and state the cutoff date in full. Say whether the block is a courtesy hold or a contracted commitment only if it changes what the attendee should do, which it usually does not. What does change their behaviour is knowing the cutoff is real: rooms release on that date and the rate goes with them. A sentence that says so raises pickup, and the post on raising room block pickup before the cutoff covers where else to place that link so the page is not carrying the block alone.
The part most pages get wrong is what happens when the block is full or closed. The usual move is to leave the section exactly as it was, so the attendee clicks through, finds nothing, and assumes the event has no lodging help at all. Instead, update the section the day the block sells out or the cutoff passes. Say the block is closed, and point down the page to the open-market and group options that are still bookable. The post on why sold-out room blocks quietly cost everyone money makes the case in full: a sold-out block is not the end of your lodging job, it is the moment the rest of the page has to take over.
This is also where the distinction between the block and the open market earns its keep. They are two answers for two kinds of attendee, and the page should offer both from day one rather than switching from one to the other after the cutoff. The post on room block versus open-market lodging explains how to hold both open without signing a second contract or adding work.
Beyond the block: houses, rentals, and the group problem
For tournaments, reunions, weddings, and any event where people travel in groups, the hotel block answers a minority of the demand. A team is really a set of families, and families split between formats: some want a hotel with a pool and breakfast, others want a house where four of them can share a kitchen and split the cost. Neither is wrong, and a page that only lists hotels quietly tells the house-seekers to go elsewhere. The post on group lodging for a tournament, hotels, houses, or both, lays out why the answer is both and how to present them side by side.
Groups also stall. Four families on one roster will spend three weeks each waiting for someone else to book first, and then all book late at whatever is left. The lodging page cannot force the decision, but it can remove the excuses: show a small set of houses that fit a group, make the dates pre-filled, and make it obvious that the choice is between these options rather than an open-ended search. A group that can see three fits and pick one in a few minutes is a group that books.
None of this requires you to hold inventory or vet properties yourself. The page needs a live, searchable set of nearby options with the event dates already applied, which is exactly what a lodging partner provides. What you supply is the context: the venue, the dates, the distance note, and the honest statement of what the block does and does not cover.
Where the page should be linked from
A lodging page nobody reaches is a lodging page that does not exist. The main navigation is the obvious link, and it should be there, but it is the weakest one because it depends on the attendee going looking. The strong links are the ones that meet the attendee at the moment the question is live. The confirmation page after checkout is the first, and the confirmation email is the second. Both arrive in the minutes when someone has just committed to the trip and has not yet decided where to sleep. The post on what your confirmation email says after the thank-you shows how a single line and a link turn the receipt into the start of the lodging conversation.
Follow-up emails are the third link, and the one most events skip. A message a few weeks out, and another inside the final month when most of the money moves, should each point straight at the lodging page rather than at the homepage. The fourth link is the box office. Your support inbox already answers "where should we stay?" over and over, and each reply should carry the page link so the answer is a page rather than a paragraph typed from scratch. The post ranking the lodging questions your box office keeps answering shows how much money sits behind each of those replies.
Think of the lodging page as the destination and every other surface as a pointer to it. The page holds the full answer, it is kept current in one place, and the confirmation screen, the email, the follow-ups, and the support replies all send people there. That is a lot less work than keeping five separate half-answers alive across five channels.
Making the page earn
A lodging page that sends attendees to book elsewhere is a cost centre: it takes time to build, time to update, and returns nothing. The same page with bookable options through a lodging partner returns a share of every booking it produces. Bookings made through Bookend's panel carry a standard 15-20% commission that comes back to your event, with nothing to pay up front and nothing to guarantee. The attendee books the room they were going to book anyway, in one place, with the event dates already applied, and the event earns from a question it was answering for free.
This is the real reason to take the page seriously. Room blocks are only half the story, as the post of that name explains: the block captures the early, predictable slice, and the rest of your attendees sleep somewhere the block never touches. A lodging page that covers that other half is where most of the bookable demand actually sits, and it is also the part of the page that is still working in the final 30 days when the block has long since closed.
Measure the page by bookings, not by visits. A page that gets a thousand views and sends everyone to an outside booking site has told you nothing except that the question exists. A page that produces a booking count, a commission line, and a picture of where your attendees actually stayed gives you something to plan the next event around, including how many rooms to put in next year's block.
Keeping the page true through the cycle
The lodging page has a lifecycle that tracks the event calendar. When sales open, it should carry the block, the open market, and the group options, all live. In the middle of the cycle, it needs a check every few weeks: is the block filling, are the rates still accurate, has a hotel dropped out. At the cutoff date, the block section changes to say the block is closed and points onward. After a sellout, the same edit happens early. In the final month, when roughly 70% of the lodging dollars move, the page should be at its most current, because that is when the most people are reading it with the most intent.
Give the page an owner and a date. A single line at the top or bottom saying when it was last updated does two things: it tells the attendee whether to trust it, and it tells you when it has gone stale. A page with a visible date that is three months old is a prompt to fix it. A page with no date can be wrong for a year without anyone noticing.
After the event, do not delete the page. Update the dates, carry over the parts that worked, and reopen it when next year's sales begin. The distance note, the group guidance, and the structure all survive. The block details and the dated statements are the only parts that need rewriting, and having last year's page as a starting point is faster than starting from a blank template every cycle.