A paywall isn't just a way to lock an article anymore. It's an attempt to answer a harder question: what is a reader actually worth?

That question matters even more in a market where paying for news has never been the default. A 2025 Reuters Institute survey found that in most countries studied, only a small minority of people say they paid for any online news in the past year - the U.S. figure sits well below half. In other words: most readers, most of the time, aren't paying for news as a category.

And yet the market keeps building more paid-access models - from large digital subscriptions to small, specialized outlets built from day one around a mix of free and paid content. That's not really a contradiction. It shows publishers no longer treat "paying for news" as one single decision. They're looking for narrower, more specific reasons a reader might actually pay.

Readers are reluctant to pay for news in general. But they'll pay for something concrete: data, analysis, access to know-how they can't get anywhere else.

The problem doesn't start at the paywall

For a long time, publishers thought of the paywall mainly as a tool to grow subscriber counts. A reader hits a few articles, a prompt appears, some users buy access.

Piano's data across its publisher base points to a more interesting pattern. Between 2022 and 2024, traffic across the publishers it tracked grew only 5%.  Conversions - cases where a visitor actually bought a subscription - rose 14%. Subscription revenue rose 28%. Among sites that were losing traffic during that period, 54% still managed to grow their number of paid subscriptions.

So it wasn't about finding more users. It was about finding higher-value ones - readers more likely to convert.

The 2025 numbers make that gap even sharper. According to a follow-up Piano report, search traffic across the same publisher base fell 36%, but revenue fell by much less, because the readers who remained converted at a higher rate than before. Average new-subscription revenue per search visitor rose 31%.

Less traffic doesn't have to mean proportionally less money.

That's a meaningful shift, because for years, a publisher's success was measured mostly in users and pageviews. Increasingly, the more important question is how many of those users come back, how often they engage, and whether there's a reason for them to stay.

The most valuable reader isn't the one who clicks the most

The same Piano data shows a sharp split between two kinds of search visitors. The first are casual readers - people who land on a single article from a specific search and typically never return. They made up nearly half of all search traffic across the publisher base. But they accounted for only 0.3% of new subscription revenue, and their average revenue per reader was under 20 cents.

The second group are highly engaged readers - people who come back to a publisher regularly, read widely, and treat that outlet as a recurring source of information. This group is far smaller in raw numbers, but generates a disproportionate share of subscription revenue. Its share of search traffic changed far less in 2025 than the casual group's did - meaning it was largely insulated from the broader traffic decline.

In practice, a shift in search algorithms can look far worse in traffic charts than it does in revenue. Thousands of casual visits disappear, but a large share of them were never worth much in subscription terms to begin with.

For a publisher, the more important question stops being "how many users do we have?" and becomes "how many of them have a reason to come back?"

That shifts the focus from pure traffic acquisition toward relationship-building. A newsletter, a reader account, personalized recommendations, or a direct return visit can matter more than a single search click.

In Piano's 2025 data, direct traffic - readers typing in a URL directly or using a bookmark - overtook search traffic's share for the first time, and traffic from aggregators, including Google Discover, also grew.

Digiday: registration as the bridge to a subscription

A smaller, specialized publisher shows this shift clearly. Digiday is a New York-based trade publication covering media, marketing and advertising. It launched in 2008 with what Wikipedia's own entry on the outlet describes as "optional registration" for most of its history - readers could browse freely, register, or do neither.

In 2019, Digiday explained its own strategy shift directly to readers. Rather than putting up a hard paywall, it expanded its existing membership program, Digiday+. Non-members would be capped at a small number of free articles - typically around four - while members got unlimited access, original research, and event perks. The company noted it had built this into a profitable, roughly 80-person media business without venture capital backing.

The first currency doesn't have to be money. It can be consent to further contact.

This matters especially for trade and specialist media. If a reader works in marketing, advertising or media, their value doesn't have to come from how many articles they've read - it can come from simply being part of a specific professional audience that advertisers and business partners want to reach. That's part of why Digiday built its membership tier around research, events and daily briefings, not just article access.

Not every registered reader becomes a paying subscriber. But every registered reader stops being anonymous - and that's already a starting point for a longer relationship.

Google leaves publishers room to decide how much to show

Discussions about paywalls often get reduced to a choice between protecting content and staying visible on Google. In practice, the system is more flexible than that framing suggests.

Google lets publishers decide for themselves how much of a locked article a casual search visitor sees before hitting a paywall. A publisher might give every reader a handful of free articles per month before restricting further access - Google itself suggests a starting point of roughly 6 to 10 articles a month, recommending publishers start near the higher end and test how tightening that limit affects traffic and conversion over time. A publisher can also choose to show only an opening excerpt - a few sentences, sometimes called a lead-in - instead of cutting a reader off completely once they hit the limit. Google treats this as good practice, since even a short excerpt gives a reader some value and can build curiosity that helps conversion, rather than simply presenting a wall. Google doesn't mandate any particular approach here - it leaves the decision to the publisher, as long as paid content is properly labeled.

This also affects visibility in search results: the more of an article Google can actually read and index, the better it understands what the piece is about, and the easier it is to surface it to the right searcher.

Google also pays attention to the experience of readers who aren't subscribers yet. Its own documentation for publishers states that reader satisfaction starts dropping noticeably once a paywall blocks access more than roughly 10% of the time - and Google explicitly advises against approaching that threshold without testing first, since that's the point where a publisher risks losing readers who haven't yet had a chance to see the value of the content.

A paywall can be more effective when most readers never actually encounter it - and only run into it when they're genuinely interested in that specific piece of content.

For a publisher, that means distinguishing between someone who stumbled onto a single article and a reader who consumes content regularly. For the second group, the barrier can reasonably appear sooner, since the odds they'd be interested in a subscription are higher.

The paywall is also a technical problem

How a paywall is built has direct consequences for SEO.

Google requires publishers to clearly mark which part of a page is paid content. Structured data is the mechanism for that - specifically the property isAccessibleForFree. It tells the search engine that a piece of content is deliberately restricted, rather than simply hidden from readers while still being served to the crawler - which would otherwise look like deception.

In practice, this is straightforward to set up. A publisher wraps the paid portion of an article in its own CSS class - say, .paywall - and then references that same class in the article's structured data. From that point on, Google knows exactly where the restricted content starts and ends, without having to guess.

Problems start when that labeling stops matching reality. Content that's actually free to everyone shouldn't be marked as paid, and vice versa - and the same labeling has to work identically across every version of the page, including mobile.

There's a more fundamental rule underneath all of this: a crawler and a reader have to see the same page.

If the full article isn't meant to be available before login, the publisher should choose an implementation that simply doesn't send that content to the browser at all - rather than sending it and hiding it with CSS. That second approach is called cloaking: Googlebot gets a different version of the page than an ordinary visitor, and Google treats that as a policy violation regardless of the publisher's intent.

A well-built paywall doesn't hide that content exists from Google. It restricts an ordinary reader's access to it.

After implementation, it's worth validating the markup - for example, with a rich results testing tool - and fixing any critical errors. Correct structured data is exactly what lets Google tell a legitimate paywall apart from cloaking, so a mistake here can cost an article its visibility entirely.

At large publishers, there's also the question of crawl budget. Thousands of new articles, category pages, filters and duplicate URLs create an environment where server performance and response time start to affect how efficiently a crawler can move through the whole site.

It's worth treating a paywall rollout as an SEO change, not just a business decision. That means separately tracking search traffic, individual article visibility, click-through rate, and what share of visits end at the paywall before a reader gets to read anything. Overly aggressive restrictions can hurt both user experience and search rankings - so it's better to roll changes out gradually and watch the effect than to set a limit once and forget about it.

The New York Times shows subscriptions can become the main revenue line

The U.S. market already has publishers for whom digital subscriptions aren't an experiment but one of the core pillars of the business.

The New York Times ended the first quarter of 2025 with 11.66 million net digital-only subscribers, after adding roughly 250,000 net subscribers in that quarter alone. Digital-only average revenue per user rose 3.6% year over year, driven largely by subscribers moving off promotional pricing onto higher-priced tiers. Growth in both subscriber count and revenue per user pushed digital subscription revenue up 14.4% year over year in that same quarter - and the company continued adding subscribers through every subsequent quarter of the year.

Digital subscription isn't a side project for a large publisher anymore. It's become the mechanism replacing the revenue print advertising used to provide.

That doesn't mean every outlet can copy this model. The Times has brand recognition, a large existing audience and scale that most publishers simply don't have. Digiday, described above, sits at the opposite end of that same problem - a smaller, specialized outlet for which a hard paywall would have been a risk, not an obvious choice.

A specialized outlet sells more than just an article

A general-news reader might show up for something they'll forget within days. A specialist publication can build value differently.

A reader might pay for data, analysis, expert commentary, tools, newsletters, or organized access to knowledge. The article becomes part of the product rather than the whole product.

The New York Times shows this even within a single subscription. Alongside news, the Times built NYT Cooking into a standalone paid product - a recipe database with step-by-step guides and its own app, launched free in 2014 and turned into a $5-every-four-weeks subscription in 2017, drawing over 10 million monthly users even before that shift. Today it sells separately for about $6 a month or $50 a year, but its bigger role is inside the Times' "All Access" bundle: executives have said repeatedly that subscribers who add Cooking, Games or other non-news products to their plan engage more, churn less, and pay more over time than a news-only subscriber does.

The more specialized the offering, the less sense it makes to treat a single article as the only thing being sold.

That's also an opening for smaller publishers. They don't need to compete with large outlets on volume or traffic if they can build a smaller but genuinely engaged audience around one specific, well-defined need - the way Digiday does within its own niche.

Not every publisher needs a complicated system

For the largest media groups, building sophisticated models that predict a reader's likelihood to convert can make financial sense. For a small outlet, the cost of that kind of system can outweigh the potential payoff.

That's part of why Google's Reader Revenue Manager is a useful option for smaller publishers - a tool that lets an outlet launch paid subscriptions or voluntary contributions without building its own payment infrastructure from scratch. Google takes a 5% transaction fee.

That lowers the barrier to entry considerably. A small newsroom can first test whether readers are willing to pay at all before investing in anything more elaborate.

For a small outlet, simplicity can be an advantage rather than a limitation.

 Substack is the clearest example of that kind of simplicity, and it's become impossible to ignore on the U.S. market. The platform lets a writer publish a newsletter with a free and a paid tier, handles billing through Stripe, and takes a flat 10% cut of whatever a writer charges. No separate infrastructure, no negotiation.

By early 2025, Substack had crossed 5 million paid subscriptions across its writers, with the platform's own creators collectively earning roughly $450 million a year in gross revenue. Some of that is concentrated at the very top. Historian Heather Cox Richardson's newsletter, Letters from an American, has more than 2.5 million subscribers and, by outside estimates, over 200,000 paying - enough to outearn most newsroom editors on a single email a night.

But most writers on the platform earn far less, and the typical paid publication charges around $5 a month or $50 a year - a price low enough that a reader can subscribe to several without much friction.

What Substack shows at scale, a lot of small U.S. newsrooms have started doing individually: skip the custom subscription system, charge a simple flat monthly or annual rate, and let the writing carry the sale.

Medium takes the opposite bet: one paywall, thousands of writers

Substack lets each writer set their own price and their own wall. Medium does the reverse - it runs a single, platform-wide paywall, and individual writers opt into it rather than build their own.

Readers get a handful of free articles a month; unlimited access costs $5 a month or $50 a year, with no ads anywhere on the site. A share of every reader's subscription fee is then split among the writers whose paywalled stories that reader actually engaged with - based on how long they read, not on traffic alone. A writer never sets a price or manages billing. They simply mark a story as members-only and let Medium's pooled subscription revenue do the rest.

That's a genuinely different answer to the same problem this whole piece has been circling: who decides what a reader pays for, and how directly is that tied to one specific piece of writing. Substack ties it directly - one writer, one price, one relationship. Medium pools it - thousands of writers sharing one reader base, with individual earnings shaped by engagement rather than a subscription of their own.

Neither model is "the" answer. They're two different bets on the same basic question: does a reader pay a writer, or pay into a pool that writers draw from?

What about the reader who won't pay?

Not every user becomes a subscriber. That doesn't automatically mean they stop being valuable.

Some publishers are experimenting with rewarded ads - a model where a reader unlocks a piece of gated content by watching a short ad instead of paying directly. In this setup, the money doesn't come from the reader at all. The publisher is selling an advertiser something else: a moment of attention and a chance to engage that reader directly.

That's an interesting direction precisely because it doesn't try to turn every reader into a subscriber.

A gentler version of the same logic shows up on platforms built around direct, voluntary support for creators, like Patreon. You're Wrong About, a journalism-driven history podcast, funds its production this way, drawing tens of thousands of supporters who pay a small monthly amount directly to the hosts - proof that with a genuinely engaged audience, this kind of model can support a real ongoing production team.

The hardest case is local news

The toughest challenge belongs to small, regional newsrooms. They don't have the scale of large outlets, their local ad market is limited, and they're often competing against free content produced by publicly funded local government sources.

In that situation, a hard paywall can be too risky. If an outlet doesn't already have a large audience and a strong brand, simply locking articles doesn't automatically create a willingness to pay.

That's one reason subscriptions are just one piece of a larger puzzle at small outlets. Alongside them, sponsored content - commissioned by local businesses and institutions, often through ad platforms that connect publishers with advertisers such as Ads4Media - sits next to grants, donations, and event revenue.

It's worth noting that the choice between paid access and registration doesn't have to mean building a separate, expensive system from scratch. Our CMS 4media includes a built-in Paywall and Registration Wall module, where a publisher decides which content to restrict, whether access requires payment or just registration, and how much material a reader sees before hitting that wall - without building any of it in-house.

A local publisher can't just copy a major newspaper's model. It has to assemble revenue from several smaller sources at once.

The biggest shift might come from search itself

Until now, Google has served publishers in two ways at once. It delivered traffic, and it helped readers discover a brand in the first place.

The growth of AI-generated answers complicates that arrangement. A reader can get an answer to their question without ever visiting the source site, and the publisher can lose the moment where it might have shown an ad, invited a newsletter signup, or nudged someone toward registration.

That threat has a concrete face now. In September 2025, OpenAI launched ChatGPT Pulse, a feature that researches overnight and delivers a personalized morning briefing. Each day it produces a handful of visual cards, built from a reader's chat history, saved memory, and - if connected - their calendar and inbox. It's explicitly modeled on the habit publishers have spent years trying to build: open an app first thing in the morning and get caught up on what matters to you.

One journalist covering the launch put the question bluntly: can this replace your morning newsletter? The difference is that Pulse's "newsletter" has exactly one subscriber. It's written by a model instead of an editor. And it cuts the publisher out of the loop entirely - no click, no ad impression, no registration prompt, nothing for a newsroom to convert.

There's a second problem buried inside the first one: what a reader gets back from an AI tool isn't always reliable, and few examples make that clearer than shopping. The Business of Fashion analyzed how ChatGPT, Claude and Gemini recommend sustainable clothing brands and found that a brand's online reputation and how a shopper phrased the question mattered more to the chatbot's answer than the brand's actual environmental record. In practice, that means a chatbot can recommend a brand that's simply good at talking about sustainability - a pattern regulators call greenwashing - over one that's actually doing the harder, less marketable work.

That finding cuts both ways. If a model is mostly reading what's already been written about a brand rather than verifying what a brand actually does, then being written about - clearly, repeatedly, in places a model is likely to pull from - stops being a nice-to-have for that brand. It becomes close to a requirement. A brand with no coverage, no reviews, no press, is effectively invisible to a chatbot regardless of how sustainable its supply chain actually is. Media coverage isn't just a shopper's discovery layer anymore; it's the training signal for how AI describes a company at all.

That matters for publishers too, not just shoppers. Specialist and trade outlets have spent years building the kind of editorial authority that's supposed to cut through exactly this kind of noise - vetting claims, checking sourcing, calling out greenwashing when they see it. If an AI tool skips that layer and answers straight from a model's read of brand reputation, the publisher doesn't just lose a click. It loses the one thing a subscription was supposed to be worth paying for in the first place: a source a reader can actually trust.

At the same time, Piano's data suggests that readers arriving via AI tools are currently few in number but potentially high in value. In December 2025, they accounted for just 0.23% of all conversions across the publisher base Piano tracks, but their average revenue per reader was $15.50 - compared to $3.36 for an ordinary search visitor.

The scale here is still small, so it's too early to call this a breakthrough. But the direction is worth watching, especially as tools like Pulse specifically target the daily-briefing habit that newsletters were built to own.

How many readers land on a page is becoming less important than the intent they arrive with.

That also changes what a paywall is for. A reader who lands on a specific, deliberate question can be worth more than someone who happened to open five articles off a homepage.

In that context, the newsletter-and-registration approach described above through Digiday's example gains extra weight. A publisher that knows a reader by name and email doesn't have to rely entirely on where that traffic came from - a classic search result, an AI-generated answer, or a briefing tool that never sends a reader to the source at all. It can simply reach that reader directly.

The paywall is no longer a wall

Publishing is shifting away from a simple free-or-paid choice toward multiple ways of monetizing the same attention. One reader might be monetized through ads, another through registration, a third through a subscription, a fourth through voluntary support, and a fifth through access to a specialized product - a paywall is just one of a broader set of ways to monetize a news site, alongside ads, affiliate networks, and sponsored content.

That also means there's no single correct paywall. A different model makes sense for a large general-news outlet than for a business publication, a specialized trade outlet like Digiday, or a small local weekly.

The shared problem stays the same: finding the right balance between how much content to leave open and how much is actually worth restricting.

The best paywall doesn't need to cover most of a site. It just needs to reach the right readers with the right offer - the ones who actually have a reason to pay.

That might be the most important shift happening in how online publishers make money today. A publisher isn't just fighting for the largest possible audience anymore - it's fighting for a relationship with a reader who has a reason to come back, register, and eventually pay.

And in a world where earning attention through search alone keeps getting harder, that relationship might be the most valuable asset a publication has.

Those are important corrections to the original proposal. They also reveal a persistent missing middle.

An outlet below A$150,000 has a grant route. A large publisher has negotiating staff, legal resources and scale. Between them sit established local organizations that are too large for the smallest-publisher grant but still too small to bargain with a global platform on equal terms.

If a platform pays the charge, the statutory distribution formula may reach some of those outlets. If the platform pursues direct agreements instead, the multiplier makes them attractive but still does not give them a seat at the table.

Australia closed Meta’s escape route

The new law is a response to a weakness exposed by Australia’s earlier News Media Bargaining Code.

That code helped produce more than 30 commercial agreements, reportedly worth roughly A$250 million a year. Then Meta stopped renewing its Australian news deals and discontinued Facebook News in Australia in 2024. Under the earlier structure, removing news could also remove the reason to bargain.

The News Bargaining Incentive closes that exit. The charge is tied to covered digital advertising revenue, not to whether a platform chooses to carry news. A platform cannot make the obligation disappear simply by taking news off its service.

It can, however, choose to pay rather than negotiate.

That choice determines what the mechanism becomes in practice. If platforms sign a broad range of meaningful agreements, the law operates as an incentive for commercial cooperation. If they pay the charge and keep publishers at arm’s length, it operates more like a sector levy with a journalism distribution program attached.

Both outcomes produce funding. Only one produces a working relationship.

The U.S. is testing a different route

There is no national American equivalent to Australia’s new charge. Federal efforts to create a collective bargaining framework for publishers have repeatedly stalled, while states have moved toward programs that subsidize newsroom employment or civic information more directly.

New York’s Empire State Newspaper and Broadcast Media Jobs Program makes up to $30 million a year available through refundable credits for retaining and creating newsroom jobs. Half of the annual allocation is reserved for businesses with 100 or fewer New York employees.

Illinois uses a smaller but more tightly defined program. Its $5 million annual Local Journalism Sustainability Tax Incentive Program offers a $15,000 refundable credit for each qualifying journalist retained and another $10,000 for a new position. Eligibility turns on concrete local-news indicators: original public-interest reporting, a journalist working at least 30 hours a week and living within 50 miles of the coverage area, ownership disclosure and, for digital-only outlets, at least one community story per week plus an Illinois audience threshold.

Demand itself offers a lesson. Illinois reports that its 2026 allocation for retained-journalist credits is already fully committed, while credits for net-new positions remain available. An early implementation review found that smaller organizations could qualify, but paperwork, limited administrative capacity and payment delays still created barriers. Funding a job that exists and inducing a publisher to add a job are not the same policy problem.

California is considering another version. AB 2222, which reached the state Senate in an amended form in August, would provide refundable credits of up to $20,000 for each of a publisher’s first five qualifying full-time journalists, with separate amounts for additional, part-time and newly created positions. It is still a bill, not money a publisher can put in the budget. We examined the architecture and the caveat in The $20,000 Reporter.

The contrast with Australia is useful:

The American programs define the newsroom, employee or civic outcome first and then direct support toward it. That can target local reporting more precisely. Australia starts with the platform’s contribution and then creates two possible routes for the money: negotiated deals or statutory distribution.

The U.S. could eventually combine those strengths. A serious national model would guarantee a contribution, publish transparent distribution data, protect a meaningful share for independent and regional publishers, and let smaller outlets bargain collectively rather than approach global companies one by one.

The number of agreements should never be the only success metric. Policymakers and publishers need to know the value distribution, ownership profile, geography and newsroom employment supported by those agreements.

A payment buys runway. It does not build a business.

There is a temptation to treat any new policy dollar as the missing business model. It is not.

A platform agreement, employment credit or grant can keep a reporter on payroll. It cannot make readers return, convert anonymous traffic into a known audience, sell a local advertising campaign or turn strong reporting into recurring revenue. Public policy can lower the cost of journalism. The publisher still has to build the other side of the equation.

That is why the operational lesson matters as much as the legislative one. We made the same point in The $129 Million Scaffolding: institutional support rewards publishers that can document what they are, execute a campaign and handle new funding without creating a workflow bottleneck.

The infrastructure should also help the newsroom outlast the support. A Paywall and Registration Wall can turn selected reporting into subscription revenue or first-party reader relationships while leaving other coverage open. Within CMS4media, that capability sits inside the same publishing environment as the content it is meant to sustain.

The point is not that every local outlet should lock every article. It is that a temporary inflow should finance permanent capacity: better reporting, a stronger owned audience, cleaner reader data and more dependable revenue.

What American publishers should watch next

Australia’s headline number will be easy to follow. The more revealing evidence will take longer.

Watch how many platforms choose direct deals instead of paying the charge. Watch how much of the deal value reaches independent and regional publishers—not merely how many names appear on a list. Watch whether the small-publisher grants and the statutory distribution arrive quickly enough to affect newsroom employment. And watch how much disclosure the system produces around confidential commercial agreements.

Most of all, watch the missing middle. If established local publishers still cannot enter meaningful negotiations, the 200% multiplier will have improved the math without fixing the market.

Australia can now make Big Tech contribute to journalism even when a platform does not carry news. That is a genuine policy advance, and American lawmakers should study it closely.

But payment is an input. Distribution is a policy choice. Sustainability is still a business model.

Before signing it, ask one question: what will a machine be able to read afterward that it cannot read today?

For many publishers with open, crawlable article pages, the answer is: not much. Modern search and AI systems can already parse ordinary web pages. The real problem is not whether a model can enter the archive. It is whether the model — or a human reader — can identify what is in there, who reported it, when it happened and how one story connects to the next.

This is why the New York Post’s new AI product matters even to a local newspaper with no AI budget: it reveals that the quality of the answer begins with the quality of the archive.

What Hamilton actually does

On August 11, 2026, New York Post Media Group launched Hamilton inside the New York Post and California Post apps. Built with Google Cloud’s Gemini Enterprise Agent Platform, Hamilton combines conversational search, personalized news briefings, recommendations and notifications.

The conversational search is the part local publishers should study. According to A Media Operator’s reporting, it searches five years of the publisher’s archive at launch, answers questions in plain language and cites the Post articles behind each answer. Newly published stories can be ingested and made searchable within seconds, Axios reported.

The boundary is deliberately narrow. New York Post CTO Ariscielle Novicio described the rule given to the system this way: “If we don’t write about it, do not even try to answer.”

Hamilton does generate conversational answers and personalized digests, so it would be inaccurate to say the software writes nothing. What it does not do is original reporting or independent editorial judgment. The Post controls the source material and editorial boundaries; the model retrieves, organizes and presents journalism the newsroom already produced.

Even one of Hamilton’s least glamorous components makes the same point. The Post built a caching layer so thousands of similar reader questions do not create thousands of fresh, paid model calls. The visible product is AI. The work underneath it is information architecture, cost control and editorial discipline.

Readable is not the same as useful

There is an important qualifier to the claim that an archive is already AI-readable. Its pages must actually be accessible under the publisher’s chosen terms. A broken URL, an accidental noindex, a login wall or content rendered in a way a crawler cannot retrieve is still a locked door.

“Readable” also does not mean “free to train on,” “licensed for reuse” or “available to every model.” Access, licensing and technical readability are different questions, and publishers should decide each of them deliberately.

Once a system has legitimate access, however, another problem appears. What happens when almost everything has been filed under one category called “News”? What can it establish about provenance when the byline on thousands of stories says only “Staff”? What does it learn from a photograph with no caption, no alt text and a filename such as IMG_4827.jpg?

At 4media, this is a recurring pattern during newspaper migrations. Inside the disorder may sit 20 or 30 years of the only continuous record of a town: elections, school boards, floods, business openings, obituaries, high-school championships and the people who shaped the community.

Usually, nobody made one disastrous decision. The disorder accumulated one deadline at a time. A broad category was faster than choosing the right one. “Staff” was easier than maintaining author accounts. Captions and tags felt optional because the article still looked fine when it went live. Two decades later, those shortcuts have become the architecture of the archive.

An AI interface does not repair that history by appearing above it. It exposes the condition the archive was already in.

Google is not asking for a second, AI-only website

Google’s current guidance for generative AI features in Search is unusually direct: the foundations of visibility in AI search are still the foundations of SEO. Google recommends valuable, non-commodity content, a clear technical structure and pages its systems can crawl and understand. It says there is no special schema.org markup required for generative AI search and advises publishers to evaluate supposed AEO or GEO services against the same established SEO principles.

That matters because “AI readiness” is already becoming a label that can be attached to almost any service. A new text file, a block of machine-generated FAQs or a promise to “chunk” every article for an LLM may sound advanced without improving the underlying journalism at all. Our analysis of whether AI systems actually use llms.txt found the same gap between adoption and evidence.

Seven fields that decide what the AI finds

The durable work is less fashionable:

1. Specific categories and consistent tags. “News” is a container, not a useful description. Geography, institution, beat and recurring topic labels give retrieval systems meaningful ways to narrow a search.
2. Named authors with real profile pages. Google’s people-first guidance encourages clear bylines and information about who created the content. E-E-A-T is not a single ranking factor or score. It is Google’s framework for thinking about experience, expertise, authoritativeness and — most importantly — trust. CMS4media’s Authors module connects a byline to a profile, biography and the writer’s other work.
3. Reliable publication and modification dates. An AI assistant trying to reconstruct a mayoral race or storm response needs to understand the sequence of events. Silent date changes and missing update notes turn a timeline into guesswork.
4. Captions and descriptive alt text. A photograph is part of the reporting. A vision model may be able to guess what an old image shows, but it should not have to guess who is pictured, where the photo was taken or why it matters. Captions preserve editorial context; alt text makes the page more accessible.
5. Stable URLs, canonical signals and honest redirects. A citation is only valuable if it still resolves to the story it names. Our guide to redirects and HTTP status codes for news archives explains why sending every retired article to the homepage creates confusion instead of preserving value.
6. Article-level structured data. Google says Article and NewsArticle markup can clarify a story’s headline, author, images and publication dates. It is not a magic ranking switch and not special AI markup. It is a consistent description of what is already on the page.
7. Source relationships and internal links. A developing story is rarely one URL. Links between the first report, public records, corrections, follow-ups and analysis give both readers and retrieval systems the surrounding record.

None of these fields can turn thin reporting into authoritative journalism. They do something more practical: they stop authoritative journalism from disappearing inside its own database.

The archive should work before the chatbot arrives

Hamilton is an audience product, not merely an archive demo. The New York Post team says it is moving beyond raw pageviews to measures such as visit frequency, session depth, retention, conversion and reader lifetime value. That is the right test: not whether an AI answer looks futuristic, but whether it helps readers build a deeper relationship with the publication.

A local publisher can start extracting the same kind of value without building a conversational assistant. Old reporting should appear beside current reporting. A reader following a new zoning dispute should be able to reach the original development proposal, earlier council votes and the reporting on the officials involved.

The Related Articles module in CMS4media, for example, can resurface stories by category or tag. That helps a human reader today and rewards the same classification work a future retrieval system will depend on tomorrow.

The migration is another decisive moment. In a recent CMS4media project, Hartmann Media Consulting moved six local news portals. On its larger sites, the work included years of articles, photographs and metadata, followed by redirect cleanup, indexing checks and Search Console monitoring. An independent audit cited in our migration case study found that organic search traffic held steady while Google Discover grew by close to 41 percent and Google News by 14.9 percent.

This is what responsible archive work looks like: preserve what has value, map the old URLs, expose technical problems and measure what happens after launch.

No responsible CMS can reconstruct a missing byline or invent a reliable caption for a photograph whose context has been lost. What it can do is preserve the information that still exists and make better habits easier from this point forward.

CMS4media’s AI Assistant, for example, can help editors fill repetitive fields such as titles, introductions and SEO descriptions from the reporting they have already entered. It can reduce the daily friction that caused metadata to be skipped in the first place. The newsroom still reviews the result. AI should help maintain editorial structure, not substitute for it.

Ask vendors three questions, not one

Soon every CMS vendor will say it has AI. Most will be telling the truth. The label will therefore tell publishers almost nothing.

Ask instead:

1. What have you already built and migrated? Look for live publishers, intact archives, working author records, stable URLs and measurable post-migration results.
2. What are you building now? A roadmap should solve problems editors and publishers can recognize, not simply follow the vocabulary of the latest keynote.
3. How is the next roadmap decided? At 4media, regular conversations with publishers and patterns in real support requests shape what we build next. That process matters more than the number of AI logos on a sales slide.

Your archive may need cleanup. It may need a careful migration. It may need better taxonomy, author records, captions, redirects and structured data. Those are real projects, and some require serious work.

What it probably does not need is an expensive costume called “AI readiness.”

The New York Post did not make five years of journalism valuable by placing Hamilton in front of it. Hamilton made the existing value easier for readers to reach. For a local publisher, the order of operations should be the same: protect the reporting, organize the record and make every source easy to retrieve. Then decide which new door you want to build into it.

Metadata will never be the most exciting line in a press release. It still runs the show.

But what happens when a new resident moves to town and asks ChatGPT or Google’s AI Overview, "Who is the most reliable plumber near me?"

If the AI can’t verify your existence across multiple trusted sources, to the machine, you simply do not exist. You will not be recommended.

The digital foundation of many local business organizations is showing serious cracks. Anecdotal evidence and industry observations suggest that across various states, local chamber directories often suffer from broken links, outdated platforms, or missing websites altogether. When a directory listing points to a defunct address or an unverified subfolder, it represents a catastrophic failure of local verification in the AI era.

The New Math of AI Local Search

When a large language model (LLM) decides whether a local business is real and worth recommending, it doesn't just read your website. It looks for consensus across sources it has been trained to trust. The big three are typically:

1. Google Business Profile
2. The local newspaper
3. The local Chamber of Commerce directory

Chamber listings rank among the highest authority local citations available. They are a definitive signal of legitimacy—one of the few that an automated SEO service cannot fake for you. This aligns perfectly with Google's emphasis on E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness). A verifiable link from a recognized local authority is a powerful trust signal.

The stakes are incredibly high. Data from SOCi, a leading local visibility platform, reveals a harsh reality: currently, only 1 in 80 local businesses ever get named when someone asks an AI for a recommendation.

With an estimated 80% of U.S. consumers searching for local businesses online every week, failing to appear in AI-driven discovery is a massive lost opportunity. AI visibility is exponentially harder to win than traditional map pack rankings, and it demands flawless consistency across trusted local data sources.

Verification Infrastructure, Not Just a Perk

This paradigm shift means a Chamber directory is no longer merely a "membership perk." It is critical verification infrastructure for every business in the county.

If a Chamber’s listing is a static PDF, or if the Chamber's own web address resolves to a broken link or an unverified free blog page, it is failing to vouch for its members at the precise moment a machine is deciding whether they exist.

This lack of digital discoverability couldn't come at a worse time for some regions. Southern Nevada, for example, recently experienced some of its slowest visitation periods and casino revenue dips since the pandemic recovery began in 2021. When foot traffic is down and macro-economic factors compress margins, local businesses rely even more heavily on digital discovery to capture remaining demand. It is a very bad year to be hard to find.

Building What the Machines Trust

The solution lies in robust, localized digital platforms that prioritize structured data, first-party control, and unshakeable authority.

Just as local newsrooms must build direct relationships with their audience to survive the AI transition (as discussed in our recent piece, Google’s "Velvet Rope": What New Search Profile Thresholds Mean for Local Publishers), community organizations must build infrastructure that AI engines can seamlessly read and trust.

This is why modern publishing systems are adapting. The technology required to power a trustworthy local news site is the exact same technology required to power a trustworthy community directory.

Platforms like 4community (an adaptation of the CMS4media infrastructure designed for publishers) are built specifically to solve this problem. Used by organizations like the White Pine Chamber of Commerce in Ely, Nevada, this system provides:

• Structured, verifiable directories: Ensuring every member business is presented in a way that AI models recognize and validate.
• High-authority domain structures: Moving away from third-party subfolders to owned, authoritative domains.
• Integrated local ecosystems: Connecting local news, business directories, and community classifieds into a single, trusted web of local information.

The Ultimate Test

The test for local legitimacy is no longer a manual search. It is a prompt.

If you run a local business organization, try it yourself. Ask ChatGPT, Claude, or Google’s AI: "Who should I call in [Your Town] for a plumber, an accountant, or an insurance agent?"

If your dues-paying members are not in the answer, your digital infrastructure is failing them. In the platform era, authority isn't just about who you know in town; it's about whether the machines can verify that you know them.

Here's the problem: given how search actually works today, that instinct backfires. Search engines read a blanket redirect-everything-to-homepage move as a technical error, not a save. The result isn't preserved rankings — it's lost rankings and wasted crawl budget.

This piece walks through the HTTP status codes that matter for a newsroom, one at a time, with the kind of real-world scenarios editorial teams run into constantly. You'll see what separates a permanent redirect from a temporary one, and when it's actually better to just tell visitors — and search engines — that a page is gone for good.

We'll also get into how AI systems handle these same codes, because that's turned into a different game entirely.

Status 200 (OK): The State Everything Should Be In

Let's start with the basics — status code 200.

It's the simplest possible message: everything worked exactly as it should. The server tells the browser and the crawler, "here you go, the page is ready."

This is the state you want for every URL on your site.

Articles, the homepage, category pages — all of it should return this code. No technical friction. The reader sees the content instantly, and the crawler indexes it without any obstacles.

Take a simple example: someone clicks a link to yesterday's game recap. The page loads normally, the content is there, the response code is 200. Nothing else needs to happen — and that's exactly the point. Traffic flows without friction because there's no intermediate step where anything could go wrong.

Status 301: The Classic That Preserves Your Link Equity

Now for status 301 — probably the best-known status code in SEO.

It's a clear statement: this content has moved to a new address, permanently. Used correctly, it's a genuinely powerful tool.

When you serve a 301, you're giving the search engine a specific instruction: forget the old link, replace it with the new one in the results. A crawler that had previously indexed the old article URL starts treating the new URL as the true home for that content — and that's the version that shows up in search results going forward.

But that's not all a 301 does. It also carries forward the SEO value that old URL built up over time. Picture an article from five years ago that dozens of other sites have linked to — blogs, other newsrooms, industry forums. Each of those links functions as a kind of trust vote in Google's eyes. A 301 makes sure those votes don't disappear along with the old URL — they carry over to the new one.

That's why 301s show up in a few specific situations. First: restructuring your URL scheme, say when a site moves from a clunky, technical URL format to something cleaner and more SEO-friendly. Second: fixing a typo in a headline that forced a change to the URL itself. Third: migrating an entire publication to a new domain, where every old URL needs a matching address on the new site. Fourth: merging two short, archival stories about the same event into one more complete article — you'd redirect both old URLs to that new, combined piece.

That power is exactly why so many damaging myths have built up around the 301 — and the biggest one is the idea that a 301 works like a universal patch: slap it on any dead URL and the problem disappears. In practice, a 301 only carries link equity forward when the new page genuinely continues the topic of the old one. Redirecting a deleted sports story to a homepage full of political news doesn't save anything — which brings us to the mistake covered next.

Why Redirecting a Deleted Story to the Homepage Is a Mistake

Newsrooms are terrified of blank pages and 404 errors.

That fear is where a bad habit comes from: delete an article from the archive, and the system automatically bounces the reader to the homepage. The logic seems sound — preserve the traffic, hold onto the link equity.

To Google, though, this is completely illogical behavior.

Picture someone searching for results from a local election a decade ago. They click the link and land instead on today's homepage with the weather forecast. Something feels off immediately.

Google recognizes this pattern easily. When it sees that the destination content has nothing to do with the original, it treats the redirect as deceptive — and triggers a defensive response.

The industry term for this is a soft 404 — because the page technically returns a 200 status ("OK"), but the content isn't actually what the user asked for.

The result? All the link equity you were trying to save simply doesn't transfer. It gets stuck halfway there.

The rule is simple: a 301 only makes sense when the new URL genuinely answers the same question the old one did.

Redirecting an old sports story to a new sports story on a similar topic — sure. Redirecting that same story to today's general news homepage — no.

Status 302, 307, and 308: Temporary Redirects and the Password Problem

Sometimes you need to route traffic elsewhere, but only briefly — during an outage in one section, or while testing a new layout.

For years, 302 was the tool for this: a temporary move. The message to the crawler was, "don't forget the old URL, it's coming back soon."

But it had a real technical flaw, one that was especially painful for subscription sites.

When a reader logged into their paid account and the system quietly ran a 302 redirect behind the scenes, older browsers could actually lose the submitted form data along the way. Take a concrete case: a reader fills out the login form, hits "sign in," and the system redirects them back to the article via a 302. Somewhere in that handoff, the login and password data could get dropped. The result: the reader has to type everything again, or just sees a login error — frustrating, especially for paying subscribers.

That's why newer standards emerged: 307 (temporary) and 308 (permanent). They behave the same way 302 and 301 do from an SEO standpoint, but they have one important advantage.

They never lose submitted data. Period.

When a reader submits a password through a payment gateway, 307 guarantees it reaches the new address safely, with no risk of anything getting lost along the way. Google trusts these codes fully, so it's worth making sure your engineering team uses them anywhere data is being submitted — logins, payments, forms.

Status 404: An Empty Page Isn't a Disaster

The internet's most famous status message: 404.

It simply means the server couldn't find the requested page. A persistent myth in marketing circles is that every 404 is a nail in the coffin for your Google rankings.

That's one of SEO's more stubborn myths.

The web is alive — articles get published and eventually disappear, and dead links are a completely normal part of running any large site. Google understands this and doesn't penalize you for cleaning up your archive.

There is a catch, though, and it matters for large publishers in particular.

When a crawler hits a 404, it assumes this might be temporary — maybe an admin is about to fix the link. Take an example: a site removes an old story about a water-main break from three years ago. The crawler hits a 404 and, instead of considering the matter closed, comes back to check that same empty page month after month — just in case the content returns.

That's crawl budget being wasted on something the crawler could be spending on more useful work, like indexing today's articles.

If your site is dealing with an indexing problem more serious than the occasional stray 404 — say, Google isn't seeing your site at all — that usually points to a deeper crawling or indexing issue worth auditing separately.

Status 410 (Gone): The Tool That's Easy to Overlook

There's a second code for the exact same situation as a 404 — but with a very different meaning attached.

A 410 differs from a 404 in one key way. It doesn't say "I couldn't find this." It says, plainly, "this was intentionally removed, and it isn't coming back."

That's a very specific signal to anything crawling your site.

When a crawler hits a long-deleted story about a local traffic accident and gets a 410 instead of a 404, it registers that decision and stops coming back. If the content is gone permanently, there's no reason to check again next week, next month, or next year.

That's a real benefit for the entire site.

The crawl budget a search engine spends scanning your site stops getting wasted on dead URLs. Instead of circling back to old, empty pages, crawlers get to your five-minute-old articles that much faster.

For news publishers, this often determines whether you show up in Google News at all.

Don't Forget the Human Who Actually Sees This Page

There's one thing that's easy to overlook when you're building out a page for deleted content.

Returning the right error code for the crawler is one thing. What that page looks like to an actual reader is a completely different problem. Nobody wants to land on a bare white page with a technical error message — that's the fastest way to lose someone for good.

It's worth building a dedicated, friendly view for these cases.

Something on-brand, with a simple message: "this story has been moved to our archive because it's no longer current." Add a search bar.

Below that, surface a few of today's best stories.

That way, Google gets the signal to clear the link from its index, and the reader stays on your site instead of bouncing.

Status 451 and 418: The Law, and an Industry Joke

The HTTP vocabulary also has codes for some very specific situations.

One is 451 — it sounds grim, and that's intentional. The name is a nod to "Fahrenheit 451," the novel about book burning. This code shows up when a publisher has to take down an article for legal reasons.

A court order, a law enforcement takedown request, a copyright claim, state censorship — in any of these cases, independent outlets generally prefer to show a 451 rather than quietly delete the piece. It's a clear signal that the removal came from outside pressure, not an editorial decision.

For organizations tracking press freedom, that distinction matters.

A more amusing case is status 418 — a pure industry joke.

It was created more than twenty years ago, as an April Fools' gag. It literally means: "I'm a teapot, I can't brew you coffee." It was meant as a harmless joke among developers, with no real-world use.

Today, though, it occasionally gets a genuinely practical application.

News sites regularly fight bots that scrape content en masse. Picture a script hitting a server hundreds of times a minute, copying article after article into its own database. When a defense system catches that pattern, it can deliberately return a 418 instead of the actual page content.

The confused script often just chokes, unsure how to interpret the response.

Redirect Chains: Getting Lost Inside Your Own Site

Now that you know what the individual codes mean, it's worth looking at what happens when they stack up into long chains.

A publication grows over years — an SSL certificate gets added, section names change, the "www" prefix disappears. A link from 2011 jumps to a 2015 version, then 2018, and finally lands on the current URL.

That's a redirect chain — and it's the enemy of any optimization effort.

Every hop in that chain costs time. On a fast office connection you barely notice it, but a reader on a weak mobile signal sees a blank white screen for several seconds. Some of them will just close the page before it loads.

Google treats these chains just as unfavorably.

Per Google's own documentation: past ten hops, the crawler gives up. It stops following the chain, and whatever link equity you were trying to preserve evaporates along the way. That's why your technical team should keep the structure flat — old link straight to the final URL, no historical layovers in between.

Are All Redirect Chains Bad? A Few Exceptions

There are situations where a short chain makes business sense and doesn't hurt anyone.

The first is affiliate links. When you recommend a product, you route the reader through a server that logs the commission before they land in the retailer's cart. That's a deliberate, revenue-generating redirect, and search engines have no issue with it.

The second is access verification on subscription sites.

To check whether a reader has a paid subscription covering a given article, the system may need to briefly route them through a separate authentication service before sending them back to the article.

As long as that process is short and built on safe codes — like the 307 mentioned earlier — search engines don't see any red flags.

AI and HTTP Status Codes: A Different Set of Rules

Finally, it's worth looking at what publishers are up against beyond classic Google search these days.

The traffic numbers coming out of 2026 make that clear. Multiple outlets have reported steep, sustained drops in Google referral traffic since AI Overviews rolled out — enough that companies including USA Today's parent and Reddit have publicly discussed blocking Google's crawler entirely rather than keep feeding a system that sends them less and less traffic in return. Industry groups tracking member sites have documented year-over-year referral declines across both news and entertainment publishers, and the debate has moved well past "is this happening" into boardroom conversations about whether staying visible in Google is even worth the cost anymore.

That backdrop matters here because language models and generative AI search engines pull knowledge from news sites to serve users ready-made summaries — and AI bots handle redirects noticeably worse than Google's crawler does.

Back to the same example: a deleted story redirected to the homepage.

A classic search crawler will quickly spot the trick and disregard that URL. An AI bot tends to be far more credulous — it'll follow an old link to a deleted TV review, land on today's homepage featuring a political scandal interview, and simply merge the two as if they were connected.

The result? The model generates nonsense for the user, citing your newsroom as the source.

That's a fast way to burn reader trust in your brand — and at a moment when every newsroom is already fighting to hold onto whatever traffic and credibility AI systems leave them, that risk is harder to shrug off than it used to be. Therefore, using 410 honestly, wherever content is genuinely gone for good, is more than a technical best practice today — it's protection against misinformation that can spread across the web with your name attached to it.

A Few Questions Before You Hit "Redirect"

A large archive means constant decisions, and every one of them has a cost — in traffic, in team time, or both.

Knowing the 300 and 400 status code families isn't just an IT department concern. It's a strategic tool for anyone responsible for how a site shows up in search.

Before ordering another mass redirect of old topic sections, it's worth asking your team a few questions.

Does the new page genuinely answer the same question the old headline did?

Is a ten-year-old story about a long-forgotten local event still delivering any real value?

Would removing that content from the index via 410 free up crawl budget for fresher, current publishing?

If the answers point toward cleaning up the archive — do it. Build a proper error page, cut the dead links loose, and let the crawlers focus on what's actually current.

Imagine a local newspaper that has dutifully covered city hall for 70 years. It employs six dedicated reporters, maintains a robust historical archive, and is the lifeblood of its community’s civic information. Yet, under Google’s latest framework, it might fail the test to be recognized with a dedicated Search Profile.

Meanwhile, a food review account launched just last year can breeze past the velvet rope simply by holding a large Instagram following.

That is how Google Search Profiles work in the United States today. Marketed to creators, brands, and publishers, these profiles offer a substantial reward: a customizable space connected directly to Search and Discover. Qualifying entities get the chance to shape a Knowledge Panel, pin posts, add direct links, and let readers follow their source right from the search results page.

But the gatekeeper isn't journalistic rigor or local impact; it's social media followers.

The Follower-Weighted Era

Historically, the fundamental unit of the web was the page. Today, the platform era’s new unit is the audience account.

Initially, Google set the entry bar incredibly high: 100,000 followers on YouTube, Instagram, or X (formerly Twitter), or 300,000 on TikTok. While Google recently (August 2026) lowered these thresholds slightly for some platforms—dropping the requirement to 35,000 subscribers for YouTube, Instagram, and X (though keeping TikTok at 100,000)—the underlying philosophy remains unchanged.

This is follower-weighted legitimacy.

While Google explicitly states that creating a profile does not directly change search rankings, the implications for visibility are real. Users who follow a source via their Search Profile may see more of that creator's content surfaced in Google Discover.

For local publishers, this trend is a stark reminder: platforms evaluate worth through the lens of global scale, not local necessity. Google’s threshold tells us where its product is going. It should not tell a local newsroom what it is worth.

Why the Timing Matters (And What It Means for AI)

The push toward audience accounts comes at a critical juncture. As we've tracked in our recent coverage, including The Messenger Becomes the Author and Google Search Live and the End of Drive-By Traffic, publishers are facing an existential question: How much of our reporting should we keep feeding into AI search ecosystems as traditional referral traffic continues to fall?

Google is elevating social accounts to first-class properties inside Search Console, accommodating creators who might not even own a traditional website. This shift underscores a broader industry pivot: reliance on third-party platform traffic is becoming a losing game for hyper-local entities.

The Strategy for Local Newsrooms: Audience Sovereignty

Local publishers cannot afford to play by "national creator math." Instead, they need a two-pronged approach:

1. Claim Every Available Surface If your newsroom meets the new 35,000 follower threshold on a platform like X or Instagram, claim your Google Search Profile immediately. Optimize it, pin your best investigative work, and use it as a funnel. Play the game where you can.

2. Build What Platforms Cannot Revoke The ultimate defense against shifting algorithm thresholds is Audience Sovereignty. Local publishers must relentlessly build direct relationships with their readers.

This means prioritizing:

• Direct website readership
• First-party data collection
• Paid subscriptions and paywalls
• Owned newsletters

Platforms can change the rules of the velvet rope overnight. They cannot take away a loyal subscriber who visits your homepage directly or opens your morning email.

How CMS4media Supports True Independence

Building a sustainable local news model requires the right infrastructure—one that doesn't rely solely on algorithmic goodwill. This is where moving beyond a basic website to a comprehensive publisher platform becomes vital.

CMS4media is designed specifically to help publishers build that unshakeable direct audience.

• First-Party Revenue Streams: Rather than waiting for platform payouts, CMS4media allows publishers to easily implement Paywalls & Subscriptions, establishing a direct financial relationship with readers.
• Engagement Tools: Modules like the Content Hub and Quizzes keep readers on your site longer, turning casual visitors into habitual readers.
• Sovereign Monetization: With built-in features for a Classifieds marketplace, Business directory listings, and seamless integration with the Ads4media network, local newsrooms can diversify their revenue away from programmatic display ads and build local business partnerships.
• AI Efficiency: The built-in AI Assistant helps resource-strapped newsrooms optimize content for SEO and generate related materials quickly, ensuring that when you do compete for search traffic, your content is perfectly primed.

The Bottom Line

Google’s evolving Search Profiles are a fascinating tool for creators with mass appeal, but they expose a blind spot when it comes to the vital role of local journalism. A local publisher's worth is defined by the community it serves, not an arbitrary follower count.

By focusing on direct readership and utilizing tools designed for independent media growth, local newsrooms can ensure they remain the indispensable town crier, regardless of who is allowed past Google's velvet rope.

But as the standard has grown in popularity, the claims about it have gotten bolder. Some call llms.txt "robots.txt for AI." Others suggest it improves your odds of being cited by ChatGPT or Perplexity.

The problem is that opinions are multiplying faster than evidence.

Server log analyses suggest that most published files are barely ever fetched, and Google hasn't confirmed that llms.txt plays any meaningful role in its systems.

That gap between hype and evidence is exactly what makes llms.txt one of the more interesting topics at the intersection of SEO and AI right now. So instead of jumping straight to "does llms.txt work," it's worth looking at what we actually know. 

Where did the standard come from? What does its author actually propose? How are AI model providers responding to it? And does the available data really back up the narrative that's built up around it?

Where Did the Idea for llms.txt Come From?

The standard wasn't created by Google or OpenAI, and its origins have nothing to do with search engines.

It comes from Jeremy Howard, co-founder of Answer.AI and creator of fast.ai, who published the first version of the spec in September 2024.

Howard wasn't trying to invent a new ranking signal or an alternative to robots.txt. His starting point was a much more practical problem: modern websites are designed primarily for humans and browsers, while language models need the simplest possible path to the actual content that matters.

In the spec's description, Howard points out that a single web page often contains a huge amount of material that adds zero value from a model's perspective. Menus, footers, ads, JavaScript, banners, and heavy navigation all inflate the number of tokens needed to process a document, making it harder to reach the actual knowledge inside.

That observation is what led to llms.txt. The original goal wasn't SEO — it was making it easier for language models to find the most important content on a site.

The Problem Jeremy Howard Was Trying to Solve

The project's premise can be summed up in one sentence: since language models read the web differently than people do, maybe they need a different way to navigate it too.

Howard's proposal: a site owner writes a simple text file listing the site's most important resources, each with a short description. Instead of parsing the entire structure of a site, an AI agent gets a ready-made list of where to start.

That distinction matters. The spec doesn't propose replacing a site's existing structure or building a new indexing mechanism. The file is only meant to point to whichever documents the author considers most valuable.

You could say llms.txt proposes an additional layer of communication between a site owner and AI systems. Howard himself describes it as a guide to a site — not a new way of publishing content.

Is llms.txt an Official Web Standard?

Not yet.

This is one of the most commonly overlooked distinctions in discussions about llms.txt. Despite its growing popularity, the project hasn't been adopted by standards bodies like the W3C or IETF. That means it has no official status as a web specification, and implementing it is entirely voluntary.

That has real consequences. No AI model provider is obligated to read the file. No site owner is obligated to publish it. The whole project's success depends entirely on whether both sides find it useful.

That's what separates llms.txt from standards that eventually became a fixed part of internet infrastructure. Right now, llms.txt should be treated as an open proposal from the AI community — not a binding web standard.

What Does the llms.txt Spec Actually Look Like?

Simplicity was one of the project's core goals.

Per the spec, the file should live at /llms.txt in a domain's root directory. Its content is written in Markdown, not XML or JSON — a deliberate choice. Howard argues Markdown is one of the formats language models recognize best, since so much technical documentation is already written in it.

At minimum, the document includes a project name, a short site description, and sections grouping the most important resources with brief descriptions and Markdown-formatted links.

What the spec recommends against is just as telling. Howard doesn't suggest copying an entire sitemap or listing hundreds of URLs. The idea is the opposite: a short, hand-picked set of the most important materials. llms.txt is meant to read like a carefully curated table of contents, not an auto-generated list of every page on a site.

Why Isn't This Just Another sitemap.xml?

At first glance the two look similar — both contain links to pages. That's about where the similarities end.

sitemap.xml helps search engines discover URLs to crawl and index. In practice it often lists thousands of pages and is generated automatically by a CMS or SEO tool.

llms.txt does something completely different. It doesn't try to describe an entire site. It's meant to point to a small number of materials that, in the author's judgment, best represent the knowledge the site contains.

The difference isn't just technical — it's philosophical. A sitemap answers "what's on this site?" llms.txt tries to answer "where should you start?"

Actual Adoption of llms.txt: Industry Enthusiasm Is One Thing, AI Usage Is Another

A rising number of implementations doesn't mean a rising amount of usage

The number of domains publishing llms.txt is growing fast. In the roughly 15 months since the spec was published, the file has shown up on hundreds of thousands of sites, and popular SEO tools and documentation platforms have started offering it as a built-in generator.

That doesn't mean language models are actually using it. Site owners implementing the file and AI systems actually reading it are two separate questions — and that gap is really the whole debate.

BuiltWith shows the scale of adoption

BuiltWith's data confirms rapid growth in the number of sites with an llms.txt file. But that only shows that the technology is present — not whether AI models are using it. SEO has a long history of tactics that got adopted en masse mainly because they were bundled into CMS platforms and plugins. A rising implementation count isn't, by itself, evidence that the standard matters in practice.

Ahrefs checked server logs

Ahrefs ran a much more revealing analysis, based on HTTP logs from more than 137,000 domains. Instead of counting implementations, they checked whether llms.txt files were actually being fetched.

The results were sobering: roughly 97% of the files received zero HTTP requests during the study period. That doesn't prove AI models never use them, but it does show that actual usage of the standard is far from widespread today. What's more, a large share of the traffic that was recorded came from monitoring tools and technology scanners — not from systems generating answers for real users. A file being downloaded doesn't necessarily mean a language model made use of it.

OtterlyAI reaches similar conclusions

OtterlyAI published comparable findings. Looking at more than 60,000 AI bot visits, requests for llms.txt accounted for only about 0.1% of that traffic.

Two independent studies point to the same conclusion: llms.txt implementations are growing fast, but there's currently little evidence of widespread use by AI systems.

What Does Google Say About It?

Google's position is far more cautious than the industry conversation around it. John Mueller has said Google's systems can analyze page structure on their own and don't need an extra file to understand a page's content. Google hasn't communicated any ranking benefit tied to implementing llms.txt.

Google has also pointed out that the file's content is written by the site owner — meaning it's a self-reported signal. That kind of information is easy to manipulate, so search engines tend to weight signals they observe independently more heavily than claims made by page authors themselves.

Right now, there's no basis for treating llms.txt as equivalent to robots.txt or sitemap.xml, or as a ranking factor on Google.

If Models Can Already Read HTML, Why Do They Need Another File?

This is the skeptics' central argument

Discussions about llms.txt often boil down to one assumption: if language models get a "better map" of a site, they should produce better answers.

The problem is that modern models already have very sophisticated tools for parsing documents. Both search systems and language models can distinguish main content from navigation, ads, footers, and interface elements — that's not some new AI-specific skill; classic search engines have used similar techniques for years.

If a model can already identify the right part of a document on its own, it's fair to ask what additional value a hand-curated guide really adds. This is precisely the sticking point that keeps coming up between supporters and skeptics of the standard: the better models get at parsing pages, the harder it becomes to justify an extra descriptive layer on top.

Why the Distinction Between a Training Crawler and a RAG System Matters

Not every AI system visits a site for the same reason

A training crawler works much like a classic search-indexing bot: its job is to gather a huge volume of documents that will later be used to train a model. In that scenario, what matters most is the ability to pull large datasets and clean them up afterward.

Retrieval-Augmented Generation (RAG) systems work completely differently. They're not trying to build a full copy of the internet. Their job is to find the right documents at the moment a user asks a specific question.

This distinction changes how you should think about llms.txt — whether the standard is useful at all depends heavily on which stage of a model's workflow you're talking about.

In RAG systems, speed is what matters

Modern AI search tools generally work in stages: first they find potentially relevant documents, then fetch their content, then hand that content to the language model that generates the actual answer.

That raises an obvious question: if a system already knows the answer lives at a specific URL, why would it make an extra HTTP request just to fetch llms.txt, read a list of recommended materials, and then go right back to the page it already found?

This is where the biggest doubts about the standard's practical usefulness come from. Every extra step adds latency and adds another operation for the system to perform. In an environment where milliseconds matter, that's not a trivial argument. If an AI search tool already knows the right document, an extra guide file may simply be redundant.

There are scenarios where llms.txt makes more sense — developer tools are the best example

The fact that Google is cautious doesn't mean the whole standard is worthless. Quite the opposite — research suggests the strongest interest in llms.txt isn't coming from classic search engines but from the developer-tools ecosystem.

Coding assistants, task-executing agents, and systems that parse technical documentation typically work with much smaller, more focused datasets than general web search does. In that context, a hand-curated guide to a documentation set really can cut down the time it takes to find the right information.

It's no coincidence that some of the earliest adopters of llms.txt were API documentation sites, developer libraries, and open-source projects — an environment that fits Howard's original premise far better than a news site or an e-commerce store does. The most compelling use cases for llms.txt today are in technical documentation, not broad-based SEO.

Separating the Standard's Potential From Its Current Role

Weighing the Ahrefs data, the OtterlyAI analysis, and Google's stated position together, it's hard to argue that llms.txt has become a widely used piece of AI infrastructure. It's just as hard to call it a pointless project.

The spec solves a specific, real problem its author described, and it has real applications in specific scenarios — especially where models are working with technical documentation or performing agentic tasks. That's not the same thing as confirming broad adoption by the AI search engines handling millions of queries a day.

That distinction is central to the whole debate. Instead of asking whether llms.txt "works," it's more useful to ask who it was designed for and in what environment. Only then can you fairly assess its actual potential.

The Case For and Against llms.txt: Why Is the SEO Industry Split?

The controversy around llms.txt isn't really about the spec itself — the format is simple and easy to implement. The disagreement is about whether it solves a real problem for today's language models.

You can think Howard's idea is logical and still doubt that today's AI systems actually need it. In practice, the question isn't whether llms.txt is a valid standard — it's whether models have any reason to use it.

Websites are built for people, not models

Supporters point out that modern web pages are full of elements that are just noise to a language model. llms.txt is meant to shorten the path to the most important material and flag priorities — not replace HTML or sitemap.xml. In this view, the standard acts as a guide, not a new publishing format.

Models are getting better at doing without it

Skeptics point out that modern models are increasingly good at recognizing document structure on their own and separating real content from navigation elements. In RAG-based systems, reading an extra file means another HTTP request and added processing cost. If a model has already found the right document, an extra guide may just be dead weight.

Both sides have a point

Current evidence suggests llms.txt may be worthwhile in specific use cases — technical documentation and agentic systems, for example — while there's no evidence it plays a meaningful role in mainstream AI search today. That makes it worth treating as a promising experiment, not a mandatory piece of technical SEO.

What Can We Actually Confirm?

The standard exists and is gaining traction quickly. There's no question llms.txt is an active, evolving project. Since the spec was published, more implementations, generators, and documentation-tool integrations have appeared, and adoption is climbing fast. The debate isn't about whether the standard exists — it's about how much it's actually being used.

There's no evidence it affects Google. Google hasn't confirmed that llms.txt influences rankings or AI Overviews. John Mueller has emphasized that Google's systems can analyze page structure on their own and don't need an extra file to understand what a page contains. There's currently no basis for treating llms.txt as a ranking factor.

What Should Be Considered a Myth?

"llms.txt works just like robots.txt."

This is one of the most repeated oversimplifications. Yes, both files live in a domain's root directory — but they serve completely different functions. robots.txt talks to crawlers and sets rules for what they can access. llms.txt doesn't block anything and has no effect on indexing; its only role is to flag the materials a site owner considers most important. The robots.txt comparison works fine as a loose metaphor, but technically the two solve entirely different problems.

"Implementing llms.txt improves SEO."

There's currently no data supporting this. No available study has shown an increase in organic visibility after implementing the standard, and Google hasn't indicated it treats llms.txt as a ranking signal. That could change down the road, but as of today, linking llms.txt to classic SEO outcomes goes beyond what the evidence actually shows.

"Without llms.txt, AI won't use your site's content."

This isn't supported either. Language models have been analyzing websites for years without llms.txt, relying on crawlers, their own indexes, and search mechanisms. When an AI system does draw on a site's content, it's almost always thanks to existing indexing infrastructure — not because it happened to find an llms.txt file. Not having llms.txt doesn't make a site invisible to AI systems.

What Should Publishers Take Away From This?

If you run a website, you can implement llms.txt — but right now there's no reason to expect it to move the needle. Putting the file together isn't hard and usually doesn't cost much. The issue is that there's currently no evidence tying its implementation to better Google visibility, more frequent AI citations, or more traffic.

That doesn't make llms.txt worthless. If you run an extensive documentation site, a knowledge base, or a resource-heavy expert content site, a curated guide like this could turn out to be useful down the road, especially as AI agents become more capable. For now, it's best treated as a low-cost experiment whose benefits haven't been proven yet.

For most publishers, the bigger wins will keep coming from tactics with a proven track record: producing genuinely valuable content, improving information architecture, using structured data well, and keeping your site fast. That's exactly where CMS 4Media earns its keep — with built-in SEO automation, structured data handled for you, and an AI assistant built into the editorial workflow, it takes care of the fundamentals that actually move the needle, so your team can spend less time on technical busywork and more time on the content itself.

• They use the AI Assistant module.
• They have specifically two language versions enabled simultaneously.

Tip: Detailed information on language configuration and instructions on how to activate additional language versions of your portal can be found in the following article:

Where Can You Find the Translation Feature?

Automatic translation works in most sections of your panel. You can use it in the following modules:

• Articles
• Authors
• E-editions
• Information ticker
• Photo galleries
• Multimedia
• Live coverages
• Boards
• Polls
• Plebiscites
• Events
• Obituaries
• Subpages
• Categories
• FAQ
• Paywall
• Classifieds
• Business Directory
• Terms
• Quizzes

How Does Language Selection Work?

The language you are translating from depends on the language version of the Admin Panel you are currently working in:

• Working in the English version of the panel: The button will trigger a translation from English to the second active language (e.g., Spanish).
• Working in the Spanish version of the panel: The button will trigger a translation from Spanish to English.

To change the language version of the admin panel itself, click the flag icon in the top right corner of the screen.

How the AI Translation module works.

The following description is based on the [Articles] module. The feature works exactly the same way in all other modules.

1. Prepare and save the text in your native language (e.g., in English).
2. Click the translation button (e.g., [English > Spanish]) in the top right corner of the form.
3. The AI Assistant will start working and display a message indicating that the translation is being prepared.

Once the process is complete, a green success confirmation message will appear at the top of the screen.

In addition, a flashing green dot will appear to indicate changes that have been made to the currently inactive tab of the second version of the post. It disappears when you switch to the aforementioned ES tab.

Important Rules for AI Assistant Operation

Preserving Formatting: The translated text retains its original layout. The AI copies the structure of headings and paragraphs, and correctly transfers links and images embedded within the content.

Content Protection (No Overwriting): The AI Assistant does not overwrite fields that you have already filled in manually. If you enter your own title in the Spanish (ES) tab before running the AI, the system will skip that field and leave it unchanged.

Empty Fields: The AI only translates fields that contain text. If you leave a field empty, the system will skip it. If the AI Assistant does not detect any content to translate on the page, it will display an appropriate warning message.

Image Metadata (Descriptions and Titles): The system also automatically translates the descriptions and titles of the main image and additional images, provided they were previously entered in the source language.

Translating Individual Images: If you are editing the metadata of a single, previously added image, you can find a dedicated translation button directly inside the edit panel for that specific image.

Key results at a glance

• 6 portals migrated to CMS4media, live since April 1, 2026
• Google Discover traffic up close to 41 percent month over month
• Google News traffic up 14.9 percent
• Organic search traffic retained through the migration, with no meaningful drop
• The Koronowo portal grew from roughly 90,000 to roughly 115,000 monthly users, and now stays consistently above 100,000
• Editorial team productive on the new system within about 5 days

Who this is about

Przemysław Hartmann runs Hartmann Media Consulting, the business formerly known as the Kujawy Media Group. The company has been on the market for about 12 years, and his flagship title, mojakruszwica.pl, just passed its 12th anniversary. He publishes across a cluster of local sites in the Kujawy region of Poland, including portals in Koronowo, Strzelno, and Janikowo, each serving a different small-town audience with different interests.

He did not start as a software person. He started as a journalist and editor, then grew into a publisher when it became clear the business had to be run as a business, not just a place to post news. That background matters, because it makes him exactly the kind of reader this case study is written for: a hands-on local publisher, not an IT department.

The starting point: two kinds of pain

Hartmann had been through several content management systems before CMS4media, and the history was not happy.

In the early years, his team ran home-grown, frankly amateur solutions. He remembers the "blood, sweat, and tears" of that first portal, a site that broke down often and left him and a partner to fix every problem alone, with no one to call.

His most recent provider solved the "build it yourself" problem but introduced a new one: advertising. Heavy, resource-intensive ads were getting between readers and the content. Readers complained. As he put it, people today expect straightforward access to a story, not a page that makes them wait while ads stack up. When a page takes several seconds to load, the bounce rate climbs, because almost no one is that patient anymore.

There was also a fear that keeps many independent publishers out of any network: the worry about losing independence and having someone interfere in the newsroom workflow. Looking back, he says that fear did not come true.

The part every publisher dreads: migration

Migration is the moment publishers lose sleep over, because it puts the archive and the search traffic at risk at the same time. Hartmann faced a real decision on each site: migrate the full database, or archive it and start clean. On some portals his team archived the old database. On the heavier sites, including Koronowo and Kruszwica, they migrated the entire archive, years of articles, photos, and metadata.

A migration at that scale is not a one-click event, and the honest version of this story includes that fact. After go-live, the portals were checked with a post-migration audit on the 4media side, and the work also included an independent SEO audit of the result. That review drives a prioritized cleanup of the usual long-tail migration issues, things like setting 301 redirects on the highest-traffic legacy URLs, retiring an old service worker left over from the previous setup, and resolving indexing notifications from Google, with follow-up checkpoints in Google Search Console to measure each fix. None of that is glamorous, but it is the difference between a migration that holds and one that quietly leaks traffic for months.

The aggregate result, which Hartmann read out himself on camera, was the part that mattered to him. Google Discover grew by close to 41 percent. Google News grew by 14.9 percent. Search traffic was effectively held in place rather than collapsing. Old broken links from the previous system stopped being a problem. (See roughly the 19:25 to 23:00 mark in the interview.)

He is also candid about the human side. Some traffic loss always happens at first, because readers have to get used to a new site, and reactions are mixed in the first weeks. April was a test month. By June he could see the numbers settling and then climbing. The Koronowo portal, his most representative site, moved from around 90,000 monthly users last summer to around 115,000, and now holds above 100,000. Crucially, that growth was not only local readers, which was a specific goal for a portal based in a very small town.

What changed in daily work

Speed came first. The heavy, intrusive ads are gone, and the site stays fast even when it is carrying a lot. Hartmann stress-tested this by pasting in HTML-heavy material, building an entertainment zone, even embedding a game. On his old setup that would have dragged the whole template to a crawl. On CMS4media it did not freeze or slow the page.

Then came the breadth of the platform, which he describes not as a place to add articles but as a full "media environment." A few modules stood out in his daily use:

• The Classifieds module finally gave his listings a place to be promoted, and reader interest in them took off in a way the old template never allowed.
• Quizzes and other engagement modules keep readers on the page and coming back.
• Photo galleries became a real tool rather than a dump of images. He tests different formats against his audience, including the hybrid gallery that shows a few photos and then prompts a click-through, and the scroll-based cascade gallery, trading off between time on page and page views.
• Related Articles let him link stories together and resurface older material from the archive, which keeps readers moving through the site.

For a publisher running six titles, the multi-site capability is the quiet hero. He can manage and share content across portals from one place. His early fear was that sharing the same content across sites would get him penalized by Google for duplicate content. It does not work that way here, because the system points the duplicates back to the source portal, so the main site is the one that benefits and SEO is not hurt. That means a story that fits two towns does not have to be written twice.

He is also testing the platform's AI assistant, which generates suggested titles, tags, and SEO-oriented material, and lets him set tone and format. For quick news, where typing tags by hand is a chore, it works instantly. He was wary of the common claim that AI tools hurt a portal's ranking, and his experience is that they speed up the work without that downside. Behind the assistant sit more than 70 prompts and a different model matched to each module, which is the reason it behaves sensibly rather than generically. (See roughly the 24:00 to 26:00 mark.)

The "free CMS" question

Plenty of small publishers start on a free CMS and never want to add a cost. Hartmann understands that instinct, and he pushes back on it from experience. After more than a decade online, his view is blunt: there is no good software that is truly free. Someone has to recover the cost, and with a free CMS they usually recover it by cluttering your pages with the very ads that drive readers away. In an era when publishers already have to fight social platforms for every visit, paying that hidden tax in ad clutter is, in his words, not worth it. He would rather pay a subscription for a stable, professional, flexible system and run a portal he is proud of. He moved six sites over knowing that meant real cost. (See roughly the 14:30 to 16:30 mark.)

On the revenue side, 4media supplies ads and sponsored articles, and the two sides split ad profit 50/50. What impressed him was the transparency: the ad report was clear and detailed rather than a black-box number in a Word document, he could see where the amounts came from and how engagement fed into them, and when he sent follow-up questions he got specific answers. The contract itself was negotiable, adjusted along the way to fit how he works.

The FREE Trap You Never Knew Existed

Onboarding and support

A powerful system raises a fair fear: will it be too complex to use. Hartmann's first reaction was exactly that, a large system and the worry of figuring it out. In practice it took about five days, maybe less, to feel at home, helped by four or five solid training sessions. His verdict is that the system is extensive but it makes sense, and that drag-and-drop content handling makes everyday publishing genuinely pleasant.

Support is the other half. He felt, especially during the migration, that the team was essentially at his disposal, to the point he worried he was leaning on them too much. When Google flagged indexing issues, he got help getting the archive indexed and available. When an ad-provider glitch surfaced content that should not have appeared, that got resolved too. Beyond day-to-day contact with the team, there are quarterly roadmap meetings where publishers can raise ideas for what gets built next.

What comes next

Part of why Hartmann recommends the platform is that the runway keeps going. He can cover live events, add audio and radio streams, and is preparing an e-edition, a PDF version of his printed newspaper sold behind a paywall, alongside plans to move his radio onto the portal so people can hear the local news there too. For a publisher who also prints, that combination of print, web, and audio under one roof is the point. As he sums up the platform's flexibility, "basically nothing limits us now."

Would he recommend it to other publishers?

Yes, without hesitation. After nearly three months he says it works the way it should and makes sense, the team has ideas for the future, and the experience extends beyond Poland, including publishers in the United States and the server-side solutions behind them. For any publisher, in print or online, looking for serious, professional tools, his advice is simple: it is worth a conversation, and worth testing. (See roughly the 28:00 mark.)

Frequently asked questions

Will I lose my SEO or search traffic if I migrate my news site? Migration always carries risk, and some short-term wobble is normal as readers adjust. In this case, organic search traffic was retained through the move, while Google Discover rose by close to 41 percent and Google News by 14.9 percent, supported by a post-migration audit and a prioritized cleanup of legacy redirects and indexing issues.

Is a paid news CMS worth it compared to a free one? This publisher's view, after more than a decade online, is that no capable software is truly free, and that free systems often recover their cost by loading your pages with intrusive ads that cost you readers. He chose to pay for a stable, flexible, professional platform instead.

Can I manage several local sites from one place without a duplicate-content penalty? Yes. The multi-site capability lets you publish and share content across portals from a single admin, and shared content points back to the source portal, so the main site benefits and search rankings are not harmed.

How long does it take to learn the system? For this team, about five days to feel comfortable, supported by four or five training sessions and ongoing support.

Does using the AI assistant hurt my SEO? In this publisher's experience, no. The assistant generates titles, tags, and SEO material and speeds up routine work, with a different model matched to each module rather than one generic engine.

If you do not publish in California, do not look away. Illinois, New York, and New Mexico already run versions of this idea, and more than a dozen states are drafting their own. This is a template, not a local curiosity.

The number is the headline. The architecture is the story. Read the bill closely and the intent is unmistakable. California is not subsidizing local news in general. It is paying for a particular kind of it: full-time, locally resident, independent, and paid like a profession.

Reading the Architecture

Four design choices reveal what the state is actually buying.

Refundable, not a deduction. Credits beyond an outlet's tax bill are paid out in cash, like a grant. A nonprofit with no tax liability still receives a check. The money reaches the newsrooms that need it most, not only the ones already turning a profit.

A 50-mile residency rule. Qualifying journalists have to live within 50 miles of the area they cover. That single clause quietly outlaws the remote-stringer model dressed up as local news.

A salary floor and real hours. Credits attach to full-time jobs of at least 30 hours a week paying no less than $35,000 a year. Part-time roles earn a smaller $7,500 credit. The state is drawing a line against gig-economy journalism and the side-hustle byline.

A 15% cap on political money. An outlet controlled by a PAC or a 501(c)(4), or drawing more than 15% of its revenue from them, does not qualify. Editorial independence is treated as a precondition, not a line in a marketing deck.

A Math Problem, Not an Audience Problem

The bet underneath the bill deserves to be stated plainly. Local news did not collapse because readers stopped caring. It collapsed because the unit economics of a reporter's salary broke roughly a decade ago and never recovered. Subscriptions, events, and the occasional grant could not close the gap on a full-time wage.

The scale of the damage is on the record. The United States has lost about 75% of its local journalists since 2002. California, for all its size and wealth, ranks 42nd of 50 states, with roughly six full-time local journalists per 100,000 residents, against a national average near 40 per 100,000 two decades ago.

AB 2222 aims straight at that bottleneck. It does not chase audience. It lowers the cost of keeping a reporter on payroll, which is the exact line item that broke.

The Catch

This is not money in the bank, and it is worth being honest about why. The bill is not law yet. It still has to clear the Senate, where budget hawks are pushing for tighter guardrails, and the program is estimated to cost the state around $22 million in its first year and roughly $50 million a year after that. California's tax agency has already flagged practical questions, including how to measure baseline headcount and how to stop outlets from gaming the credit. Critics also note that nonprofits, which already avoid most taxes, would receive what amounts to a second subsidy.

History argues for patience too. In 2024, a high-profile, Google-backed deal promised California newsrooms a large support package, and much of that money still has not reached individual publishers. Treat any policy dollar as pending, not banked.

Why This Matters Outside California

The credit itself will not reach a publisher in Ohio or Idaho. The precedent will. New York has committed $30 million a year to its version, and California's bill has now cleared its first chamber, which is exactly the kind of momentum that moves an idea from one statehouse to the next.

Two things follow for any publisher, in any state. First, watch your own legislature, because this is the most credible policy lever local news has gained in years. Second, understand what every one of these laws rewards: documented, qualifying, independent newsrooms. The money flows to outlets that can prove what they are.

The Half a Tax Credit Cannot Fix

A credit repairs one side of a reporter's unit economics, the cost. It does nothing about the other side, the revenue that reporter generates. A $20,000 credit buys time. It does not, on its own, build a business.

This is where we spend most of our time with publishers at 4media. The newsrooms that turn policy support into lasting stability share one trait: a platform that converts reporting into recurring revenue, through paid memberships, newsletters, and reliable ad delivery, so that every reporter the state helps fund also earns. That is the same shift toward owned, durable audiences we traced in Google Search Live and the End of Drive-By Traffic, and the same logic behind public money rewarding readiness in The $129 Million Scaffolding.

There is also a paperwork reality. To claim these credits, an outlet has to document full-time status, residency, salary, insurance, editorial independence, and, for digital outlets, that at least a third of its audience sits in-state. When we audit publishers, the most common gap is not editorial, it is data: many cannot produce a clean, defensible audience report, which is precisely what these credits require. Proving what you are takes systems, and aging software that cannot generate a reliable traffic number will leave money sitting on the table.

The Real Question

California will not fix local news with one bill, and the Community NEWS Act does not pretend to. But of every proposal in the past five years, this is the one aimed at the actual bottleneck: the broken math under a reporter's salary.

So the open question is not really whether the policy works. It is whether other states copy it, and whether your newsroom is built to claim the money when they do. California has decided a local reporter is worth $20,000. The reporters covering your community are worth more than that to you. Build the platform that can prove it before the check is on offer, not after.

(Source: AB 2222, Community Newsroom Employment and Workforce Sustainability Act, California Legislature)

Community event coverage is often treated as disposable content. Editors publish a quick announcement about this weekend's farmers market, a summer concert series, or a county fair, and once the event is over, the page quietly fades into Google's archive.

Meanwhile, thousands of people continue searching for phrases like "things to do this weekend," "free events near me," "family activities in Phoenix," or "live music in Nashville tonight." These highly specific searches may not generate blockbuster traffic individually, but together they represent one of the most valuable long-tail traffic sources available to local publishers.

An event calendar shouldn't be a digital bulletin board filled with copied press releases. Done right, it becomes a long-term SEO asset that consistently attracts readers month after month—provided you stop creating disposable URLs for recurring events.

A well-structured events hub, supported by smart internal linking, can generate reliable organic traffic regardless of the season. More importantly, it matches how people actually consume content today. Readers aren't settling in with a cup of coffee to read every word of a 1,500-word article—they're scanning for answers.

If your website can't tell someone what's happening this Friday night within a few seconds, Google will likely send that reader to another local publisher who can.

The good news? Building an AI-friendly, search-optimized events hub doesn't require a massive editorial overhaul. With a few structural changes and the right publishing workflow—and a little storytelling instinct—your newsroom can turn routine event listings into a dependable source of evergreen search traffic and content readers actually want to share.

How to Build an AI-Friendly Events Calendar

Traditional search results are no longer the only gateway to your content. As Google's AI-powered experiences continue to evolve, users increasingly receive complete answers before they ever click a blue link.

If someone searches for "things to do in Austin this weekend," Google's AI may summarize the best options directly in search results. The publishers that earn those mentions are usually the ones that present clear, structured information from the very beginning.

One of the biggest mistakes newsrooms make is burying the essential details halfway through an article. If readers—and AI systems—have to hunt for the event date, location, admission price, or start time, you've already made your content harder to understand.

Instead, follow the classic inverted pyramid.

Immediately below the headline, include a concise information box covering the essentials:

• What is the event?
• Where is it taking place?
• When does it start?
• How much does it cost?
• Who is it for?

This format doesn't just improve the reader experience. It also makes your content significantly easier for search engines and AI systems to interpret, increasing the likelihood that your information will appear in AI-generated answers, rich results, and other enhanced search features.

Long introductions, marketing language, and unnecessary storytelling may read well, but they often delay the information users are actually searching for. In an AI-first search landscape, clarity consistently outperforms cleverness.

Every event page should answer the user's primary question within the first few seconds. When your newsroom consistently publishes content that directly satisfies search intent, you build topical authority—a signal that has become increasingly important as search evolves beyond traditional keyword rankings.

This doesn't mean your events hub has to read like a spreadsheet. The facts come first—but the color and connection that make a story feel local can live comfortably right after the info box. See the next section for how to do both at once.

Give Readers the Facts—Then Give Them the Feeling

Structured data gets your event in front of readers. Good storytelling is what makes them stay, and what makes them trust your newsroom enough to come back for the next one.

The inverted pyramid isn't a reason to strip your event coverage of personality—it's a sequencing rule. Facts first, feeling second. Once the info box has answered what, where, when, how much, and who, the rest of the article has room to do what a press release never can: make the event feel like part of the community's life, not just an entry on a calendar.

Where cultural detail belongs, and where it doesn't

• Use it in the narrative body, never in the info box, headline, or structured data. Schema markup and the essentials block stay clean and literal—that's what search engines and AI summaries parse.
• Use it to answer a question the facts alone can't: why does this event matter here, and why now?
• Keep it brief. A sentence or two of texture is often enough. The goal is a reader feeling recognized, not a travel brochure.

A few examples of the kind of detail that earns its place:

• Independence Day: backyard barbecues, neighborhood fireworks, baseball games, small-town parades, concerts in the park, flags on front porches, families packing coolers for the lake—the unofficial midpoint of summer.
• Thanksgiving: crowded airports, family reunions, football rivalries, the start of Black Friday anticipation.
• Memorial Day: the unofficial start of summer travel season and ceremonies honoring veterans.
• Labor Day: the last beach weekend of the season and the shift into back-to-school routines.
• Election Day: campaign signs on lawns, polling places set up in school gyms and church halls, "I Voted" stickers.
• Christmas: tree lightings downtown, community toy drives, packed shopping districts.

Add context, briefly, when it helps a reader connect:

• A short line on why a tradition exists (a county fair rooted in the region's agricultural history, a parade that's run every year since a specific founding event).
• A nod to how the tradition has been passed down—"families have brought lawn chairs to this same stretch of Main Street for three generations."
• A connection between today's specific event and the wider ritual it belongs to.

Keep it grounded, not decorative. The test for any cultural detail: does it help a reader picture themselves at this event, or is it filler that could be swapped into any city's coverage of any event? If a sentence would read the same whether the event were in Ohio or Oregon, it's not doing its job. Specificity—this venue, this neighborhood, this year's twist on an old tradition—is what separates a locally reported guide from a generic listing, and it's also what keeps the writing from feeling like a press release run through a rewriter.

This is where a well-designed AI editing workflow earns its keep: it can be prompted not just to reorganize facts, but to notice where a sentence of local color belongs—and to leave it out everywhere else.

Keep Event Pages Working Long After the Event Ends

Here's how event coverage typically works in most newsrooms.

An editor publishes a preview of this weekend's event. The festival ends. The article stops receiving traffic. A year later, the newsroom creates an entirely new page for the next edition—and starts from scratch.

It's an incredibly common workflow, but it's also one of the biggest missed SEO opportunities for local publishers.

Every new URL created for the same recurring event dilutes your site's authority. Instead of strengthening a page that already has backlinks, search history, and rankings, you're asking Google to evaluate an entirely new piece of content every single year.

Publishing dozens of one-off event pages also wastes crawl budget and increases the risk of keyword cannibalization, especially when multiple pages compete for nearly identical searches.

Imagine your city hosts an annual county fair, a summer music festival, or a popular holiday parade.

Avoid creating URLs like:

yournewsroom.com/events/2026/summer-music-festival-2026

Instead, create a permanent, evergreen URL:

yournewsroom.com/events/summer-music-festival

The page becomes the long-term home for that event.

Before each new edition, simply update the date, schedule, featured performers, ticket information, and any other relevant details. Once the event ends, don't archive the page or let it go stale. Refresh it with a photo gallery, attendance highlights, key moments, or a recap of what happened.

That single URL keeps accumulating authority year after year.

Rather than abandoning everything you've already built, you're continuously improving an asset that search engines already trust. Readers searching for next year's event are far more likely to discover a page with an established history than a brand-new URL with no authority.

Think of every recurring event page as an evergreen resource—not a temporary news story.

An evergreen page also has a storytelling advantage the disposable model never gets: it can grow richer every year. This year's recap paragraph—the crowd size, a photo gallery, a specific moment from the parade route—becomes next year's "last year's festival drew a record crowd" line, building a sense of continuity a brand-new URL can never have on day one.

What If Local Organizations Don't Make Event Data Easy to Access?

Maintaining a comprehensive community events calendar by hand is one of the most repetitive jobs in any local newsroom.

Every day, editors copy information from city websites, museums, libraries, schools, theaters, nonprofit organizations, and community centers. It's important work—but it's also time that could be spent on original reporting.

Copying information from flyers, Facebook posts, or outdated websites isn't the best use of a journalist's expertise.

Fortunately, much of that workflow can be automated.

With Content Hub in 4Media CMS, publishers can aggregate external content feeds directly into their editorial workflow. New event announcements can be collected automatically, allowing editors to focus on reviewing, enriching, and publishing content instead of manually retyping it.

But what happens when a local theater or community center doesn't provide an RSS feed?

That's a surprisingly common problem.

Many smaller organizations still rely on basic websites—or simply post updates on Facebook or Instagram.

Fortunately, there are tools that can bridge that gap.

Services such as RSS.app, FetchRSS, and PolitePol can generate RSS feeds from almost any publicly accessible webpage or social media profile. Instead of checking dozens of websites every morning, your newsroom can automatically collect new event announcements in one place.

Once those generated feeds are connected to Content Hub, new content flows directly into your CMS, where it can be reviewed, enhanced with AI, and published in just a few clicks.

The result is a workflow that scales effortlessly—even if your community includes hundreds of organizations publishing events across dozens of different websites.

Give AI Better Instructions, Get Better Articles

Automatically importing event announcements into your CMS can save hours of manual work every week. But automation comes with one important responsibility: don't publish imported content exactly as you receive it.

If your CMS pulls an event description directly from a city website, library, museum, or community organization and republishes it word for word, you're simply duplicating content that's already available elsewhere on the web.

That creates little value for readers—and even less for search engines.

The solution isn't to abandon automation. It's to combine automation with AI-assisted editing.

Instead of treating AI as a content generator, think of it as your newsroom's first editor. Its job is to reorganize information, improve clarity, and transform raw event announcements into useful local guides.

A simple prompt can accomplish most of that work in seconds.

Example prompt

Act as an experienced local news editor. Transform the provided source material into an original, publication-ready article for a local news website. The source may be an event listing, press release, RSS item, webpage, social media post, or any other informational content. Preserve all verified facts while completely rewriting the text in original language and adding clear editorial structure.

An expanded version of the prompt, once your newsroom is ready to bring in cultural texture:

Act as an experienced local news editor writing for a community that knows this town well. Transform the provided source material into an original, publication-ready article. Lead with a concise facts block (what, where, when, cost, audience) before any narrative. Preserve all verified facts and never invent details, quotes, or attendance figures. After the facts block, you may add one or two sentences of authentic local or seasonal color—a relevant tradition, a seasonal routine, or a piece of context that helps a local reader picture the event—only if it fits naturally and stays factual. Do not add cultural references to the headline, facts block, or any structured data. If no genuine local angle is available, do not force one.

This approach does far more than rewrite sentences.

A well-designed AI workflow surfaces the information readers care about first, organizes it into a logical structure, and produces content that's easier for both people and search engines to understand—while still sounding like it came from a newsroom that knows the difference between a county fair in July and a harvest festival in October.

Instead of publishing another generic press release, your newsroom delivers a genuinely useful event guide while maintaining original, search-friendly content.

Help Search Engines Understand Your Events

Even the best-written event article is just plain text unless search engines understand what it represents.

To Google, an article about a summer concert, a county fair, or a charity fundraiser looks no different from a recipe or a restaurant review unless the page clearly identifies it as an event.

That's where structured data makes the difference.

By adding Schema.org Event markup behind the scenes, publishers give search engines the context they need to understand exactly what the page contains. This improves eligibility for enhanced search features, including rich results and AI-generated summaries.

With Events Widget in 4Media CMS, this process is built directly into the publishing workflow. Editors simply complete an event form, while the CMS automatically generates the structured data required by Google—no custom coding or developer involvement required.

One small detail is worth remembering.

Avoid adding marketing slogans or promotional copy to event titles and URLs. This applies to seasonal flourishes too—save the color for the body text, never the title, the URL slug, or the structured data fields.

Search engines prefer clarity over creativity. A title like:

Downtown Summer Music Festival

is far more useful than:

Don't Miss the Biggest Music Event of the Summer!

The same principle applies to event locations.

Always provide a real venue and physical address whenever possible. Accurate event names, locations, dates, and times don't just improve the reader experience—they also give Google's systems the structured information they need to confidently identify and display your event in search results.

In other words, you're not writing for robots.

You're giving search engines the context they need to understand what your newsroom has already created—and giving your readers the story around it.

Keep Your Events Hub Crawl-Friendly

Building a comprehensive events database is one of the best long-term SEO investments a local publisher can make.

But without proper technical maintenance, that same database can create unnecessary problems for search engines.

Google allocates a limited crawl budget to every website. The more time its crawlers spend exploring low-value pages, the less time they have to discover your newest stories and most important content.

This often happens when event directories include dozens of filter combinations, outdated archives, or dynamically generated search pages.

Imagine an events calendar where visitors can browse concerts from five years ago, combine multiple filters, sort by dozens of tags, and generate thousands of unique URLs.

To users, those filters may seem helpful.

To search engines, they're often an endless maze.

Instead of crawling your latest breaking news or upcoming event coverage, Googlebot may spend valuable crawl resources indexing thousands of low-value pages that have little chance of attracting organic traffic.

Fortunately, preventing this is straightforward.

Use your robots.txt file to block crawlers from unnecessary search results and dynamically generated filter pages.

Rules such as:

Disallow: /events/search

Disallow: /*?date=

Disallow: /*?tag=

help keep crawlers focused on the pages that matter most.

A clean crawling strategy allows search engines to spend their resources discovering fresh content instead of wandering through outdated archives and duplicate filter combinations.

The result is faster indexing, better crawl efficiency, and a healthier site overall.

Key Takeaways

A well-managed events hub isn't just another section of your website—it's a long-term traffic engine, and with the right editorial touch, a long-term relationship with your readers.

When built with both readers and search engines in mind, recurring event coverage can deliver consistent organic traffic throughout the year while strengthening your publication's authority in local search.

Here are the strategies every local newsroom should follow:

• Lead with the facts. Use the inverted pyramid and place the most important information—date, time, location, admission details, and audience—at the very beginning of every event page.
• Create original editorial value. Never republish municipal announcements or press releases verbatim. Use AI to transform source material into reader-friendly guides that provide unique value.
• Add authentic local color, sparingly. After the facts, a sentence or two of genuine seasonal or community context—why this tradition exists, how the town has marked it for years—helps readers feel connected without slowing down the search-and-AI-friendly structure.
• Use structured data. Help search engines understand your content by implementing Schema.org Event markup. Properly structured pages are more likely to qualify for rich search features and AI-generated answers.
• Build evergreen URLs. Instead of publishing a new page every year for recurring events, maintain one permanent URL and update it as each edition approaches. Over time, that page accumulates authority—and a running story of its own.
• Protect your crawl budget. Prevent search engines from wasting time on outdated archives and endless filter combinations. Keep crawlers focused on the pages that generate meaningful traffic.

Those are familiar shapes of decline. The newer and more useful part of this year's index is not how many reporters vanished. It is what fills the space they leave.

The Order of Collapse

A newsroom does not lose all its coverage at once. It loses it in a predictable sequence. As staff shrinks, editors keep the beats that reliably draw traffic and quietly drop the ones that take patient, time-consuming reporting. The civic beats go first.

The index measured this directly. Across 4.2 million articles published in the first three months of 2026, nearly 77% of U.S. counties produced zero local education stories that named a specific community. About 76% produced none on local health. These are not fringe topics. School closures, enrollment fights, hospital cuts, and insurance gaps are the decisions that shape a family's year, and in three out of four counties no reporter wrote a single local word about them.

Then comes the part that should unsettle every publisher. The vacuum does not stay empty. In counties with fewer than five journalists per 100,000 residents, nearly one in five local articles is about crime, against roughly 13% where reporters are more plentiful. That is about 50% more crime coverage, and not because there is more crime. It is because fear is the cheapest form of attention. When a shrinking newsroom cannot afford the slow work of covering a school board, it covers the police scanner instead. "If it bleeds, it leads" was always a tendency. Scarcity turns it into a business model.

What the Silence Costs

The consequences reach past the newsroom and into the ledger of the community itself. The index pairs its capacity data with civic outcomes, and while the authors are careful to call some of these correlations illustrative rather than proven, the pattern is consistent.

Local governments in states with below-average reporting capacity pay about 17% more in extra municipal borrowing costs, part of an estimated $1.1 billion that news deserts add to public borrowing every year. With no reporter watching the books, lenders price in the risk of waste, and taxpayers cover it. Residents of those communities also report measurably higher loneliness, three to eight points above comparably rural states with more journalists. And on a composite civic-participation score covering voting, volunteering, and giving, the most under-covered counties average 40 out of 100, against 58 for the best-covered. In the worst cases, the "double deserts" with almost no reporters and no outlets at all, that score falls to 23.

Strip out the local signal and a community does not just go uninformed. It goes numb: worse management, weaker oversight, lonelier residents, higher costs. One honest caveat belongs here. The study's content filter is strict and misses television, radio, and reporting that lives only on Facebook, so a few rural counties are covered slightly better than the raw counts suggest. The capacity trend itself, though, is not seriously in dispute.

What Reverses It

Here is the part worth holding onto: the decline is not uniform, and where it has turned around, the mechanism is clear.

Maryland now sits above the national average at 10.6 journalists per 100,000, largely because of The Baltimore Banner, a newsroom launched in 2022 that has grown to about 100 journalists funded by 82,000 paying subscribers. Baltimore now devotes roughly 8% of its local articles to health, three times the national rate. In Chicago, investment in outlets like Block Club has pushed Cook County's education coverage above the national average. These are not miracles. They are business models. A reader-funded newsroom can afford to keep the civic beats that an ad-dependent one is forced to drop.

That is the lever, and it is where we spend our time with publishers at 4media. The index makes the unit economics impossible to ignore: the beats that survive are the beats that pay, and right now crime pays in clicks while education does not. Changing that math means changing how a newsroom earns. A platform that lets a small team publish efficiently, convert readers into paying members, run newsletters and local events, and prove its audience to funders is what turns civic coverage from charity into something that sustains itself. We have made the case for revenue that does not depend on chasing the algorithm in Why Publishers Are Becoming Service Hubs and The $129 Million Scaffolding.

Technology does not conjure reporters. It decides which reporters a community can afford to keep.

Read Your Own County

The 2026 index lets you drop down to your own county and see exactly where your community stands. For a lot of American publishers, that map is uncomfortable reading. It is also the clearest brief you will get on where the need, and the opening, actually sit.

The silence is not permanent. Baltimore and Chicago are proof that capacity returns when someone builds a model that pays for it. Whether the desert keeps spreading is no longer the open question, the data has settled that. The open question is whether your newsroom becomes one of the places that proves it can be pushed back.

(Source: Local Journalist Index 2026, Muck Rack and Rebuild Local News)

The case began when two Munich publishers found that Google's AI Overview, triggered by searches for their names next to words like "scam," was telling users they ran subscription traps and dubious businesses and were tied to shady firms. None of it was true, and none of it appeared in the sources the AI cited. The system had confused them with genuinely sketchy companies, invented the connection, and served it as a confident answer at the top of the page. The court issued a preliminary injunction (case 26 O 869/26) barring Google from repeating the claims, under threat of fines up to €250,000.

The reasoning is the real precedent. A search engine that links to third-party pages is an intermediary, shielded by the liability protections platforms have leaned on for decades, including under the EU's Digital Services Act. A system that reads multiple sources and writes "entirely new, independent statements" in its own words is, the court found, producing its own content. Google argued that users can click through and check the sources for themselves. The court was unmoved: an AI Overview is a self-contained statement, barely 1% of users ever click a source link, and only Google can compare its output against the pages it drew from. The author answers for what it publishes.

What the Court Did and Did Not Say

It is worth being precise about the limits here, because the headline runs ahead of the ruling. This is a preliminary injunction from a regional court, not a final judgment and not a decision from Germany's highest court. Google has said it will appeal, and a full trial is expected later this year. The court stopped short of formally branding Google a "publisher" in the press-law sense; it ruled more narrowly that the AI Overview is Google's own statement, for which Google is directly liable. It deliberately broke from existing German case law on search engines, and a Frankfurt court reached a more cautious conclusion on a similar question last year. None of it binds a single American court.

What it does is puncture, in a courtroom and for the first time, the idea that an AI summary is just a neutral mirror of the web. As one media lawyer put the principle: if a platform's AI creates a statement, the platform is the author of it.

The Two Fronts Every Publisher Is Now Fighting

Step back and the position local publishers occupy looks strange. On one front, the whole industry is racing to get into these systems: AI visibility, LLM citations, "generative engine optimization," an entire advisory market grown up overnight, and the honest truth is that nobody can yet verify what reliably works. Everyone is measuring it as they go.

On the other front, those same systems can manufacture a damaging claim about you out of nothing. For a national brand, a hallucinated accusation is a problem. For a local outlet whose entire asset is the community's trust, an AI Overview that calls you a scam is closer to an existential threat. Your name is your business, and most local publishers have no communications team to fight a machine that defamed them above every search result.

The exposure is not hypothetical. An analysis for the New York Times found Google's current AI model answers correctly about 91% of the time, which sounds reassuring until you account for scale: at Google's search volume, the rest still means millions of wrong answers an hour. The same analysis found that 56% of even the correct answers could not be traced back to the sources cited. The machine is making claims its own citations do not support. The Munich ruling is the first sign that, in that fight, the law can land on the publisher's side.

What You Can Actually Do

You cannot file in Munich. But the ruling points at the real issue, control over how your name appears when a machine describes you, and there you are not powerless.

This is where we work with publishers at 4media, and three things matter. First, your own site has to be the authoritative, machine-readable source of truth about your organization: clean structured data, a clear masthead and "about" record, real author identities. When the ground truth about you is unambiguous and well-formed, an AI has less room to invent. Second, monitor what these systems actually say about your brand, so you can document harm the moment it appears, exactly as those publishers did before they went to court. Third, own your audience. The more your relationship with readers runs through channels you control, newsletters, memberships, direct visits, the less hostage you are to how any algorithm chooses to summarize you. We made that case in Google Search Live and the End of Drive-By Traffic.

A modern platform will not make you immune to a hallucination. It makes you legible to the machines and independent of them at the same time, which is close to the only durable position left.

Google's Move, and Yours

Google's next step is the question everyone is watching: tie AI Overviews tightly to the linked sources, add real correction tools, or fight the principle all the way up. Any of those would reshape how publishers appear online, and notably, binding the AI back to its sources is exactly what the publishers losing reach to AI Overviews have wanted all along.

You do not get to decide that. You do get to decide whether your outlet is easy for a machine to describe accurately and hard for one to misrepresent, and whether your business still stands if Google's summary of you is wrong tomorrow. Build for both. The era of "we just summarize, don't blame us" is ending. The work of controlling your own record is not.

(Source: Landmark German ruling on Google's AI Overviews (LG München I, case 26 O 869/26), The Decoder)

Modern language models process vast amounts of data in a matter of seconds, and then select only those sources they deem most credible and useful. It is precisely based on these that they create answers for users. If your website is not recognized as a valuable source of information, its content may remain invisible to potential clients.

Fortunately, this is not a process based on chance.

Visibility in AI-generated answers can be analyzed, measured, and systematically increased through properly planned optimization.

From SEO to GEO. What is the Paradigm Shift?

For years, the effectiveness of SEO activities was evaluated primarily using the Share of Voice metric. It determined what share of search engine traffic a given domain captured for selected keywords in traditional Google results, often analyzed alongside popular domain authority metrics like Ahrefs DR and Majestic TF.

Today, however, another metric is gaining importance - Share of Source, i.e., the share in sources utilized by artificial intelligence systems.

Share of Source shows how often content from a given website is indicated as a source of information and cited in AI-generated answers. While the goal previously was to achieve the highest possible position on the search results list, it is now crucial to provide information credible and valuable enough for the language model to use it when generating an answer.

With the development of AI-based search engines, the rules of optimization are also changing. Traditional activities, such as excessive keyword stuffing or expanding the backlink profile, are losing their significance for digital marketers figuring out how to survive and rank in the era of generative search.

GEO (Generative Engine Optimization) is playing an increasingly important role, which is an approach focused on preparing content and data structure in a way that makes it easier for AI systems to quickly find, interpret, and use them as a credible source of information.

Market analyses indicate that traffic coming from AI-based platforms, such as ChatGPT or Gemini, often features a higher conversion rate than traditional organic traffic from internet search engines.

This is primarily due to user intent. People using AI tools are usually looking for specific answers, recommendations, or solutions, rather than a list of pages to analyze themselves.

When an artificial intelligence system recommends a specific product, service, or company, and simultaneously bases its answer on information from a given website, the probability of performing the desired action - purchase, contact, or sending an inquiry - significantly increases.

Why Does the AI System Choose This Particular Article?

Most modern AI assistants, including ChatGPT, Gemini, or Perplexity, use solutions based on the RAG (Retrieval-Augmented Generation) architecture.

In practice, this means that the model first searches for information in available sources, and only then generates an answer for the user. However, before data is used, it goes through a quality and usefulness evaluation process.

One of the most important criteria is semantic relevance. The content should directly answer the user's question and provide specific information, without unnecessary digressions.

A clear site structure and architecture that Google loves is equally important for AI parsers.

Headings, tables, lists, and correctly applied HTML tags make it easier for AI systems to interpret and organize data. The timeliness of information and the presence of specific data, examples, and facts confirming the credibility of the content also matter.

For this reason, the BLUF (Bottom Line Up Front) method is playing an increasingly important role, which consists of presenting the most important information right at the beginning of a section or paragraph. AI models look for quick and unambiguous answers during content analysis, which is why it's worth placing key conclusions, definitions, or recommendations right at the beginning. The elaboration, additional explanations, and broader context should only be included later in the text.

The robots.txt File - How to Manage AI Bot Access?

One of the first steps in optimizing a website for AI search engines - alongside ensuring Google can discover your portal via a modern sitemap - is to check if the robots responsible for indexing and searching content have access to the site (i.e., what is the content of the robots.txt file located on the server).

Even valuable and well-optimized materials will not appear in AI-generated answers if the appropriate bots are blocked at the server level. This is a technical hurdle similar to diagnosing why a site is blocked in certain regions even without illegal content. The basic access control tool is the robots.txt file located in the site's root directory.

Many misunderstandings have arisen around AI bots.

Some website owners block all robots associated with artificial intelligence, wanting to prevent their content from being used to train models. However, this approach can unknowingly limit the site's visibility in AI-generated answers. It's crucial to understand that not all bots serve the same function.

For example, GPTBot is primarily used to acquire data utilized in developing and training OpenAI models. On the other hand, OAI-SearchBot is responsible for searching and retrieving content used when presenting results and answers to users.

PerplexityBot plays a similar role in the Perplexity ecosystem. Blocking robots responsible for searching can cause content to no longer be included in answers generated by AI tools, even if it remains visible in traditional search results.

To check the configuration, log into the hosting panel or connect to the server using an FTP client. Then, locate the robots.txt file located in the domain's root directory, usually in the public_html folder. It's worth making sure it doesn't contain rules blocking access to robots responsible for searching and indexing content.

If you care about restricting the use of materials for training AI models, but at the same time want to maintain visibility in AI-generated answers, you can block training bots while leaving access for search bots. A properly configured file should include the following directives:

User-agent: OAI-SearchBot Allow: /

User-agent: PerplexityBot Allow: /

User-agent: GPTBot Disallow: /

After saving the changes, it's worth checking the correctness of the configuration and regularly monitoring the documentation of AI service providers.

The development of AI-based search engines is very dynamic, so the list of used bots and their functions may change over time.

The most important rule is simple: blocking bots responsible for training models does not have to mean giving up visibility in AI answers.

To retain the chance of appearing in results generated by artificial intelligence systems, you must ensure that robots searching and indexing content still have access to the website.

The llms.txt File - An Additional Content Map for AI Systems

Traditional website HTML code contains many elements that have no meaning for language models. Navigation menus, analytics scripts, ads, CSS styles, or UI components are essential for users but make it difficult to quickly reach the actual content, especially if your CMS choice slows down the site and kills your SEO.

For this reason, the concept of the llms.txt file, which acts as a simplified guide to the site's most important resources, is generating increasing interest.

The llms.txt file is placed in the site's root directory, just like robots.txt. Its task is to point to the most valuable sections of the website in an organized, easy-to-process format.

Instead of analyzing the entire site structure, the AI system can more quickly identify pages containing key information, documentation, guides, or expert articles.

In practice, the file contains a list of the most important URLs - which should ideally follow a logical and optimized structure - along with a short description of their content. The simple Markdown format is most often used for this, which is readable by both humans and text-processing systems.

How to Create an llms.txt File?

Preparing the file is relatively simple and does not require advanced technical knowledge. First, create a new text file and save it under the name llms.txt.

Then, add links to the most important sections of the site along with a short description of their content.

The sample content of an llms.txt file might look like this:

XYZ Company Website

Knowledge Base

Knowledge Base Expert articles on SEO, GEO, and internet marketing.

Documentation

Documentation Instructions, guides, and technical materials for clients.

After preparing the file, it must be placed in the site's root directory so that it is accessible at your main domain address followed by /llms.txt.

Although llms.txt does not replace an XML sitemap or standard SEO activities, it can serve as an additional signal making it easier for AI systems to find the most important content.

In the case of extensive websites with a large number of articles, documentation, or expert materials, it also allows for better organization of resources intended for indexing and analysis.

Re-architecting the Technical Foundation: The Imperative for CMS 4Media

The transition from SEO to GEO necessitates a rigorous reevaluation of a publisher's underlying technological stack. Legacy Content Management Systems (CMS), particularly open-source platforms bloated with decades of plugins, unstructured code, custom widgets, and heavy client-side scripts, actively impede AI retrieval. LLM crawlers operate with strict context windows and parsing limits. If a crawler is forced to navigate a labyrinth of inline CSS and complex JavaScript to locate the core content, it will likely abandon the crawl entirely.

To capitalize on GEO, publishers require an agile, structurally clean, and media-rich platform. This is where specialized infrastructure like CMS 4Media becomes a distinct competitive advantage.

Developed as a comprehensive, enterprise-grade ecosystem tailored exclusively for digital publishers, local media, and broadcasters, CMS 4Media natively addresses the mechanical requirements of Generative Engine Optimization through several core architectural advantages:

• Structured Content and Semantic Clarity: CMS 4Media employs an advanced visual widget system that enforces a clean, modular hierarchy. Editors can construct complex layouts without touching the underlying code, ensuring the HTML output remains pristine and highly readable for AI parsers.
• GEO-Optimized Workflows: The text editor is designed specifically for modern publishing. It includes dedicated fields for content "Introductions" that perfectly align with the BLUF (Bottom Line Up Front) methodology. These leads are automatically formatted and wrapped in specific HTML markers that explicitly communicate with search robots, identifying the most vital, extractable summaries required for RAG systems.
• Rich Multimedia Contextualization: As generative models become increasingly multimodal, contextualizing video and audio is paramount. CMS 4Media features a robust multimedia module that creates dedicated subpages for uploaded assets, allowing editors to append detailed titles, descriptive metadata, and WebVTT subtitles. This provides AI crawlers with deep, text-based context, drastically increasing the likelihood that a publisher's rich media will be referenced in AI answers.

For media organizations looking to survive the transition to generative search, upgrading to an AI-ready infrastructure like CMS 4Media ensures that high-quality journalism is perfectly formatted for the algorithms that now distribute it.

How to Measure AI Search Engine Traffic in Google Analytics 4?

One of the biggest challenges associated with optimization for AI search engines is measuring the effects of the conducted activities. Proper tracking requires a solid understanding of web analytics, similar to setting up your workspace with a technical guide to Google Analytics 4 and Search Console.

Unlike traditional search engines, traffic coming from tools such as ChatGPT, Perplexity, or Gemini is not always unambiguously classified in analytics reports.

Some visits pass on source information, while others may be assigned to Direct, Referral, or Unassigned channels, which makes it difficult to assess the real impact of traffic generated by AI.

To get a more complete picture of the situation, it's worth creating a dedicated channel group in Google Analytics 4 for visits coming from the most popular AI-based platforms. This allows you to monitor the number of sessions, user behavior, and conversion rates for this traffic source.

How to create an "AI Traffic" channel in GA4?

In the Google Analytics 4 panel, go to the Admin section, and then select Channel groups under the Data display area.

You can create a new channel group or edit an existing custom group. Click the "Create new channel group" button.

Next, add a new channel, giving it a name, for example, "AI Traffic".

In the conditions configuration, select the Session source parameter, and set the operator to matches regex.

Depending on your needs, you can create one collective channel covering all traffic from AI platforms or separate channels for each tool.

The first solution allows you to quickly assess the scale of AI-generated traffic, while the second makes it easier to analyze the effectiveness of individual platforms.

For the collective "AI Traffic" channel, you can use a regular expression such as:.*chatgpt.*|.*openai.*|.*perplexity.*|.*claude\.ai.*|.*gemini.*|.*copilot.*

If you care about more detailed data, create separate channels for individual traffic sources using partial expressions:

• ChatGPT/OpenAI: .*chatgpt.*|.*openai.*
• Perplexity: .*perplexity.*
• Claude: .*claude\.ai.*
• Gemini: .*gemini.*
• Microsoft Copilot: .*copilot.*

During channel configuration, select the "matches regex" condition, and then paste the appropriate pattern.

Special attention should be paid to the order of rules in the channel group.

Google Analytics analyzes them from top to bottom and assigns the session to the first matching channel.

After creating the channel, click the "Reorder" button located next to the channel list. Move the newly created channel, and confirm the decision with the "Apply" button.

This means that the newly created "AI Traffic" channel should be above general rules, such as Referral.

Otherwise, some visits will be qualified into other categories, which will hinder later analysis.

After saving the configuration, data will start appearing in reports according to the new classification rules. Thanks to this, it will be possible to monitor what share of traffic and conversions is generated by users landing on the site via artificial intelligence tools.

Where exactly to look for this information?

To find the new group in the Google Analytics 4 panel, select Reports from the menu on the left, then expand the Acquisition (Lead generation) section and click Traffic acquisition. In the main data table, you will find your newly created "AI Traffic" channel.

Tools for Monitoring Citations. From SaaS to Python

Occasionally checking brand visibility by manually entering queries into ChatGPT, Gemini, or Perplexity only allows you to get a general picture of the situation.

However, this approach is hard to consider a reliable measurement method.

Answers generated by language models can vary depending on the context of the conversation, current data sources, the phrasing of the question, or the search mechanisms used.

For this reason, effective monitoring in the GEO area requires a more systematic approach.

More and more tools specialized in analyzing brand visibility in AI-generated answers are appearing on the market.

Platforms such as Otterly.ai or Profound automatically send sets of predefined queries to various language models, and then analyze the answers for the presence of indicated brands, products, or domains.

A free, budget-friendly alternative to start with is to use a free account in the Ahrefs tool (Ahrefs Webmaster Tools). You just need to add your domain there as a project.

In the basic reports, a list of AI systems in which citations of your website appeared will be visible.

However, it should be remembered that this is a very basic version - to see more detailed data, such as specific subpages used as a source or exact citation dates, it is necessary to upgrade to a paid package.

Thanks to this, it is possible to track changes in visibility over time and identify topics where the competition is more frequently cited as a source of information.

Companies with technical resources can also create their own monitoring system. In practice, this involves using APIs provided by AI model providers to automatically ask questions and analyze the obtained answers.

These types of solutions allow you to monitor specific keywords, check the frequency of brand occurrences, and identify sources indicated by models when generating answers.

The greatest advantage of automation is the ability to regularly collect data and observe trends.

Thanks to this, it's easier to detect areas where the brand is rarely cited, and then supplement the content with missing information or expand sections answering users' specific questions.

In practice, this allows you to react faster to changes occurring in AI search engines and more effectively increase the site's share in sources utilized by language models.

FAQ Section

How does AI optimization (GEO) differ from classic SEO?

SEO and GEO share a common goal - increasing content visibility on the internet - however, they use slightly different mechanisms.

Classic SEO focuses on improving the site's position in search results by optimizing content, site architecture, user experience, and the link profile. GEO (Generative Engine Optimization) focuses on increasing the probability that the content will be used as a source of information by artificial intelligence systems.

In practice, this means a greater emphasis on clear information structure, unambiguous answers, credible data, and formats that facilitate analysis by language models. It's no longer just about taking a high position in search results, but also about the content being recognized as a valuable source when generating an answer by AI.

Why does ChatGPT point to a competitor's site more often than mine?

There can be many reasons. Language models and AI search systems prefer content that clearly answers users' specific questions.

If competitors publish more organized materials, use clear headings, sections with key takeaways, tables, lists, and data backed by sources, their content may be easier to interpret and cite.

Domain authority, the timeliness of published information, brand presence in other credible sources, and the way knowledge is presented also matter.

In many cases, improving the overall content quality and applying technical on-page fixes - such as using the proper canonical tag in sponsored content to consolidate link equity - can significantly increase the chances of appearing in AI-generated answers.

Will blocking GPTBot in the robots.txt file cause the site to disappear from ChatGPT results?

No. GPTBot is primarily responsible for acquiring data used to develop and train OpenAI models.

Blocking it does not mean automatic removal of the site from search results or answers generated by ChatGPT.

If you want to restrict the use of content for training purposes while maintaining visibility in search, it is crucial to leave access for bots responsible for indexing and retrieving content for search purposes, such as OAI-SearchBot.

These are the ones that can use the website's content when creating answers and presenting sources to users.

Key Takeaways

• Share of Source is gaining importance as a complement to the traditional Share of Voice metric. It's becoming increasingly important not only to occupy high positions in search results, but also to be present in sources utilized by AI systems.
• The robots.txt file requires conscious configuration. Blocking bots responsible for training models does not have to affect website visibility, however, blocking searching and indexing robots can limit its presence in AI-generated answers.
• The llms.txt file can make it easier for language models to find the most important content on the site and is a valuable addition to GEO-related activities.
• A modern technical foundation is essential. Upgrading to an AI-ready infrastructure like CMS 4Media ensures clean HTML, GEO-optimized workflows, and proper media contextualization, bypassing the limitations of legacy platforms.
• Traffic coming from AI platforms is not always unambiguously visible in Google Analytics 4. It's worth creating custom channel groups to more effectively monitor this user segment.
• Optimization for AI search engines is based on a clear content structure, exposing the most important information at the beginning of a section, and providing specific, credible data.
• GEO does not replace SEO, but extends it with activities increasing the chance of using content as an information source in answers generated by artificial intelligence, which is equivalent to the classic positioning process in the AI era.

He is not a coastal fluke. Wichita has Wichita Life. Upstate New York has Catskill Crew. London has Wooden City, with more than 12,000 subscribers, enough to support its writer full-time. The New Yorker recently profiled the whole wave. The pattern holds across very different markets, and the reason is not better writing. It is sharper focus, a visible human, and relentless local utility.

This is not a story about Substack replacing local journalism. It cannot. Real newsrooms have reporters, archives, sources, and decades of community trust that no part-time writer can assemble. But these solo operators are doing five things, visibly and profitably, that a lot of American local publishers have stopped doing. They are worth studying.

Market Data Brief: The Solo Operator Advantage

• Conversion gap: The Eastside Rag converts roughly 20% of its 5,500-plus subscribers to paying, while most newsletters convert only five to ten percent.
• Engagement premium: Beehiiv reports neighborhood newsletters earn a 2.5x higher click-through rate than the platform average.
• Audience scale: Wooden City has passed 12,000 subscribers on a single-city beat and now pays its writer a full-time living.
• Revenue logic: Paid newsletter subscriptions are recurring, first-party revenue. They do not depend on ad networks, search algorithms, or third-party cookies, which are the exact revenue sources draining out of local media.

Five Things Solo Operators Get Right

1. A face, not a masthead. Every one of these newsletters is one named person. Readers know who walked past the new café, who sat through the council meeting, who holds the opinion. The institutional voice is losing to a single human with a byline.

2. Utility before everything. Isaac Rangaswami's rule for Wooden City is that every issue has to be practical enough for people to pay for it. Where to eat. Where to park for the game. Which contractor actually showed up on time. When Google answers a local question with an AI summary or a wall of SEO sludge, a person who has actually been there is the entire differentiator.

3. Narrow beats broad. The instruction is to go smaller than feels comfortable. Not the whole metro, but one side of the highway. Not the county, but the school district. That focus is what produces the engagement premium. A tight beat creates mail people actually open.

4. Opinion is an asset, not a liability. These writers take sides, on a bike lane, a zoning variance, a beloved diner that closed. Hard news reporting still needs to run straight. The voice around it does not. Neutrality reads as absence, and if no reader ever writes in angry, no reader is invested.

5. Design that signals place. Alexa Tietjen Dornagon built Court Street Journal to feel like a storybook, with watercolor illustrations of local storefronts. It looks like the place it covers. Most local news sites look interchangeable, and that sameness is a positioning failure. Aesthetic is positioning.

What Real Newsrooms Already Have

Here is the part the "we can't compete with Substack" argument misses. Established local publishers already hold the assets a one-person operation will never build: trained reporters, a searchable archive, real sources inside city hall, and years of accumulated trust. The solo operator is improvising the credibility your newsroom earned decades ago.

What you are missing is not capability. It is the willingness to write, design, and edit like one person who actually lives on the block.

The Infrastructure That Decides It

It's where we hit the same wall constantly when auditing publishers at 4media. A newsroom decides to put named writers up front, build a genuinely useful local beat, and give the site a look of its own, and the legacy CMS fights every step.

Author identity gets buried under a generic template. The newsletter tool cannot segment a neighborhood list or gate paid content without a third-party bolt-on. The design is locked to a stock theme shared by a thousand other sites. When publishing like a human requires a custom development project, the initiative stalls before the first issue ships.

A modern platform treats these as core features, not optional add-ons. CMS4media gives every writer a real author profile and byline, runs newsletters and paid membership natively, and lets editors shape the look of the site so it reflects the place it covers. Whether your audience ever turns into recurring, first-party revenue is, in the end, a product decision, and your software either enables it or blocks it.

Take It as an Opportunity, Not a Threat

The town crier is back, and the lesson is not that local publishers have been beaten. It is that the winning playbook is now obvious, visible, and cheap to copy.

You already have the reporters, the archive, the sources, and the trust. Put a face on the front page. Make every issue useful enough to pay for. Go narrower than feels safe. Hold an opinion. Make the site look like the place it serves. Then make sure your technology can actually deliver all five, because right now that is the only thing standing between your newsroom and the conversion rates a part-time writer is posting before breakfast.

We traced the collapse of search referral traffic in Google Search Live and the End of Drive-By Traffic and The End of "Back Button Hijacking". The through line is the same: the open web is no longer a reliable landlord. The audience you own is the only one you can count on.

(Source: Your Friendly Neighborhood Newsletter, The New Yorker)

FAQ

How many subscribers does a local newsletter need to be profitable? Far fewer than most publishers assume. When the beat is tight, engagement runs high: Beehiiv reports neighborhood newsletters get 2.5x the click-through rate of the platform average. Solo operators are sustaining themselves on audiences in the low thousands, because a focused local list converts to paid at much higher rates than a broad one.

What paid-conversion rate should a local newsletter expect? Most newsletters convert five to ten percent of free subscribers to paying. The strongest neighborhood newsletters, such as The Eastside Rag, reach roughly 20%. The difference comes from focus, a named human voice, and consistent utility, not from a larger audience.

Can an established newsroom compete with a solo Substack writer? Yes, and it starts ahead. A newsroom already owns reporters, archives, sources, and community trust a part-time writer cannot replicate. The gap is execution and tooling: a CMS that supports real author identity, native newsletters, paid membership, and a distinct design.

How to Activate These Features?

Go to: Settings module → Ad Block Detection

The first available option concerns the audio/video player.

Activating this feature means that a user who is actively using ad-blocking software will see a message informing them that video playback has been blocked when they click on the player. The restriction will be lifted once the user disables the ad blocker for the website they are browsing.

The second available feature is an informational banner, which is automatically displayed to users using ad-blocking software.

Clicking the Show information banner button expands additional settings.

There are two available modes:

• Show banner but do not block access to the portal - with this option enabled, the user will see a notification informing them about detected ad-blocking software, but they will still be able to continue browsing the website.

• Show banner and block access to the portal - with this option enabled, users with an active ad blocker will see a banner informing them that access to the portal is blocked. The restriction will be removed automatically once the user disables the ad blocker. After clicking Refresh page, the user will be able to access the portal without restrictions.

Additional Settings

When enabling the banner feature, two text fields must be filled in: banner title and banner content. It is the publisher’s decision what message will be displayed to users with an ad blocker.

Additionally, the portal administrator can configure the visual layer. Using available settings, it is possible to define the font color and background color of the banner. There is also an option to enable a border, where its color, thickness, and style can be defined.

In this layout, users browse photos by scrolling vertically. After scrolling through a set number of images, the browser tab refreshes (reloads) to display the next batch of photos in the gallery.

This solution allows for the seamless display of banner ads between photos, while ensuring page views are accurately tracked during the refresh triggered by scrolling. Ads are served using the Type C ad widget.

How to activate the Hybrid Gallery:

• Navigate to Settings -> Photo Galleries.
• In the Gallery Type field, select Hybrid Cascade Gallery.
• Define the number of photos after which the browser tab should reload and load the next set of images.
• Save your changes by clicking the Save button.

Hybrid Gallery Interface

After viewing the first group of photos, the user will see a "Next Page" button. They can either click it to reload the tab or simply scroll further down to trigger an automatic refresh, which will load the next batch of images.

Users can return to the previous set of photos by clicking the arrow button.

Below the last image in the gallery, the user can use the Previous page button

To activate ad widgets displaying C-type banners between images in the gallery:

• We log in to the Ads4Media advertising platform
• in the CMS4media Portals tab, click the Options button and then the Ad spots button
• click the green Add new C ad space button
• select the option Available on the lists, in between the elements
• from the expanded options, select  – List of photos in the cascade gallery
• specify after how many images the ad widget should appear for the first time and whether it should be displayed again – if so, specify every how many images its display should repeat

As part of the cascading gallery and hybrid gallery, a solution has been implemented that enables the activation of independent C widgets displaying central ads as well as separate widgets with local ad delivery.

To customize the watermark settings, go to the [Settings] > [Multimedia] module.

Further down the page, a new section named "Watermark" has been added, where you will find the following personalization options:

1. Activating the watermark feature per module and setting its default status
   
   Each module includes two dedicated toggles:
   1. Enable the watermark – determines whether the watermark feature is active in a given module.

   2. Enabled by default – an option available only when the first toggle is enabled. It allows you to decide whether the watermark should be automatically activated after adding a main image.

      If the [Enabled by default] option remains disabled, the watermark must be activated manually within a specific entry. This solution is useful when only selected publications use the watermark functionality.

2. Watermark – a field to select the watermark graphic. It must first be uploaded to the portal's file library; supported formats are png and webp.
3. Watermark - location– a grid interface that allows you to adjust the position of the watermark on the photos.
4. Vertical / Horizontal spacing / Maximum width – in addition to the position, you can adjust the margins from the edges and the size of the watermark. All values are expressed in pixels.

After configuring all settings, remember to save your changes at the bottom of the page by clicking the dark blue "Save" button.

Configuring the watermark for a featured image in a specific entry

In addition to the global settings described above, you can also customize the watermark position for the featured image of a specific post. This applies to all modules where this functionality is available.

We will walk through the process using the [Articles] module as an example. Other modules follow the exact same method.

In the article edit view, within the [Multimedia] section, after uploading a featured image, the following will appear:

1. "Enable the watermark" toggle along with a grid to adjust its position for this specific image. By toggling this switch, you can also completely deactivate the watermark for this graphic.
2. A preview of the uploaded main photo showing the watermark visualization.

If you already have a featured image uploaded and wish to update it, the preview of the new graphic will be displayed below the currently uploaded one.

Watermarks in additional photos and galleries

These cases automatically follow the global configurations set in [Settings] > [Multimedia].

IMPORTANT: Watermark settings do not work retroactively. This means that new settings, as well as a newly uploaded logo, will only be applied to new entries or after manually editing existing ones. The same applies to additional photos and individual images in galleries.

How to activate the Cascade Gallery?

To activate it in the Photo Galleries module:

• Go to Settings → Galleries
   
• In the Photo gallery type field, select Cascade Gallery
   

• Save the changes by clicking the Save button
   

  

  
   

To activate for photos displayed in an article:

(photos uploaded as additional images or a gallery linked to the article)

• Go to Settings → Articles
   
• In the [Images view below article content] field, select [Cascade Gallery]
   

• Save the changes by clicking the [Save] button
  
   

  

  
  
  
   

To activate the widget (or widgets) displaying type C ad banners between photos in the gallery:

• Log in to the Ads4Media platform
   

• In the CMS4media Portals tab, click Options, then click Ad Spots
  
   

  

  
   

• Click the green Add new C ad space button
   

  

   

• Select Available on the lists, in between the elements

• From the expanded options, choose the new feature – List of photos in the cascade gallery
   

  

   

• Specify after how many photos the advertising widget should appear for the first time, and whether it should be displayed again – if so, define after how many photos it should reappear.
  
  In the cascade gallery, a solution has been implemented that allows independent activation of type C widgets displaying central ads, as well as separate widgets for displaying local ads.

The [Content Hub] is located in the left sidebar menu of the CMS 4media admin panel.

When you open the module, you will see the following buttons:

1. Add new data source – redirects to a short form for adding an RSS feed as a new source for third-party articles.
2. Data sources – takes you to the list of already added sources.
3. Draft articles – redirects to a list of "drafts," which are articles the system has read from the provided RSS feeds. These appear only after the added sources have been scanned.

Adding a data source

Click the first green button, "Add new data source." 

You will be redirected to a short form containing the following fields:

• Data source URL – paste the link to your chosen RSS feed here.
• Title – name the data source for your own convenience.
• Language – select the language of the RSS feed from the dropdown list.
• Category – select the default article category to which the AI-generated articles from this source will be assigned.
• Scan frequency – settings for automatic scanning of the RSS feed. This eliminates the need to manually check for new articles.

After filling in all required fields (marked with an asterisk), click "Save."

Once the page reloads, you will see the view of your newly added data source. The top section shows a summary of your settings, while the "Draft articles" section below lists entries retrieved from the RSS feed.

Initially, this list will be empty because the source hasn't been scanned yet. 

To fix this, click the blue "Scan" button to perform the first read and populate the list with the latest posts.

To generate a paraphrase of a selected post using the AI Assistant, click the gray "Generate article" button next to a draft.

You will be taken to a summary of the selected article. Click "Generate article" again to confirm.

IMPORTANT: If the source image is smaller than 540x540px, it will not be uploaded as a main photo of generated article. In other cases, it is being added automatically.

The system will display the progress in 4 steps. Once complete, everything will light up in green, then you will be automatically redirected to the Article Edit view. This ensures you maintain full control over the content. A notification will remind you that you are editing a post generated from external content, and all original source details will be listed.

Note: A note regarding the original source, including a direct link, will always be placed at the end of every generated article.

You can publish the resulting article immediately, schedule it for later, or save it as a draft if you wish to finish editing it later.

Content Hub Dashboard

Once you have added multiple sources and performed the initial scans, the main dashboard will provide a comprehensive overview:

1. "Scan all sources" – a global action that forces a manual scan of all added feeds simultaneously.
2. [Categories] section – displays lists of scanned articles sorted by the thematic categories assigned during the setup phase.
3. [Data sources] section – a quick preview of your active sources and their basic information.

Entries that have already been used to generate an article in your CMS are highlighted in green to help you avoid duplicates.

However, a highly organized effort is quietly building the framework for what local media will look like on the other side of this decline. According to the inaugural 2025 Annual Report from Rebuild Local News, public policy and state-level legislation are rapidly becoming reliable, structural revenue pillars for independent publishers.

For newsroom operators evaluating their balance sheets, the following numbers require immediate attention.

Market Data Brief: The Policy ROI

• Total Public Funds Secured: $129.1 million distributed to local newsrooms across six U.S. states since 2020.
• Investment Efficiency: A 13-to-1 return on policy-focused philanthropic investment (an estimated $9.2 million in advocacy generated the $129 million return).
• Near-Term Projections: More than 15 states are preparing new legislative proposals for 2026, with $74 million already committed from existing laws.

Moving Beyond Grants

For years, the conversation around saving local news centered on private philanthropy. While valuable, private grants alone cannot replace the commercial revenue lost to tech platforms over the last two decades.

The strategy has shifted from asking for charity to altering the legal and tax frameworks in which publishers operate. State governments are realizing that news deserts lead to measurable increases in municipal borrowing costs, lower civic participation, and higher instances of local corruption. Investing in local journalism is now being treated as civic infrastructure repair.

We are seeing two highly effective mechanisms driving this capital:

1. Employment Tax Credits: In 2025, Illinois launched the nation's first refundable tax credit for local news employment. This program directly lowers the operational cost of keeping reporters on payroll. It is a direct financial incentive to maintain and expand editorial headcount, applicable to both commercial and nonprofit newsrooms.

2. Government Advertising Set-Asides: States like Minnesota, Illinois, and California have enacted statutes to redirect state agency advertising budgets. Following a model pioneered in New York City - which steered $72 million to smaller publications over five years - these laws force public institutions to spend their ad dollars with local community media rather than defaulting to global social networks.

The Requirement for Institutional Readiness

When the revenue model shifts from programmatic web traffic to institutional state support, the operational requirements of a newsroom change immediately. This is the exact point where many legacy publishers face a hard reality check regarding their technology.

To capture government advertising contracts or administer state-funded fellowships, a publisher must demonstrate institutional readiness. You cannot secure a lucrative public health advertising campaign from a state agency if your website’s ad-serving architecture is broken, slow, or fails to provide accurate delivery metrics.

At 4media, we constantly audit the technology stacks of publishers looking to diversify their revenue. We frequently find that aging legacy systems become the primary roadblock. If adding three state-funded reporters creates a workflow bottleneck, or if your platform cannot reliably execute a targeted local ad campaign without crashing, your technology is disqualifying you from new revenue streams. A modern publishing platform provides the stability and professional formatting required to accept and execute on serious public and institutional investments.

Preparing for 2026

The Local Journalist Index (the first national map of reporting capacity down to the county level) makes the severity of the crisis undeniable to lawmakers. The political momentum to subsidize, support, and protect local news is accelerating.

Publishers who understand this shift will make very different strategic decisions in the coming months. If your business model relies entirely on pleasing search algorithms, you are fighting the last war. The immediate future of local media may lie in funding that is being built state by state, law by law. Make sure your newsroom has the strategy and the operational infrastructure to participate in it.

(Source: Rebuild Local News Annual Report 2025, rebuildlocalnews.org)

For the average reader, this stops a frustrating browsing experience. For publishers, this is a final warning regarding technical control.

Ignorance Is Not an Excuse

But let's look past the corporate press release about user satisfaction. The publishing market is dealing with declining search traffic. To patch bleeding revenues, many publishers have turned their websites into Frankenstein's monsters, bolted together with third-party affiliate scripts and aggressive advertising tech.

The goal is to squeeze out a few extra cents per visitor. The result is a broken website that holds the reader hostage.

When you outsource your monetization to third-party vendors, you outsource your control. Many publishers have no idea that a vendor's background script is manipulating the browser history of their readers.

Google's update sends a brutal message to the industry: ignorance is no excuse. If a cheap advertising widget breaks the back button, the publisher takes the penalty, not the ad network. Search engines have zero tolerance for sites that trap users in a maze of bad code.

Technology as a Toxic Asset

This policy change highlights a broader business reality. If you do not have absolute control over the code running on your website, your technology is a toxic asset.

We see this vulnerability frequently when auditing legacy sites at 4media. A newsroom works hard to produce great local reporting, only to have their outdated CMS allow unchecked third-party scripts to ruin the site and trigger Google penalties.

Regaining absolute sovereignty over your platform means implementing an infrastructure that blocks cheap ad-tech from coming through the back door. You need a system that prioritizes clean code and direct audience control, rather than leaving the back-end open to unverified vendors.

Audit Your Stack Today

The June 15 enforcement date leaves very little time to clean up a messy tech stack.

Every publisher needs to run a full audit of the third-party scripts operating in the background of their website right now. If you cannot confidently identify what every piece of injected code does, your search ranking is at immediate risk.

(Source: New spam policy against back button hijacking, Google Search Central Blog, April 13, 2026)

For the average consumer, this is a major product update. For local publishers, it signals the final stages of a critical structural change. Relying on search engines to deliver readers to your website is no longer a viable business plan.

The Context Monopoly

When a user points a camera at a problem, Google captures their real-world intent instantly. More importantly, it delivers the answer directly within its own interface.

This new format bypasses the traditional Search Engine Results Page (SERP) entirely. If a user receives an instant, conversational answer via voice and video, they have no reason to click a blue link and visit a publisher's website. The traditional transaction (we provide the information, Google provides the traffic) is breaking down. Search engines are becoming answer engines, keeping users firmly within their own ecosystem.

The Illusion of the Open Web

For years, local media companies built their financial models around "drive-by" traffic. You publish an article, optimize it for search, and wait for visitors to click through.

As features like Search Live scale, the volume of that passive traffic will drop sharply. A newsroom cannot run payroll based on the hope that an algorithmic search query will result in a pageview. The open web, functioning as a reliable and free distribution channel for local news, is closing.

The Pivot to Audience Sovereignty

If external traffic sources are drying up, the most practical defense is building your own walled garden. The goal is not to keep readers out, but to protect the community inside.

Transitioning casual, anonymous readers into logged-in, authenticated members is now a survival requirement. Advertisers are demanding verified audiences. In a market where third-party cookies are dead and tech platforms generate instant answers, the first-party data of a dedicated local readership will soon be the only currency advertisers trust. You cannot sell ads against anonymous pageviews if those pageviews no longer exist.

The Infrastructure for Authenticated Communities

Converting anonymous traffic into a logged-in community requires specific technology. Most legacy publishing software was built strictly to maximize pageviews and serve banner ads to unknown visitors. It lacks the basic tools to manage user accounts, gate premium content, or collect zero-party data efficiently.

We see this exact bottleneck constantly at 4media. A publisher decides to focus on audience sovereignty, but their current CMS cannot handle user authentication without crashing or requiring expensive custom development.

To survive this shift, your platform must treat reader registration and data collection as core features, not optional add-ons. Keeping users on your domain requires software built for community management, not just content delivery. If your technology cannot seamlessly transition a casual reader into a known, registered member, you are entirely dependent on traffic sources you do not control.

Stop Renting Your Audience

The introduction of real-time, camera-based search proves that tech platforms will continue to prioritize their own interfaces over your website.

Evaluate your current audience strategy. If your business model relies on renting attention from search engines, your margins will continue to shrink. The only durable asset a newsroom owns is its direct relationship with its readers. Now is the time to build the infrastructure required to own that relationship completely.

(Source: Google Search Live Goes Global, Giving Users Real-Time Search With Voice And Video, Forbes, March 29, 2026)

You immediately check your analytics and server health. Everything on your dashboard is glowing green. You don't host pirated movies, you don't distribute malware, and your business is strictly legitimate. You sell B2B software, run a local news blog, or operate a boutique e-commerce store.

So, why is a perfectly legal, non-controversial website suddenly facing a digital embargo in specific regions of the world?

The contemporary internet is often romanticized as a borderless network, but the reality is a highly fragmented infrastructure defined by aggressive security algorithms, localized technical failures, and rigid legal boundaries.

If your website is experiencing unexplained regional blocking, you are likely the victim of what we call "non-punitive digital exclusion." Here is the exhaustive breakdown of why this happens, the invisible mechanisms at play, and how you can diagnose and resolve the issue.

Table of contents

1. 1. The Crossfire of Shared Infrastructure (IP Contamination)
2. 2. Regulatory Geofencing and the Crushing Cost of Compliance
3. 3. The Protocol Arms Race: How Upgrading Security Gets You Blocked
4. 4. Overzealous Web Application Firewalls (WAF) and Anomaly Scoring
5. 5. Invisible Glitches: BGP Leaks and SSL Misconfigurations
6. How to Diagnose and Resolve Non-Punitive Regional Blocks

1. The Crossfire of Shared Infrastructure (IP Contamination)

The architectural design of the modern web relies heavily on resource pooling. When you use a Content Delivery Network (CDN) or a shared hosting provider, your domain does not get a solitary, isolated IP address. Instead, your site shares an IP address with hundreds, sometimes thousands, of entirely unrelated websites.

While this makes hosting affordable and fast, it creates a profound vulnerability.

Imagine a governmental regulatory body - like Italy’s communications authority, AGCOM - deploying an automated system to block illegal live streaming of football matches. Their system, known as "Piracy Shield," empowers copyright holders to demand ISPs block specific IP addresses within 30 minutes.

Because illicit operators frequently lease generic CDN infrastructure or dynamically rotating IP addresses, authorities often end up blacklisting a shared node. When that happens, your legitimate business, which simply happened to be assigned the same IP address by your CDN provider, is instantly erased from that country’s internet.

In February 2024, a single block directed at a Cloudflare IP address by the Italian government accidentally rendered tens of thousands of innocent websites completely inaccessible to Italian users for hours. Furthermore, if you lease a new server and inherit an IP address previously "polluted" by a malicious tenant, you will find your site blocked from day one, entirely unaware of the historical baggage attached to your network routing.

2. Regulatory Geofencing and the Crushing Cost of Compliance

Sometimes, the block isn't coming from an external firewall; it’s being enforced by your own hosting infrastructure due to international data privacy laws.

The rollout of the European Union’s General Data Protection Regulation (GDPR) fundamentally altered global data processing. Because the GDPR carries severe financial penalties (up to €20 million or 4% of global turnover), it forces international companies to heavily audit their data flows.

For many small to medium-sized enterprises and regional publishers based in the US or Asia, the cost of auditing data, hiring Data Protection Officers, and risking devastating fines far outweighs the value of incidental web traffic from Europe.

As a result, thousands of legitimate sites deploy preemptive server-side geoblocking. They automatically serve a standard HTTP 451 (Unavailable For Legal Reasons) error code to any IP address originating from the EU. This trend is accelerating globally with the implementation of strict data localization laws in India (DPDPA), Vietnam, and various US states.

If your website relies on standard infrastructure configurations that automatically enforce geographic compliance and data sovereignty, you might need a comprehensive site structure optimization to ensure legitimate users from strictly regulated regions aren't blocked at the server level just to mitigate corporate risk.

3. The Protocol Arms Race: How Upgrading Security Gets You Blocked

There is a fascinating and highly destructive arms race occurring between global privacy advocates and state censors, and your website might be caught in the middle simply because you upgraded your security.

Historically, authoritarian regimes used Deep Packet Inspection (DPI) to monitor unencrypted Server Name Indication (SNI) data during a user's connection request, allowing them to block specific dissenting websites while leaving the rest of the web untouched.

To close this privacy loophole, the internet engineering community introduced TLS 1.3 and Encrypted Client Hello (ECH), which encrypt the entire handshake process. Because national firewalls (like China's Great Firewall or Russia's Roskomnadzor) can no longer read the destination domain name within the encrypted traffic, they face a binary choice: allow all traffic, or drop the connection entirely.

They often choose the latter. In recent years, both China and Russia have deployed updates to their firewalls to systematically drop traffic utilizing TLS 1.3 and ECH. If your site uses a major CDN that enables these modern encryption protocols by default, your content will be instantly blocked in these regions - not because of what you published, but because your connection is too secure for the state to monitor.

4. Overzealous Web Application Firewalls (WAF) and Anomaly Scoring

If your site is suddenly inaccessible to a cluster of corporate users or a specific geographic demographic, the culprit is often your own Web Application Firewall (WAF) generating false positives.

Enterprise firewalls provided by AWS, Microsoft Azure, and Cloudflare use anomaly scoring algorithms to protect against DDoS attacks and bot scraping. These managed rule sets (like the OWASP Core Rule Set) are intentionally designed to be exceedingly strict out of the box.

Legitimate user behaviors frequently trip these thresholds:

• Non-Browser Agents: AWS WAF Bot Control routinely blocks traffic from custom mobile apps or legacy browsers prevalent in specific developing regions.
• False Attack Signatures: A user submitting a standard form containing formatting that vaguely resembles code (e.g., the string 1=1) might trigger an Azure SQL Injection rule (Rule 942130), resulting in a silent block.

• BGP ASN Blackholing: To stop scraping, security administrators often ban entire Autonomous System Numbers (ASNs) associated with certain internet service providers. If a legitimate user accesses your site via a corporate VPN or an ISP that shares an ASN with bad actors, they are locked out.

  

Even essential tools, like automated compliance scanners verifying website accessibility or crawlers utilizing modern sitemaps in practice, are frequently flagged as malicious scrapers by aggressive IP reputation blacklists like the Spamhaus Blocklist (SBL), cutting off your ability to perform critical site audits.

5. Invisible Glitches: BGP Leaks and SSL Misconfigurations

Finally, regional blocking is often a symptom of deep structural failures in the internet's core routing architecture.

• BGP Route Leaks: The Border Gateway Protocol (BGP) dictates how traffic physically moves across the globe. Because it relies on trust, misconfigurations are common. A single automated routing error at a major data center can cause massive volumes of global internet traffic to be drawn into hardware not provisioned for it, resulting in localized traffic drops (such as the highly disruptive Cloudflare route leak incident in Miami). Users in Brazil might lose access to your site for hours while users in London see no issues.
• Incomplete SSL Certificate Chains: If your hosting server fails to transmit intermediate certificates during the secure handshake, modern browsers might dynamically fetch them, but older, legacy mobile devices (highly prevalent in developing regions) will fail the handshake entirely. To the end-user, this appears as an impenetrable regional block.
• CDN Point-of-Presence (PoP) Failures: If a specific regional CDN node in Frankfurt experiences hardware failure, users routed to that node will face timeouts, while users in Asia connecting to a Tokyo node experience flawless load times. Keep in mind that speed is the new currency; a slow, misconfigured CDN node can act exactly like an intentional regional block.

How to Diagnose and Resolve Non-Punitive Regional Blocks

Resolving these issues requires moving beyond basic server metrics and looking at the web from the outside in. Here is the operational checklist:

Deploy Synthetic Global Monitoring: Standard uptime tools ping your server from one location. You must use tools like DebugBear, Check-Host, or Semonto to test reachability, HTTP status codes, and SSL handshakes simultaneously from dozens of different global vantage points.

Audit Your WAF Logs: Dive deep into your Azure or AWS firewall logs. Look for the specific transaction IDs and rule triggers (e.g., details.data). Create highly granular exclusion lists rather than globally disabling essential security rules.

Evaluate Multi-CDN Architectures: Relying on a single CDN creates a single point of failure. Implementing a multi-CDN strategy ensures that if one provider faces an IP blacklist in Italy or a BGP routing leak in Miami, traffic seamlessly fails over to a healthy network.

Review Protocol Compatibility: If you are losing traffic in specific developing nations, audit your SSL/TLS configurations. Additionally, check if complex routing rules based on your structure are triggering legacy WAF rules. Ensure your certificate chains are complete and assess whether strictly enforcing TLS 1.3 is prematurely alienating users on legacy hardware.

Check Global IP Reputation: Regularly verify your server IP addresses against databases like Spamhaus, Cisco Talos, and Microsoft SmartScreen. If your shared IP is blacklisted due to a previous tenant, you must initiate the manual delisting process immediately.

The assumption that an inaccessible website is the result of targeted, punitive action is a misunderstanding of the modern internet's fragility. By understanding the architectural, legal, and cryptographic fault lines that divide the web, you can ensure your content remains truly global.

Are you struggling with unexplained traffic drops or complex technical SEO issues? Discover the top 10 reasons why your site might be invisible on Google and learn how to resolve them today.

What "Other" Actually Means

When industry reports track "Other" revenue, they are measuring direct business initiatives that fall outside traditional publishing. This includes local events, B2B marketing services, specialized directories, and custom commercial partnerships.

The data points to a clear trend: readers and local businesses are willing to pay for direct utility and connection. While standard display ads suffer from banner blindness and algorithmic shifts, targeted community events and local business services provide measurable value that advertisers will sponsor.

The Shift to a Service Hub

To build this revenue stream, publishers must rethink their core product. A newsroom can no longer function strictly as a daily newsfeed. It needs to operate as a local "service hub."

This strategy changes the relationship with the audience. Instead of just reporting on a local business trend, a service hub hosts a networking event for those business owners. Instead of just running standard banner ads for a local contractor, it builds a verified, searchable local business directory.

Building "Other" revenue is currently the most reliable path to achieving financial independence from Big Tech. You control the event, you control the service, and you control the direct relationship with the sponsor.

The Infrastructure Blocking the Shift

Pivoting to a service hub sounds straightforward until a publisher actually tries to execute it on legacy software.

Most traditional content management systems were built for one specific task: publishing text articles chronologically. They lack the architecture to support diverse business models. When editors try to launch a ticketed local event or build a rich B2B directory, the software breaks down, forcing them to rely on clunky third-party plugins or build entirely separate websites. If launching a new revenue stream requires a massive IT workaround, the initiative stalls before it even begins.

A modern CMS has to function as a true business platform. This is exactly why CMS4media includes a dedicated "Other" Revenue Engine. With over 30 built-in modules, publishers can instantly deploy tools like an advanced Calendar of Events or comprehensive Business Directories. The infrastructure allows you to monetize your community expertise immediately, without extra development costs or third-party subscriptions.

Build the Third Pillar

Relying entirely on ads and subscriptions is a high-risk model in the current media market.

Evaluate your profit and loss statement. If non-traditional services, events, and B2B partnerships do not form a solid third pillar of your revenue, your business remains highly vulnerable to the next algorithm update. The market is paying for utility and connection; make sure your newsroom has the strategy and the software to deliver it.

(Source: Global news industry revenue level in 2025 as publishers diversify beyond print, Press Gazette / WAN-IFRA Outlook)

By prioritizing proximity, TikTok is building a video-first alternative to Google Maps and local search. For local media organizations, this feature completely changes the rules of distribution. It rewards geographic relevance over global virality.

Stop Waiting for Google Search Traffic

Many publishers are still holding onto the hope that traditional search traffic will eventually return to previous levels. That plan is failing.

The organic reach is moving elsewhere. Audiences are increasingly turning to vertical video platforms to find out what is happening in their neighborhoods right now. TikTok’s shift to hyper-local content means the platform actively needs high-quality, geographically relevant information to populate this new feed. Local newsrooms are sitting on exactly the data this algorithm wants.

Geographic Relevance Beats Virality

For a long time, the problem with social video for local news was the scale. A detailed report on a city zoning change or a niche town hall meeting was never going to get a million views globally. It was considered "bad" content for the algorithm.

The Local feed flips that logic. You no longer need to chase global viral trends. A short video explaining a local tax hike doesn't need to appeal to someone across the country; it just needs to reach the people living in that specific zip code. The new feed turns highly localized, seemingly dry municipal reporting into a highly discoverable asset for thousands of neighbors.

The Pivot to a "Vertical Video Utility"

To take advantage of this, newsrooms must stop treating video as a promotional trailer for a text article. The strategy now is to pivot into a "vertical video utility."

This means providing raw, useful, and immediate local facts directly in the video format. If a user is checking the Local tab to find out why a major street is closed or what the city council decided about the new park, the newsroom that delivers that answer quickly on video wins the audience.

The Infrastructure for a Video-First Workflow

Executing this shift exposes a major operational problem for many legacy publishers. Transitioning to a video utility model requires looking closely at how your reporters actually file their work.

Most older content management systems treat vertical video as a frustrating afterthought. They were built specifically for text paragraphs and static photos. We see this growing need clearly at 4media, and we are actively planning new solutions to respond to it—ensuring that embedding vertical videos directly onto your website is a simple, clean process. Currently, when a newsroom tries to increase its video output using outdated software, editors end up spending hours fighting with clumsy upload tools, external hosting links, and broken embed codes.

If your reporters view adding video as a tedious technical chore, the strategy will fail. A modern CMS puts multimedia at the center of the workflow. It allows an editorial team to upload, tag, and distribute video assets just as easily as writing a headline. Technology should accelerate your video strategy, not hold it back.

Audit Your Video Strategy

The distribution model has changed, and the tools for discovery are now video-first and location-based.

Evaluate your current output. Determine if your newsroom can adapt its daily reporting to serve as a local utility on these new feeds. The audience is already using the Local tab to explore their cities; local publishers simply need the right strategy and the right publishing infrastructure to show up there.

(Source: Introducing the Local Feed on TikTok, TikTok Newsroom, Feb 11, 2026)

Why Chasing Output is a Losing Strategy

For years, the digital playbook for many newsrooms was simple: publish as much as possible to capture search engine traffic and social media algorithms.

The industry looks different now. Between zero-click searches, AI summaries, and video feeds, basic news is a commodity. Rewriting press releases or publishing standard event recaps puts you in direct competition with automated systems and global platforms. They will always beat you on speed and distribution.

Trying to win by publishing more commodity content is a dead end. Local news needs a different approach.

Adopting the Creator Playbook

Newsrooms successfully adapting to this change are doing the exact opposite of the old model. They publish less, but connect with their readers more directly.

The GNI report suggests adopting a "Creator Playbook." In practice, this means moving away from the institutional, anonymous voice of traditional reporting and focusing heavily on author personality and hyper-local value. Readers don't show loyalty to a masthead anymore; they follow specific journalists who understand their town.

To survive, editorial teams must strip away the generic filler and focus entirely on their core product: in-depth investigations, specific local context, and neighborhood-level analysis. Everything else is just noise.

Technology Built for Connection, Not Churn

The "Creator Playbook" is hard to execute on a platform built for volume. Most older content management systems operate like digital printing presses, built to push out dozens of short articles a day for ad impressions. They act as content factories, not community hubs.

Building real connections requires different tools. When a newsroom shifts to high-value reporting, its technology needs to support:

• Rich storytelling formats: Easy multimedia integration that goes beyond standard text blocks.
• Journalist branding: Personalized author pages that build loyalty to individual reporters.
• Direct distribution: Built-in newsletter and engagement tools that don't require custom coding or complex hacks.

This is why at 4media we are replacing older publishing tools with new modules and widgets that are truly useful in local newsrooms. A modern creator strategy fails if editors constantly fight their workflow. If the goal is to drive subscriptions through quality reporting, the technology must support that directly, rather than forcing teams to hack older software.

Competing on Context

An AI tool can instantly summarize a city council agenda. It cannot summarize the mood of the room, the history of a zoning dispute, or what the decision actually means for the neighborhood down the street.

Hyper-local context is a local newsroom's strongest asset. The goal is no longer to be the fastest with the basic facts. The goal is to provide unique insight that a generic summary cannot replicate.

(Source: Google News Initiative Impact Report, newsinitiative.withgoogle.com)

But this transition puts smaller publishers in a vulnerable spot. The systems that will dictate how AI developers pay for news are being built today. If your publishing infrastructure isn't ready to plug into those systems, you simply won't get paid.

The Risk of Standards Built by Giants

When massive global publishers team up to create technical standards, they design those standards for their own enterprise-grade technology stacks. The Financial Times and the BBC have vast engineering teams and custom-built platforms. A regional newspaper or an independent trade magazine does not.

The risk for smaller publishers isn't that AI companies will refuse to license their content. The risk is that the technical barrier to entry will be set too high. If the new SPUR standards require complex, embedded signals to prove ownership and set licensing terms, publishers using outdated software simply won't be able to participate. Their content will either be scraped for free because it lacks protective tags, or ignored entirely by legitimate licensing platforms because it isn't formatted correctly.

Making Content Machine-Legible

To participate in whatever licensing framework emerges from initiatives like SPUR, a publisher's content must be "legible" to machines from the moment it is published.

This goes far beyond putting a copyright notice in the footer of a website. Machine legibility happens at the metadata level. When an AI crawler indexes a page, it needs to instantly read clear, standardized ownership signals, author attributions, and a defined rights framework hidden within the code of the page. If that data is missing, the crawler assumes the content is fair game.

This technical requirement exposes a major vulnerability for legacy publishers. Most older content management systems were built strictly to display text and images to human readers. They were never designed to communicate complex licensing terms to automated web crawlers.

At 4media, we frequently encounter this structural problem when auditing the technology stacks of local publishers. A newsroom might produce incredibly valuable, original reporting, but their legacy CMS strips out or fails to generate the necessary metadata. Modern publishing infrastructure has to handle this automatically behind the scenes. Editors shouldn't have to learn how to code rights-management tags; the CMS should natively attach that ownership data to every article, photo, and video as part of the standard publishing workflow.

Preparing for the New Standard

The SPUR Coalition is a clear indicator that the media industry is moving toward a standardized, transactional relationship with AI companies.

Publishers waiting for a definitive legal ruling on AI copyright are likely wasting valuable time. The more practical step is to audit your current publishing software today. Every piece of original content needs clear ownership signals attached at the metadata level. Ensuring your infrastructure can support these emerging standards before they become mandatory is the best way to protect your content and ensure you are in a position to monetize it when the time comes.

(Source: The SPUR Coalition, spurcoalition.org)

The Logic of Shared Infrastructure

Over the last decade, the standard approach to saving local news has been the grant. These funds plug immediate budget holes, usually paying for specific projects or temporary hires. But when the grant period ends, the newsroom faces the exact same financial pressures as before.

The APFJ operates on a fundamentally different philosophy—one that actually dates back to 1848. Back then, six fiercely competing New York newspapers were struggling with immense telegraph bills. To survive, they formed a cooperative to share the costs of gathering news from Europe. By pooling their resources for baseline infrastructure, those publishers freed up their budgets to focus on the specialized reporting that actually defined them. That cooperative eventually became the Associated Press.

The APFJ is applying this exact logic to today's market. Rather than offering a temporary financial bailout, it provides a shared resource pool. Participating local outlets gain access to AP's national coverage of elections, health, and climate data, while also distributing their own reporting back through the AP's network. By sharing the heavy lifting of national news, local publishers can protect their unique identity and focus their limited resources directly on their own communities.

Covering National Issues with a Small Team

Most local newsrooms have enough staff to cover city council meetings, local business, and high school sports. The challenge arises when a major national story requires local context. A mid-sized county paper rarely has the resources to analyze federal health data or send a reporter to cover a major political convention.

Before programs like this existed, publishers generally faced three bad options. First, they could pay exorbitant syndication fees for a traditional wire service, essentially buying a massive firehose of daily content when they only needed a few relevant stories a week. Second, they could ignore the national angle completely, leaving readers to look elsewhere to understand how macro events impacted their town. Finally, they could pull their own reporters off the city desk and assign them to untangle complex federal policies. That approach usually just resulted in missed local stories and exhausted writers.

Programs like the APFJ give smaller newsrooms access to reliable national reporting that they can adapt for their specific audience, saving time and editorial resources.

Where Content Partnerships Hit a Wall

But having the right to use national reporting and actually getting it onto your homepage are two different things. This is the exact point where many content partnerships quietly fail.

When a small team decides to run an external story, that text has to physically enter their system. Ideally, this is seamless. In reality, it often involves an editor manually copying text from a wire portal and pasting it into an aging CMS. Suddenly, the time saved on reporting is lost to basic formatting. Paragraphs merge together. Image alignments break the layout. What was supposed to be a quick addition to the morning news mix becomes a frustrating chore of fighting with the software.

We see this specific bottleneck constantly when migrating legacy publishers to the 4media CMS. A newsroom will join a great network like the APFJ, only to realize their daily publishing tools are too rigid to handle outside content efficiently. If your technology turns a ready-to-publish article into a tedious copy-editing task, the partnership loses its value. Shared content only works when the newsroom's software allows editors to ingest it without a second thought.

Building Sustainable Media Networks

Local publishers cannot compete with tech platforms on sheer scale or personalized distribution. Their advantage lies in deep community ties and reliable reporting.

From our perspective at 4media, this expansion of the APFJ is a highly positive move. Working daily with local publishers, we consistently see that systemic, structural support yields far better long-term results than one-off cash injections. While this is just our assessment based on the current market landscape, combining shared editorial networks with the right publishing software seems like the most practical way for local newsrooms to increase their output and remain competitive without burning out their teams.

(Source: AP Fund for Journalism expands landmark local news program to 100 newsrooms, AP press release, 2026.)

A new text field is now available in the admin panel while:

• Adding or editing an article
• Adding or editing a poll
• Adding or editing a photo gallery

This field allows you to enter content that will be displayed directly above the main title.

New field in the article add/edit view
 

Example of how the kicker appears in an article.

Example of the kicker on the article list

How to Enable Kicker Display in a Thematic Widget

In Page Builder > Templates, a new option “Show Kickers” has been added when editing article widgets. This setting lets you choose whether or not to display kickers in the widgets.

Customizing the Visual Style of the Kicker

To adjust the kicker’s color scheme globally across all widgets, go to the Template Design tab in the Page Builder module.

If you want to change the appearance of the kicker for a specific widget, follow these steps:

• Go to Page Builder > Templates > select your template
• Hover over the widget you want to edit and click the Edit button
• Choose Widget Desing > Component Content > Kicker Style

The available customization options are the same as for other template elements.

To customize the kicker’s colors in both the entry list view (articles, galleries, polls) and inside individual entries (articles, galleries, polls), go to Settings > Custom CSS styles and add the necessary CSS styles.