Chapter 36: How to Do SEO for News Sites

A laptop, a camera and a microphone in front of screens in a newsroom

Last updated: November 1, 2026.

News site SEO is quite different from corporate site or e-commerce SEO. Because on the news side, one of the most important variables is time.

A product page being discovered by Google a few days later can sometimes be tolerated. But a trending story getting indexed 20 minutes late can cause it to lose a large part of its value.

On top of that, speed alone isn’t enough on news sites. Dozens, sometimes hundreds, of sites produce content about the same event.

That’s why I think news SEO has two core questions:

How fast can we get the story discovered?

and

What does the user find in our story that they can’t find on other sites?

1. Why is news site SEO different?

A corporate site may publish a few new pages a month. An e-commerce site may add dozens of new products a day. A news site, on the other hand, can produce 100-200, sometimes far more, new URLs a day.

So on a news site, these are managed within a system that changes much faster:

  • Fast discovery
  • Indexing
  • News sitemap
  • Internal linking
  • Categories
  • Tags
  • Headlines
  • Images
  • Publish and update dates
  • Old stories
  • Server performance
  • Discover
  • Google News
  • Crawl budget

In news SEO, making the publishing system SEO-friendly matters as much as optimizing individual pages.

2. Publishing the story fast isn’t enough, Google has to discover it fast

Let’s say there’s a breaking development. People start searching on Google a few minutes after the event happens.

You published the story at 14:00, but Google discovered the URL at 14:20. If your competitor was indexed at 14:05, those 15 minutes in between can be huge for a hot story.

That’s why, the moment a story is published, these systems need to work together as much as possible:

  • The story URL should be created.
  • It should get a link from the home page or a suitable module.
  • It should be added to the category.
  • Related stories should link to it.
  • It should go into the news sitemap.
  • The page should be accessible to Googlebot.

In other words, the SEO process should start automatically when the editor clicks “Publish”.

3. The news sitemap and a real cache problem we ran into

On news sites, the news sitemap is one of the important tools for getting new URLs discovered quickly by Google. But just having a sitemap isn’t enough.

How fast it gets updated matters too.

On a large news site, we had a problem where new stories were showing up in Google late. At first glance, everything was technically normal:

  • The sitemap loaded.
  • The XML was valid.
  • The story page was accessible.
  • The server wasn’t returning errors.

And no SEO tool was telling us, “The problem here is the sitemap.”

While investigating, we saw that the sitemap was being cached for about 10 minutes to reduce server load. A story was published at 10:00, but the new URL appeared in the sitemap at around 10:10.

For a corporate site, 10 minutes might not matter. On a news site, those 10 minutes are very valuable.

When we cut the cache time down to a matter of seconds, the late indexing problem decreased significantly.

I think this example explains news SEO really well:

A system that works technically can still be working wrong for the business model.

Another important lesson is this:

No error showing up in a tool doesn’t mean there’s no problem.

First we noticed the problem: “Why are new stories getting indexed late?” Then we worked through the possibilities and found the cause. A big part of SEO expertise sometimes starts right there.

4. The home page and category structure matter for fast discovery

How quickly a new story becomes visible within the site after it’s published matters. The home page can be one of the areas Googlebot visits most often.

Similarly, these areas can also help a new URL get discovered:

  • Category pages
  • Latest news section
  • Related stories
  • Topic pages

But if a story shows up on the home page for a few minutes and then immediately sinks very deep, discovery can get harder.

That’s why the home page is not just a design area. It’s one of the main internal linking hubs of a news site.

5. News categories are not just navigation

Category pages like sports, economy, technology, entertainment and world can turn into strong pages over the years.

A good category structure:

  • Makes it easier to discover new stories.
  • Strengthens topical relationships.
  • Takes the user to similar stories.
  • Organizes the internal link structure.

But increasing the number of categories unnecessarily can also complicate the site architecture. Rather than adding each story to three to five different categories, it’s healthier to keep it in the structure it really belongs to.

6. Tags can be useful, but they cause serious problems if they grow uncontrolled

Using tags is very common on news sites. For example, topic pages like Galatasaray, Bitcoin, Elon Musk, Istanbul and Earthquake can be very meaningful.

But if every editor creates new tags on every story, a few years later you can end up with:

  • Thousands of tags with only one story
  • Different tags that mean the same thing
  • Misspelled tags
  • Empty tag pages
  • Duplicate topic pages

This can create index bloat.

It’s better to think of the tag system not as “Let’s turn every word in the story into a tag” but as “Let’s create real topic pages users will want to come back to.”

7. A news headline should think about both search and journalism

A headline can be very creative, but if it doesn’t say what the event is, it can be weak for SEO. On the other hand, a headline stuffed with keywords is bad for the user too.

I think a good news headline should:

  • Clearly describe the event.
  • Name the key person or topic.
  • Avoid unnecessary wordplay.
  • Not mislead the user.
  • Deliver on the curiosity it creates, if it creates any.

For example, a headline like “You won’t believe this!” may bring an instant click. But a news site that constantly uses that kind of language can damage its brand trust over time.

8. Sometimes SEO prep can be done before the story is published

In news SEO, not everything has to be done after the event happens. Sometimes we know in advance what’s going to be trending.

We experienced this years ago when Emre Mor was about to play for the Turkish national team for the first time. Emre Mor was still a very new footballer that people were curious about. We prepared a comprehensive story about him. But we didn’t publish it right away.

We watched the national team match. The moment Emre Mor came on, we published the story.

At the same moment, people started searching things like “Who is Emre Mor?” and “Where is Emre Mor from?” That story alone got around 3,000-4,000 visitors at once.

2-3 hours later, almost every major news site had similar content. But by then, we had already taken a big share of the first big wave of traffic.

I think the nice thing about this example is this:

News SEO is sometimes not about writing fast, but about being ready for the right moment.

If the news agenda can be planned, preparing content in advance can give you a very serious advantage.

9. Does the first to publish win?

Not always. Being first to publish gives you an advantage on a hot story.

But if you publish the story incomplete, wrong, unsourced or without value, that advantage won’t last long.

I think the ideal equation on a news site should be speed + accuracy + added value.

For example, if everyone is publishing the same official statement, our story can:

  • Explain past events.
  • Offer a timeline.
  • Add expert opinion.
  • Provide data.
  • Go to the original source.
  • Link to previous stories on the topic.

That way we’re not just fast, but more useful too.

10. Publishing a wire story as is isn’t enough

Hundreds of sites can publish the same text from a news agency at the same time. When we publish the text as is, this question comes up:

Why should Google or the user choose our page?

That’s why, when using a wire story, it helps to add differentiating elements like these whenever possible:

  • Additional information
  • Past developments
  • The original source
  • Information from our own reporter
  • Expert commentary
  • Data
  • Images
  • Video

“Original content” doesn’t just mean changing the words in the sentences.

It means adding new value to the story.

11. Trace the source back as far as possible

Instead of using a source by going from one news site to another, and from there to yet another story, you need to get to the original source whenever possible.

For example, if there’s one of these, it’s healthier to look at the source directly:

  • A ministry
  • The Official Gazette
  • KAP (Turkey’s Public Disclosure Platform)
  • A club’s official statement
  • A court ruling
  • A company statement

Because as news sites quote each other, even a small error can grow. Citing your sources also matters for user trust.

12. Should a new URL be opened for every development in the same event?

This depends entirely on how the event unfolds.

For example, a major earthquake happens. The first story is published. Then:

  • The magnitude changes.
  • A minister makes a statement.
  • New damage information comes in.
  • An aftershock happens.

If each development has its own news value, a new URL can make sense. But opening the same story over and over for 20 small developments can create a lot of pages that look alike.

In some cases, updating the main story makes more sense. Especially for elections, transfers, disasters or live developments, continuously updating one strong main URL can be very useful.

13. Using the publish date and update date correctly

On a news site, it’s important for the user to be able to see the answers to “When was this information published?” and “When was it last updated?”

If we made a meaningful change, the update date can be shown. But changing a single punctuation mark in the story and refreshing the date to make the content look “new” is not right.

The date should inform the user. It shouldn’t be a manipulation tool.

14. Using news schema

On news pages, types like NewsArticle can be used for structured data. For example, information like this can be described to Google more clearly:

  • Headline
  • Image
  • Author
  • Publish date
  • Update date

But as with all schema work, the same rule applies here:

Adding schema is not a guarantee of visibility.

It helps Google understand the information on the page more easily.

15. Author information and transparency

On a news site especially, there should be an answer to “Who wrote this story?”

Author pages can include, for example:

  • Name
  • Short bio
  • Area of expertise
  • Stories they’ve published

Especially on topics that require more expertise, like economy, health and technology, the author’s identity becomes more valuable.

Also, having clear about, contact and company information for the publisher matters for trust.

16. Google News and classic Google Search are not the same thing

A story can perform in Google Search but not appear to the same degree in Google News. Likewise, a story that gets serious traffic in Google News may not be very strong in classic Search over the long term.

That’s why, if possible, these channels need to be separated in performance reports. Total organic traffic alone doesn’t tell the whole story.

17. Google Discover can show completely different traffic behavior

Discover can be a huge traffic source for news sites. But it’s quite volatile.

A piece of content can bring hundreds of thousands or even millions of visitors one day. The next day the traffic can be gone. That’s why you shouldn’t confuse Discover traffic with lasting Search growth.

I think it’s healthier to evaluate Search, Discover and News performance separately as much as possible.

18. Images are especially important for Discover

Discover is a very visual experience. That’s why the image should be:

  • High quality
  • Relevant to the story
  • Large enough
  • Sharp
  • Not misleading

Using an old photo as if it were from a new event, or adding an eye-catching image unrelated to the story, may bring clicks in the short term but can create a trust problem.

Also, copyright shouldn’t be forgotten with news images. Taking on legal risk for the sake of SEO doesn’t make sense.

19. Can Google access the image?

The editor being able to see the image in the browser doesn’t always mean Googlebot can access it too.

For example, bot access can be a problem because of a CDN rule, robots.txt, hotlink protection or a temporary URL.

Especially on news sites targeting Discover, image accessibility needs to be checked too.

20. Evergreen content can be far more valuable on a news site than we think

When people hear “news site”, everyone thinks of the daily news agenda. But some content brings traffic for years.

We saw this very clearly on one of our own projects. We had prepared a story on “Istanbul Animal Shelters”. It wasn’t a ready-made wire text. We did the research ourselves and produced comprehensive content that didn’t exist on other sites at the time.

This story was getting around 300 visits a day. It never stood out on any day’s “Today’s 10 most-read stories” list. But it kept producing traffic steadily, every single day.

When we looked at total traffic at the end of the year, it had made it into the site’s top 10 most-read stories.

I think this example shows really well why looking only at daily traffic numbers on news sites is wrong.

A story can get 200,000 visits on the first day and then die out completely. Another story gets 300 visits a day but keeps that up for years. We can’t say which one is more valuable just by looking at the first 24 hours.

21. Daily news and evergreen content should be treated as separate strategies

On news sites, two different content engines can be built.

The first: The news agenda. Fast traffic. Discover. Google News. Social media.

The second: Evergreen. Long-term Search traffic. For example:

  • Biographies
  • Guides
  • Local resources
  • Information about institutions
  • Historical topics
  • Explainers

The success criteria for these two content types should also be different.

22. Automatically deleting old stories is not right

A story may have been published three years ago. But it may still:

  • Get searches
  • Get backlinks
  • Serve as a historical source
  • Be referenced by new stories

That’s why I don’t agree with the “Let’s delete old stories and clean up the site” approach. You need to look at the data first.

For an old story, you need to decide:

  • Will it be updated?
  • Will it stay as it is?
  • Will it be merged with another page?
  • Will it really be removed?

23. A 301 isn’t always the solution for very old or removed stories

If the story really has a follow-up or a meaningful equivalent, a 301 can be considered. But redirecting an unrelated story from 10 years ago to the home page just because it was deleted is not right. If there’s no real equivalent, a 404 or 410 can be normal.

The logic we discussed for e-commerce applies on a news site too:

For a redirect, there needs to be a meaningful target.

24. Canonical errors can grow fast on a news site

Because a news site runs on templates, a small technical error can spread to thousands of URLs.

For example, the canonical template was updated incorrectly. Today, 200 stories. Tomorrow, 200 more. A week later, you can have thousands of wrong canonicals.

That’s why pre-release testing, post-deploy checks and monthly audits are especially important on news sites.

25. Crawl budget matters on large news sites

A news site that publishes 100-200 pieces a day and has been live for years can end up with hundreds of thousands or even millions of URLs.

If Googlebot spends most of its time on:

  • Empty tags
  • Unnecessary parameters
  • Endless archives
  • Duplicate URLs

then fast discovery of new stories can get harder. That’s why URL generation needs to be kept under control.

26. Server performance is critical on a news site

News traffic may not be steady. A site that normally gets a small number of requests per second can get very serious traffic during a major event.

If the server crashes at exactly the moment the most users arrive:

  • Users can’t get into the site.
  • Ad revenue is lost.
  • Googlebot sees 5xx errors.
  • Traffic goes to competitors.

That’s why a news site’s performance plan should be made not just for average traffic but also for traffic peaks.

27. Caching is necessary, but the wrong caching can be dangerous for a news site

Caching is necessary for a high-traffic news site. But as we saw in our sitemap example, where and for how long caching is used matters.

If the breaking news section on the home page stays 15 minutes out of date, that’s a problem. If live score data updates late, that’s a problem. If the sitemap shows a new URL late, that’s a problem.

So:

Using a cache is right. Caching everything for the same amount of time is wrong.

28. A balance has to be struck between ads and user experience

News sites make money from ads. So we can’t just say, let’s remove the ads.

But if the page:

  • Keeps shifting
  • Shows ads in front of the content
  • Makes the user click in the wrong place
  • Strains the device with JavaScript load
  • Makes the story unreadable

that’s also a problem in the long run.

Especially in performance areas like CLS, LCP and INP, ad systems can have a serious impact. The SEO team and ad operations need to work together.

29. Mobile experience should be a priority on a news site

A large share of news consumption comes from mobile devices. On mobile, these should be checked:

  • Does the story load fast?
  • Are the headline and intro readable?
  • Do ads cover the content?
  • Do the images look right?
  • Is the font readable?
  • Do the related story links work?
  • Are the sharing options easy to use?

A site that looks great on desktop being unusable on mobile is a serious loss for a news site.

30. Uptime should be monitored in real time

On a news site, it’s not enough for the site to be up all day. It needs to not be down at the moment of the biggest story.

That’s why the site, critical services, the server and SSL can be monitored with systems like UptimeRobot.

Saying “The site was down for 45 minutes last week” at the end of the month is far too late. These checks should be in real time.

31. Search, Discover and News shouldn’t be read like the same report

Total traffic on a news site may have gone up. But the entire increase may have come from Discover. Or lasting Search traffic may be growing while Discover drops.

That’s why, in reporting, Search traffic, Discover traffic and News traffic should be read separately as much as possible. That way we can understand whether the site is getting daily spikes or sustainable organic visibility.

32. The story with the most traffic is not always the most successful one

One story can bring 1 million visits on the first day. Another story can bring 300 visits a day.

The first piece of content can die out completely the next day. If the second piece produces traffic for 365 days, it can generate over roughly 100,000 visits a year.

That’s why, for news performance, you shouldn’t just look at “How many people read it on the first day?” The total value over time matters too.

Our Istanbul Animal Shelters example was exactly that.

33. Editor training is a must on a news site

I think this is one of the most important topics in news SEO.

Over the years, we’ve given SEO training to the editorial teams of many news sites. Because if a news site publishes 100-200 pieces a day, it’s not possible for the SEO agency to intervene in every story one by one.

The agency can:

  • Set up the system.
  • Define the rules.
  • Run audits.
  • Provide training.
  • Track problems.

But the editor:

  • Writes the headline.
  • Chooses the image.
  • Enters the source.
  • Adds the tags.
  • Updates the story.
  • Adds internal links.

So the people entering content need to know SEO at least at a basic level.

For example, the editor should know that:

  • The headline should be clear.
  • Unnecessary tags shouldn’t be created.
  • The source should be cited.
  • Older related stories should be linked.
  • The same event shouldn’t be opened again unnecessarily.
  • The image should be chosen correctly.
  • If the story is updated, the date should be used correctly.

I think one of the agency’s jobs in news site SEO is also:

Building an editorial system that knows SEO.

34. An SEO checklist can make the editor’s job easier

We discussed checklists in Chapter 34. For a news site, a short publishing checklist can be prepared for editors.

For example:

  • Is the headline right?
  • Is the URL right?
  • Is the category right?
  • Is there a source?
  • Is the image right?
  • If alt text is needed, has it been entered?
  • Are there links to related stories?
  • Were unnecessary tags created?
  • Is the date right?

With this list, the editor doesn’t need to ask the SEO specialist about every story. The system doesn’t depend on one person.

35. Automation is very valuable on high-volume news sites

In a system where 200 stories are entered a day, there’s no point doing some tasks manually.

When a story is published, these can happen automatically:

  • The sitemap can be updated.
  • NewsArticle schema can be generated.
  • The category link can be set up.
  • Related stories can be calculated.
  • Social media output can be prepared.

But there’s another risk here. If the automation is working wrong, it produces the error not in one story but in all of them.

That’s why automation and a control mechanism should be set up together.

36. News SEO is not just the SEO team’s job

In successful news site SEO, these teams need to work together:

  • Editors
  • SEO
  • Software development
  • Systems team
  • Ad operations
  • Design
  • Data team

For example, the SEO team wants to speed up the page. The ad team adds a new script. The editor wants more modules on the home page. The server team wants to reduce load.

All of these need to meet at a common point. News site SEO is truly a team effort.

To sum up

Seeing news SEO at the level of “Let’s write titles and submit a sitemap” is very incomplete.

There are several different races going on here at the same time.

The speed race. Catching the first big wave of searches by publishing at the right moment, as in the Emre Mor example.

The quality race. Being able to offer more valuable information than the hundreds of sites publishing the same wire story.

The long-term value race. Creating content that produces traffic all year without ever being a headline, as in the Istanbul Animal Shelters example.

The technical race. Building a system Google can discover within seconds of publishing a story.

And all of these require the editorial, software and SEO teams to work together.

I think the summary of news SEO is this:

Being fast is important. But being ready at the right time, getting discovered fast and offering more value than other stories is more important.

Sometimes that pays off as 3,000-4,000 visitors at once. Sometimes 300 people come every day and, by the end of the year, it turns into one of the site’s most valuable pieces of content.

Good news SEO is being able to do both.

Previous: Chapter 35: How to Do E-commerce SEO · Contents · Next: Chapter 37: How to Do Local SEO

This chapter was first published in Turkish on X (October 14, 2026).