Blog Autopilot keeps a site's blog alive without you writing it. On a schedule you choose, Haven runs a real research pass on your destination, picks the one post a traveler or homeowner would actually search for, writes it from the pages it read, has an editor check every claim, and either saves it as a private draft for your review or publishes it for you — then emails you either way. It is designed so that a machine-written post can only ever help your search ranking, never hurt it.
The fastest way to turn it on is the Turn on AI auto blog tip on your Home tab (/host): it opens your blog's Autopilot card directly.
When to use Blog Autopilot
- Your blog has a handful of posts from launch day and nothing since.
- You run a brand or multi-unit site and want steady content about your homes, your area, and what it is like to have you manage a property.
- Your destination is seasonal — blooms, festivals, ski openings, harvest weekends — and you want the post live before travelers search for it.
- You tried generic AI blogging, got invented restaurants and wrong dates, and want something grounded instead.
Step 1: Open the blog
The Blog Autopilot card appears wherever you manage a blog:
- From a site editor — open the property or multi-unit site editor, click the site's Blog page, then the Manage blog tab in the right panel. The card sits under Blog source. If the blog source is None, pick a blog (or click Generate blog to start one) and the Autopilot switch appears. Click Choose topics, schedule and review mode to open its settings.
- From the library — Grow your brand → Shared Page Content → Blog library (
/host?tab=page-content&contentSub=blog), then open a blog. The card sits at the top of the blog's articles.
It is the same setting in both places — a blog has one Autopilot, shared by every site that blog is attached to. A listing that inherits its blog from a multi-unit site shows a note instead: set Autopilot on the multi-unit site's blog.
The blog must be attached to at least one property or multi-unit site — Autopilot needs a site (and its location) to write about. See Reusable Content Libraries & Inheritance for attaching a blog.
Tick the content pillars you want. Autopilot rotates through them, covering the one you have covered least first. Six are built in:
- Our properties — what makes each home worth booking.
- Local destinations — neighborhoods, day trips, and places guests ask about.
- Events & what's on — real, dated happenings nearby. Skipped automatically when Haven knows of nothing upcoming.
- Travel tips — practical planning advice for your area.
- Property management — homeowner-facing posts about hosting and what you handle for owners.
- The brand experience — what staying with you is actually like.
Add your own below them — type a name (for example Wellness retreats or Our sourdough), press Add, and give it a one-line description of what a post under it should be about. That description is the brief Autopilot writes from. Untick any pillar to rest it; the trash icon removes one of yours.
Add Voice and focus notes — a sentence or two on tone and what to mention ("warm, plain, no exclamation marks; mention the sunrise coffee ritual"). They travel with every brief.
Step 3: Pick how often and what happens to a finished post
- How often — every week, every two weeks, or every month. One post per run.
- Draft for my review — Haven saves a private draft and emails you a link. Nothing is public until you publish.
- Publish automatically — Haven publishes when the post passes the quality checks (below), adds it to your sitemap and notifies IndexNow, and emails you the live link with a one-click way back to draft.
Flip the switch to On. The first post lands within the hour; the card shows Next post from then on. Every control saves as you change it (watch the Saving / Saved pill).
Generate one now writes a single post on demand with the same research and checks — useful before you commit to a schedule. It respects whichever publish mode is selected.
How a post gets written
Every run goes through the same stages, and each one leaves a sentence in the post's Why Autopilot wrote this log:
- Research. Within the chosen pillar, Haven searches for the queries people type about your area, looks at the pages that rank today and what they miss, then opens and reads the pages it will cite — organiser, park, venue, government and tourism-board pages first, reputable local news second. It comes back with one topic, the query it answers, the questions people also ask, a sourced outline, and a list of verified facts, each pinned to the page it came from. A source Haven did not actually open is thrown away. If nothing is worth writing, the run says so and tries the next pillar.
- Write. The writer has no web access. It works only from that research and your listing's own facts, so every specific in the post traces back to a page Haven read or to your data. Posts are built the way search engines and AI answer engines reward: the answer to the query in the first paragraph, a short Key takeaways list, headings that mirror the questions people ask, one concrete sourced fact per paragraph with the source linked in the sentence, your first-hand perspective (how far things are from your homes, what you recommend), a Frequently asked questions section, a link back to your site, and a Sources list at the end. The writer also sets the page's search title and description.
- Editor review. A second pass scores the draft (0–100) on how well it answers the query, whether every claim is supported, specificity, structure and voice. When it falls short, the findings go back to the writer for one revision, which is scored again; the better version is kept. An unsupported specific is removed, never kept.
- Pictures. A post about a place shows that place. Haven looks for a Google Places photo of the first place the post features and uses it as the hero, adds up to two more photos under the sections about other places (reusing photos already in your local guide when it can), and credits the photographers in a closing line. When no place photo exists it generates a photo of a fitting generic scene — never a made-up picture of a real landmark. One of your own listing photos is the hero only when the post is about your home or your brand.
- Quality checks (below), then draft or publish.
The same picture step runs when you click Add blog post or Generate blog yourself, so those posts no longer all open with a photo of the house.
The log also records roughly what the run cost in model usage, so you can see what each post took.
Posts with an FAQ section also get FAQ search markup on the article page automatically, so the questions can appear as rich results and be quoted directly by AI answers. That applies to any post whose body has a ## Frequently asked questions section with ### questions — yours included.
- "A new draft is ready for {site}: {title}" — a review link, the excerpt, why this topic, and — when Autopilot is in auto-publish mode but held the post back — why it is waiting for you.
- "Published on {site}: {title}" — the live link, the excerpt, why this topic, and an edit link.
Emails go to your account's notification recipients (Settings → Account & Profile → Notifications).
Why a post was written
Every Autopilot post carries a plain-language log. Open the post in the editor and expand Why Autopilot wrote this to see which pillar was chosen and why, what the planner found, what the quality checks said, why it was published or held, and the Sources read — the exact pages the writer grounded the post in. Posts show an Autopilot badge in the article list.
Search engines penalize scaled, unhelpful content, so Autopilot is deliberately stricter than a human publishing by hand:
- Grounded research — Autopilot only cites pages it actually opened, and the writer can only use what the research and your listing facts contain. No invented events, businesses, or dates. If a pillar has nothing worth writing right now, the run says so and waits rather than producing filler.
- Editor score — an editor pass scores the finished post; anything under 75/100 is held as a draft.
- Quality checks before auto-publish — 500–1,800 words, at least two section headings, a title and excerpt sized for search results, no placeholder text, no near-duplicate of an existing title, the destination actually named for local pillars, the words people search for present in the title or opening, at least one source for timely and local posts, every outside link pointing at a page the research opened (no invented links), a link back to your site, and a verified hero image. A miss saves the post as a draft with the reasons in your email.
- Monthly caps — at most 5 Autopilot posts per blog per 30 days when the posts live on your own domain (a verified custom domain, or your website via the Blog widget), and 2 on a Haven-hosted site (whose pages canonicalize under bookwithhaven.com). Over the cap, posts land as drafts. Weekly auto-publish needs the posts on your own domain — a verified custom domain, or the Blog widget set to index on your website; weekly review mode works anywhere. See Custom domains.
- One canonical URL — when a blog appears on a multi-unit site and on member listings, every copy of an article points search engines to the multi-unit site's version (or the first property's, when there is no group), so the pages never compete with each other. This applies to every blog post, not only Autopilot's.
- Thin-content gate — posts under 300 words of body copy are left out of your sitemap and index pings, whatever their source. A short post that ranks on your Haven site also carries a
noindex tag until it reaches 300 words.
- Drafts are never indexed — a draft is only visible to you, through the editor's preview.
Already have a website you are keeping? The Blog widget puts your Haven blog on it — every post you write and every post Autopilot writes — as real page content, not an iframe, so search engines can index it on your own domain. New posts appear on their own.
- Open Settings → Widget (optional), then switch to Blog widget (
/host?tab=booking-widget&widgetSub=blog).
- Pick the blog to embed, choose an accent color, grid or list, and how many posts to show.
- Copy the two-line code and paste it on the page you want to be your blog — for example
yoursite.com/blog. It works anywhere custom code can be pasted (WordPress, Squarespace, Wix, Webflow, plain HTML). Each post opens on that page with ?post=… on the end, so every post has its own address on your site.
- Enter that page's address under The page on your website with the widget and click Check my page. Haven loads the page and confirms the code is there.
- Choose where search engines should index the posts:
- My Haven site (default) — posts rank on your Haven site; the copy on your website credits it, so the two never compete.
- My website — posts rank on your own domain. Your Haven site's copies point to your page and leave Haven's sitemap. Autopilot then treats the blog as living on your own domain: up to 5 auto-published posts per 30 days, and weekly auto-publish is allowed. This only takes effect once Check my page has found the widget.
On post pages the widget sets the page title, description, canonical link and article markup for you. It uses your page's own font so it looks native.
- It does not publish anything in Draft for my review mode.
- It does not run when the blog is attached to no visible site, or when no pillars are selected.
- It does not translate posts itself — published posts flow through the normal guest-translation pipeline like any other article.
- It does not touch posts you wrote by hand, and it never edits a post after it is saved.
Flip the switch to Off on the card. Nothing scheduled runs; existing posts stay exactly as they are. Switch it back on later and the next post is scheduled within the hour.