How to Build a News Website That Ranks on Google News and Discover
News website development for Google News and Discover comes down to four foundations: pages that load fast on mobile, technical SEO built for news (news sitemaps, NewsArticle structured data and clean URLs), clear transparency about who runs the publication and who writes each story, and large, high-quality images on every article. There is no fee or application that buys a place in Google News, because Google considers sites automatically based on its content policies and quality signals. Get the foundations right, keep publishing original and timely journalism, and your platform will help rather than hold you back.
This guide explains how to build a news website step by step: the newsroom workflow and CMS, speed, technical SEO, Discover, AMP, agency feeds, the ePaper and apps, and monetization. It is written for publishers and editors planning a new site or a rebuild.
Key takeaways
- Plan the newsroom workflow first; the CMS should make publishing fast for editors on desktop and mobile.
- Speed matters most on article pages carrying ads. Aim for good Core Web Vitals on mobile.
- Keep a news sitemap of stories from the last two days, updated automatically on every publish.
- Add NewsArticle structured data with accurate headlines, dates, authors and images.
- For Discover, use large images at least 1,200 pixels wide and allow large image previews.
- AMP is no longer required for Top Stories; a fast standard page is enough.
Start with the newsroom workflow
A news site is a production system before it is a website. Map how stories move: who writes them (staff reporters, contributors or agency feeds), who edits and approves them, and how breaking news skips the queue. Then define roles such as reporter, desk editor, section editor and admin, so the right people can publish without bottlenecks.
Editors increasingly work from their phones, so a mobile-first admin is a requirement, not a luxury. Publishing a breaking story, updating a headline or swapping an image should take seconds on a phone.
Choosing a news CMS
There are three broad routes, and the right one depends on your size, languages and plans for apps. This comparison shows the trade-offs:
| Option | Strengths | Trade-offs | Best for |
|---|---|---|---|
| Off-the-shelf CMS with plugins | Quick to start, familiar to many editors, low upfront cost | Plugin overload slows pages; agency import and ePaper need add-ons | Small sites with simple workflows |
| Headless CMS with a custom frontend | Fast frontend, one content API for web and apps | Newsroom features need development | Growing publishers with app plans |
| Purpose-built news platform | Newsroom roles, agency feeds, ePaper, apps and ads designed in from the start | Higher effort if built from scratch; lower if you start from a ready-made platform | Publishers who depend on search and Discover traffic |
Build for speed from day one
News readers arrive from search, Discover and social links, mostly on phones and often on slow connections. A slow article page loses them before the first paragraph. Google's Core Web Vitals measure this experience, and the "good" thresholds are a Largest Contentful Paint of 2.5 seconds or less, an Interaction to Next Paint of 200 milliseconds or less and a Cumulative Layout Shift of 0.1 or less.
A handful of architecture choices make the biggest difference. Build them in from the start rather than retrofitting them later:
- Pre-rendered pages served from the edge. Frameworks such as Next.js can generate article pages ahead of time and refresh them on publish, while a CDN such as Cloudflare serves them from locations close to readers.
- Instant cache refresh, so corrections and updates appear immediately without slowing every page view.
- Optimized images: responsive sizes, modern formats such as WebP or AVIF, and lazy loading below the fold. Never lazy-load the lead image.
- Lean fonts: few font files, subset for the scripts you publish in, which matters for Hindi and other Indic languages.
- Disciplined third-party scripts: audit trackers, widgets and ad code regularly, and load them so they never block the article text.
- Reserved ad slots: fixed space for every ad unit, so the page doesn't jump as ads load.
Technical SEO checklist for Google News
Work through this news website SEO checklist before launch and again after every major release. For an existing site, an SEO audit against the same list is a sensible first step.
- News sitemap. List articles published in the last two days with the publication name, language, publication date and title. Keep each news sitemap to 1,000 URLs or fewer, generate it automatically and submit it in Google Search Console, alongside a regular XML sitemap for everything else.
- NewsArticle structured data. Use schema.org markup with the headline, images, datePublished, dateModified and author names linked to author pages. Supply the lead image in several aspect ratios, such as 16:9, 4:3 and 1:1.
- Honest dates. Show published and updated times on the page, matching the structured data, and change dateModified only when the story meaningfully changes.
- Stable, readable URLs. Give each story one permanent URL with a canonical tag, and never change URLs without permanent redirects.
- Transparency pages. Publish author pages with bios, plus About, Contact, Editorial policy, Corrections and ownership details. They help readers and Google judge who stands behind your journalism.
- Useful section and tag pages. Keep them crawlable and substantial, and avoid thousands of thin tag pages holding one story each.
- Video markup. Add VideoObject structured data to stories built around video.
- Open access for crawlers. Make sure robots rules don't block Google's crawlers, your images or the files needed to render the page.
Getting your stories into Google Discover
Discover is a personalized feed, not a results page, so no special markup gets you in. Google Discover optimization is mostly about content that matches readers' interests, from sites that show expertise and trustworthiness, with strong visuals.
- Use large, high-quality images at least 1,200 pixels wide on every story, and enable large previews with the max-image-preview:large robots setting.
- Lead with real photos, not your site logo or generic graphics.
- Write headlines that capture the story. Google's Discover guidance discourages clickbait and exaggerated previews, and readers who feel tricked don't come back.
- Publish timely and evergreen work. Explainers and guides can appear in Discover long after publication.
- Watch the Discover report in Search Console to learn which topics and formats earn visibility.
Do you still need AMP?
No. AMP is no longer required to appear in Top Stories, and a fast standard page qualifies on its own. Running AMP alongside your main templates means a second set of templates to design, test and maintain. If you already have AMP pages, retire them carefully with redirects or canonical tags, and monitor Search Console during the transition.
Agency feeds and AI-assisted SEO
Most news sites combine original reporting with stories from news agencies. A good platform imports agency copy automatically through the agency's feed or API, maps it to your sections, removes duplicates, and either publishes it under your rules or queues it for an editor. Always credit the agency and follow the terms of your subscription.
AI can speed up the SEO work around each story by drafting search-friendly headlines, tags and meta descriptions in seconds. Keep editors in control of the final versions, and never let AI add facts to the story itself. Because many sites carry the same agency copy, your original angles, local reporting and explainers are what set your coverage apart.
ePaper and apps on one backend
If you publish a print edition, a digital ePaper extends its reach. Look for a page-turn viewer that works on phones, article clipping and sharing, a date-wise archive and optional subscriptions.
Android and iOS apps bring loyal readers back through push notifications for breaking news. The key design decision is to run the website, apps and ePaper from one backend and content API, so editors publish once and every channel updates together. Our mobile app development team builds news apps on this model.
Running editions in more than one language
If you publish in two or more languages, decide early whether each edition is a separate site, a subdomain or a section of one domain. Each edition needs its own news sitemap with the correct language code, its own section structure and fonts that render its script quickly. Use hreflang annotations only when articles are true translations of each other, because independently reported editions should stand on their own. A shared codebase across editions keeps workflows, ads and apps consistent while each newsroom keeps its own voice.
Monetization: ads, subscriptions and more
- Programmatic display ads through platforms such as Google AdSense or Google Ad Manager. Publish an ads.txt file, keep ad density reasonable on mobile and lazy-load ads below the fold.
- Direct-sold ads for local and regional advertisers, managed from the CMS, with clear labels on sponsored content.
- Subscriptions and memberships for the ePaper, premium stories or ad-free reading. Mark paywalled content with the matching structured data so search engines understand it.
- Newsletters and push notifications that bring readers back directly and reduce dependence on any single traffic source.
Moving an existing news site without losing traffic
Many publishers are rebuilding rather than starting fresh, and a migration is where search traffic is most often lost. Treat it as an SEO project, not just a design launch:
- Crawl the old site and export every URL that has traffic or links, including articles, sections, tags, authors and images.
- Keep URLs unchanged where you can. Where they must change, map each old URL to its new equivalent with a permanent (301) redirect.
- Carry over structured data, canonical tags and sitemaps, and check that article dates and author names migrate correctly.
- Test on a staging address with real content before switching, including page speed on mobile.
- Switch during a low-traffic window, submit the new sitemaps in Search Console and watch crawl errors and traffic daily for the first few weeks.
A working example: The Hawk and Dainik Hawk
ZedBlu built and runs the digital platform behind The Hawk, an English news site, and Dainik Hawk, a Hindi news site. It follows the approach in this guide: a Next.js website served from Cloudflare's global edge, a mobile-first newsroom admin and CMS, and automatic import of news-agency stories with AI-generated SEO headlines, tags and meta descriptions. A digital ePaper and Android and iOS apps run on the same backend.
Mistakes that hold news sites back
- Heavy themes and dozens of plugins or scripts that slow every page.
- Ads that push content down as they load.
- Site migrations without a complete redirect map, which throw away years of search visibility.
- Missing bylines, author pages or visible dates.
- Agency copy published with nothing added while other sites run the identical story.
- Small images, logos as lead images, or clickbait headlines that hurt Discover performance.
What to measure after launch
A new platform is only the start. Review these numbers every week, and act on what they show:
- Search Console performance for Search, News and Discover, broken down by section and story type.
- Core Web Vitals field data for article pages, especially those carrying the most ads.
- Indexing speed, meaning how quickly new stories appear in search after publishing.
- Returning readers from apps, newsletters and push notifications.
- Ad revenue per thousand page views by section, so ad decisions rest on data rather than guesswork.
Plan your news platform
If you are launching a publication or rebuilding one, ZedBlu's platform for news portal development includes the CMS, agency feed import, ePaper, apps and ad management described above. You can subscribe monthly under your own brand, license it with source code or commission a custom build. See our work for media and publishing companies, or book a free demo to see the newsroom in action.
