Upgrade to Pro — share decks privately, control downloads, hide ads and more …

The Most Common Technical SEO Issues for News P...

The Most Common Technical SEO Issues for News Publishers

Slides from my talk at the 2025 News Reach conference in Dortmund, where I spoke about the most common technical SEO issues affecting news and publishing websites.

Avatar for Barry Adams

Barry Adams

October 28, 2025
Tweet

More Decks by Barry Adams

Other Decks in Marketing & SEO

Transcript

  1. Barry Adams ➢ Active in SEO since 1998 ➢ Specialist

    in SEO for News Publishers ➢ Newsletter: SEOforGoogleNews.com ➢ Co-founder of the News & Editorial SEO Summit
  2. Crawling Crawl Queue Crawling Processing Index Render Queue Rendering Index

    Index Serving Rendered HTML URL HTML Indexing Ranking
  3. Technical SEO is… … all aspects of SEO that are

    focused on the technical aspects of a website that enable crawling, indexing, and ranking of webpages in search results. Everything to do with SEO that’s not content or marketing/brand.
  4. Server response time • Fast response = more pages crawled

    • Optimal is < 200ms; ➢ Very hard to achieve ➢ ‘Good enough’: < 600ms
  5. Example of wasted URLs 8% Indexable 41% Canonicalised 51% Redirects

    1 million URL Sitebulb crawl of a news publishing website
  6. Internal links should never redirect • Some redirects are unavoidable;

    ➢ Old URLs should redirect to new URLs to preserve inbound links • But internal links should always point directly to final destination URLs; ➢ Minimise crawl waste on redirected URLs
  7. Canonical tags don’t solve crawl waste <link rel="canonical" href="https://www.website.com/page"/> •

    Google crawls the alternative URLs, only then to be informed it’s not allowed to index them; ➢ Still consumes crawl effort • Use canonicalisation wisely
  8. Indexing and rendering Render Queue Rendering Crawl Queue Crawling Processing

    Index Index Index URL HTML Rendering takes time, and news doesn’t have time. News article indexing is initially with raw HTML only.
  9. Don’t rely on client-side JavaScript • All critical content should

    be in the HTML response • Google will eventually render the page and see JS-loaded content; ➢ However, this can be a delayed process ➢ The article is relatively old by then ➢ Google strongly prefers fresh articles in Top Stories & Google News
  10. Pagination is almost always done wrong • Wrong implementations: ➢

    Infinite scroll ➢ Client-side JavaScript ➢ Paginated series canonicalised to the 1st page <link rel="canonical" href="https://www.website.com/category/" /> Load More Articles Google doesn’t perform actions No clicking or scrolling
  11. Why do we want indexable pagination? • A section /

    category / tag page collects articles around a specific topic; ➢ More articles = more topic authority ➢ We want Google to see a decent body of journalism on specific topics to show you are an expert on those topics
  12. Correct pagination • Crawlable links to page 2 & beyond;

    ➢Each page canonicalised to itself <link rel="canonical" href="https://www.website.com/category/?page=2" /> • Limit pagination to preserve crawl budget; ➢ Supplement with an article archive ➢ This enables discoverability of older articles • Example: TechRadar.com
  13. Semantic HTML helps indexing • HTML generated by JS-frameworks often

    lacks semantic tags • Use the most appropriate HTML tag for every element; ➢ This helps Google identify the important aspects of the page ➢ Also critical for accessibility
  14. Structured data • Standard articles: Article / NewsArticle • Live

    articles: LiveBlogPosting • Reviews: Review • Author pages: Person / ProfilePage • Homepage: NewsMediaOrganization • Others: FactCheck / FAQ / Event / Q&A / …
  15. Common mistakes: Featured image • Featured image in Article SD

    is the wrong size & aspect ratio; ➢ Ideally, SD defines 3 images: -16:9 (1200 x 675) -4:3 (1200 x 900) -1:1 (1200 x 1200) • Too many images; ➢ In my experience, too many images defined in the Article SD confuses Google ➢ Keep it to three – no more, no less ➢ If you have just one image, make it the 16:9 version
  16. Keep your SD snippets lean • No need for elaborate

    structured data code; ➢ Google doesn’t rely heavily on linked SD ➢ Include only the recommended attributes according to Google’s documentation
  17. Core web vitals • Objective metrics designed to emulate subjective

    experience • Not a big direct ranking factor
  18. Core web vitals & engagement • Google measures click signals;

    ➢ Feeds directly into their rankings • Bad CWV = bad usability; ➢ Bad usability = negative click signals Img credit: https://www.mariehaynes.com/navboost/
  19. Don’t obsess over ‘perfect’ CWV • At some point it’s

    ‘good enough’ • Mostly green with some yellow & red is fine; ➢ It doesn’t need to be perfect
  20. Two aspects to LLM optimisation 1. Training data ingestion; ➢

    Ensuring your content can be extracted and ingested by LLMs for training purposes 2. Retrieval Augmented Generation (RAG); ➢ Ensuring your URLs are cited as sources in LLM answers
  21. 1. Training data ingestion • LLMs crawl and scrape the

    web; ➢ Content is extracted and tokenised Img credit: https://yaelgomez.substack.com/p/how-llms-see-the-world-the-magic
  22. 1. Training data ingestion Optimisation tactics: ➢ Semantic HTML to

    aid extraction ➢ All content in the HTML (no client-side JavaScript)
  23. 2. RAG citation • LLMs perform searches in the background

    to ‘ground’ answers and provide citations; ➢ ‘Query fan-out’ to capture a broad range of relevant pages ➢ Top ranked pages are cited more often
  24. 2. RAG citation Optimisation tactics: ➢ Top ranked webpages for

    related keywords and topics ➢ Content ‘chunking’ to structure your webpages ➢ Structured data for additional relevancy
  25. Technical SEO isn’t complicated… …but it can be hard. •

    Make things easy for Google; ➢ URLs are sacred ➢ Be careful with canonicalisation ➢ Load all content in the HTML ➢ Make your pagination indexable ➢ Use semantic HTML tags ➢ Short & focused structured data ➢ Correct image sizes for Google