Skip to main content

SEO Optimization

Organize SEO-related settings in Studio.Design — including titles, descriptions, OGP images, favicons, HTML, alt attributes, sitemaps, and 404 pages — to clearly communicate your content to search engines and visitors.

What is SEO?

SEO stands for Search Engine Optimization, which refers to the practices used to help your site appear more prominently in search results. Many on-site improvements also enhance accessibility. This article introduces the main SEO-related settings you can configure in Studio.Design.

For detailed steps, please refer to the help articles linked in each section.

Tip: Switch to the new site publishing 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. Projects created on or after this date use this new infrastructure as the default.

The new infrastructure makes it easier for search engine crawlers to read page content, making it better suited for SEO. If your site is still published on the previous infrastructure, we recommend switching to the new infrastructure.


(1) Help search engines discover your site

Set up your site's meta information so that your page content is easier for both search engines and visitors to understand.

(2) Clearly communicate your site structure and image content to search engines

Organizing your HTML structure and adding alternative text to images helps both search engines and assistive technologies understand your content.

(3) Make your site easy for search engines to crawl

Organizing internal links and handling errors properly improves crawl efficiency.

(4) Take additional SEO measures

Beyond the settings in Studio.Design, improving content quality and external reputation is also important.

(5) Understand how search engines work

Understanding how search engines work makes it easier to prioritize your SEO efforts. For an overview of key concepts and terms, see: "How Google Search works" (Google official documentation)

Did this answer your question?