Most newspaper paywalls are client-side. The full article loads in the browser, then JavaScript hides it and asks the reader to subscribe. For humans, that gating process works. For AI crawlers, it doesn't — they pull the raw HTML without running any scripts, so they see everything. Your premium content is sitting in the page source for any bot that requests it.
The ability for these crawlers to access content matters more now than it did two years ago. Today, more than half of web traffic is bots. Google referral traffic to publishers keeps falling. AI products are summarizing newspaper content and answering reader questions without sending anyone to your site. If your gated articles are technically accessible in the HTML, they're being scraped, ingested and repurposed, and you're footing the bandwidth bill without getting the traffic benefit.
Server-side gating works differently. The server checks whether the request is entitled before deciding what to include in the response. If there's no valid subscription or token, the article body never leaves the server. The bot gets a headline and a teaser. That's it. There's nothing to scrape because nothing was sent.
This has a direct bearing on AI licensing revenue. Publishers negotiating content deals with AI companies need leverage, and leverage comes from scarcity. If your content is already freely available in the page source, you're asking to be paid for something that's already out there. If it's architecturally locked behind server-side checks, you're selling genuine access, and that's a different conversation entirely.
Glide Verify is a server-side enforcement layer built into Glide CMS that strips protected content at the API level before it ever reaches a browser or bot.
Read the full article for more on the impact of server-side gating and how Glide verify works alongside existing paywalls without replacing them, allowing publishers to configure gating rules by section or content type without needing a developer.
