--- id: "10.11" title: "Getting found ourselves" dept: marketing-and-growth status: draft owner: Param branded: false last_verified: 2026-10-26 sources: - "brew origin/main a559de6: public/index.html:1-2; server.js:937, 946-947, 1019; handoff.js:135; jam2/ready.js:61; legal-pages.js:5-8, 53; live-watch.js:4-6, 22-24; public/demo-picker.html:6" - "git grep robots.txt, sitemap.xml and llms.txt over server.js, legal-pages.js, feed-service.js at origin/main" - "brand-directions/BRIEF.md:37" - "memory: brand-directions-2026-10-25, brew-brand-book" - "handbook/AGENTS.md" --- # Getting found ourselves ## Answer How people and AI answers find Brew itself in search; today they cannot, because the product has no chosen name, its pages carry no description, sitemap or guide for AI tools, and nobody has checked what AI answers say about us, so the work starts the day the name is picked. ## Today ### Our own pages | Page | What search sees | Source | |---|---|---| | Landing, feed.joinsquareup.com | Title Brew, no meta description, no social preview tags | [src: brew/public/index.html:1-2] | | Demo picker, demo.joinsquareup.com | Title Brew ยท Demo | [src: brew/public/demo-picker.html:6] | | Privacy and Terms | Plain pages, contact hello@joinsquareup.com, updated 19 October 2026 | [src: brew/legal-pages.js:5-8] [src: brew/legal-pages.js:53] | | robots.txt, sitemap.xml, llms.txt for our own site | No route serves them | [src: git grep robots.txt sitemap.xml llms.txt origin/main -- server.js legal-pages.js feed-service.js] | | Brief pages and ready to post pages | Marked noindex on purpose | [src: brew/handoff.js:135] [src: brew/jam2/ready.js:61] | | The shared docs, docs.joinsquareup.com | Public, hosted on Firebase; never names the product | [src: memory brand-directions-2026-10-25] | ### The brands' pages we host | Page | What it carries | Source | |---|---|---| | A brand's brand book, `//brand` | Title, the brand's name and brand book; a description that says it is free to use with any AI tool | [src: brew/server.js:946-947] | | `//llms.txt` | A guide for AI tools about that brand | [src: brew/server.js:937] | | A brand's pages in the app | Title, the brand's name then Brew | [src: brew/server.js:1019] | These pages are the brand's, not ours. They can carry a small sign off and nothing more, see [word of mouth and referrals](/marketing-and-growth/word-of-mouth-and-referrals). ### What we already know how to check The product asks a fixed set of shopper questions every week to ChatGPT, Gemini and Perplexity through treg, and to Claude with web search, and reads whether a brand is named [src: brew/live-watch.js:4-6]. A failed run waits six hours; one run costs about $0.50 [src: brew/live-watch.js:22-24]. We have never run it on ourselves, because there is no name to look for [src: handbook/AGENTS.md]. ## Tomorrow | Item | Version | Tag | |---|---|---| | Pick the name and the domain first; nothing else here is worth doing before | v1 | New | | A real title and description on the landing, in plain words, with no product claims beyond v1 | v1 | Changes | | robots.txt, sitemap.xml and an llms.txt for our own site, built the same way as a brand's | v1 | New | | Social preview tags with the chosen character, so a shared link shows who we are | v1 | New | | Run our own weekly AI answers check on our name and on questions like best marketing tool for a small online store | v1 | New | | Write the pages AI answers cite: what it does, who it is for, how a read works, what it never does | v1 | New | | The docs site linked from the landing once it may name the product | v1 | Changes | | Pages for posting with your yes, once it ships | v2 | New | | Pages for what worked, once it ships | v3 | New | ## How we do it 1. After the name is picked, add the title, description and preview tags to `public/index.html` in brew, in one change, checked on staging. 2. Serve `robots.txt`, `sitemap.xml` and `llms.txt` from `server.js`, next to the legal pages. Keep brief pages and ready pages noindex. 3. Write the five answer pages from [positioning](/product-marketing/positioning) and [claims we can make](/product-marketing/claims-we-can-make). Every figure on them comes from the allowed list in brand-directions/BRIEF.md. 4. Add our own set of questions to the weekly AI answers check and log each week in [how AI answers describe us](/product-marketing/how-ai-answers-describe-us). 5. Ask before the first paid run of the check; it costs money each week. ## Numbers | Metric | Definition | Where measured | Status | |---|---|---|---| | Named in AI answers | Share of our fixed questions where an answer names us | Our own weekly AI answers check | Proposed | | Search visits | Visits from search to the landing | Analytics on the landing, once installed | Proposed | | Indexed pages | Our pages in Google's index | Google Search Console, once set up | Proposed | ## Open 1. **Which domain will the product live on?** Proposal: decide it with the name in [naming](/brand/naming); keep feed.joinsquareup.com as a redirect. 2. **Do we run our own AI answers check before we have a name?** Proposal: no; wait for the name, then run it weekly. 3. **May the docs site be indexed?** Proposal: yes, once it names the product; today it stays as it is. 4. **Who writes the answer pages?** Proposal: Param drafts with Claude, Sai reviews for plain words.