# Ask this page: a question box on every deliverable, answered from the page · Stacktree Source: https://stacktr.ee/ask-this-page [Skip to content](#main) [stacktr.ee](/) [Examples](/#proof) [How it works](/#how) [Pricing](/pricing) [Security](/security) [Log in](https://app.stacktr.ee) [Publish one](https://app.stacktr.ee/?join=1) By [Steve Smith](/about) · Founder, Stacktree Last updated September 19, 2026 feature # Let the page answer the question. You sent the proposal. Now they want to know what it costs after year one. Turn on Ask this page and they can ask the page. The answer streams in the page's own type, comes from the page and nothing else, and lights up the sentence it came from. What they asked comes back to you, with the questions the page could not answer first. [ Publish a page free ](https://app.stacktr.ee/?join=1&from=seo_ask_this_page) install npx stacktree-install Copy No card · 3 pages free · about a minute reports.northwind.agency/site-refresh ### Warranty Defects reported within 30 days of launch are fixed at no charge. Requests for new features after launch are quoted separately at the day rate of £720. ### What we need from you Access to the current CMS export by the end of week one, a named reviewer for design sign-off, and brand assets in vector format. what happens if we want changes after launch? Defects within 30 days are fixed for free. Anything that is a new feature rather than a defect is quoted separately at the £720 day rate. ↑ on this page Answered from this page only Ask anything on this page… ## What is Ask this page? An opt-in question box on a Stacktree page. A reader asks in plain words and the answer streams in below, drawn from the page only, with the passages it used lit up on the page. Off-page questions get "That isn't on this page." No account for the reader, the same passcode gate as the page, and every question listed for you, unanswered first. On every plan, switched on per page. ## The moment this exists for A deliverable answers the questions you thought of. The reader has one you did not. What happens next is an email, a wait, and an answer that lives in a thread instead of on the page. Or the reader gives up, decides on the basis of the section they skimmed, and you never find out what they wanted to know. The page already has the answer, most of the time. It just has nine sections and a table, and the reader has thirty seconds. Ask this page turns the page into something you can ask, without turning it into a chat. ## How it works - They ask. A small pill at the foot of the page, in the page's own typeface, says "Ask this page". It opens into a field. They type "what happens if we want changes after launch?" and press Enter. - The page answers. A caption says "Reading the page" while the model reads it. The answer arrives in a card that rises out of the field, a sentence or two, no preamble. The page is the only document the model is given, and it returns a citation for every sentence it relies on. - The page points. Each cited passage lights up in amber on the page and the first one scrolls into view. An "on this page" chip steps through them. The reader can check the answer against the page in one glance, which is the difference between an answer and a claim. - You find out. Every question lands in the page's What came back section, beside reactions and notes. The ones the page could not answer come first. Each is a sentence the next version needs. ## Why it is not a chatbot Chat widgets on documents tend to fail in the same three ways: they answer from things outside the document, they answer confidently when the document is silent, and they show you a paragraph with no way to check it. Each of those is a design decision here, made the other way. - The page is the whole world. Nothing else is read. Not your other pages, not the web, not a knowledge base. A proposal answers as the proposal, and cannot be talked into anything the proposal does not say. - Silence is an answer. Ask a page who the CEO is when the page never says, and the reply is "That isn't on this page." followed at most by the nearest thing it does cover. That sentence is also what makes the owner's list useful: an honest "not here" is a gap you can close. - Every answer points. The highlight is not decoration. It is the reader's audit trail, and it makes the box a faster way to read the page rather than a way to avoid reading it. - One question, one answer. No thread, no memory, no persona, no branding. Press Escape and the page is exactly as it was. ## Private pages stay private The box talks to the page's own address, so it sits behind whatever gate the page has: a passcode, a company email domain, a client space. A reader who has not passed the gate cannot ask the page what it says. The questions are stored for you and shown to nobody else, and the reader never needs an account. ## The same page, for their agent The person you sent the link to increasingly has an agent reading over their shoulder. Two things make that work. A browsing agent on the page finds a WebMCP tool, `stacktree_ask_page`, that returns the same grounded answer with its sources. And any agent that can fetch a URL can read the page itself as Markdown by sending `Accept: text/markdown` to the page's address, or fetching it with `/_page.md` on the end: headings, lists, tables and links intact, the design stripped. The HTML advertises it in a `Link` header and a ``, and the gate applies exactly as it does to the HTML. So the link you send a client is now three things at once: a page for the person, a Markdown document for their agent, and something both of them can ask. ## Turning it on On the page's screen in the dashboard, under What came back, switch on Let them ask the page. It is off by default. Over the API it is `ask: true` on the page's settings, and the same question box is available to agents as `POST {page URL}/_ask`, which streams the answer and its citations. Details are in the [docs](/docs). ## How this compares Criterion A chat widget on a document Ask this page Answers only from the page Usually not Yes, by construction Says when the page does not cover it Rarely Yes, in one fixed sentence Shows where the answer came from A source list, sometimes Lights the passage on the page Works behind a passcode Depends Yes, same gate as the page Reader needs an account Sometimes No Owner sees what was asked Sometimes Yes, unanswered first Available to the reader's agent No WebMCP tool plus Markdown of the page Conversation and memory Yes No, one question at a time FAQ ## Frequent questions What is Ask this page? + An opt-in question box on a Stacktree page. A reader clicks "Ask this page", types a question in plain words, and the answer streams in below in the page's own typeface. The answer is drawn from the page and nothing else, cites the passages it used, and lights those passages up on the page so the reader can check it. If the page does not cover the question, the answer says so. Does the reader need an account? + No. The box works for anyone the link works for. On a passcoded page or a client space, the box sits behind the same gate as the page, so a reader who has not entered the passcode cannot ask the page to leak it either. Where do the answers come from? + From the page. The page is converted to text and handed to the model as the only document it may use, and the model returns citations for every sentence it relies on. Nothing is looked up elsewhere, no other pages of yours are read, and a question about something the page does not say gets "That isn't on this page." rather than a guess. What do I see as the owner? + Every question asked, newest first, in the page's What came back section beside reactions and notes, with the ones the page could not answer at the top. Each of those is a gap in the page: if three readers ask what it costs and the page never says, you know what the next version needs. The answers given are kept too, so you can check them. Which plans include it? + Every plan, today, switched on per page from the page screen. It is off by default so a deliverable stays clean until you want the box. If it turns out to be heavily used we may meter it on the free plan; the page screen will say so before anything changes. Can an agent use it? + Yes, two ways. A browsing agent on the page finds a WebMCP tool called stacktree_ask_page and gets the same grounded answer with its sources. Any agent that can fetch a URL can also read the page itself as Markdown by sending Accept: text/markdown to the page address, or fetching the page with /_page.md appended, so a proposal you sent a client is readable by the client's agent as well as the client. Is this a chatbot? + No. There is no conversation, no memory between questions, no persona and no widget branding. One question, one answer, from this page, pointing at where on the page it came from. It is closer to an index than to a chat: a way to find the sentence you needed without reading all nine sections. Keep reading ## Related guides - [ The launch post The clip that prompted it, the design decisions, and what we deliberately left out. ](/blog/ask-this-page) - [ See how your shared pages get read Reactions, notes, opens and the attention heatmap: the other return channels. ](/page-engagement) - [ The client feedback loop When a question becomes a change request: comments your agent reads and resolves. ](/client-feedback-loop) - [ Send a client report as a link The deliverable this was built for. ](/send-client-report-as-link) - [ Pricing On every plan today. Passcodes, domains and client spaces from Solo. ](/pricing) References ## Sources and further reading - [ Citations (Claude API docs) ↗ The mechanism behind the highlights: the model returns the exact passage each sentence relies on, which the page then finds and lights up. ](https://docs.claude.com/en/docs/build-with-claude/citations) - [ Stacktree docs: reading a page as Markdown and asking it ↗ The Accept: text/markdown negotiation, the /_page.md and /_ask routes, and the owner route that lists questions. ](https://stacktr.ee/docs) ## Send the link. Let the page take the questions. Off by default, one switch per page, on every plan. The next thing a reader wants to know, the page can tell them. [ Sign up free → ](https://app.stacktr.ee/?join=1&from=cta_ask_this_page) install npx stacktree-install Copy stacktr.ee [About](/about) [Blog](/blog) [Changelog](/changelog) [Pricing](/pricing) [Security](/security) [FAQ](/faq) [Made with Stacktree](/made-with) Building with AI agents? See the [developer docs →](/developers) --- Full markdown summary of the Stacktree marketing surface: https://stacktr.ee/llms-full.txt