Drupal 10 End of Life: What UK Website Owners Need to Know Before December 2026

If your organisation runs a Drupal 10 website, 2026 is the year to decide what happens next.

Drupal 10.6.x is currently receiving security support, but Drupal 10 is approaching end of life in December 2026. Drupal.org confirms that Drupal 10.6.x will receive security support until December 2026, while older Drupal 10 minor versions have already reached end of life.

For website owners, the question is therefore not simply whether Drupal 10 still works. The more useful question is:

What should we do with our Drupal website before Drupal 10 support ends?

For many organisations, the answer will be an upgrade to Drupal 11. For others, particularly those with an older codebase, extensive custom development or outdated website requirements, this may be the right time to consider a wider rebuild.

When does Drupal 10 reach end of life?

Drupal 10 reaches end of life in December 2026.

The current Drupal release information confirms that Drupal 10.6.x receives security support until December 2026. Drupal 10.5.x and earlier supported branches have already reached the end of their security support periods.

Drupal's published development issue proposes 9 December 2026 as the specific Drupal 10 end of life date, although the Drupal.org release information currently states the end of life simply as December 2026.

For that reason, organisations should plan against December 2026 rather than relying on a particular date until Drupal officially confirms the final schedule.

What does Drupal 10 end of life mean?

End of life means that the Drupal 10 branch will no longer receive normal security support.

This is different from saying that a Drupal 10 website will immediately stop working.

Your website may continue to function after Drupal 10 reaches end of life. However, the Drupal project will no longer provide ongoing security coverage for that major version.

That creates a maintenance and security concern for organisations that continue running the unsupported version.

Drupal's release information already demonstrates why keeping a supported version matters. Recent Drupal 10.6 releases have included fixes for security vulnerabilities, including cross site scripting and information disclosure issues.

Do you have to move from Drupal 10 to Drupal 11?

Not every organisation should automatically assume that a Drupal upgrade means a simple version change.

Drupal's official upgrade documentation states that Drupal 10.3.x is the minimum source version for an upgrade to Drupal 11.x. The process also requires checking the hosting environment, contributed modules, themes and custom code for compatibility.

Drupal 10.6 was specifically designed to provide good forward compatibility with Drupal 11. Drupal.org describes it as providing the best forward compatibility with Drupal 11 within the Drupal 10 series.

So, if your website is on an appropriately maintained Drupal 10 release, an upgrade to Drupal 11 may be a sensible route.

But it should not be treated as a blind one click update.

What needs to be checked before upgrading?

A Drupal website can contain much more than Drupal core.

It may have:

• Contributed modules
• Custom modules
• Custom themes
• Third party integrations
• Custom database structures
• Composer dependencies
• Hosting requirements
• Custom code
• Modified core or scaffold files
• Content workflows
• Search functionality
• Forms and marketing integrations

Drupal's official Drupal 10 to Drupal 11 upgrade guidance specifically recommends checking contributed and custom code and using tools such as Upgrade Status to identify compatibility issues.

Some extensions that were deprecated in Drupal 10 have been removed from Drupal 11. Drupal's documentation lists examples including Actions UI, Activity Tracker, Book, Forum, Statistics and Tour.

This is why the first step should be an assessment rather than immediately changing the production website.

Can you upgrade directly from Drupal 10 to Drupal 11?

Yes, provided the site meets the requirements for the Drupal 11 upgrade.

Drupal's official documentation identifies Drupal 10.3.x as the minimum source version for a Drupal 11 upgrade. It also specifies PHP 8.3 or later for the Drupal 10 to Drupal 11 upgrade process described in its current documentation.

Drupal also requires major versions to be upgraded sequentially. A major version cannot simply be skipped. Drupal's own documentation gives the upgrade path as:

Drupal 10 → Drupal 11 → Drupal 12

rather than attempting to jump directly between major versions.

How long does a Drupal 10 to Drupal 11 upgrade take?

There is no reliable single timeframe that applies to every Drupal website.

A relatively straightforward website with compatible modules, limited custom code and a suitable hosting environment may require considerably less work than a large Drupal installation with custom functionality and third party integrations.

The amount of work depends on factors such as:

• Current Drupal version
• Number of contributed modules
• Module compatibility
• Amount of custom code
• Theme implementation
• PHP and hosting requirements
• Third party integrations
• Database and content structure
• Automated and manual testing requirements
• Deployment and rollback arrangements

Drupal's official upgrade process itself includes preparation, compatibility checks, code updates, Composer changes, database updates and post upgrade testing.

A proper assessment should therefore come before giving a fixed project estimate.

Should you upgrade Drupal 10 or rebuild your website?

This is one of the most important questions for a business website.

A Drupal version upgrade and a website rebuild are not the same project.

An upgrade primarily addresses the underlying Drupal platform and compatibility.

A rebuild may also address:

• Website design
• Information architecture
• Content structure
• User journeys
• Technical SEO
• Performance
• Accessibility
• Content management processes
• Integrations
• Search functionality
• Conversion paths

If the existing website is performing well and its architecture remains appropriate, an upgrade may make more sense.

If the website already has significant technical debt or no longer meets the organisation's requirements, rebuilding may be worth considering at the same time.

What about SEO during a Drupal upgrade?

A Drupal upgrade should not be treated as an SEO neutral technical exercise without testing.

The technology change itself does not automatically improve search visibility.

What matters is whether important website signals and content remain accessible and correctly implemented after the work.

Before and after an upgrade, review areas such as:

• Important URLs
• Redirects
• Canonical URLs
• XML sitemaps
• Robots directives
• Page titles
• Meta descriptions
• Structured data
• Internal links
• Indexability
• Status codes
• Page performance
• Mobile rendering
• Search Console coverage

Google's guidance for AI features is particularly relevant here. Google states that the same foundational SEO practices remain relevant for AI Overviews and AI Mode. There are no additional technical requirements specifically for appearing in those AI features.

That means a Drupal upgrade should preserve the fundamentals that allow search engines to crawl, understand and index the website.

What about AI search, AEO and GEO?

There is a lot of marketing language around "GEO" and "AI optimisation", so it is worth separating established guidance from speculation.

Google's current guidance says that the same SEO fundamentals apply to AI Overviews and AI Mode. Google also recommends useful, reliable, people first content and says that pages must meet the normal technical requirements for Google Search to be eligible as supporting links in AI features.

Google has also published specific guidance in 2026 addressing optimisation for generative AI features. It stresses valuable, unique content and states that SEO remains foundational. It also addresses several common misconceptions about AEO and GEO.

Therefore, there is no credible basis for telling a Drupal website owner that simply moving from Drupal 10 to Drupal 11 will make their website more visible in ChatGPT, Google AI Overviews or other AI systems.

The better approach is to use the upgrade as an opportunity to check whether the website has:

• Clear answers to genuine customer questions
• Well structured information
• Strong internal linking
• Accessible content
• Crawlable pages
• Appropriate structured data
• Original and useful information
• Clear authorship and organisation information
• Good technical SEO

The CMS version is only one part of that picture.

A Drupal 10 upgrade checklist for UK website owners

Before starting the project, establish:

Technical

• Current Drupal version
• Current PHP version
• Hosting compatibility
• Composer configuration
• Contributed modules
• Custom modules
• Custom themes
• Deprecated Drupal functionality
• Third party dependencies
• Database backup and recovery process

Website

• Important URLs
• Redirects
• XML sitemap
• Robots directives
• Canonical URLs
• Structured data
• Forms
• Search
• Analytics
• Conversion tracking
• Third party integrations

SEO

• Organic traffic baseline
• Important landing pages
• Search Console data
• Indexation
• Page titles
• Meta descriptions
• Internal linking
• Core Web Vitals
• Mobile experience
• Broken links

Testing

• Development environment
• Staging environment
• Automated tests
• Functional testing
• Content testing
• SEO testing
• Accessibility testing
• Performance testing
• Redirect testing
• Production rollback plan

What should you do now?

If your website is running Drupal 10, you do not need to panic.

But waiting until the final weeks of 2026 is unlikely to be a good project strategy.

Start by establishing exactly what you have.

1. Identify your Drupal version.
2. Audit your modules, themes and custom code.
3. Check Drupal 11 compatibility.
4. Review your hosting and PHP environment.
5. Decide whether an upgrade is sufficient or whether the website needs wider work.
6. Protect SEO, accessibility, analytics and important functionality during the change.
7. Test the upgraded website before production deployment.

Drupal's own documentation recommends preparation and compatibility checking before beginning the Drupal 10 to Drupal 11 upgrade.

The key question is not simply "Can we upgrade?"

For many organisations, the more useful question is:

"What should our Drupal website look like for the next several years?"

If the existing architecture, content and functionality still meet your needs, upgrading Drupal may be the sensible choice.

If the website has accumulated technical debt, has poor performance, an outdated user experience, weak search visibility or no longer supports the organisation's requirements, the Drupal 10 end of life deadline may provide a sensible point at which to assess the website more broadly.

Either way, the decision should be based on the actual condition of the website rather than the Drupal version number alone.

Frequently asked questions

When does Drupal 10 reach end of life?

Drupal 10 reaches end of life in December 2026. Drupal.org currently states that Drupal 10.6.x will receive security support until December 2026.

Can I still use Drupal 10?

Yes. Drupal 10.6.x remains under security support until December 2026. Older Drupal 10 minor versions may already be unsupported.

Should I upgrade from Drupal 10 to Drupal 11?

For a site that remains suitable for Drupal, upgrading to Drupal 11 is the main supported path. However, the site should first be checked for module, theme, custom code, hosting and dependency compatibility.

Can Drupal 10 be upgraded directly to Drupal 11?

Yes, provided the site meets the Drupal 11 upgrade requirements. Drupal's current documentation identifies Drupal 10.3.x as the minimum source version.

Will upgrading Drupal improve my SEO?

Not automatically. An upgrade can provide an opportunity to address technical issues, but search performance depends on many factors beyond the CMS version.

Will upgrading Drupal improve visibility in Google AI Overviews?

There is no official basis for making that claim. Google says that the same fundamental SEO practices apply to its AI features and that there are no additional technical requirements specifically for appearing in AI Overviews or AI Mode.

Should I rebuild my website instead of upgrading Drupal?

That depends on the condition and requirements of the existing website. A technical assessment should consider the codebase, modules, content, design, integrations, performance, accessibility, SEO and future requirements before making the decision.

Final takeaway

Drupal 10 is approaching the end of its supported life, but this is not simply a matter of changing one version number.

For UK organisations running Drupal 10, the sensible approach is to assess the existing website now, determine whether Drupal 11 is appropriate, identify compatibility issues and decide whether the project should be an upgrade or a wider website rebuild.

The December 2026 deadline gives website owners a clear reason to start that assessment before the deadline rather than after it.

If you are responsible for a Drupal 10 website, the first useful step is to find out exactly what needs changing before you decide what to build next.