docs: streaming metadata, dynamic pages and generateMetadata#80453
Merged
docs: streaming metadata, dynamic pages and generateMetadata#80453
Conversation
Hardanish-Singh
approved these changes
Jun 12, 2025
delbaoliveira
approved these changes
Jun 13, 2025
docs/01-app/05-api-reference/04-functions/generate-metadata.mdx
Outdated
Show resolved
Hide resolved
| Since page metadata primarily targets bots and crawlers, Next.js will stream metadata for bots that can execute JavaScript and inspect the full page DOM (e.g. `Googlebot`). However, metadata will continue blocking the render of the page for **HTML-limited** bots (e.g. `Twitterbot`) as these cannot execute JavaScript while crawling. | ||
| Streamed metadata may end up in the `<body>` tag. Since metadata mainly targets bots and crawlers, Next.js streams metadata for bots that can execute JavaScript and inspect the full DOM (e.g. `Googlebot`). We have verified that these bots, interpret the metadata correctly. | ||
|
|
||
| For **HTML-limited** bots that can’t run JavaScript (e.g. `Twitterbot`), metadata continues to block page rendering and is placed in the `<head>` tag. |
Co-authored-by: Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com>
ztanner
approved these changes
Jun 17, 2025
egermano
added a commit
to egermano/next.js
that referenced
this pull request
Jun 17, 2025
* canary: (77 commits) [devtools] fork next-logo (vercel#80457) [devtools] fork devtools-indicator (vercel#80456) [devtools] add feature flag for new panel ui (vercel#80251) Improve Incremental Cache Locking Algorithm (vercel#80497) [fix] clone the config module to avoid mutation (vercel#80573) fix: mark file system incremental cache as external so it's memory is shared (vercel#80586) Ensure custom relative distDir resolves properly (vercel#80569) Turbopack: correct export usage in EcmascriptModulePartReference (vercel#80526) docs: streaming metadata, dynamic pages and generateMetadata (vercel#80453) fix: Rspack dev gets stuck after removing a page (vercel#80555) perf(turbopack): Detect more immutable tasks (vercel#80423) test: fix failures caused by format discrepancies between rspack and other bundlers (vercel#80314) perf(turbopack): Do not allocate vectors if we are not going to use it (vercel#80504) perf(turbopack): Introduce runtime analysis for immutable tasks (vercel#80422) [devtools] Port cache invalidation logic from turbopack to webpack (vercel#80184) v15.4.0-canary.84 Update Turbopack production test manifest (vercel#80562) Update Rspack production test manifest (vercel#80561) Update Rspack development test manifest (vercel#80560) [turbopack] Simplify `Request::parse(Pattern)` the recursive portion doesn't need to be async (vercel#80510) ...
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes: https://linear.app/vercel/issue/DOC-4687/docs-streaming-metadata-implications