透過集合功能整理內容 你可以依據偏好儲存及分類內容。
使用動態轉譯功能做為暫時替代方案
在某些網站上,當使用者在瀏覽器中開啟網頁時,JavaScript 會載入其他內容。這就是所謂的用戶端轉譯。Google 搜尋會看到這項內容,以及網站 HTML 中的內容。請注意,Google 搜尋中的 JavaScript 有一些限制,且部分網頁可能會在轉譯的 HTML 中遇到無法顯示內容的問題。其他搜尋引擎可能會選擇忽略 JavaScript,而且不會看到 JavaScript 產生的內容。
如果搜尋引擎看不到 JavaScript 產生的內容,動態轉譯功能就是網站的替代方案。動態轉譯伺服器會偵測可能看不見 JavaScript 產生內容的漫遊器,並在沒有這些 JavaScript 的情況下提供伺服器轉譯的版本給這些漫遊器,同時向使用者顯示用戶端轉譯內容的版本。
動態轉譯是一種替代方案,而非建議的解決方案,因為使用動態轉譯會增加複雜性和資源需求。
可能會使用動態轉譯的網站
動態轉譯功能是一種替代方案,適用於符合以下條件的內容:可供建立索引、由 JavaScript 產生且會經常變更的公開內容,或者是使用了檢索器不支援的 JavaScript 功能但卻很重要的內容。並非所有網站都需要使用動態轉譯,而且還有比動態轉譯更好的解決方案,如網路上的轉譯總覽所述。
瞭解動態轉譯的運作方式
使用動態轉譯時,您的網路伺服器需要偵測檢索器 (例如檢查使用者代理程式)。如果網路伺服器偵測到檢索器的要求不支援 JavaScript,或不支援轉譯您的內容所需的 JavaScript 功能,就會將這項要求導向轉譯伺服器。使用者和檢索器提出的要求,如果沒有 JavaScript 問題,系統就會照常處理。轉譯伺服器會針對要求提供適合檢索器的內容版本,例如靜態 HTML 版本。您可以選擇為所有網頁啟用動態轉譯器,或針對每個頁面個別指定是否啟用。
動態轉譯並非偽裝行為
一般來說,Googlebot 不會將動態轉譯視為偽裝行為。事實上,只要動態轉譯產生的是類似內容,就不會被 Googlebot 視為偽裝行為。
設定動態轉譯時,網站可能會產生錯誤網頁。Googlebot 不會將這些錯誤網頁視為偽裝行為,而是會比照處理其他錯誤網頁的方式來處理這個錯誤。
但是,如果您使用動態轉譯向使用者和檢索器提供完全不同的內容,Googlebot 可能就會將其視為偽裝行為。舉例來說,如果網站向使用者提供有關貓的網頁,但卻向檢索器提供有關狗的網頁,就可能會視為偽裝行為。
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-08-04 (世界標準時間)。
[null,null,["上次更新時間:2025-08-04 (世界標準時間)。"],[[["\u003cp\u003eDynamic rendering was a temporary solution for search engines having trouble accessing JavaScript-generated content, and it is not recommended for long-term use.\u003c/p\u003e\n"],["\u003cp\u003eWebsites may utilize dynamic rendering to present a server-rendered version of their content to search engine bots while displaying the client-side rendered version to users.\u003c/p\u003e\n"],["\u003cp\u003eModern solutions like server-side rendering, static rendering, or hydration are preferred over dynamic rendering.\u003c/p\u003e\n"],["\u003cp\u003eDynamic rendering is not considered cloaking by Google as long as the content served to bots is similar to that presented to users.\u003c/p\u003e\n"],["\u003cp\u003eWebsites with rapidly changing JavaScript-generated content or using JavaScript features unsupported by crawlers might have previously used dynamic rendering as a workaround.\u003c/p\u003e\n"]]],["Dynamic rendering serves search engine crawlers a server-rendered version of content, while users see client-side rendered content, as a workaround for JavaScript limitations. It detects crawler requests and routes them to a rendering server for static HTML delivery. While not considered cloaking if content is similar, serving entirely different content is. This method is complex and not recommended long-term; server-side, static rendering, or hydration are preferred alternatives. Dynamic rendering was used for public, rapidly changing or incompatible Javascript content.\n"],null,["Dynamic rendering as a workaround Dynamic rendering was a workaround and not a long-term solution for problems with JavaScript-generated content in search engines. Instead, we recommend that you use [server-side rendering](https://web.dev/articles/rendering-on-the-web#server-side), [static rendering](https://web.dev/articles/rendering-on-the-web#static), or [hydration](https://web.dev/articles/rendering-on-the-web#rehydration) as a solution.\n\n\nOn some websites, JavaScript loads additional content when the page is open in a browser.\nThis is called [client-side rendering](https://web.dev/articles/rendering-on-the-web#client-side). Google Search sees this content along with the content in the HTML of a website. Keep in mind that there are some [limitations for JavaScript in Google Search](/search/docs/crawling-indexing/javascript/javascript-seo-basics#write-compatible-code)\nand some pages may encounter problems with content not showing up in the rendered HTML. Other search engines may choose to ignore JavaScript and won't see JavaScript-generated content.\n\n\nDynamic rendering is a workaround for websites where JavaScript-generated content is not available to search engines.\nA dynamic rendering server detects bots that may have problems with JavaScript-generated content and serves a server-rendered version\nwithout JavaScript to these bots while showing the client-side rendered version of the content to users.\n\n\nDynamic rendering is a workaround and not a recommended solution, because it creates additional complexities and resource requirements. \n\nSites that might use dynamic rendering\n\n\nDynamic rendering was a workaround for indexable, public JavaScript-generated content that changes rapidly, or\ncontent that uses [JavaScript features that aren't supported by the crawlers](/search/docs/guides/rendering)\nyou care about. Not all sites need to use dynamic rendering, and there are better solutions than dynamic rendering as explained in\n[an overview of rendering on the web](https://web.dev/articles/rendering-on-the-web).\n\nUnderstand how dynamic rendering works\n\n\nDynamic rendering requires your web server to detect crawlers (for example, by checking the\nuser agent). When your web server identifies a request from a crawler that does not support JavaScript or the JavaScript features required to render your content,\nthis request is routed to a rendering server. Requests from users and crawlers without JavaScript issues are served normally.\nThe rendering server responds to requests with a version of the content that's suitable to the crawler, for example, it may serve a static HTML version.\nYou can choose to enable the dynamic renderer for all pages or on a per-page basis.\n\nDynamic rendering is not cloaking\n\n\nGooglebot generally doesn't consider dynamic rendering as [cloaking](/search/docs/essentials/spam-policies#cloaking).\nAs long as your dynamic rendering produces similar content, Googlebot won't view dynamic rendering as cloaking.\n\n\nWhen you're setting up dynamic rendering, your site may produce error pages. Googlebot doesn't consider these error pages as cloaking and [treats the error as any other error page](/search/docs/crawling-indexing/javascript/javascript-seo-basics#use-meaningful-http-status-codes).\n\n\nUsing dynamic rendering to serve completely different content to users and crawlers can be considered cloaking.\nFor example, a website that serves a page about cats to users and a page about dogs to crawlers is cloaking."]]