Someone just asked AI who you are.
Did it get the story straight?

Old jobs, abandoned projects, outdated biographies, namesakes, and disconnected credits can all become part of the answer. The more varied your path is, the easier it becomes to mix up your roles, miss important work, or confuse you with somebody else.

1. 01

   Build your profile

   Add your work, projects, credits, roles, and professional links to one clear, structured public profile.

2. 02

   Share your link

   Add your soloTHING— address to LinkedIn, Instagram, your website, and other public bios so search engines and AI systems can find the source you maintain.

3. 03

   OptionalConfirm shared work

   Your profile works on its own. When a collaboration or shared credit would benefit from another participant’s confirmation, send a Handshake so they can review and confirm the project, roles, and dates.

Bring your work, relationships, credits, and supporting context into one public record.

The same public profile can be understood as a professional page and as structured information in the raw HTML.

{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Avery Chen",
  "jobTitle": "Product Designer",
  "url": "https://solothing.com/avery-chen",
  "address": "Lisbon, Portugal",
  "sameAs": [
    "https://averychen.studio",
    "https://github.com/averychen"
  ],
  "subjectOf": {
    "@type": "CreativeWork",
    "name": "Northline Atlas",
    "contributor": {
      "@type": "Role",
      "roleName": "Lead designer",
      "verificationStatus": "mutually-confirmed"
    }
  }
}

When confirmation matters, invite a collaborator to review the project, their role, and the dates before it appears as confirmed on both profiles.

Invite colleagues, collaborators, clients, production partners, and other creative professionals. As shared projects are confirmed, your profile becomes a clearer record of what happened, who contributed, and what each person did.

Every public soloTHING— page is server-rendered with Schema.org structured data in the raw HTML, giving crawlers direct access to essential public information instead of requiring them to interpret everything from scattered text.

• Server-rendered pagesEssential public information is included directly in the page HTML.
• Schema.org structured dataPeople, projects, contributors, and roles are described using recognised standards.
• Clear professional relationshipsProjects connect to the people involved and the roles they performed.
• Public canonical URLsEvery public profile and project has a stable, shareable address.
• Accessible without JavaScriptCrawlers can reach essential information without waiting for browser scripts.
• Confirmed collaborationsThe public page states when a collaboration was confirmed by both participants.