Studio Brand, Customer Service, SEO, and Login

This article transforms the newly created subsite into a complete brand site and accurately sets the languages, customer service, and login access that visitors can use.

¶ Completion Effect

After the page runs, the homepage, browser title, Logo, Favicon, theme color, and shared authentication page will display your brand; customers can access through an accepted login method and find real and usable customer service channels.

¶ Preparation Before Starting

• Have clicked Manage in "My Subsite" from the official Studio to enter the target subsite;
• Horizontal Logo, square Favicon;
• Brand primary color;
• Language range for external use;
• Customer service name, link, or QR code;
• At least one login method prepared for long-term maintenance.

¶ Step 1: Configure Site Identity and Language

Open Site Settings in the subsite settings:

1. Modify the site title;
2. Upload Logo and Favicon separately;
3. Choose the theme color;
4. Select the "Site Language" that visitors can switch;
5. If targeting a single language market, set "Forced Language";
6. Add real customer service contact information that responds;
7. Save and refresh the subsite homepage.

The system domain name and display title are not the same field. The system domain name is used to resolve the Site, and the title can continue to be modified.

¶ Step 2: Fill in SEO Information

Open SEO Settings and fill in:

• Site description: Clearly state the target users and core capabilities in one sentence;
• Site keywords: Use a small number of keywords directly related to your business.

After saving, check the title, description, canonical, Open Graph, Twitter Card, and Favicon in the completed DOM of the page.

Studio currently mainly loads Site branding on the client side. Original HTML, no JavaScript clients, or some sharing crawlers may still see the unified product shell first. Do not miswrite "correct after browser runs" as "all crawlers' first screen has been fully white-labeled."

¶ Step 3: Configure Login Methods

Open Authentication:

1. Only enable login methods that have been accepted and are prepared for long-term support;
2. Keep at least one, otherwise visitors cannot log in;
3. Select the default login method from the enabled options;
4. Choose the display method for Web login, such as full-page redirect or popup embed;
5. Save, then log out, and log in with an incognito window to confirm the redirect.

Logins will go through the shared authentication domain name. The authentication page will load your title, icon, and theme color after receiving Site information, and may briefly display the unified product shell on slow networks.

¶ Step 4: Access Custom SMS as Needed

Only when "Mobile Number" login is enabled and you have your own SMS sending service is it necessary to have a "Custom SMS Sender Address":

• Configure a publicly accessible HTTPS webhook;
• Use the signature key generated/saved by the page to verify requests;
• The key is sensitive information and will not be fully returned when reading the page;
• Test in a controlled environment according to the page documentation before going live, and do not send secrets, mobile numbers, or verification codes to group chats.

Screenshots and read-only acceptance in this tutorial will not send test SMS.

¶ Step 5: Configure Homepage Banner and Website Statistics as Needed

• Homepage Banner: Choose the system banner to keep and create your current subsite's own image, title, subtitle, and redirect link;
• Website Statistics: Only fill in the statistics ID for supported platforms, do not insert any JavaScript or HTML; synchronize and update the privacy policy before enabling.

Banners should point to real capabilities or pages. Website statistics should only load on the official domain and need to inform visitors of the data usage and third-party processors.

¶ Step 6: Acceptance of Brand and Customer Service

Check desktop and mobile separately in an incognito window:

1. Homepage title, Logo, Favicon, and theme color;
2. Language switch or forced language;
3. Brand on the login page and redirect after login;
4. Customer service link, QR code, and external pages should not require administrator permissions;
5. SEO metadata after the page runs;
6. Preview of links for common sharing tools, and record whether they still read the unified product shell.

¶ Success Indicators

• The page runs showing your title, Logo, Favicon, and theme color;
• Visitors only see the languages and login methods you are prepared to support;
• At least one login method completes login, logout, and redirect;
• Customer service links are available to non-logged-in visitors;
• The team knows that Studio/shared Auth branding is loaded asynchronously, not as an independent authentication system.

¶ Frequently Asked Questions

¶ Logo updated but Favicon did not change

Favicon caching usually lasts longer. Confirm that the Favicon has been set separately, then check with a brand new incognito window or another device.

¶ Authentication page first shows unified brand

Wait for the Site configuration to load completely before judging. If the final title and icon are still incorrect, record the page domain name, time, and browser; do not provide passwords, tokens, or SMS secrets.

¶ Ordinary users cannot see the site management section

This is a permission design. Site settings are only open to the current Site administrator, and ordinary customers should not see them.

¶ Next Article

Continue configuring Studio Capability Directory and Pricing.