The new publishing infrastructure, first introduced in beta in January 2026, is now generally available.

The new infrastructure replaces our previous Single Page Application (SPA) architecture with a Multi-Page Application (MPA) architecture built on Server-Side Rendering (SSR), delivering improvements across performance, crawlability, and compatibility with search engines and AI systems. This release also incorporates feedback from the beta period and adds support for previously unavailable features.

What's Changing

Starting today:

• All newly created projects will automatically use the new publishing infrastructure.

• Until the end of January 2027, you can freely switch existing projects between the new and legacy publishing infrastructure.

• Some existing projects may experience compatibility differences. Please review the migration notes and Help Center articles before switching.

• Support for the new publishing infrastructure is now covered under our standard support.

We've also updated our migration guide and optimization checklist to help you get the most out of the new infrastructure.

Related Help Articles

• Switching your published site from the old infrastructure to the new one

Performance Improvements

Testing on Studio.Design’s websites and templates showed significant improvements after migrating to the new infrastructure.

Increased Search Traffic

Across our website, we observed notable improvements in both search visibility and traffic.

On Studio.Design’s Blog, where we publish educational content, search rankings improved, resulting in approximately 84% more daily signups from organic search. Across other pages, average search rankings improved from approximately 40th to 25th, while some pages experienced up to 9× more traffic from non-branded search queries. We also observed an increase in visits from AI-powered tools.

Higher Lighthouse Performance Scores

The general availability release expands on the beta with broader compatibility and additional improvements while maintaining excellent performance.

Using an optimized implementation based on one of our templates:

• Lighthouse Performance Score improved from 63 → 100 on mobile.

• Sites using Studio CMS also achieved performance scores of approximately 98.

Studio.Design also provides additional features and best practices to help improve website performance. See our Performance Optimization Checklist for more details.

Improved AI & Search Accessibility

The new publishing infrastructure adopts an MPA architecture that makes website content easier for both search engines and AI systems to crawl and understand.

In our testing, AI tools such as NotebookLM, previously unable to reliably process websites built on the legacy infrastructure, were able to successfully read content from the website after migration.

We also confirmed through Studio.Design server logs that external crawlers consistently receive valid responses from websites using the new infrastructure.

Note: These findings are based on internal analysis of Studio-owned websites and templates. Results may vary depending on your website implementation and external factors.

Want to Improve Your Website's Performance?

We've published a Performance Optimization Checklist to help you achieve higher scores in tools such as Google Lighthouse and PageSpeed Insights.

The guide covers optimization techniques and related Studio.Design features to help maximize your website's performance.

Things to Keep in Mind

If you migrate an existing website to the new publishing infrastructure, improvements in search engine rankings may take time to appear.

Before switching, please review the migration guide and related documentation.

Related Help Articles

• Switching your published site from the old infrastructure to the new one

Support for the Legacy Publishing Infrastructure

Existing websites using the legacy publishing infrastructure will not be migrated automatically.

You can switch to the new publishing infrastructure at any time from your Project Settings after reviewing the migration notes.

However, the ability to switch back to the legacy infrastructure will be discontinued at the end of January 2027, along with support for the legacy infrastructure.

While the legacy infrastructure will continue to receive security updates and existing websites can remain published, please note:

• Some future features will only be available on the new publishing infrastructure.

• Updating websites on the legacy infrastructure may result in unexpected display issues.

You can continue comparing the new and legacy infrastructure by switching between them until the end of January 2027.

To ensure a smooth transition, we recommend migrating and validating your websites before this date.

What's Next

We'll continue improving Studio.Design's publishing infrastructure to deliver faster, more reliable websites.

Upcoming improvements include:

• Faster font delivery

• Reduced website payload sizes

• More stable caching

Finally, we'd like to thank everyone who participated in the beta and shared valuable feedback. Your input helped shape this general availability release.