Skip to content

Explainer 05 · 7 scenes · about 5 min

The weekly Google post

From the fact sheet, the owner’s note and the festival calendar to one Google post a week, including Google’s rule that hotel posts may not mention deals.

Hands on: Change the type of business, add a discount line, and watch the hotel-post rule decide.

Illustration: a lit brass diya and marigolds on a wooden ledge beside a blank card and a pencil.
Fictional example

1 · The fact sheet (a few lines)

  • F5Front desk phone: +91 90000 00000
  • F6Breakfast: home-cooked breakfast included
  • F10Winter stay offer: 15% off stays of 3 nights or more

2 · The owner’s note · typed, or spoken into the mic

“Bonfire on the terrace every Saturday evening from this week. Gajar ka halwa after dinner on Diwali night.”

3 · The festival calendar · Uttarakhand, three weeks from Mon, 2 Nov

  • Fri, 6 NovDhanteras · धनतेरसNot on the DoP&T lists; the date comes from a panchang site. The tithi runs from 10:30 am on 6 Nov to 10:47 am on 7 Nov, so the evening of 6 Nov is the usual day. Confirm with your local panchang.Date source
  • Sun, 8 NovDiwali · दिवालीDate from the DoP&T holiday order (Deepavali, gazetted holiday). Some panchangs put Naraka Chaturdashi on 7 Nov and the DoP&T list on 8 Nov.Date source
  • Wed, 11 NovBhai Dooj · भाई दूजDate from the DoP&T holiday order (restricted holiday list). Some panchangs list 10 Nov; the tithi depends on your local sunrise.Date source

  1. 01 / 07

    Three things go in

    Once a week Shiva drafts one post for the owner’s Google Business Profile. It starts from three things: the fact sheet, a short note from the owner (typed, or spoken in English or Hindi), and Shiva’s festival calendar.

    Every date in the calendar comes with its source, preferring official holiday lists, and notes where regions differ. Tap a source on the stage.

  2. 02 / 07

    This week’s ideas

    The app offers up to three ideas: festivals in the next three weeks, national or in the owner’s state, and the owner’s confirmed offers.

    Change the type of business on the stage. A restaurant gets its offer as an idea; a hotel doesn’t, because of a Google rule you’ll meet in scene 6. Shiva treats a homestay the same way, to be safe.

  3. 03 / 07

    Evidence, frozen first

    As with replies, the evidence is gathered and frozen before writing: fact-sheet lines, the owner’s note, the calendar entry with its source.

    If the owner allows a few websites, Shiva may read pages from those sites only. A model with no tools summarises each page, and the page is treated as data, never as instructions.

  4. 04 / 07

    Hook, fact, call to action

    A post is planned in three parts: a hook (Diwali at the homestay), a fact (the Saturday bonfire, breakfast included), and a call to action (call to book). Each part names its sources.

  5. 05 / 07

    The draft

    The post, written from that outline in the owner’s voice. Tap a line to see its source: the calendar, the owner’s note, or the fact sheet.

  6. 06 / 07

    Hotels: no deals in posts

    Google’s rules for posts say hotels may not post offers or mention deals and discounts. Shiva’s rule check knows this: for a hotel, a discount line blocks the post; for a homestay, where the rule is unclear, it asks the owner to look again; a restaurant may post its offer.

    Add the winter offer and switch the business type to watch the rule decide. The fact check still makes sure “15%” matches the offer on the fact sheet.

  7. 07 / 07

    Checked twice, then handed over

    Posts get one more check: questions about the post are answered from the sources alone, without seeing the draft, and the answers are compared with what the draft says. Independence is the point.

    Then the owner approves, copies the post and opens their Google profile. Direct posting through Google’s API comes once Google grants access.

In plain words

The short version

  1. One Google post a week, drafted from the fact sheet, the owner’s note and a festival calendar whose every date has a source.

  2. Ideas come from upcoming festivals and the owner’s confirmed offers, but hotels (and, to be safe, homestays) get no offer ideas.

  3. The post is planned as hook, fact and call to action, and each line names its sources.

  4. Google’s hotel-post rule is checked by code: a deal in a hotel’s post blocks Approve.

  5. The owner approves and posts by copy and paste until Google grants direct access.

For the curious: sources and technical terms

Sources

Where this comes from

  1. Post content policies (“Hotel posts”)

    Google Business Profile Help · as cited in Shiva’s rule check

  2. Work with review data, and local posts

    Google Business Profile APIs · updated 2026-08-28 · reviews.updateReply and localPosts need Basic API Access

  3. Chain-of-Verification Reduces Hallucination in Large Language Models (CoVe)

    Dhuliawala, Komeili, Xu, et al. · 2023 · answer verification questions independently of the draft

  4. Assisting in Writing Wikipedia-like Articles From Scratch with Large Language Models (STORM)

    Shao, Jiang, Kanell, et al., NAACL · 2024 · research, then outline, then write

  5. Defeating Prompt Injections by Design (CaMeL)

    Debenedetti, Shumailov, Fan, et al. · 2025 preprint · a reader with no tools for untrusted pages

Fictional example

Example Homestay, Meera’s note and the post are fictional and written by hand for this page. The festival dates and their sources come from Shiva’s own calendar. The rule check and the fact check run live in your browser with Shiva’s own code; the verification questions are an illustration. Nothing you type is sent anywhere.

Next · Explainer 01A review comes inSwitch between an English, a Hindi and a Hinglish guest, type your own review, and tap any line of the reply to see where it came from.

Shiva is in development. It has no customers yet, so these pages show how it works, not results. The demo shows the real screens, with a made-up business.