Carrd and holiday rental
One page, one document, and why uploads are the only real source
A holiday let on Carrd is a scroll of photographs, a short description and a booking button. Everything about that is fine as a website. It is a problem as source material, because a crawl of a one page site returns exactly what the reader is already looking at, which means the assistant knows nothing the visitor could not have found by scrolling.
Why this pairing is its own job
The Carrd install guide covers the tag, and the holiday rental guide covers what the assistant has to know. What follows is the part that belongs to neither.
- There is one URL, so there is one document. A crawl of it produces the description a visitor has already read, and nothing else exists to follow. This is the one setup in this family where crawling the site is close to pointless and uploading documents is the entire job.
- The page is mostly images. Cots, towels, parking, dogs, wifi and the walk from the car are what people message about the week before they travel, and none of those questions have text behind them on a page built to look good.
- The booking button leaves for a listing or a booking engine on another domain, which is where the terms that bind are shown and agreed. Everything the assistant can usefully do happens above that button.
- One page also means one launcher for two audiences at once: a stranger deciding whether to book, and a guest currently in the property at midnight with no hot water. There is no second page to separate them on.
What changes about the install here
<script src="https://cdn.askably.xyz/w.js" data-key="pk_live_YOUR_KEY" defer></script>The tag is the same one on the Carrd guide. Everything below is about where it goes on a holiday rental site specifically.
The crawl is a formality here, so plan around uploads
Embed elements are a Pro feature, so the install starts with an upgrade whatever else you decide. Once the tag is in, resist the instinct to point a crawl at the site and call the material done. It will succeed, it will read one page, and the assistant will be able to recite your headline and very little else.
Write the documents instead, and treat them as the real content of the operation. An inventory list, an arrival and departure routine in general terms, both cancellation policies, and the local rules. None of these belong on a one page site and all of them are what people ask.
This is the unusual case where the assistant ends up knowing considerably more than the website does, which is the correct arrangement rather than a compromise. The page sells. The documents answer.
What goes in, and what must never go in
The uploads are the only source of material, which makes it very easy to reach for the welcome pack, since it is the one file that already has everything in it. It also has the full address, the key safe code and the alarm sequence, and once it is in, those are answerable facts.
Split it. The pre arrival half, covering the inventory, the routine, the local rules and what to bring, goes in. The confirmed guest half, with the address and the codes, stays wherever you already send it after a booking and goes nowhere near the material.
A property that is empty most of the year has a stronger reason for this rule than most trades. A fact that was never indexed cannot be talked out of an assistant by somebody being clever with a question.
Two audiences, one launcher, one greeting
The stranger and the current guest arrive at the same launcher on the same page, so the greeting and the refusal have to serve both. The refusal is where the work goes: anything describing something wrong at the property should end immediately with the phone number from the booking confirmation rather than with a paragraph from a welcome guide.
Put that number in the refusal wording itself rather than trusting the material to surface it. A guest with no hot water at eleven at night needs a person in the first reply, and a well written paragraph about how the boiler works is the wrong response to a boiler that is not working.
Where the answerable material lives
| The inventory, uploaded as a document | Linen, towels, cot, high chair, kitchen basics, what is provided and what is not. On a multi page site this could be a page. Here it has nowhere to live on the site at all, so the upload is not a backup for it, it is the only copy. |
|---|---|
| Both cancellation positions | Yours for a direct booking and the platform's for one made through a listing, kept as separate labelled sections. The button on your page probably leads to the second of those, so the assistant needs to know which is which before it answers. |
| Local rules, tax and the registration number | Tourist tax on arrival, any licence or registration number you must display, quiet hours, waste collection, parking permits and the permitted occupancy. A one page site never has room for these and guests ask about all of them. |
| The paragraphs the page had no room for | The steep steps, the single track lane, the bathroom being upstairs, the pool with no fence, the patchy signal. Design pressure cuts these from a one pager first, and they are the ones that turn into the worst reviews when a guest discovers them on arrival. |
The first thing to get right
Write and upload the inventory document before pointing anything at the site itself.
On a one page site the crawl contributes almost nothing, so the first upload is not an enhancement, it is the moment the assistant becomes able to answer anything at all. The inventory is the highest volume question in the trade and the fastest of these documents to write.
The failure that belongs to this combination
An assistant that can only recite the page in front of the reader
Someone scrolls the page, does not find out whether there is a cot, and opens the chat to ask. If the only material is a crawl of that same page, the reply comes back built from the description they just read, phrased warmly and containing no cot.
That exchange is worse than silence. The visitor has now confirmed that nobody is going to answer them tonight, and a holiday let competes almost entirely on who replies first in the week before travel. They will message the next property instead.
The tell is a run of answers that all cite the same single source. On a multi page site that pattern would suggest a thin crawl. Here it means the crawl was the whole of the material, and the documents that would have carried the answers were never written.
Before you go live
- The origin the page is served from has to be on the allowlist for that assistant, or nothing renders and the browser console says which origin was refused. An apex domain and its www are two different origins to a browser, so list both, along with any staging or preview host you want it to work on.
- Open the site as a visitor would, on the pages a holiday rental visitor actually lands on, and ask it something only your own material could answer. A widget that renders is not the same as a widget that has read anything.
Questions
- Is a crawl worth running at all on a one page site?
- It costs nothing and it does pick up the description and any captions, so run it. Just do not treat it as the material. On every other kind of site the crawl is the foundation and documents fill gaps. Here it is the other way round, and planning it the usual way is how people end up with an assistant that can only paraphrase a landing page.
- Can we keep it off part of the page?
- No. One document means one decision, so the launcher is on the whole thing or on none of it, and there are no other pages to move it to. The place to draw boundaries here is in the material and the refusal wording rather than in the placement.
- How do we stop it giving out the address?
- By never putting the address into anything it reads. Uploads are read in full and there is no partial version of a file, so the welcome pack has to be split before it goes in rather than trimmed afterwards. If the code is not in the material, no amount of persistence in a chat window produces it.
Keep reading
- Installing on CarrdCarrd needs a Pro plan and an Embed element set to code, hidden, loaded at the end of the body. One page means one install everywhere.
- Everything for a holiday rentalWhat is provided, deposits and cancellation terms answer well. The exact address and the door code stay back until a booking exists.
- The page password protects the crawl, not the uploadSquarespace page passwords keep the arrival pack out of a crawl. The upload field is where owners hand over the door code without noticing.
Try it on your own material
Upload a document or point it at your site, paste one line of HTML, then ask it something only your business could answer.