ℹ️ In this article, the published site infrastructure used before June 11, 2026 is referred to as the "legacy infrastructure," and the current published site infrastructure is referred to as the "new infrastructure."
About Studio.Design's published site infrastructure
As of June 11, 2026, Studio.Design's published site infrastructure has been updated to a setup that returns fully rendered HTML from the server. This new infrastructure is designed to deliver improvements in page load speed, stability, and SEO.
For projects created on or after June 11, 2026, this new infrastructure is the default for published sites.
Projects created before June 11, 2026 will continue to be published on the legacy infrastructure until you manually switch them over. At this time, Studio.Design will not force a switch to the new infrastructure.
Going forward, new features and improvements will be built around the new infrastructure. We recommend reviewing the differences in specifications and considering a switch to the new infrastructure when appropriate.
💡 For full details on the published site infrastructure, see Studio.Design's Published Site Infrastructure.
💡 If you want to improve your published site's load speed, check out these articles as well:
How to switch your published site infrastructure
Important: Recommendations before switching infrastructure on a production site
Because the legacy and new infrastructures have different underlying configurations, differences in specifications or in how external services are integrated may affect how your site displays or how analytics are measured.
In particular, if any of the following applies, we recommend testing the new infrastructure's behavior using a test Studio.Design project before switching your production site:
The site is a business-critical production site
Some pages have external service tags installed, such as ad or conversion tracking
The site receives heavy traffic and is sensitive to display or load impact
Step 1: Check and record the current site display on the legacy infrastructure
Open the target project and review how your currently published site is displayed.
If needed, record the current state of your site using a separate environment or screenshots.
Step 2: Switch your published site infrastructure
Tip: Check the A record for your custom domain
Custom domain sites with an A record pointing to the old IP address "35.194.122.208" cannot be switched to the new infrastructure.
Before switching, update the A record to point to "34.111.141.225".
Open your project's dashboard > [Project Settings].
Open [Switch Published Site Infrastructure] > [Settings].
Select the published site infrastructure you'd like to use.
Review the description and notes, and if everything looks good, [Save] the setting.
It takes about 5 minutes for the switch to complete after you click [Save].
Step 3: Confirm the switch and generate the cache (first time only)
Point: How cache generation works on the new infrastructure
On the new infrastructure, HTML for key pages is prepared in advance when you publish or update your site, so pages tend to load quickly from the first visit.
For details on when caches are generated and which content is excluded, see Studio.Design's Published Site Infrastructure > Cache generation timing on the new infrastructure.
Open your published site and bring up your browser's developer tools.
In Chrome, you can open the developer tools by right-clicking on the page and selecting [Inspect].
Open the [Elements] tab and search for the keyword "Studio.Design.HRC".
You can open the search with [Ctrl / Cmd ⌘] + [F].
If you see
<meta name="generator" content="Studio.Design.HRC">, the switch is complete.Finally, update your site to generate the initial cache.
Tip: Check your settings if you're using Google Analytics
If you've connected Google Analytics via the Apps integration, review your enhanced measurement settings after switching.
On the legacy infrastructure, we recommended disabling [Page changes based on browser history events], but on the new infrastructure, you can use the default settings.
For details on the configuration, see Apps Integration: Connecting Google Analytics.
Frequently asked questions about switching and managing the published site infrastructure
Will already-published sites be switched to the new infrastructure automatically?
No. Sites already published on the legacy infrastructure will continue to be served on the legacy infrastructure unless you manually switch them.
At this time, Studio.Design will not force a change to your published site infrastructure.
Which infrastructure will newly created projects use?
Newly created projects use the new infrastructure as the default published site infrastructure.
Will future new features also be available on the legacy infrastructure?
Future new features and improvements will be provided based on the new infrastructure. Behavior on the legacy infrastructure may not be supported in some cases.
After switching to the new infrastructure, can I switch back to the legacy infrastructure right away?
You can switch back to the legacy infrastructure until around the end of January 2027. After that, switching back to the legacy infrastructure once you've moved to the new one will no longer be possible.
Are there any pages or features that are likely to be affected when switching to the new infrastructure?
Pages that use external scripts embedded via an Embed box or that include custom code are more likely to be affected. In addition, if you're using implementations that are scheduled for specification changes on the new infrastructure, the display may differ from what you expect.
Please review the resources below, and pay particular attention to any changes in display or behavior on affected pages before and after switching.
Will my site's load speed always be faster after switching to the new infrastructure?
In general, you can expect improvements in load speed and stability compared to the legacy infrastructure, but actual performance varies based on factors like image sizes, external scripts, embedded elements, and page structure. Please review the articles below and consider making additional adjustments as needed.
Will switching my published site to the new infrastructure always improve SEO?
Switching to the new infrastructure makes it easier for search engines to read your page content, so it provides a setup that's well-suited for SEO.
However, SEO results are influenced by many factors beyond the infrastructure switch, so simply switching won't necessarily improve your rankings. For more details, see our article on SEO best practices.
After switching to the new infrastructure, parts of my site display differently. What should I do?
There are some differences in behavior and specifications between the legacy and new infrastructures.