The tobecited blog

Playbooks and research on getting cited by ChatGPT, Claude, Gemini and Perplexity — and turning AI answers into customers.

What this blog is for

This blog is written for the person answerable for a website’s traffic — a founder, a marketer, an in-house SEO — who has noticed that ChatGPT, Claude, Gemini and Perplexity now answer the questions their site used to answer, and that those answers name somebody else. Every article starts from a check you can run yourself and ends with a change you can ship this week.

Three kinds of pieces get published here. Explainers on the mechanics assistants actually use: llms.txt, structured data, server-rendered HTML, crawler access. Step-by-step guides that take an hour or less and say plainly what they will and will not change. And measurements from our own runs, including the ones where the result contradicted what we expected.

What we do not publish: ranking factors nobody has documented, and the promise that a technical fix earns citations. Markup makes your facts machine-readable — no AI provider has said it buys a mention. Where the evidence stops, the article says so instead of filling the gap.

How these articles are made — one byline, no invented authors, no number without a primary source — is set out in our editorial policy.