News Website Design

A news website is not tested on launch day but six months later: hundreds of articles have piled up, three writers share the same dashboard, the ad network wants another slot and an old story needs a correction. Decisions skipped during design turn into costly technical debt at that point.

We, Talha Aslan and team, wrote this guide in the order we follow when we build a publishing site: the publishing model and legal frame first, then the archive, page templates and team workflow, then platform, ads, search and measurement. Each section gives you criteria you can apply to your own project or to a proposal from any agency.

01Name your publishing model before anything else

The first decision that shapes a news website is what kind of publication you run. A local outlet that puts out dozens of short stories a day and a content site that publishes twenty long guides a month cannot share the same front page, archive or workflow. The first needs speed and ordering, the second needs topic clusters and a habit of updating older pieces.

Before the first call with any agency, write down answers to these questions:

• Frequency: How many pieces go out per day or per week, and how that number will change over the next year.
• Shelf life: Whether your articles are read for a few days or collect search traffic for years.
• Revenue model: Display ads, sponsored content, memberships, an organization's budget or a mix of these.
• Team: How many writers and editors you have, and whether freelance reporters or guest authors will contribute.
• Status: Whether you publish as a press outlet with legal duties in your country or as the publication of a company or association.

A theme picked before these answers are clear usually brings the template of the wrong model, such as a trade magazine squeezed into a newspaper layout with a breaking news ticker.

02Legal duties that end up in the template

Wherever you publish, some legal duties land directly in the site template, and they are much harder to add after launch than to plan from the start. The details depend on the country, so we design the fields and leave the legal assessment to your lawyer.

Examples from the markets we work in most:

• Turkey: The Press Law (No. 5187) requires internet news sites to make contact and hosting provider details reachable from the front page, show first published and updated dates on content, keep content for two years and publish a correction within one day.
• Germany: For journalistic and editorial offerings, § 18 (2) of the Interstate Media Treaty requires a named responsible person with address in addition to the legal notice.
• European Economic Area: Consent is needed before non essential tracking, and Google requires consent mode for its measurement and personalized advertising features for users there.

In the template this becomes a permanent masthead page linked from the footer, a date line under every headline that fills itself, a corrections field editors can use in minutes and an archive policy where unpublished content is kept rather than deleted. Registration, regulators and editors' codes are questions for your legal advisor.

03Section tree and permanent URL plan

On a news website, the section structure is the most expensive decision to change after launch, because every change creates work on URLs, redirects and internal links. We therefore plan sections for the content you will publish two years from now, not just for what you have today.

We plan it in this order:

1. List the headlines you published, or plan to publish, over the last few months and group them by topic.
2. Decide whether each group is permanent or seasonal; elections, campaigns and tournaments become tags, not sections.
3. Keep the number of main sections small enough to fit the main menu and be scanned at a glance; open a subsection only if enough content will really accumulate.
4. Give every article exactly one main section, and build URLs and breadcrumbs on that section.
5. Fix the URL format before launch: whether the section name and the date appear in the address is settled once.

Tags need rules as well. Tag pages that hold one or two articles create thin pages that look like copies of each other. Keeping tag pages out of the index until they reach a set number of articles, and letting editors choose from an existing tag list rather than typing new ones, prevents that sprawl. To keep a page out of the index, leave it crawlable and add noindex; if robots.txt blocks the page, Google cannot read the noindex at all.

04Front page and top story logic

The front page has one job: show readers what matters today within seconds and carry them to the next click. A grid with a few boxes from every section does not do that job. The top story area is filled by an editor's decision, the latest feed fills itself by publication time.

When we design the front page, we look at these criteria:

• Number of top stories: One lead story with a few supporting pieces instead of a rotating slider; sliders are slow and most readers never see the second slide.
• Manual and automatic areas: Which blocks editors curate and which fill by date or section is defined before design starts.
• Section blocks: Only sections readers actually follow get a block on the front page; the rest are reached through the menu.
• Breaking news bar: Added only if you really cover developing stories during the day; an empty bar or one showing yesterday's story damages trust.

The first screen on a phone is the most important decision on the page. The lead image, headline and date should load before ads and pop ups. We design the phone order first and treat desktop as its wider version.

A most read block should count only recent days, or a months old story sticks in the list and the front page looks stale.

05What belongs in the article template

Readers spend most of their time on individual article pages, not on the front page, so every part of the template must earn its place.

The components we recommend for an article template:

• Headline and standfirst: The headline tells the story; the standfirst answers who, what and where in two sentences and is a separate field, not a copy of the first paragraph.
• Byline and date line: The author name links to an author page, with published and updated dates next to it.
• Lead image: A fixed aspect ratio with caption and credit; because the ratio is fixed, text does not move while the image loads.
• Subheadings: Meaningful subheadings that help readers scan longer pieces.
• Correction and update note: A short note saying what changed whenever the content is materially revised.
• Related articles: A few pieces from the same main section and topic, which keep older content in circulation.

Link previews are part of the template too. When an article is shared in a messaging app or social network, the title, image and description should match the page. We add separate share image and description fields to every article and fall back to the lead image and standfirst when they are left empty.

06Author pages and why the byline matters

Who wrote a piece directly affects whether readers trust it, so a byline should be more than a name tag. Search engines also use author information to understand who stands behind the content, and Google recommends that author markup link to a page that identifies the writer.

A complete author page includes:

• Identity: Name, photo and a short introduction to the topics the person covers.
• Expertise: Professional background, training or concrete reasons why this person writes on the subject.
• Article list: Everything the author has written, newest first and paginated.
• Contact: A way for readers to reach the author or the editor with corrections or tips.

On the structured data side, every piece carries Article or NewsArticle markup, and headline, image, author and dates must match exactly what the page shows. Google recommends a visible, clearly labeled published or updated date that matches the structured data; a date in the text and a different date in the markup leaves the search engine guessing which one to trust. You can check the markup your template produces with our schema markup tool before launch.

We also create a page for shared bylines such as "Newsroom". It explains which team stands behind that name and what your editorial principles are.

07Drafts, approval and scheduled publishing

When publishing depends on one person's working hours, the site goes quiet whenever that person is on holiday; tying the workflow to roles and times removes that dependency. Every piece follows the same path, and each step shows who did what.

A typical article moves like this:

1. The writer prepares a draft; it cannot be sent for review until headline, standfirst, main section and image are filled in.
2. The editor reviews the draft, leaves notes if changes are needed and sends it back to the writer.
3. The approved piece is given a publication date and time, or goes live immediately.
4. When that time comes, the server publishes it, and the front page, section page, sitemap and RSS feed update with it.
5. Later changes are recorded as an updated date, and material changes get a correction note.

Permissions are set per person: writers see only their own drafts, editors manage everything and administrators add or remove users. When a writer leaves, their account closes but their articles and author page stay.

We run the scheduling part of this workflow live on Güncel Bilgin, our own publishing site. Güncel Bilgin is not a news agency; it is a Turkish content site with salary, severance and pension calculators and practical guides. Articles are scheduled ahead and the server publishes each one on time.

08WordPress, a static build or a mix of both

The platform for a news website is less a technology preference than an answer to how your team works: which dashboard editors work fastest in, and who maintains the site, how often.

We compare the options with these criteria:

• WordPress: Sensible when editors already know the dashboard, many pieces go out each day and several writers work at the same time; in return the plugin count must stay low and updates must run on a schedule.
• Statically generated site: Pages are built in advance and served as files, so they are fast, expose little to attackers and need little maintenance; a strong fit when content is less frequent but longer.
• Headless setup: Content is managed in one system and the site is generated by a separate front end; worth considering if the same content also feeds an app or other channels, though setup and upkeep take more technical effort.

Whatever the platform, we keep the dashboard simple: only the fields that content type needs, with free layout tools that could break the design switched off. When we moved Güncel Bilgin from WordPress to a static build, we made that choice based on publishing frequency and maintenance load, and we apply the same criteria to your project.

The platform question is at heart a website design decision, to be settled before design starts.

09Designing ad slots and speed together

On an ad funded news website, ads and speed are not rivals; they are two sides of the same design decision. Ad slots are placed while the page is drawn, their size is reserved in advance and their number is limited, so the text does not jump when an ad loads.

Google's page experience metrics are the guide here. LCP, the time until the largest content on the page has loaded, should be 2.5 seconds or less; INP, how quickly the page responds to a tap, 200 milliseconds or less; CLS, how much content shifts while the page loads, 0.1 or less. These count as good when met at the 75th percentile of visits. On ad heavy pages, CLS is the value that breaks most often.

The rules we apply to ad placement:

• Reserved space: Each slot's height is set from the start and stays in place even when no ad fills it.
• Slot limit: The number of slots per page depends on article length, and the text is not broken after every other paragraph.
• First screen: On phones the first screen belongs to the headline and lead image; ads start after the first scroll.
• Lazy loading: Slots further down load only as the reader approaches them.

We always measure speed with ads switched on. A test without ads does not reflect the page readers actually see.

10Helping search engines read your publication

Search visibility for a news website depends on technical order as much as on individual articles: search engines must find new content quickly, keep finding old content and know which date applies.

The technical points we watch:

• Sitemap: New and updated articles appear with their real last modified date; a setup that refreshes every date each night makes that signal worthless.
• Crawlable pagination: Section archives are paginated with normal links; an infinite feed that only loads on scroll leaves older articles without links.
• Permanent URLs: The URL stays the same even if the headline changes later; if it must change, the old address redirects to the new one.
• Date consistency: The visible date and the structured data date are the same, and a typo fix is not shown as an update.

Use our XML sitemap tool to see whether your sitemap is set up correctly. As output grows, internal linking matters more: when new articles link to older guides on the same topic, older content keeps being read and found. If you want article visibility handled together with your content plan, our SEO service is run by the same team. We do not promise rankings, but we make sure the technical foundation is complete.

11Channels that bring readers back, and measurement

Search and social traffic rise and fall; what keeps a publication alive is readers coming back on their own. That is why at least one return channel goes into the design from day one.

• Email newsletter: A daily or weekly digest, with the signup box at the end of the article, where the reader has just finished a piece.
• RSS feed: For feed readers and aggregators, with separate feeds per section if useful.
• Membership or subscription: Opening part of your content to members needs its own structure; we cover it on our membership website page.

For measurement, look beyond page views. Returning reader share, newsletter signups, scroll to the end of an article and clicks to related pieces show which content really adds value. Defining these on day one gives you comparable data six months later.

Analytics and ad tools process personal data, so a privacy notice is required, and readers in the EU must consent before non essential cookies are set. We design the consent banner like an ad slot, with its space planned so it does not cover the lead story or shift the page when it appears.

12Moving an old site without losing the archive

For an established news site, the archive is the most valuable asset; every URL lost in a migration takes its links and search traffic with it. We treat migration as an inventory job, not a design job.

1. Collect every old URL from the sitemap, a crawl and Search Console into one list.
2. Map each old URL to its counterpart on the new site; articles, sections and author pages are matched separately.
3. Redirect URLs that have a counterpart with a permanent 301; pages without one are closed as permanently removed.
4. Move images, author details and published and updated dates together with the content, so the migration date never shows up as the publication date.
5. Watch Search Console in the weeks after launch and fix any URL that returns an error right away.

When we moved Güncel Bilgin off WordPress, thousands of old URLs were handled this way. The detail most often missed is dates: imported articles must not all look as if published on one day.

If you are thinking of renewing an existing site, we describe the full process on our website redesign page; for news archives the same steps apply, with a larger inventory.

13Common mistakes in news website projects

We see the mistakes below on news website projects again and again, and all of them can be avoided cheaply during design.

• Choosing a theme by its demo: An impressive demo comes with blocks and plugins that do not fit your model; write down your page types and workflow first and judge any theme or design against that list.
• Adding ads after launch: Boxes added later shift the text and slow the page; draw ad slots with their sizes into the first design draft.
• Opening a section for every topic: Sections created for passing topics leave an empty, scattered archive a year later; make permanent topics sections and passing topics tags.
• Unsigned articles or empty author pages: Readers and search engines cannot see who stands behind the content; give every writer a complete page and explain shared bylines on a principles page.
• Updating dates the wrong way: Refreshing the updated date for small fixes, or resetting all dates during a migration, erodes trust; change the updated date only for material revisions.
• Measuring speed without ads: Values that look good in testing fall apart in production; measure on a phone with ads and the consent banner switched on.

14Questions to ask before you decide, and the next step

When choosing a partner for a news website, look less at design samples and more at how many questions the agency asks to understand your editorial routine. A proposal that never asks about your publishing frequency, team and revenue model is most likely the installation of a ready made theme.

We suggest asking every agency you talk to:

• How is the size of each ad slot reserved, and how is speed measured with ads running?
• Does scheduled publishing run on the server, or does it depend on someone keeping a dashboard open?
• Do the masthead, date line and corrections field come ready in the template?
• How are URL mapping and dates handled when migrating from the old site?
• Who handles updates and maintenance after launch, and on what schedule?

You can see the setup we use on our own publishing site, along with our other work, on our references page. If you are thinking of a simpler company site or blog, our fixed packages are listed under web design pricing; news and publishing sites are priced with a written quote based on scope.

For your news website, tell us briefly how often you publish, who is on your team and how you earn through our contact page. After a short call we send the site structure, workflow and scope we recommend in writing.