Technical SEO and Editorial Debt in Drupal at Scale

There are many tools to audit a website: the URL is pasted, several requests are launched that analyze an already rendered page, and a superficial report is returned, with a paywall starting from the fifth point. The open Drupal ecosystem can be leveraged to obtain a deeper and more complete report freely.

Drupal has a solid foundation for running tools that report in real time what happens on the site. An example used almost daily is Watchdog, which shows website errors in real time, or the Drupal status page, where the points to review are listed by criticality level. But all those sections mostly discuss infrastructure.
Several tools can be made available to monitor content that has been written in real time, as is already done with other reports.

The guidelines for a website to be optimized for search engines are already available. The question is whether they are actually being followed.
In the end, when adopting a CMS, a client not only seeks something robust, secure, and maintainable over time, but also for the content to reach the right audience. If the search engine or AI considers the content to be low quality, it will not be shown.

This talk lists a series of problems that appear in content and end up degrading the site, from the editorial side to how a paragraph or a header is rendered and how this can affect SEO. The goal is to bring errors to the surface so action can be taken.

To do this, modules such as entity_mesh and content_first will be presented, focused on analyzing and auditing content synchronously from the perspective of technical SEO, along with other modules that complement SEO, such as redirect, redirect_audit, or metatag. The goal is to lay the foundations on which to build well-optimized and solid content.