Google's rich results engine looks for schema.org JSON-LD on your pages before it will show your site's knowledge panel, pricing cards, FAQ accordions, or review stars on search results. Most sites either skip it entirely or hand-code it once and forget about it. Velocity X does something weird: it auto-generates 5 different schema types from your `brand.json` file, embeds them on every relevant page, and keeps them in sync as your site evolves. No maintenance required.
Why Schema.org Matters More in 2026
Schema.org structured data tells search engines and LLMs what your content actually is: this page is a BlogPosting, that page is a Product, this section is an FAQPage. Without it, crawlers have to guess.
Google rewards schema with rich results: pricing tiers show up as cards in the SERP, testimonials show as stars, blog posts show publish dates and thumbnails. That's the search engine layer. The LLM layer is newer and more powerful. When Claude, ChatGPT, or Perplexity citations pull from your site, they cite more confidently and more often if your content carries schema markup. Structured data is a trust signal for both.
The Architecture: brand.json → Schema Generator → JSON-LD
Here's how Velocity X works. Your `brand.json` file defines the business: name, logo, phone, email, service categories, pricing tiers, social links. A schema generator reads `brand.json` once at build time and outputs JSON-LD objects. These objects get embedded in the `
` of every page. As new pages get added (via category-pages or item-pages JSON), they automatically pull the right schema without any code changes.The generator lives in `src/lib/content.ts`. It reads the brand context and renders `