Katarzyna

Search measurement used to be one line: rank, click, convert. Yay! AI search broke it. Boo! The answer now arrives before the click (and often without one). Your analytics never see that step.

Keep reports true. Split them by engine. Read patterns across many prompts, not one. Separate AI-referred from AI-influenced outcomes. Treat any vendor score as a sample, not a fact.

Search measurement used to be one line: rank, click, convert. Yay! AI search broke it. Boo! The answer now arrives before the click (and often without one). Your analytics never see that step.

The old chain was already weak: privacy changes limited the data access. AI made it worse. Last-touch attribution reads the return visit as direct or branded traffic. Then it tells you: “AI did nothing”.

Non-Git teammates can't edit your @astro.build Starlight docs. Add a CMS so they can. You have two choices: an API (headless) CMS, or a git-based one. One takes ten steps. The other takes three. 🤔

Git-based route: connect your repo. It reads the docs folder, infers the fields and commits your edits to Git. Astro builds the same files as before. Three steps, no upkeep.

Non-Git teammates can't edit your @astro.build Starlight docs. Add a CMS so they can. You have two choices: an API (headless) CMS, or a git-based one. One takes ten steps. The other takes three. 🤔

Zero-click does not mean zero-website. Impressions climb while visits fall. Your site now works before anyone arrives. It feeds AI Overviews, ChatGPT answers, and Perplexity citations. I do not make the rules. 🤷 For your static site, that is not a threat. It is your existing workflow.

AI answers are bland by nature, so your weird and human voice wins. That voice lives on the site you fully own: the fonts, the words, the strange phrase that says “not a bot”.

Zero-click does not mean zero-website. Impressions climb while visits fall. Your site now works before anyone arrives. It feeds AI Overviews, ChatGPT answers, and Perplexity citations. I do not make the rules. 🤷 For your static site, that is not a threat. It is your existing workflow.

llms.txt is one Markdown file at your root. It tells AI tools what you are, in their terms. llms-full.txt inlines every page, so an AI tool reads your whole site in one fetch. On a static site generator, you build it from frontmatter you already write. About twenty lines. Minutes of work!

Zero-click does not mean zero-website. Impressions climb while visits fall. Your site now works before anyone arrives. It feeds AI Overviews, ChatGPT answers, and Perplexity citations. I do not make the rules. 🤷 For your static site, that is not a threat. It is your existing workflow.

You already have a home base. Your content is a folder of Markdown in Git. That is one true source you own. Not a database row behind a login, nor a post on some platform. “Write once, build everywhere” is what zero-click now demands of everyone else.

SEO on a static SaaS site still works. But AI search changed where buyers start. 51% of B2B buyers now begin research in a chatbot more often than in Google. Ranking first no longer decides it. Getting cited inside the AI answer does.

Comparison pages are what AI answers cite. On a static generator they cost one template and a CSV. We ship about 75 of them.

SEO on a static SaaS site still works. But AI search changed where buyers start. 51% of B2B buyers now begin research in a chatbot more often than in Google. Ranking first no longer decides it. Getting cited inside the AI answer does.

A static stack gives you speed, control, and build-time templates for free. Core Web Vitals pass by default. What you hand-roll instead: JSON-LD, headings, robots.txt.

SEO on a static SaaS site still works. But AI search changed where buyers start. 51% of B2B buyers now begin research in a chatbot more often than in Google. Ranking first no longer decides it. Getting cited inside the AI answer does.

Google now lets readers pick your site as a "preferred source." Those readers then see your content flagged with a badge in Top Stories, AI Mode and AI Overviews. It is optional, and it asks something of you first. My thoughts.

My take? If you want the badge, start with the plain deeplink. It costs nothing and needs no script. Skip the JavaScript. The readers worth keeping come to your domain with or without a badge.

Google now lets readers pick your site as a "preferred source." Those readers then see your content flagged with a badge in Top Stories, AI Mode and AI Overviews. It is optional, and it asks something of you first. My thoughts.

The reward? A “preferred“ badge inside AI surfaces that answer without a click. You would be promoting a Google feature to stand out inside the same system that reduced your traffic. 🤡

Google now lets readers pick your site as a "preferred source." Those readers then see your content flagged with a badge in Top Stories, AI Mode and AI Overviews. It is optional, and it asks something of you first. My thoughts.