From 92e14433b675d3a06f2ecae2c2ebdad322fd6121 Mon Sep 17 00:00:00 2001 From: TooBug Date: Mon, 27 Oct 2025 12:34:47 +0800 Subject: [PATCH] Update site-config.md with metadata extraction details Explain the benefits of extracting pages metadata to a separate JavaScript chunk, including improved caching and reduced server bandwidth. --- docs/en/reference/site-config.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/en/reference/site-config.md b/docs/en/reference/site-config.md index a6c64cb6..9d4bdf7a 100644 --- a/docs/en/reference/site-config.md +++ b/docs/en/reference/site-config.md @@ -478,6 +478,8 @@ export default { When set to `true`, extract pages metadata to a separate JavaScript chunk instead of inlining it in the initial HTML. This makes each page's HTML payload smaller and makes the pages metadata cacheable, thus reducing server bandwidth when you have many pages in the site. +By default, metadata is output in the page's HTML source. Some search engines crawl the source code to find link-like strings and may recognize the .md links within the metadata JSON content, which are inaccessible. This interferes with search results, potentially leading to numerous 404 errors reported in search consoles. To avoid this, enable this option to output the metadata in a separate JS file instead of embedding it within the page's HTML source. + ### mpa - Type: `boolean`