For inn owners

An illustration of a person managing a guest's access to a web page through nginx, PHP, WordPress, and MySQL, and Docker organizing each service. WordPress basics

Role of Docker, nginx, PHP, MySQL | Introduction to WordPress server for hosts

Explaining to hosts the roles of Docker, nginx, PHP, and MySQL used in WordPress on VPS.Organize the flow to display, failure symptoms, and places to check.
Illustration where the VPS operator manages the physical infrastructure and the inn staff manages the OS, firewall, WordPress, monitoring, and backup layers. WordPress basics

Scope of responsibility for operating WordPress on a VPS | Things that the host should manage and delegate

Explains the scope of responsibility when operating an inn's WordPress using a VPS. Organizes responsibilities for OS, firewall, SSH, PHP, DB, SSL, backup, and monitoring.
Illustration where the host and the person in charge save WordPress files and database separately and restore them to the test environment for confirmation. WordPress basics

Backup and restore before WordPress update | Make the inn site ready to return

Before updating your inn's WordPress, we will explain the necessary file/database backups, separate storage, restoration tests, and recovery decisions to avoid losing reservations and inquiries.
Illustration of a host updating WordPress one by one after backing up on the rental server management screen and checking it on a computer and smartphone WordPress basics

How to safely update WordPress on a rental server | Instructions for the host

We will explain to beginners the steps to safely update your inn's WordPress using a rental server such as Lolipop or Sakura. We handle everything from backup, update order, public screen confirmation, and restoration.
Illustration where the host and staff sequentially check the status of canceled reservations, guest room inventory, refunds, and operation records Reservation/Payment

How to deal with accommodation cancellations, refunds, and no-shows | Practical procedures for payment, inventory, and records

For small inns, we will explain the order, confirmation table, and recording method for correctly reflecting cancellations, schedule changes, refunds, and no-shows in reservations, inventory, and payments.
Illustration where the host and staff consolidate reservations made by phone, OTA, and company website into one guest room ledger to prevent double reservations. Reservation/Payment

Operation to prevent double reservations by phone, OTA, and in-house reservations | Inventory management procedures for small inns

For small inns that have a mix of phone, OTA, and company website reservations, we will explain the original ledger to prevent double reservations, instant entry, temporary holding, changes/cancellations, and procedures in case of synchronization failure.
Illustration where the host compares the flow of online advance payment, local card payment, reservation system standard payment, and refund process. Reservation/Payment

Should I choose Stripe, Square, or the reservation system standard payment method for online payment at an inn?

Compare Stripe, Square, and standard payment reservation systems for small inns. In addition to fees, we will explain how to confirm your reservation, make a deposit, pay on-site, and choose cancellation/refund options.
Illustration where the host compares four types of accommodation reservation OSS and operational responsibilities for server protection, updates, backups, payments, email, and support. Reservation/Payment

Comparison of OSS that can be used for accommodation reservations | How to choose QloApps, HotelDruid, and WordPress plugins

Compare OSS that can be used for accommodation reservations for the host. We will explain the differences between QloApps, HotelDruid, MotoPress Hotel Booking Lite, and VikBooking, as well as points to note regarding operating costs, maintenance, and OTA cooperation.
At an inn with less than 10 rooms, reservations made by phone, official website, and reservation site are all in one ledger.Summary, illustration shared by two hosts Reservation/Payment

Reservation system for guesthouses and pensions with less than 10 rooms | Necessary functions and operational design

For guesthouses and pensions with less than 10 rooms, we will explain the necessary functions of the reservation system, summary methods for telephone, OTA, and official reservations, countermeasures against double reservations, and implementation procedures.
Illustration where a host of a small inn compares reservation systems based on the same criteria for accommodation, consecutive nights, inventory synchronization, payment, support, and data output. Reservation/Payment

Comparison of reservation systems for small accommodations | How to choose DYNA IBE, e-YOyaku, SelectType, Beds24, etc.

We will compare official information for DYNA IBE, e-YOyaku, SelectType, Beds24, Room Manager, and Second, which are suitable for small inns and pensions, and explain how to select among them.
Illustration showing the three roles of managing direct reservations by travelers, inventory synchronization of multiple reservation sites, guest room assignments, and cleaning. Reservation/Payment

Differences between reservation engines, site controllers, and PMS | How to choose a small inn

We will explain the roles and differences between accommodation reservation engines, site controllers, and PMS in terms of the flow of reservation reception, inventory synchronization, and front desk operations, and explain how to choose a small inn.
Illustration that focuses on host approval, consultation with AI, investigation of official information, manuscript creation, limited release, and repeated confirmation on PC and smartphone AI site management

How is Neko Yado Research operated with AI?Examples of article creation and WordPress publishing

Neko Yado Research uses Codex/Claude Code to introduce actual examples of planning, official information research, Markdown manuscripts, images, internal links, WordPress publishing, display confirmation, and rule improvement.