MotoPress Booklium - WordPress Theme

How to Set Up MotoPress Booklium for a Rental and Booking Website

MotoPress Booklium should be treated not as a typical visual theme, but as a ready-made foundation for a hotel, villa, guesthouse, or multi-property rental website. In this guide, we will walk through how to approach the installation, choose the right demo, configure the homepage, connect the design to the booking system, and verify that a guest can actually move from selecting dates to submitting a booking request without unnecessary friction.

This guide is written for a site owner, WordPress administrator, or webmaster who already has the theme archive and wants to understand what to do next. We will not repeat the marketing copy. Instead, we will go through a practical workflow: preparing the site, installing the theme, importing a demo, configuring pages, menus, Gutenberg blocks, MotoPress Hotel Booking settings, testing the search form, diagnosing common issues, and comparing similar solutions.

The main strength of Booklium is the connection between the theme design, Getwid blocks, and the built-in MotoPress Hotel Booking system. That means a successful setup depends not only on whether the theme activates, but also on whether accommodation types, rates, check-in rules, booking pages, form fields, and the homepage structure are all configured correctly.

What the Theme Offers and Where It Really Fits

Booklium works best for websites where two layers matter: an attractive presentation of the property and a working booking flow. If you only need a blog or a landing page without calendars, the theme may be more than you need. But if the site must showcase rooms, villas, apartments, services, seasonal pricing, and available dates, the product becomes much more compelling because it includes integration with MotoPress Hotel Booking.

The official page describes the theme as a multipurpose WordPress template for B&Bs, hotels, and vacation rentals. The more important point is this: Booklium does not force you to assemble a booking system out of unrelated extensions. The developer ties the theme directly to Hotel Booking, and the demo pages already use the required blocks, forms, and pages. In practice, that shortens the "how do I connect everything?" stage, but it does not remove the need for careful setup.

Who the Theme Is For

Booklium is especially useful when the site needs to drive direct bookings while also looking like a modern property showcase. Typical use cases include:

• A small hotel or guesthouse that needs to present room categories, prices, amenities, and an availability calendar.
• The owner of a single villa or apartment who needs a standalone page with a date search form and a way to submit a booking request.
• An agency managing several properties that wants to launch quickly with a demo and then replace the content, photos, and booking rules.
• A project where seasonal pricing, minimum stays, extra services, and iCal calendar sync all matter.

When Booklium Is Not the Best Starting Point

The theme may be inconvenient if you already have a complex custom design and only need the booking engine. In that case, it makes more sense to evaluate the standalone MotoPress Hotel Booking plugin or another booking tool instead of moving the entire site to a new theme. Another case is a project built entirely around Elementor, where the team does not want to work with Gutenberg and Getwid. Booklium was designed around the native block editor, so trying to replace the entire structure with a third-party builder often creates unnecessary work.

You should also think carefully about scenarios involving a large property marketplace, complex partner logic, or a custom owner dashboard. Booklium handles a direct booking website well, but it does not turn WordPress into a full-scale aggregator platform without additional development and supporting tools.

Practical takeaway: choose Booklium if you need an accommodation website with a ready-made visual foundation, date-based search, and booking management. If you only need design without booking, or only need a booking engine without changing the theme, this product may not be the shortest path.

What to Check Before Installing It on WordPress

Before installation, it is important to separate two tasks: the technical readiness of WordPress and content readiness. Mistakes at this stage often show up as "the demo imported incorrectly," "the form is not finding rooms," or "the page does not look like the screenshot," even though the real cause is plugins, old content, or unprepared images.

A Fresh Site or an Existing Project

MotoPress documentation specifically warns that demo data is best imported into a clean site. That makes sense: the demo creates pages, posts, menus, images, sample accommodations, and settings. On a live site with real content, that import can mix the old structure with the new one and make cleanup much harder.

If the project is already running, the safer approach is to make a copy on a staging domain or in a local environment first. There, you can import the right demo, understand the page structure, and only then transfer the settings manually to the production site. If the site is brand new, make sure there are no leftover pages, test plugins, or conflicting themes.

Plugins That Affect the Visual Layout

After activating Booklium, WordPress will prompt you to install recommended plugins. Some of them are needed to make the demo look like the original, while others handle booking functionality and blocks. The documentation explicitly says that after theme activation, you will be prompted to install several plugins, and any unnecessary ones can be disabled later.

Do not disable everything right after installation. First import the demo, verify that the homepage, search form, blocks, and property cards display correctly, and only then remove what you know you will not use. If you disable Getwid before configuring the homepage, some blocks may disappear from the editor or become harder to edit.

Photos, Copy, and Property Structure

For a rental theme, image quality matters more than it does on a standard corporate site. The Booklium demo relies on a large hero photo, an interior gallery, amenity cards, and a news section. If you replace those with random horizontal and vertical images that do not share a visual style, the page quickly loses its polished look.

Before installation, prepare at least a minimal set:

• A logo or text-based property name to use in Appearance - Customize - Site Identity.
• Good-quality photos of the main property, rooms, bathroom, grounds, services, and nearby area.
• A list of accommodation types, for example "Seaside Villa," "Family Room," or "Terrace Apartment."
• A clear idea of whether you need instant online payment, a booking request with manual confirmation, or availability search only.
• A draft of your rules: minimum stay, check-in days, seasonal periods, services, taxes, and extra fees.

These details do not have to be perfect, but they help you test the site against real scenarios instead of abstract demo content.

Installation, Demo Import, and the First Check

Installing Booklium starts the standard WordPress way: in the admin panel, go to Appearance - Themes, upload the theme ZIP file, install it, and click Activate. After activation, the theme prompts you to install the required plugins. This is not a cosmetic step: without them, some demo blocks and booking features may not work.

The Right Order for Initial Setup

1. Install and activate the theme through Appearance - Themes.
2. Follow the link to install the recommended plugins and activate them.
3. If the site is new, open Appearance - Import Demo Data and choose the demo that best matches your property type.
4. After the import, confirm that the pages were created, the menu appeared, and the homepage is assigned as a static page in Settings - Reading.
5. Open the public site in a separate tab and compare the header area, menu, date search form, and first sections with the demo you selected.

If the homepage was not assigned automatically after import, do not run the import again. Create or choose the correct page, then go to Settings - Reading, enable a static homepage, and save the changes.

How to Choose a Demo Without Creating Extra Rework

Booklium includes several ready-made designs for different accommodation types. The documentation notes that the demos share a similar plugin set and overall logic, but differ in homepage design, number of inner pages, color scheme, and booking system settings. That means you should choose a demo not by name, but by how closely its homepage structure matches your business.

If you run a single property, choose a demo focused on one property and its key advantages. If you manage several properties, it is easier to start with a demo that already includes an accommodation list, search form, and catalog blocks. If visual presentation is especially important for a villa, pay close attention to the hero section, gallery, and amenities block, because those are the hardest parts to rebuild without disrupting the page rhythm.

Why You Should Not Keep Switching Between Demos

A common mistake is to import one demo, look at it, and then import a second demo on top of the first. The documentation recommends deleting the first demo's data before importing a new one. The reason is simple: pages, menus, media files, and settings are not always replaced cleanly. The result is duplicate pages, outdated menu items, extra images, and confusing blocks.

Post-import check: open Pages, Appearance - Menus, Appearance - Widgets, and Accommodation. If you see demo pages, menus, footer widget areas, and sample accommodation types there, the import was complete enough for further setup.

Homepage: Hero, Date Search, and Getwid Blocks

The Booklium homepage is built like a storefront, where the first screen should immediately answer a guest's question: what is this property, where is it located, and can I check dates right now? In the attached reference, you can see a typical "Multiple villas" layout: a clean header, a large photo, a semi-transparent hero block with a headline, and a form with Check-in Date, Check-out Date, and an availability search button.

In its documentation, MotoPress explains that the homepage can be edited through Gutenberg and that the demo uses combinations of Getwid blocks. For a site owner, that means the core work happens not in a separate visual page builder, but in the WordPress block editor. That is convenient if you want to preserve WordPress's native structure, but it requires care when selecting the correct nested block.

How the First Screen Is Built

In the villa demos, the header section is built with a Getwid Section. Inside it are text blocks and the availability search block connected to Hotel Booking. The background can be an image, a slider, video, or a solid color. That is why the best way to edit the first screen is through block navigation, not by clicking somewhere at random on the page.

A practical sequence looks like this:

1. Open the homepage in the block editor.
2. Turn on the block list or top-level block navigation so you select the outer Section, not an inner heading.
3. Replace the background, heading, and subheading without removing the availability search block.
4. Make sure the form remains visible against both light and dark parts of the photo.
5. Save the page and review the public site while logged out of the admin area.

Do not change the background, spacing, width, and nested blocks all at once. If the form shifts or loses its styling after saving, it becomes much harder to understand which edit actually broke the layout.

The Search Form and Additional Fields

The basic search form uses check-in and check-out dates. The rest of the fields depend on Hotel Booking settings and accommodation attributes. The documentation notes that you can create extra parameters through Accommodation - Attributes - Add New and then use them as sorting fields or catalog details.

For a villa site, that might include the view type, number of bedrooms, whether there is a pool, or the neighborhood. For a small hotel, it might mean room category, meal plan, child-friendly accommodation, or window view. The main rule is simple: only add fields that genuinely help the guest choose a property. An overly long form reduces the chance that someone will submit a booking request, especially on the first screen.

Blocks After the First Screen

The Booklium demo shows several characteristic sections: a short property overview, a gallery, an amenities block, and recent blog posts. These sections should not be treated as a mandatory order for every site. They create a page rhythm that you can adapt:

• For a single villa, it makes sense to keep a large gallery, amenities, a location block, and answers to common questions.
• For a hotel, it is more useful to show room categories, the search form, and booking terms sooner.
• For multiple apartments, the priority is a property catalog, filters, a neighborhood map, and an amenities comparison.
• For a premium property, strengthen the trust layer: real photos, cancellation rules, contact methods, and reviews from a verified add-on or a separate source.

An important check after editing is not just "does the page look good?" but "is the booking path clear?" The user should be able to see the property, choose dates, move to available options, and avoid getting lost between sections.

Configuring the Look Through the Customizer

After importing the demo, do not rush to change everything with CSS. Booklium has built-in settings in Appearance - Customize, and those should be your first stop. That is where you configure site identity, colors, background image, menus, widgets, theme-specific options, and blog layouts.

Logo, Site Name, and Favicon

The Site Identity section controls the logo, site title, tagline, and site icon. In demos with a vertical menu, branding is especially visible because the logo is part of the navigation. If you do not yet have a polished logo, a clean text-based name is usually better than uploading a small blurry file.

Check the logo in two places: in the top header and at mobile width. Sometimes an image looks fine on a wide screen but becomes too small or too tall inside the mobile menu. If that happens, prepare a separate compact version of the logo or use a text-based site name until the final design is ready.

Colors and Visual Accents

The official Booklium page mentions deep color customization through the WordPress Customizer: you can change accent colors, buttons, the calendar, and other elements. But in real-world work, it is better to limit yourself to two or three main colors: a base text color, a button accent color, and a calm background tone. If you change dozens of colors without a system, the site starts to feel visually fragmented.

For the villa variation shown in the attached reference, a calm light palette works well: plenty of white space, a teal button accent, dark text, and natural photography. If your brand requires a different color, change the accent gradually and keep testing the search form, buttons, links, availability calendar, and hover states.

Menu and Header Variations

Booklium supports different navigation approaches, including a vertical menu in some demos and a more traditional horizontal menu in others. The available menu locations include Primary, Footer, and Social. On a booking site, the main menu should not turn into a full map of the entire website. Keep it to five to seven items: properties, services, location, blog or travel guide, contacts, and booking terms.

If the demo includes an item like Discover Booklium, replace it with a concrete action for your own site: "About the Villa," "Rental Terms," "Check Dates," or "Contact Us." For social links, use the built-in Social location, because the theme may automatically display icons based on the URL.

Footer and Widgets

The documentation notes that Booklium includes an informative footer and several widget areas. This is a good place for contacts, a short property description, rule pages, address details, social networks, and quick links to accommodations. Do not copy all of your top-of-page text into the footer. The footer should help the visitor complete an action: find contact details, check the rules, open a property page, or return to the booking form.

Blog Styles and Internal Pages

In Theme options, you can choose the blog style: classic, Masonry, or featured. On a rental website, the blog often becomes a section for "places nearby," "routes and itineraries," "guest tips," or "local events." If you have plenty of strong photos, Masonry can feel more dynamic. If the articles should be calm and easy to read, go with the classic format.

Booking: Properties, Rates, Rules, and Pages

The most important layer in Booklium is not the visual design, but how the theme connects to MotoPress Hotel Booking. The documentation explains that after activating the plugin, the admin panel gains the Accommodation and Bookings menus. That is where you create accommodation types, actual units, services, rates, rules, pages, and booking requests.

Accommodation Types and Actual Units

Hotel Booking has an important distinction: Accommodation Types describe the accommodation category, while individual Accommodations represent physical units. For example, "Standard double room" can be a type, while three actual rooms within that category count as separate units. For a single villa, the setup is simpler: create one accommodation type and set the number of units to 1.

This logic affects availability. If you accidentally create one type with multiple units for a property that is actually rented as a whole, the system may assume more inventory is available than you really have. That is why your first check after entering the properties should be the calendar: confirm that the number of units matches reality.

Amenities, Services, and Attributes

Before building a property card, it is useful to fill out the reference data: amenities, services, bed types, and attributes. Services can be free or paid, one-time or dependent on the number of guests and nights. Attributes can be used for additional search parameters and to display details in the catalog.

Do not turn attributes into a dumping ground for marketing phrases. An attribute should help users filter or understand the property: bedrooms, view, neighborhood, pool, parking, meal plan, child-friendly features. If a detail only matters in the descriptive copy, it does not have to become a separate search field.

Rates and Seasonal Pricing

The built-in booking system supports seasonal pricing, different rates, and stay conditions. For a simple launch, you can start with a base rate for each accommodation type and then add seasonal periods and special conditions. The key is to test the public form after every change, because the user does not see an admin table, they see the final price and the dates they can actually book.

If the price depends on length of stay, number of guests, or season, create test dates and compare several scenarios: a short stay, a long stay, peak season, and a blocked period. That helps you catch mistakes before a guest sees them.

Booking Pages

Hotel Booking uses system pages for search results, booking checkout, confirmation, and other steps. If the demo imported correctly, some of these pages already exist. If you are building the site manually, review the plugin settings and make sure the required pages are assigned.

A symptom of the wrong page assignment is that the form sends users to a blank page, shows a 404 error, does not display search results, or sends the booking button back to the previous page. If that happens, do not change the theme or rewrite the template. First check the assigned pages in Hotel Booking settings, the WordPress permalinks, and whether the required shortcodes or blocks are present.

Payments and Manual Confirmation

The official Booklium page lists built-in payment methods and the option to use manual confirmation. You do not have to enable online payments right away. Many smaller properties begin with requests or manual approval, test the guest flow, and only then connect payment processing.

If you enable payments, run a full end-to-end test: selecting dates, choosing a service, going through checkout, receiving the guest email, receiving the admin email, and checking the booking status in Bookings. Do not promise instant confirmation to guests if the settings still require manual review.

Scenarios for a Villa, a Hotel, and Multiple Properties

Booklium is valuable because the same toolset can support different rental models. But the data structure will differ depending on the scenario. If you use the same setup for every case, the site may look fine while the booking logic behaves strangely.

One Villa or One Apartment

For a single property, it is best to build the page around strong presentation: a hero image, a concise promise, a gallery, amenities, a neighborhood map, stay conditions, and a date search form. In Hotel Booking, create one accommodation type and one actual unit. If the property is rented as a whole, do not add multiple "rooms" just to create a prettier catalog.

On the homepage, you can keep the date search form and gallery block, while replacing the accommodation catalog with a benefits block or a conditions section. If the demo includes several property cards, remove the extras and verify that no links still point to sample properties.

A Small Hotel or Guesthouse

For a hotel, room categories and clear comparison matter more. Create accommodation types by category, add actual units for each type, and fill in the amenities and rates. In the search form, keep dates, guests, and, if necessary, additional attributes. On the results page, the user should quickly understand which room is available, how it differs, and what it costs.

The photos in the cards should feel comparable: a consistent visual style, similar proportions, and a clear category name. If one card looks premium and another shows a random hallway shot, the catalog loses credibility.

Several Separate Properties

For a network of apartments or villas, it is often convenient to use each property as a separate accommodation type, especially if each one is rented as a whole. In that setup, attributes help with filtering: neighborhood, number of bedrooms, pool, distance to the beach, view type. On the homepage, a block with several results and a quick path to the full property page is especially useful.

In this scenario, calendar synchronization becomes critical. If the properties are also listed on external platforms, configure iCal imports and exports for occupancy. The Hotel Booking documentation describes separate sync settings, including exporting admin blocks, preventing imported bookings from being exported, and accounting for booking buffer time.

A Site with Extra Services

Booklium can support not only accommodation, but also the sale of additional services. In Hotel Booking, those can be booking-related services, while the official theme page also mentions WooCommerce styling support for a separate store. Keep those tasks separate: services that naturally belong to the stay should go through the booking process, while souvenirs, gift certificates, or standalone products can be moved to WooCommerce if that workflow is truly needed.

Do not install WooCommerce just because the theme supports it visually. If the site does not need a separate store, the extra checkout, cart, and shop pages only make the site harder to maintain.

Booking Rules, the Calendar, and Search Fields

Once the basic property data is entered, the most sensitive part begins: configuring restrictions. This is where a rental site stops being a beautiful showcase and becomes a working system. The user only sees the calendar and the form, but behind them are seasons, rates, minimum stay rules, blocked dates, booking buffers, external calendars, and extra search parameters.

Booklium inherits this logic from MotoPress Hotel Booking. The official plugin documentation shows several rule groups: minimum and maximum stay length, check-in or check-out restrictions on specific days, property blocking for a period, advance reservation, and booking buffer. You do not need to turn everything on at once. It is better to build the rules gradually and test the public form after each change.

Minimum Stay and Check-in Days

A minimum stay rule is useful when the property cannot be rented for a single night or when peak season has stricter conditions. For example, a seaside villa might require "at least several nights" during the main season and a more flexible rule during the low season. In the admin panel, that looks like a restriction; on the site, it shows up in the calendar, where the user will be unable to choose an invalid date range.

Test this kind of rule with more than one date. Select a short period that should be blocked, then a period of the correct length that should work. If both scenarios behave the same way, the rule is either configured incorrectly or overridden by another restriction.

Blocked Dates and Operational Downtime

Blocking accommodation is useful for renovations, owner stays, cleaning closures, or periods when the property cannot be sold. The Hotel Booking documentation describes the not check-in, not check-out, and not stay-in restrictions. Their names are similar, but they produce different outcomes for the guest.

If you need to close an entire period, use the rule that blocks stays, not just arrivals. If you want to allow stays but prevent check-in on a specific day, use the more precise restriction. After configuring it, open the public calendar and hover over unavailable dates if the interface shows a reason. That helps you see whether the guest gets a clear explanation instead of just "something cannot be selected."

Booking Buffer

Booking buffer adds technical time before or after a stay. For a real property, that is not a small detail: cleaning, property checks, pool preparation, linen changes, and late checkout all take time. If the buffer is not configured, the site may allow a new guest to check in too close to the previous checkout.

Configure the buffer carefully, because it reduces availability in the calendar. For a single property, that effect is especially noticeable: every extra night of buffer may block dates you could otherwise sell. After enabling it, run a test: create a booking, then check nearby dates in the search form. They should reflect the selected buffer, not look randomly unavailable.

iCal Sync Without False Confidence

iCal helps you exchange occupancy data with external calendars if the platform supports that format. But iCal is not the same thing as a full channel manager with instant two-way logic. It is calendar synchronization, and it needs to be tested as a separate process. This is especially important for properties that are sold on multiple platforms at the same time.

Setup through Bookings - Sync Calendars should include importing the required calendars and, if needed, exporting WordPress occupancy data outward. The sync settings include options that affect exporting admin blocks, imported bookings, and booking buffer behavior. Do not enable them mechanically. First decide which calendar is the main source of truth for occupancy and which events should travel in both directions.

Testing iCal on a Sample Property

1. Create or choose a property where available dates are easy to track.
2. Add a test event in the external calendar or import a test iCal feed.
3. Run synchronization and verify that the blocked dates appear in Bookings.
4. Open the public search form and make sure a guest cannot choose the occupied period.
5. If export is enabled, confirm that the WordPress event does not create a duplicate in the external system.

If duplicates appear after testing, do not start by manually deleting every booking. First document which calendar imports which events, then disable the extra sync direction or adjust the export settings.

Guest Fields and Custom Search Filters

The Booklium documentation explains that the adults and children fields can be hidden through Accommodation - Settings - Guest Management, and that additional fields are added through attributes. This is a powerful tool, but it can easily turn the form into an overloaded filter.

For a single villa, dates and guest count are often enough. For multiple properties, you can add neighborhood, property type, or pool availability. For a hotel, it makes sense to keep capacity and possibly room category. If a field does not affect the guest's decision or is not filled out for all properties, it is better not to show it in the main form. An incomplete attribute creates the feeling of an error: the user chooses a filter and the results disappear without a clear reason.

Emails, Statuses, and Admin Routine After the First Booking Request

Once the form starts returning results, the setup is not finished. The real test is what happens after the first booking request: who receives the email, which status appears in the admin panel, what the guest sees, how the administrator confirms or cancels the booking, whether dates can be changed, and whether the payment history stays intact.

Guest and Admin Notifications

Hotel Booking supports automatic emails. In Booklium, those become part of the user experience: the guest should not have to wonder whether the request was received. Test the emails with a real test address, not just by looking in the admin panel. The email should clearly show the dates, property, contact details, and next step. If manual confirmation is used, the message should not promise a guaranteed stay before the administrator has reviewed it.

Email delivery depends on WordPress, the hosting environment, and SMTP settings. If the emails are not arriving, first check your mail plugin or SMTP configuration, then the sending logs, and only then the email templates. Do not change the theme or disable booking until you have ruled out a standard mail delivery issue.

Booking Statuses

In Bookings, the administrator sees booking requests and their status. For a team, it is important to agree on what each status means and who is responsible for what action. If one employee confirms bookings, another changes the dates, and a third communicates with the guest by email, inconsistencies appear quickly unless there is a defined process.

Your minimum internal workflow can be very simple: who checks a new request, when it gets confirmed, what to do when dates change, how cancellations are recorded, and where comments are stored. Hotel Booking releases have mentioned internal notes and separate roles, so if several employees are involved, it is worth reviewing access permissions instead of giving everyone full admin access.

A Final Test Booking Before Launch

Before publishing the site, run a complete test booking. Do not stop at clicking Preview. Open the site in a private window, choose dates, add a service, fill out the fields, submit the request, check the emails, review the status in Bookings, confirm the occupancy calendar, and verify the public availability of those dates after the request is submitted.

If something is wrong, fix one layer at a time. A pricing error belongs to rates and seasons. An availability error belongs to unit counts, rules, or synchronization. An email error belongs to notifications and mail delivery. A visual issue belongs to the theme, Getwid, the Customizer, or CSS. That kind of diagnosis saves hours because it separates visual causes from functional ones.

Practical Example: Build a Villa Homepage and Test a Booking Request

Let us walk through a scenario similar to the attached reference: a site for a single coastal villa where the guest sees a first screen with a date form, interior photos, amenities, and recent updates. The goal is to create a working path from the homepage to the booking request without breaking the original rhythm of the template.

Goal

You need to create a homepage where the visitor quickly understands that a villa is available to rent, sees real photos, selects dates, and reaches the available property. In the end, the administrator should see the request in Bookings or receive an email if that notification flow is enabled.

Preparation

• The theme is activated and the recommended plugins are installed.
• The demo has been imported into a clean site or a staging copy.
• One accommodation type for the villa and one actual unit have been created in Accommodation.
• A base rate and at least one available period have been added so the form can return a result.
• The photos are ready: hero image, bedroom, bathroom, living room, outdoor area, and amenities.

Steps

1. Open the homepage in the block editor and select the top Getwid Section.
2. Replace the hero background image with a real property photo, but keep the search form in the same position.
3. Update the headline and short text without overloading the first screen with a long description.
4. Open the search block and make sure it is connected to Hotel Booking rather than replaced with a generic form.
5. In the gallery section, replace the demo photos with actual property images while keeping similar proportions.
6. In the amenities block, keep three to six genuinely important benefits: pool, parking, kitchen, fast internet, airport transfer, proximity to the beach.
7. Check the menu: the main item should point to the property or the booking form, not to demo pages.
8. Save the page, open the site in a private window, and select test dates.

Checking the Result

After selecting dates, the user should see the available property or a clear message if those dates are unavailable. If a price is shown, verify that it matches the rate and stay length. If manual confirmation is enabled, the request should appear in Bookings with the expected status. If emails are enabled, check both the administrator's inbox and the guest's inbox.

Quick Public-Site Checklist

• The first screen fits without horizontal scrolling.
• The date form is visible against the background and is not covered by the menu.
• The availability button leads to results, not to a blank page.
• The property card shows real photos, capacity, amenities, and price if the price should be displayed.
• At mobile width, the menu opens correctly, the form remains readable, and the gallery does not break the grid.

A Detail That Often Gets in the Way

If the form does not show the property even though it exists, the problem is usually not the theme design. Check that the property has a rate, available dates, no blocking rule is preventing the stay, the accommodation type is published, and the number of actual units is not zero. Only after that should you look at the page template and styles.

A good test: create one date that is obviously available and one date that is obviously blocked. If the system responds differently to those two cases, the availability logic is working, and then you can move on to fine-tuning the rules.

Checking the Result: Design, Performance, SEO, and Security

After setting up Booklium, do not limit your review to the visual layout. A rental site usually attracts traffic from search, ads, social platforms, and external listings. A user may open the page on a phone, choose dates, come back later, and submit a request. That is why your quality check should include design, functionality, performance, indexability, and form security.

Design and Responsiveness

Open the homepage, property page, search results page, and checkout page on a wide screen, tablet width, and mobile width. Do not rely only on the editor preview mode. Test as a normal visitor while logged out of the admin area, because the WordPress admin bar can change the viewport height and hide real problems.

Pay special attention to the hero section. Large background photos often behave very differently on mobile widths: the key subject may get cropped, the text may land on a very light area, and the form may become too wide. If that happens, it is better to replace the photo or strengthen the background overlay than to reduce the font size until it becomes unreadable.

Performance

Booklium does not remove the need for image optimization. A rental site usually contains many large photos, and those are often what slows down the first screen the most. Use appropriately sized images, enable lazy loading for galleries, avoid uploading uncompressed camera originals, and do not use a video background unless it genuinely helps sell the property.

If you use a caching plugin, test the booking pages after caching is enabled. Date forms, the calendar, and checkout-like steps may require exclusions or careful settings. Do not conclude that "the theme does not work" until you have tested the site with caching and script optimization temporarily disabled.

SEO Structure

For search visibility, headings are not the only thing that matters. The structure of the accommodations matters too. Every accommodation category should have a clear page: a name, description, photos, amenities, stay terms, a price or pricing method, and answers to common questions. If all properties are named "Room 1," "Room 2," and differ only by photo, both users and search engines will struggle to understand the value of each page.

The blog in Booklium can act as a content layer: nearby routes, check-in rules, local events, destination roundups, and guest tips. But the blog should not replace the property pages. First build a clear booking structure, then add informational content around it.

Security and Guest Data

A booking website collects personal data. At the theme level, you can control the visual design, but responsibility for the privacy policy, consent handling, secure connections, email delivery, and payments still belongs to the site owner. The official Booklium page mentions consent options for the booking process, but the final policy language and legal compliance depend on your region and business model.

Check that the site runs over HTTPS, that forms are not sending test emails into spam, that administrators have only the permissions they need, and that access to bookings is not granted to random editors. If Hotel Booking releases introduced roles such as Hotel Manager and Hotel Worker, do not carry over an old permissions model without reviewing it.

Safe Improvements Without Editing the Theme Core

Booklium can be customized, but you should not edit the main theme files directly. Those changes are easy to lose during updates. Start with the Customizer, the block editor, Hotel Booking settings, and widgets. If you need a small visual adjustment, use Appearance - Customize - Additional CSS or a child theme.

A Careful Way to Improve Hero Form Readability

If the real photo is too bright or too high-contrast, the date search form may get lost. Instead of replacing the entire section, you can add a soft background panel behind the form block. Below is an example of a careful CSS adjustment. The selector may need to be refined for your actual page markup, so test it in the browser inspector on a staging copy first.

/* Add this to Additional CSS or to a child theme after verifying the selector */
.home .mphb_sc_search-wrapper,
.home .mphb_sc_search-form {
  background: rgba(255, 255, 255, 0.88);
  border-radius: 4px;
  box-shadow: 0 12px 34px rgba(0, 0, 0, 0.12);
}

.home .mphb_sc_search-form input,
.home .mphb_sc_search-form select {
  min-height: 42px;
}

This change does not affect the booking business logic and does not modify the theme core. It only improves the readability of the homepage form. After adding it, test both desktop and mobile widths, as well as the search results page. If the selector affects unrelated forms, remove the CSS or narrow it to the specific homepage block.

When It Is Better Not to Add CSS

Do not use CSS to hide booking errors, unavailable-date messages, or required fields. If the calendar shows blocked dates, first check the booking rules, rates, and synchronization. If a message looks unattractive, you can style it, but you should not hide it from the guest.

Localization and Interface Text

The official page mentions translation support and compatibility with popular solutions such as WPML and Weglot. For a simple single-language site, it is often enough to translate the theme and plugin strings through standard WordPress tools or a trusted localization plugin. Do not edit text directly in the theme files. Use the translation system, a child theme, or built-in settings if the string is output through a configurable option.

Accurate Video Walkthrough for Booklium

MotoPress has a Booklium video that works well as a visual follow-up to this guide: it presents the theme as a multipurpose hotel WordPress theme, shows the demo skins, and makes it easier to understand how different homepage variations look. Use the video after reading the sections on demo import and homepage setup so you can compare your settings with the actual visual structure.

Focus primarily on the structure of the first screen, the differences between demos, the placement of the search form, the accommodation blocks, and the general setup approach. The video does not replace testing your rates, rules, and booking pages, but it does help you choose the right starting demo and avoid pushing the theme in the wrong direction.

Diagnosing Common Issues After Setup

Problems with Booklium usually appear at the intersection of the theme, demo data, Getwid, Hotel Booking, and caching. The important thing is to find the cause based on the symptom instead of reinstalling the theme right away. Below is a practical troubleshooting map.

The Demo Imported, but the Homepage Looks Empty

Symptom: the theme is active, but instead of a polished homepage you see the blog, a blank page, or the wrong template. Possible cause: the static homepage was not assigned, the import only completed partially, or the demo page exists but was not selected in Settings - Reading.

Check the page list, find the demo homepage, assign it as the Homepage, and resave permalinks. If the page does not exist, confirm whether the import actually finished. Do not run another import on top of the existing site until you understand what has already been created.

Blocks on the Homepage Look Different from the Demo

Symptom: the background, sections, gallery, or cards look broken. Possible cause: Getwid is not activated, a nested Section block was removed, images of a different size were uploaded, or CSS optimization is conflicting with the layout.

Open the block editor and check whether any blocks are marked as missing. Then temporarily disable CSS minification and caching, clear the browser cache, and compare the result. If the issue started after editing a specific block, roll back that block or restore it from the demo page on a staging copy.

The Date Search Form Does Not Return the Property

Symptom: the user selects dates but sees empty results or an unavailable message. Possible cause: the property is not published, no rate exists, the date is blocked by a rule, no actual accommodation unit was created, or the form is filtering by an attribute that is not assigned to the property.

Check Accommodation Types, the number of actual units, rates, seasons, blocking rules, and attributes. Create a test period that is definitely available. If that works, the problem is in a specific rule or date, not in the theme.

The Calendar Shows the Wrong Occupancy After External Sync

Symptom: dates appear occupied or available in unexpected ways after syncing with external platforms. Possible cause: iCal is importing only events from a specific calendar, your export and import settings do not match your business model, or the booking buffer is being applied differently than you expected.

Check Bookings - Sync Calendars, the imported events, the admin-block export settings, and the buffer. If the property is listed on several platforms, make sure each calendar is connected separately and is not creating duplicates.

The Form Stops Working After Caching Is Enabled

Symptom: search works without caching, but with caching enabled the dates, results, or checkout behave inconsistently. Possible cause: caching or script optimization is affecting dynamic booking pages.

Temporarily disable caching and minification, then repeat the test. After that, exclude the results, checkout, and confirmation pages from aggressive caching if your caching plugin supports it. Run a full guest test in a private window after every change.

WooCommerce or Store Styles Do Not Look the Way You Expected

Symptom: the store is enabled, but product cards or cart pages do not match the rest of the design. Possible cause: WooCommerce was turned on as a separate scenario, but the shop pages, product images, payments, and base settings were never fully configured.

First decide whether you need a separate store at all. If you do, configure WooCommerce properly and test the shop pages independently from booking. If you do not need a store, do not keep WooCommerce active just for a possible future idea.

When MotoPress Booklium Is the Right Choice

Booklium is a strong fit if you want to launch a rental website quickly with strong visual presentation, a date-check form, and a booking management system. Its real strength is not just a single attractive page, but the combination of the theme, Gutenberg blocks, Getwid, and MotoPress Hotel Booking. That combination is what you need to preserve during setup: first choose the right demo, then replace the content, then configure booking carefully, and only after that move on to fine styling.

If the site is new, start with a clean install and a demo import. If the site is already live, test the theme on a copy. Do not try to solve functional issues with CSS tweaks: check the properties, rates, rules, pages, and caching first. Once the core guest journey is stable, you can refine colors, menus, the footer, the blog, services, and localization.

After reading this guide, you should have a clear sequence: prepare the content, install the theme, import the right demo, assign the homepage, configure the Customizer, fill in the accommodations, test the date form, run a booking request test, and only then open the site to visitors. If that workflow matches your goals, you can download MotoPress Booklium and test the theme on a staging copy of your site.