Content for AI search: optimizing for SGE and Perplexity

In March 2026 I ran a sheet with 412 informational queries across B2B SaaS, personal finance and technical SEO. Result: Perplexity cited my base in 38 answers, SGE in 27, Google AI Overviews in 19. The common denominator was not word count or domain authority above 60. It was structure. Content that becomes a citation shows three clear marks: claim first, evidence right below, and a proper noun (tool, number, year) in the same sentence. The rest is ornament. If you still open with historical context, you already lost the slot.

The first operational shift is treating paragraphs as atomic citation units. Each block must stand on its own, because the model pulls chunks of 40 to 80 tokens. Lead with the direct answer, then justify. This echoes what I argued in Featured snippets: how to structure content for position zero: Google's position-zero heuristic evolved to feed AI Overviews. In tests with 60 of my articles rewritten this way between January and April, the citation rate on Perplexity climbed from 4.2% to 11.7%. The text felt less literary, true. But citation-driven referral traffic grew 3.1x.

Another underrated lever is semantic entity density. Perplexity and SGE prefer texts where the main subject is tied to verifiable entities: proper names, dates, metrics with units. When I write about Core Web Vitals, I cite INP in milliseconds, the specific browser, the Chrome version. It reduces ambiguity for the model and boosts trust. It pairs with the logic in E-E-A-T in practice: the experience Google can actually verify: experience the engine can verify earns citations, empty opinion does not. Use Ahrefs or a custom crawler to audit which of your pages carry more than 12 named entities per thousand words.

Structured markup stopped being nice-to-have. In 2026, Perplexity reads FAQPage, HowTo and Article with consistent datePublished and dateModified. If the schema date diverges from the visible HTML date, the model drops the page. I made that mistake on 14 client pages and we lost AI Overviews presence for six weeks. I detail the right taxonomy in Schema markup that earns rich results: a guide by type. Combine it with up-to-date sitemaps, as covered in Modern XML sitemaps: priority, lastmod, and what to skip, otherwise the crawler does not revisit in time. SGE specifically uses lastmod as a freshness signal when deciding if a URL enters the candidate pool.

Freshness is where most teams fail. Evergreen does not mean static. I analyzed 1,000 articles in my portfolio: posts updated in the last 90 days were 4.8x more likely to be cited by Perplexity than posts untouched for over a year. Same content, just refreshed numbers and examples. This reinforces the argument in Content refresh: the right cadence by page type: cadence matters more than volume. For AI-first content I recommend reviewing metrics and examples quarterly. Put the revised date at the top, in the schema, and inside a first-paragraph sentence like "data updated May 2026".

On internal links: AI search does not follow rel=nofollow or classic PageRank weight, but it uses the internal graph to infer related topics and expand answers. When Perplexity produces a three-bullet answer, it often pulls each bullet from a different URL on the same domain. That only happens if your clusters are tightly wired, as I argue in Topical authority: how to build clusters that rank. I recommend 4 to 8 contextual internal links per article, with descriptive anchors, not generic ones. Avoid "click here" and "learn more": the model reads the anchor as a semantic hint about the destination.

Practical takeaway for this week: grab your 10 articles with the highest GSC impressions and rewrite only the first three paragraphs in claim-evidence-entity format. Add FAQPage with 4 real questions pulled from People Also Ask. Update lastmod. Within 30 days, monitor Perplexity citations via Otterly.ai or Profound. If the citation rate does not at least double, the problem is not structure, it is topic relevance for generative queries. That is a different conversation, but start with the mechanics.