GEO stopped being a content problem and became an infrastructure problem. This guide maps the three layers of the agentic stack, explains where MCP fits versus REST, compares the CMS publishing connectors worth using, and shows how to assemble a GEO pipeline that actually ships work instead of producing dashboards.
site: operator at scale, jumping from roughly 0.4% to about 17% of all fanout queries overnight, and nearly doubling searches per response, according to Promptwatch's data on ChatGPT site: operator fanouts. Translation: ChatGPT now runs domain-scoped lookups against specific sites. If your pages aren't crawlable and current, you lose. Content freshness became a machine-checked requirement, not a best practice. Second, the content formats that win citations shifted toward pages that need constant maintenance. Promptwatch's citation type data for July 2026 shows product pages became the most-cited content type in ChatGPT Search at roughly a third of all citations, up from about 18% in March. Listicles, comparison pages, and how-tos are all growing too. These are exactly the page types that go stale: prices change, features ship, competitors move. Keeping them current across hundreds of URLs is an automation problem. So the question for GEO teams in 2026 is no longer