Search titles and descriptions written from real searches

Sixteen pages have new search titles, and eight have new descriptions, chosen from what people actually typed into Google and Bing before reaching the site: the AKASammyThePuppy name, VRChat puppy avatars, and the developer tools by their own names.

Google Search Console and Bing Webmaster Tools both report which searches showed the site and which ones led to a click. Between 2 September and 23 October that was 510 Google impressions and 35 clicks, and about 85 Bing impressions and 6 clicks. The numbers are small, but they show three patterns the page titles were not using.

What people searched for

  • The name people type is AKASammyThePuppy. It and its misspellings were the most common Bing searches, yet only the press page’s description used it, and no title did.
  • VRChat puppy avatars. Bing showed the site at positions 1 to 7 for searches such as “puppy femboy vrchat” and “femboy puppy vrchat avatars”. The Work page has those avatars, but its title and description said only “VRChat”.
  • The tools by what they do. “tikcord” was shown 15 times at position 12, the second page of results, and “unity discord rich presence” at position 35, although UnityCord is exactly that. The project titles all read “Name — Setup & Source”, which says nothing about what each tool is.

Two pages with many impressions had no clicks at all: About (119 impressions, average position 5.7) and Schedule (67).

Searches for other creators’ names, and sexual or abusive searches, were deliberately not used.

What changed

Page New search title
/ Sammy The Femboy Puppy (AKASammyThePuppy) | VRChat Creator
/about/ About Sammy The Femboy Puppy | Furry VRChat Creator
/work/ Sammy’s Portfolio | VRChat Avatars, Streaming & Development
/connect/ AKASammyThePuppy Official Links | Twitch, TikTok & VRChat
/press/ Sammy The Femboy Puppy Press Kit | Bios, Photos & Contact
/community/ How Sammy Built Mello Zone | Furry Community Founder
/blog/ Creator Updates & Announcements | Sammy The Femboy Puppy
/schedule/ Sammy’s Stream Schedule | Twitch, VRChat & Mello Zone
/live/ Is AKASammyThePuppy Live? | Twitch & VRChat Streams
/media-kit/ Sammy The Femboy Puppy Media Kit | Audience & Platforms
/projects/ Sammy’s Developer Projects | Discord, Streaming & SEO Tools
/projects/tikcord/ TikCord: TikTok LIVE to Discord Rich Presence | Sammy
/projects/unitycord/ UnityCord: Discord Rich Presence for Unity & VCC | Sammy
/projects/pearconnect/ PearConnect: Pear Desktop Song Requests for Twitch & TikTok
/projects/rank-math-nextjs/ Rank Math SEO for Next.js App Router | Setup & Source
/projects/seo-index-variscripts/ SEO-INDEX VariScripts: Technical SEO & Indexing Toolkit

Home, About, Work, Connect, Press, Community, Blog and Projects also have new descriptions. Each now opens with who or what the page is about, so it can stand on its own as a search snippet or be quoted in an AI-generated answer. The Community title now describes Sammy’s role in building Mello Zone, because joining, standards and events belong on mellozone.site, not here.

Every title is 60 characters or fewer and every description 160 or fewer. Social-preview text that had been written separately from the old title or description was left as it was; where it was a copy of them, it follows the new text, as does the matching structured data. No visible page text changed. The project titles come from a new searchTitle field in src/data/projects.json.

A project guide now fails its tests if it has no search title, if the title is over 60 characters, or if two guides share one. Without that check, a new project added without a searchTitle would have been published with the title “undefined”.

Verification

  • Every changed page was read back from the build: the new title and description are in place, and no visible text, H1, canonical or robots directive moved.
  • tools/indexing-surface.json was rewritten deliberately. Its diff holds only the changed titles, social titles and descriptions, plus this entry’s own route.
  • npm run test:delivery 201 of 201, npm run test:worker 85 of 85, npm run test:built 391 of 391, and the release audit across all 46 canonical pages.
  • Against npm run preview: npm run test:browser reported 0 failures across 46 routes and npm run test:a11y 0 failures across 102 checks.