Ranking well in 2027 requires more than just keyword density and standard meta tags. Google is actively shifting toward AI Overviews (AEO/GEO), while punishing sites that fail strict UI responsiveness metrics like Interaction to Next Paint (INP). At the same time, many teams are moving to decoupled architectures, which often breaks traditional CMS SEO routing entirely.
This session cuts through the theory and focuses on practical execution. We will look at modern search strategy through two distinct pillars: Traditional Hosted Drupal and Decoupled/Headless Drupal.
For each pillar, we will look at the actual problems slowing down editorial teams and hurting search visibility, and then demonstrate the exact Drupal modules, API configurations, and frontend architecture required to fix them. Also, implement Edge/Drupal bot defence system so you are rolling out the red carpet for Googlebot while slamming the door on malicious scrapers.
Pillar 1: Traditional (Hosted) Drupal Sites
This pillar covers sites where Drupal handles both the backend data and the frontend Twig rendering.
- The Problem: Standard HTML output and manual SEO fields aren't enough for AI search engines, editorial teams are tired of doing manual SEO, and heavy JavaScript is causing the site to fail the INP web vital.
- Drupal Solution 1: SEO to GEO & AI-Ready Content Strategy.
- How to solve it: Stop relying solely on the Metatag module's basic fields. We will configure the Schema.org Blueprints module. This shifts the content strategy from "writing pages" to "building entities" (like Recipes, FAQs, Organisations) so Drupal natively outputs the JSON-LD structured data that Large Language Models(LLM) and AI crawler actively look for. At the same time structuring content to shield from malicious bots.
- How to solve it: Stop relying solely on the Metatag module's basic fields. We will configure the Schema.org Blueprints module. This shifts the content strategy from "writing pages" to "building entities" (like Recipes, FAQs, Organisations) so Drupal natively outputs the JSON-LD structured data that Large Language Models(LLM) and AI crawler actively look for. At the same time structuring content to shield from malicious bots.
- Drupal Solution 2: Zero-Touch Content Automation & Bad Bot Defence.
- How to solve it: We will use the ECA (Event-Condition-Action) module combined with the AI Integration module. I will show a live recording where an editor uploads an image without alt text, and ECA automatically triggers an AI API to generate descriptive alt text and meta descriptions on the node save event. We will demonstrate how to use the BotShield module to classify and rate-limit bad bot traffic by User-Agent and IP, protecting your backend AI operations.
- How to solve it: We will use the ECA (Event-Condition-Action) module combined with the AI Integration module. I will show a live recording where an editor uploads an image without alt text, and ECA automatically triggers an AI API to generate descriptive alt text and meta descriptions on the node save event. We will demonstrate how to use the BotShield module to classify and rate-limit bad bot traffic by User-Agent and IP, protecting your backend AI operations.
- Drupal Solution 3: Taming INP.
- How to solve it: Show how to track INP locally using the Core Web Vitals (CWV) module. Then, demonstrate how to break up long-running JavaScript tasks inside
Drupal.behaviorsand use Drupal 11's native asset libraries (or AdvAgg) to defer non-critical scripts so the UI responds instantly to user clicks.
- How to solve it: Show how to track INP locally using the Core Web Vitals (CWV) module. Then, demonstrate how to break up long-running JavaScript tasks inside
Pillar 2: Headless (Decoupled) Drupal Sites
This pillar covers sites where Drupal is purely an API backend, and the frontend is built in Next.js, Nuxt, or a similar framework.
- The Problem: When you go headless, you lose Drupal’s native routing, sitemaps, and Twig-rendered meta tags. If the frontend relies entirely on client-side rendering, search bots see a blank page, ruining your SEO and performance scores and exposing JSON:API endpoints creates a massive vulnerability for scraper bots.
- Drupal Solution 1: Headless GEO, Metatags, & Sitemaps.
- How to solve it: We will use JSON:API paired with the Decoupled Router module. This allows the Next.js frontend to ask Drupal for a URL path, and Drupal responds with the exact structured data, canonical links, and Schema.org JSON-LD needed for AI crawlers. We will also show how to configure Simple XML Sitemap to rewrite URLs for the headless frontend.
- How to solve it: We will use JSON:API paired with the Decoupled Router module. This allows the Next.js frontend to ask Drupal for a URL path, and Drupal responds with the exact structured data, canonical links, and Schema.org JSON-LD needed for AI crawlers. We will also show how to configure Simple XML Sitemap to rewrite URLs for the headless frontend.
- Drupal Solution 2: Headless INP & Server-Side Rendering (SSR).
- How to solve it: To pass INP and ensure AI crawlers can index the site without executing heavy client-side JavaScript, the frontend must be configured for SSR (e.g., using the
next-drupalclient). We will show a live Network Tab comparison of a slow client-rendered page vs. a fast SSR page.
- How to solve it: To pass INP and ensure AI crawlers can index the site without executing heavy client-side JavaScript, the frontend must be configured for SSR (e.g., using the
- Drupal Solution 3: Zero-Touch Content in Decoupled.
- How to solve it: Explain that because our ECA + AI automation happens on the Drupal backend during the node save event, the headless API endpoints are automatically populated with AI-optimized alt text and metadata without any extra work from the frontend developers. We will discuss how to implement Edge protection (like Cloudflare or Fastly CDN rules) combined with Drupal.
Attendees will leave knowing how to structure data for AI crawlers, automate tedious SEO tasks, pass Core Web Vitals, and safely route metadata to headless frontends.