Static content will soon start to feel like a painting in a gallery.
There is a landing page on your company’s website right now that was written eighteen months ago. A designer spent two weeks on it. It says the same thing to every single person who visits it, whether they’re a CTO at a Fortune 500 or an intern Googling your product for the first time.
That page is a painting. It took real skill to make. But paintings hang in galleries, and the rest of the world moved on to film.
We are entering the era of non-canonical content.
If you don’t live in SEO-world: Google introduced canonical URLs in 2009. It was a way for webmasters to tell search engines this is the original version of this page — the master copy. If you see duplicates, point here. One URL, one page, one message, served identically to everyone. A case study is a case study. A landing page is a landing page. You write it once, you ship it, and you hope it resonates with enough of the people who see it.
That model worked when content was expensive to produce and impossible to personalize at scale. It stops working the moment you have a large language model sitting between your data and your reader.
Soon, every asset will be generated on demand. The same URL will render differently for every visitor — individually constructed in real time for the person reading it.
Andrej Karpathy posed a question recently:
What does LLM coding feel like in the future? Is it like playing StarCraft? Playing Factorio? Playing music?
He was talking about software engineering, but the question can also be asked of every piece of content a marketing team produces. What does consuming content feel like when the content knows who you are?
One answer: walking into a room that rearranges itself around you. The furniture moves and the lighting shifts. The conversation starts exactly where you need it to.
Another answer: it feels like nothing at all. You don’t even notice. The content just… works. It addresses your questions before you ask them. It speaks your language — the way you think about problems, the frameworks you use, the objections you carry around like a backpack full of rocks.
That’s the spooky thing about perfectly optimized content. When it’s done right, you can’t see it working.
One page, one message will start to feel very old fashioned.
Today, a case study is a PDF. A customer gave an interview, then a content marketer wrote it up and now it lives on your website. Everyone reads the same story.
Tomorrow — and by “tomorrow” I mean this is buildable now, today, with off-the-shelf tools — that customer interview becomes the source truth for an infinite number of case studies. When a prospect in financial services reads it, the case study emphasizes compliance, data governance, and the regulatory nightmares that were solved. When a prospect in retail reads the same story, it surfaces supply chain insights, deployment speed, and integration with existing systems. The quotes and the data are static, but the narrative is assembled for whoever showed up.
Your case study doesn’t have a canonical version any more. The URL it lives in is a container, and what fills it depends on who arrives — their industry, the size of their company, the trail of pages they’ve already visited, and the specific problem that sent them to Google in the first place.
The URL itself stops working as a shared reference. It will become harder to Slack someone a link and say “look at this page” because they literally will not see what you saw. The web becomes personal in a way that breaks a very basic, very old assumption: that a page is a page is a page.
You can build this today
You could — and should — wire this up this quarter.
A prospect clicks through an email. A cookie picks up their session, and their profile gets enriched from whatever sources you have: Clay, your CRM, publicly available data. The system checks for history like prior visits, rep conversations, webinar attendance, past downloads.
All of that context flows into a retrieval layer. A knowledge graph maps the relationships between this person, their company, their industry’s pain points, the use cases that address them, and the customers who’ve already solved those problems. An LLM takes that assembled context and generates the page — net-new content, optimized for this visitor, at this moment.
I work in the graph database world, so take this with whatever grain of salt you want. I’ve spent years watching content infrastructure problems, and they keep converging on the same shape.
When you’re generating content dynamically, the core operation is context retrieval. And context is relational by nature. You need to traverse a web of connected entities — from a person to their company, from the company to its industry and pain points, from those pain points to the customers who solved them and what they said about your product.
Graph retrieval, or Graph RAG, is what makes non-canonical content actually work at scale. Vector search gets you “find the most similar document.” Graph traversal gets you “find the most relevant path through our entire knowledge base for this specific human.”
The last canonical landing page
Static content will soon start to feel like a painting in a gallery. You’ll admire the craftsmanship and appreciate the skill it took to write a headline that — shockingly — needs to work for a broad audience, to tell a customer story that holds together for different buyers.
We still go to galleries, and we still hang paintings on our walls. I’m not arguing this content will become worthless — but it will stop being the primary medium. And there’s a big difference between “this is beautiful” and “this is actually driving results.”
If you’re a technical marketer, a GTM engineer, or someone building where AI meets go-to-market: what would your content look like if you stopped writing pages and started writing generation functions?
The primitives are all there today. The hard part is the organizational mindset shift — from content as artifact to content as computation. From “we wrote a case study” to “we built a system that writes case studies.”
The last canonical landing page has already been written. It might still be on your website. But the page that replaces it is being generated right now, somewhere, for someone who isn’t you. And they’ll never know the difference — because to them, it will just look like a page that finally, for once, actually understood what they were looking for.