The Search block puts a search box on your site. A visitor types, and it looks through your published pages, your posts, and — if your project has a Knowledge Base — your published articles. Matching results drop down under the box. Click one to go there.
Search covers the public parts of your site: your landing page, any published page you've made public, and your published blog posts. If your project also has a Knowledge Base app, published articles are in there too. It matches on the title, the URL slug, and the SEO title and description — plus the excerpt on knowledge base articles. Only published, public content shows up. Drafts and private pages stay out of it.
As the visitor types, results appear about a third of a second later — a short pause so it isn't searching on every keystroke. Each result shows its title, a short excerpt, and a small label saying what it is: a page, a post, an article. Clicking a result opens it. An x clears the box, and clicking anywhere else closes the list.
The match is literal. It looks for your words inside the title, slug, and SEO text — it doesn't correct typos, and it isn't a fuzzy or meaning-based search. If someone searches for a word that isn't in any title or description, they won't find the page even if the word is in the body. For meaning-based questions, the Chat app is the better tool — it reads your published content and answers in full sentences.
No. Only published, public content shows up — your landing page, public pages, published posts, and published knowledge base articles. Drafts and private pages stay hidden.
Not reliably. It matches the title, the URL slug, and the SEO title and description — not the full body. If a word matters for search, put it in the title or the SEO description.
Yes. The Search block works on your website, your Knowledge Base, and your Developers docs.