What happens when you change your template or migrate to HTTPS? Could it really hurt your Google News traffic?

Does Google News handle content differently than regular search?

Yes, and this is exactly where the issue arises. The Google News algorithm uses specific parsers to extract the structural elements of an article: title, lead, body, publication date, author. Unlike standard crawling, which adapts relatively well to markup variations, the News crawler is stricter about certain expected patterns.

When you modify a template or switch to HTTPS, you may potentially alter the HTML structure, schema.org tags, canonical URLs, and redirects. If any of these elements break the reading chain, the content becomes invisible to the News algorithm even if it remains perfectly crawlable in standard organic search.

What specifically causes this loss of readability?

Common causes include poorly tagged ArticleBody tags post-migration, missing publication dates or dates in an unrecognized format, content loaded with asynchronous JavaScript that the News crawler cannot render, or incorrectly configured 301 redirects that break historical signals.

Switching to HTTPS sometimes introduces mixed content warnings that block the full rendering of the page. Other times, it's a change in URL architecture that dilutes the algorithm's recognition of News sections. The issue is rarely isolated; it’s often a domino effect.

Why does Mueller recommend contacting the News team directly?

Because Google News has a dedicated team that is distinct from regular Search Console. Parsing issues can sometimes be invisible in standard coverage reports. You'll see your pages indexed and crawled, but News traffic collapses without any visible alerts.

Direct contact allows for a manual diagnosis by engineers who can precisely identify which structural element is blocking readability. Waiting for a natural recovery can take weeks or may never happen if the error persists in the code.

• The Google News crawler is more demanding about HTML structure than the organic search crawler
• HTTPS migrations and template changes frequently break News content signals without affecting standard indexing
• Contacting the Google News team is recommended as soon as a traffic drop is observed post-migration
• Parsing issues are rarely visible in standard Search Console reports
• A minor technical error (poorly formatted date, incomplete schema.org) can completely block content extraction

Does this recommendation truly reflect on-the-ground observations?

Absolutely. I've seen media outlets lose 60 to 80% of their News traffic within 48 hours after replatforming, without any alerts in Search Console. The diagnosis is complex because the site continues to be crawled normally, pages remain indexed, but the News flow dries up abruptly.

The typical issue: a CMS generating Unix timestamp publication dates instead of a readable ISO format, or a missing article:published_time in the Open Graph meta tags. Google News does not flag these errors as coverage problems; it simply ignores the content. [To be verified]: the exact frequency with which the News team responds to inquiries via the contact form remains unclear, some publishers report delays of several weeks.

What are the most common errors post-migration?

The first pitfall: chained 301 redirects. HTTP to HTTPS, then www to non-www, then old URL to new structure. The News crawler often gives up after the second redirect. The result: historical content disappears from the flow even if new publications pass through.

The second classic error: loading the article body with lazy loading or via a too-late React/Vue hydrate. The News crawler takes a quick snapshot; if the content is not in the initial DOM, it will not be extracted. A third source of problems: paywall scripts that hide text before the algorithm can read it, especially if the schema.org markup points to hidden content.

When does this rule not apply?

If your site is not indexed in Google News as an approved source, these considerations are irrelevant. Standard organic traffic from universal search follows different rules, less sensitive to structural details. You can migrate to HTTPS without visible impact if you're not dependent on the News flow.

Another case: sites that publish evergreen content rather than hot news. Google News favors freshness and velocity; if your content is not meant to appear in the News tab, parsing requirements are less stringent. But let's be honest, if you have a publisher center set up and are targeting this channel, every detail counts.

What should you check before a HTTPS migration or a template change?

First, audit your schema.org Article markup: ensure that headline, datePublished, dateModified, author, and publisher are present and valid. Use Google's rich results test to detect errors before going live. A missing field can be enough to break readability.

Next, make sure that the main content is rendered server-side, not just client-side JavaScript. Test with a fetch as Google or a simple curl: the full article text should appear in the source HTML. If you are using a modern framework (Next.js, Nuxt), prioritize SSR or SSG for article pages.

How do you diagnose a drop in News traffic post-migration?

First, isolate the traffic source in Analytics: Google News vs standard organic search. If only the News channel drops, it is indeed a parsing issue. Compare the URLs that continue to perform with those that have lost visibility, identifying differences in HTML structure or redirects.

Use the URL Inspection tool in Search Console on a few recent articles: check that the crawled rendering displays the full text, dates, and author. If elements are missing in the crawled version but are visible during normal navigation, it's a red flag. Then, contact the Google News team via the Publisher Center with specific examples of impacted URLs.

What errors should you absolutely avoid during replatforming?

Never implement temporary 302 redirects during migration, even for testing. Google News interprets them as ephemeral content and can deindex the flow. Use permanent 301s from the start, with precise 1:1 mapping between old and new URLs.

Also avoid modifying both the URL structure and the HTML template simultaneously. Break down the changes: first migrate to HTTPS without altering the URLs or markup, stabilize traffic, then change the template. Changing multiple variables at the same time makes diagnosis impossible if something goes wrong.

• Audit the schema.org Article markup with the rich results test before any migration
• Verify that the main content is rendered server-side, not just in asynchronous JavaScript
• Implement permanent 301 redirects with 1:1 mapping, never 302s or multiple chains
• Test the crawled rendering using the URL Inspection tool on a sample of recent articles
• Monitor Google News traffic separately from standard organic traffic in Analytics
• Prepare a list of impacted URLs with before/after screenshots for contacting the News team if needed