Websites for shop owners,
in plain words.
What a site does for a Bangkok shop, how claiming works, and how to keep it true. Every post ends with the sources for what it says.


Why every branch needs its own page
A shop with several branches gets a page for each one, with a map pin, so customers can find the branch they plan to visit.


A story page made of facts
A plain About page can be built from dates, places and people rather than slogans, which suits a shop in Bangkok where claims carry real risk.


Answering questions before they are asked
A site assistant that uses only your shop's published facts can answer routine visitor questions and give your staff back their time.


Counting visits without cookies
A plain look at how Cloudflare Web Analytics counts visits to a small shop website and why its simple approach suits an owner.


Directions from the nearest station
Clear directions from a BTS, MRT or Airport Rail Link exit help visitors find a shop, and a short walk time sets their expectations before they leave.


Exits and landmarks: directions that work
A short guide to naming the station exit, a landmark and the walk so that a visitor to your shop can find it without getting lost.


Staying factual under Thailand's ad rules
A shop website should read like a directory entry, showing where you are, when you open, and how to visit, with plain facts and no sales language.


A site that loads fast on Thai 4G
A performance budget sets clear load limits for a phone on Thai 4G, so a shop site stays quick for the people who visit it.


The first changes to make after claiming
After you claim your shop's listing, four small edits matter most: the description line, opening hours, branch details and photos, in that order.


Free hosting, explained
A static site can be hosted on Cloudflare Pages without hosting fees, and it helps to know exactly what that covers and what it leaves out.


Holiday and special hours
Planning for public holidays so your website and Google Maps show the same opening hours, and why agreement between them matters to customers.


How the shop directory is made
A plain account of how DISPO builds its Bangkok shop directory from public map data, and how a shop can ask to be corrected or removed.


How to claim a free preview
A plain walk through finding your free DISPO preview, checking what it shows, and sending the changes you want made.


Installing a shop site like an app
A progressive web app can be added to a phone's home screen and keeps working offline once it has been visited.


Linking your Maps listing to your site
Adding your website to your Google Maps listing takes a few minutes, and checking the link works means opening it from the listing itself.


A Maps listing is not a website
A Google Maps listing answers a few questions well, but it leaves out much of what a visitor needs, and a site can fill those gaps for a shop.


Moving to a new address without losing visitors
When a site moves from its preview address to a domain of its own, a 301 redirect tells search engines and visitors where it now lives.


What "no hosting fees" means
A plain explanation of what a DISPO preview costs, what stays free, what you own, and the one thing that could ever cost money.


When the signal drops underground
A site saved to a phone can keep working in a basement or station, and it can point customers from the nearest transit stop to the door.


Writing a one-line description of your shop
A one-line description tells a visitor what your shop is and where it is, and it is usually the first line they read on your page.


One site for every branch
How a shop with several branches can show each location clearly, so visitors can tell which branch a page describes.


One source of truth for hours and addresses
A shop's website, map listing and signs should all state the same hours and address, so customers never get conflicting information.


Opening hours, kept true
A wrong opening time can cost a customer a trip, so a website should keep one accurate set of hours and show whether the shop is open right now.


Ordered by facts, not by opinion
Why the DISPO directory sorts Bangkok shops by distance and public data, and why it never ranks them by perceived quality.


Owning your domain
A domain is the address people type to find your shop, and this post explains why you should hold it yourself and how a preview can move onto it.


PDPA basics for a small shop site
A plain look at the personal data a simple shop website touches, and how a short privacy notice can say so clearly.


Designing for phones first
Many people who look for a shop online will use a phone, so layout, buttons and loading speed are planned around that small screen first.


Photo credits and licences
Every image and map on a shop website needs a clear source, so this post explains how licences and credit lines work.


Photos that help visitors find the door
A shopfront photo works as a set of directions, showing a visitor the street, the sign and the door they are looking for.


When a preview becomes your live site
A DISPO preview becomes your live site when you claim it, and the preview address and hosting stay as they were until you choose to change them.


The questions visitors ask before they come
Visitors often want answers about age, hours and directions before they set out, and a well-built site can answer them directly.


A site readable for everyone
Contrast, text size, tap targets and alt text decide whether a shop's website works for the people who use it, often on a small phone.


Reviews: ask, never pay
Why a website can link to customer reviews, but should never offer anything in return for one, and what that means for a shop owner.


Security basics for a small shop site
A plain look at what keeps a small shop website safe, and why a simple static site has fewer things to protect.


A site and a social page do different jobs
A website and a social page serve different purposes for a shop, and knowing those differences helps an owner decide what each one is for.


How station guides help people find a street
A station guide lists the exits and nearby places around a rail stop, so a walker can see the route to a street before leaving the platform.


Structured data in plain words
Structured data is a small labelled note that tells search engines what your shop is, where it sits and when it opens, with one note for each branch.


Telling visitors about a closure
Temporary closures and moved branches can confuse visitors, so here is how to say it clearly on your site.


Thai, English and Chinese on one site
A single website can show Thai, English and Chinese text together, so one shop can reach locals and visitors without maintaining three separate sites.


The age gate on every shop site
An age gate asks visitors to confirm they are 20 or over before they see the shop, and it is one part of a site built to be careful about who sees what.


The owner's monthly note
A short monthly summary of visits can show an owner patterns over time, but it cannot explain why people came or what they decided.


Search titles and descriptions, explained
A plain guide to what a page title and description are, how search results show them, and how a Bangkok shop owner can write them clearly.


What it takes to run a static site
A static site needs files, a content network and a domain, and this post explains which of those parts cost money and which do not.


What a visitor checks before they walk over
A first-time visitor usually wants three answers before leaving home: whether the shop is open, how to reach it, and which language the page uses.


Who builds DISPO sites, and how
A plain account of who makes DISPO websites, how AI agents use public data, and how every fact on a preview gets checked.


Why previews stay out of search
A DISPO preview is kept out of search engines on purpose, and it waits for its owner to claim it before it can be found.


Your site's code on your own GitHub
Holding a copy of your site's code means you keep control of it if you ever change who maintains the site.