{"@context": "https://schema.org", "@type": "AnalysisNewsArticle", "inLanguage": "en", "identifier": "preserve-article-urls-301-canonical-sitemap", "headline": "Preserving Old Article URLs: This Site’s 301, Canonical, and Sitemap Repair Log", "description": "What should you do when old articles return 404 after deduplication? This site’s handling of 13 old URLs shows how to review content correspondence, persist 301 redirects, and verify canonicals, sitemaps, and browser navigation.", "abstract": "Old links remain valuable when they still help readers find the corresponding content. This article reviews the implementation of 11 permanent redirects and the restoration of 2 articles at their original URLs, providing HTTP check commands, database safeguards, and the limits of what crawling and indexing can establish.", "datePublished": "2026-09-20", "dateModified": "2026-09-25T14:28:25.882373+00:00", "author": {"@type": "Person", "name": "Aperture Research Editorial Team", "jobTitle": "Engineering Practice"}, "about": ["301 redirects", "canonical", "sitemap", "old URLs", "engineering practice"], "category": "Agent technology", "authorityScore": 94, "claims": [{"text": "Removing duplicate content may reduce the number of articles, but old links in search engines, bookmarks, and articles on other sites do not disappear along with them. On September 14, 2026, Aperture addressed a batch of previously identified old URLs: of 13 URLs, 11 received permanent redirects, and 2 distinct articles were restored at their original URLs. All 22 existing public URLs and their original publication timestamps were retained, bringing the number of public articles to 24 after the repair.[S1]", "section": "After Article Deduplication, People Still Visit Old Links"}, {"text": "The goal of this case was to preserve the content relevance of old entry points: duplicate articles were redirected to relevant articles with sufficient coverage, while distinct content was restored after additional review. It did not demonstrate an improvement in search rankings or promise that search engines would complete indexing by a particular date. This article reviews the batch handled on September 14; any old links discovered later require separate review. A one-time repair should not be treated as permanently eliminating the problem.", "section": "After Article Deduplication, People Still Visit Old Links"}, {"text": "A URL returning 404 only indicates that no resource is currently available; it does not, by itself, establish which article should be restored. Before taking action, check the old article’s full text, publication history, supporting sources, and the current article catalog. Permanently redirecting the old URL to an existing page is appropriate only after confirming that the page covers its central questions and substantive content.", "section": "Determine the Content Relationship Before Deciding What to Do with the URL"}, {"text": "Google’s site migration guide calls for preparing a mapping between old and new URLs and warns against redirecting many old URLs to an irrelevant destination, such as the homepage, because this may be treated as a soft 404. The same principle can guide article consolidation: when readers arrive through a link to a specific article, the destination page should answer the original question.[S3]", "section": "Determine the Content Relationship Before Deciding What to Do with the URL"}, {"text": "In this repair, the site first compared the full texts, then incorporated substantive information that needed to be retained into the destination articles and reviewed them again. The articles on historical European Central Bank interest rates and historical Nasdaq observations could not be replaced by existing content, so they were restored at their original URLs after revisions to their sources and citations. These actions were recorded as review outcomes, rather than merely implemented as temporary rules at the edge layer.[S1]", "section": "Determine the Content Relationship Before Deciding What to Do with the URL"}, {"text": "A 301 is an HTTP response in which the server tells the client that a resource has moved permanently, with the destination specified in the Location header. MDN also notes that, depending on the request method, following a 301 may change the method to GET. This case therefore concerns GET and HEAD entry points for public content; a redirect rule for an ordinary web page cannot simply be applied to payments or write operations.[S5]", "section": "What 301 Redirects, Canonicals, and Sitemaps Each Address"}, {"text": "A canonical is a signal through which the current page identifies its preferred canonical URL; it does not make an old URL that already returns 404 work in the browser. Google classifies permanent redirects and rel=canonical as strong canonicalization signals, and inclusion in a sitemap as a weaker signal. These methods can work together, but a search engine may still choose a canonical page based on other signals.[S4]", "section": "What 301 Redirects, Canonicals, and Sitemaps Each Address"}, {"text": "The site redirects old web pages to specific destination articles using 301 responses. The destination articles return 200 and have self-referencing canonicals, while the sitemap lists only the retained public canonical pages. Google’s sitemap guide recommends listing the canonical URLs you want to appear in search results. Submitting a sitemap is a discovery mechanism, not a guarantee that every entry will be crawled or indexed.[S1][S6]", "section": "What 301 Redirects, Canonicals, and Sitemaps Each Address"}, {"text": "The site stores source_slug, the original article ID, the destination article ID, content hashes for both articles, and review records in the article_redirects table. Web pages, article JSON, and Agent entry points read the same mapping, reducing the chance that different entry points will lead to different content.[S1][S2]", "section": "Mappings Need Persistent Storage and Protection Against Later Tasks"}, {"text": "Database safeguards also constrain subsequent changes: old articles that have been mapped cannot be arbitrarily deleted, renamed, or republished, and destination articles cannot be deleted or unpublished. This prevents scheduled collection jobs and editorial operations from turning old entry points back into 404s on the next run or republishing duplicate content that has already been consolidated.[S1][S2]", "section": "Mappings Need Persistent Storage and Protection Against Later Tasks"}, {"text": "Two separate checks also precede the creation of a mapping: first, that the destination is currently public and readable; second, that the article text and sources compared during review have not changed by the time the mapping is committed. The site locks the relevant tables within a transaction, rechecks the catalog and content hashes, and then writes the mapping. These checks prevent outdated reviews from being committed.[S1] When implementing a similar process, it is advisable to complete model-based review outside the transaction so that database locks are not held during lengthy network calls.", "section": "Mappings Need Persistent Storage and Protection Against Later Tasks"}, {"text": "Seeing a normal title in the browser does not prove that the server actually issued a 301. A front-end application may change the content without updating the URL, and a CDN may continue serving an old cached response. Check the HTTP status and Location first, then the final page’s content and canonical, and finally on-site navigation with JavaScript enabled.[S1]", "section": "Verify Direct Access, Machine Interfaces, and On-Site Navigation Separately"}, {"text": "The following is an example from the actual mappings in this repair. The first command inspects the old URL’s status and Location; the second follows the redirect to confirm the final destination; the third checks the canonical URL in the destination HTML. These commands target public, read-only pages and contain no administrative credentials.[S1]", "section": "Verify Direct Access, Machine Interfaces, and On-Site Navigation Separately"}, {"text": "For ordinary GET requests to articles, old links with UTM parameters should still reach the corresponding content. Campaign parameters support traffic-source attribution, while the canonical URL generally retains the article path without those parameters. During implementation, separately check URLs with and without parameters, trailing-slash variants, and direct access to the destination to avoid redirect loops or irrelevant intermediate pages. These are checks that should be performed; the result of any single test should not be generalized into a claim that all variants will remain correct forever.", "section": "Do Not Let Campaign Parameters or Caching Hide Problems"}, {"text": "Refreshing caches only helps clients see new responses sooner; it does not make search engines update their indexes immediately. Google’s migration guide warns that fluctuations may occur during recrawling and reindexing and recommends retaining redirects for a sufficiently long time. The site’s page safeguards aim to keep valid old entry points available over time, rather than treating redirects as temporary patches that can be removed after a few days.[S3]", "section": "Do Not Let Campaign Parameters or Caching Hide Problems"}, {"text": "Machine interfaces should also retain their own semantics. For example, open JSON interfaces and paid interfaces must not be conflated. Even when they reference the same article, their paths, access conditions, and final responses must be verified. The unified mapping in this case unifies content identity; it does not remove the access requirements of individual entry points.[S1][S2]", "section": "Do Not Let Campaign Parameters or Caching Hide Problems"}, {"text": "The September 14 verification records show that GET and HEAD requests to 11 old URLs returned 301, while all 24 public articles returned 200 and had a single H1 and the correct canonical. The article sitemap contained 24 articles and excluded redirect source URLs. Browser testing also covered scripts enabled and disabled, on-site navigation through old links, URL updates, and back/forward navigation.[S1]", "section": "Acceptance Results for This Repair—and What They Did Not Prove"}, {"text": "These results establish that the paths and rendering behavior met the repair goals at that time; they do not establish that all articles had been indexed. Page indexing status, search query impressions, and clicks in Google Search Console require separate inspection. Googlebot or Bingbot visits in logs are likewise only evidence of crawling.", "section": "Acceptance Results for This Repair—and What They Did Not Prove"}, {"text": "For ongoing maintenance, “old URLs returning 404 that have still received requests recently” can become a standing checklist. For each newly discovered entry point, first revisit content coverage and publication history, then decide whether to restore it, apply a relevant 301, or retain a genuine 404. In this way, page counts, search availability, and content deduplication no longer have to conflict: what is consolidated is duplicate expression, while what is preserved is the entry point readers still need.", "section": "Acceptance Results for This Repair—and What They Did Not Prove"}], "sections": [{"type": "analysis", "heading": "After Article Deduplication, People Still Visit Old Links", "paragraphs": ["Removing duplicate content may reduce the number of articles, but old links in search engines, bookmarks, and articles on other sites do not disappear along with them. On September 14, 2026, Aperture addressed a batch of previously identified old URLs: of 13 URLs, 11 received permanent redirects, and 2 distinct articles were restored at their original URLs. All 22 existing public URLs and their original publication timestamps were retained, bringing the number of public articles to 24 after the repair.[S1]", "The goal of this case was to preserve the content relevance of old entry points: duplicate articles were redirected to relevant articles with sufficient coverage, while distinct content was restored after additional review. It did not demonstrate an improvement in search rankings or promise that search engines would complete indexing by a particular date. This article reviews the batch handled on September 14; any old links discovered later require separate review. A one-time repair should not be treated as permanently eliminating the problem."]}, {"type": "analysis", "heading": "Determine the Content Relationship Before Deciding What to Do with the URL", "paragraphs": ["A URL returning 404 only indicates that no resource is currently available; it does not, by itself, establish which article should be restored. Before taking action, check the old article’s full text, publication history, supporting sources, and the current article catalog. Permanently redirecting the old URL to an existing page is appropriate only after confirming that the page covers its central questions and substantive content.", "Google’s site migration guide calls for preparing a mapping between old and new URLs and warns against redirecting many old URLs to an irrelevant destination, such as the homepage, because this may be treated as a soft 404. The same principle can guide article consolidation: when readers arrive through a link to a specific article, the destination page should answer the original question.[S3]", "In this repair, the site first compared the full texts, then incorporated substantive information that needed to be retained into the destination articles and reviewed them again. The articles on historical European Central Bank interest rates and historical Nasdaq observations could not be replaced by existing content, so they were restored at their original URLs after revisions to their sources and citations. These actions were recorded as review outcomes, rather than merely implemented as temporary rules at the edge layer.[S1]"]}, {"type": "analysis", "heading": "What 301 Redirects, Canonicals, and Sitemaps Each Address", "paragraphs": ["A 301 is an HTTP response in which the server tells the client that a resource has moved permanently, with the destination specified in the Location header. MDN also notes that, depending on the request method, following a 301 may change the method to GET. This case therefore concerns GET and HEAD entry points for public content; a redirect rule for an ordinary web page cannot simply be applied to payments or write operations.[S5]", "A canonical is a signal through which the current page identifies its preferred canonical URL; it does not make an old URL that already returns 404 work in the browser. Google classifies permanent redirects and rel=canonical as strong canonicalization signals, and inclusion in a sitemap as a weaker signal. These methods can work together, but a search engine may still choose a canonical page based on other signals.[S4]", "The site redirects old web pages to specific destination articles using 301 responses. The destination articles return 200 and have self-referencing canonicals, while the sitemap lists only the retained public canonical pages. Google’s sitemap guide recommends listing the canonical URLs you want to appear in search results. Submitting a sitemap is a discovery mechanism, not a guarantee that every entry will be crawled or indexed.[S1][S6]"], "headers": ["Component", "Role in This Case", "Work It Cannot Replace"], "rows": [["301 + Location", "Directs visits to old URLs to relevant destination articles", "Cannot replace reviews of content coverage and quality"], ["Self-referencing canonical", "Identifies the destination page’s preferred URL", "Cannot repair an inaccessible old entry point"], ["sitemap", "Lists the current discoverable public canonical pages", "Cannot guarantee indexing, rankings, or clicks"]]}, {"type": "analysis", "heading": "Mappings Need Persistent Storage and Protection Against Later Tasks", "paragraphs": ["The site stores source_slug, the original article ID, the destination article ID, content hashes for both articles, and review records in the article_redirects table. Web pages, article JSON, and Agent entry points read the same mapping, reducing the chance that different entry points will lead to different content.[S1][S2]", "Database safeguards also constrain subsequent changes: old articles that have been mapped cannot be arbitrarily deleted, renamed, or republished, and destination articles cannot be deleted or unpublished. This prevents scheduled collection jobs and editorial operations from turning old entry points back into 404s on the next run or republishing duplicate content that has already been consolidated.[S1][S2]", "Two separate checks also precede the creation of a mapping: first, that the destination is currently public and readable; second, that the article text and sources compared during review have not changed by the time the mapping is committed. The site locks the relevant tables within a transaction, rechecks the catalog and content hashes, and then writes the mapping. These checks prevent outdated reviews from being committed.[S1] When implementing a similar process, it is advisable to complete model-based review outside the transaction so that database locks are not held during lengthy network calls."]}, {"type": "analysis", "heading": "Verify Direct Access, Machine Interfaces, and On-Site Navigation Separately", "paragraphs": ["Seeing a normal title in the browser does not prove that the server actually issued a 301. A front-end application may change the content without updating the URL, and a CDN may continue serving an old cached response. Check the HTTP status and Location first, then the final page’s content and canonical, and finally on-site navigation with JavaScript enabled.[S1]", "The following is an example from the actual mappings in this repair. The first command inspects the old URL’s status and Location; the second follows the redirect to confirm the final destination; the third checks the canonical URL in the destination HTML. These commands target public, read-only pages and contain no administrative credentials.[S1]"], "code": "curl -I 'https://aperture.zhangwangshu.com/article/agent-research-20260903-2103-396'\ncurl -L -o /dev/null -w '%{http_code} %{url_effective}\\n' \\\n  'https://aperture.zhangwangshu.com/article/agent-research-20260903-2103-396'\ncurl -s 'https://aperture.zhangwangshu.com/article/agent-research-20260905-0003-599' \\\n  | rg 'rel=\"canonical\"'"}, {"type": "analysis", "heading": "Do Not Let Campaign Parameters or Caching Hide Problems", "paragraphs": ["For ordinary GET requests to articles, old links with UTM parameters should still reach the corresponding content. Campaign parameters support traffic-source attribution, while the canonical URL generally retains the article path without those parameters. During implementation, separately check URLs with and without parameters, trailing-slash variants, and direct access to the destination to avoid redirect loops or irrelevant intermediate pages. These are checks that should be performed; the result of any single test should not be generalized into a claim that all variants will remain correct forever.", "Refreshing caches only helps clients see new responses sooner; it does not make search engines update their indexes immediately. Google’s migration guide warns that fluctuations may occur during recrawling and reindexing and recommends retaining redirects for a sufficiently long time. The site’s page safeguards aim to keep valid old entry points available over time, rather than treating redirects as temporary patches that can be removed after a few days.[S3]", "Machine interfaces should also retain their own semantics. For example, open JSON interfaces and paid interfaces must not be conflated. Even when they reference the same article, their paths, access conditions, and final responses must be verified. The unified mapping in this case unifies content identity; it does not remove the access requirements of individual entry points.[S1][S2]"]}, {"type": "analysis", "heading": "Acceptance Results for This Repair—and What They Did Not Prove", "paragraphs": ["The September 14 verification records show that GET and HEAD requests to 11 old URLs returned 301, while all 24 public articles returned 200 and had a single H1 and the correct canonical. The article sitemap contained 24 articles and excluded redirect source URLs. Browser testing also covered scripts enabled and disabled, on-site navigation through old links, URL updates, and back/forward navigation.[S1]", "These results establish that the paths and rendering behavior met the repair goals at that time; they do not establish that all articles had been indexed. Page indexing status, search query impressions, and clicks in Google Search Console require separate inspection. Googlebot or Bingbot visits in logs are likewise only evidence of crawling.", "For ongoing maintenance, “old URLs returning 404 that have still received requests recently” can become a standing checklist. For each newly discovered entry point, first revisit content coverage and publication history, then decide whether to restore it, apply a relevant 301, or retain a genuine 404. In this way, page counts, search availability, and content deduplication no longer have to conflict: what is consolidated is duplicate expression, while what is preserved is the entry point readers still need."]}], "citations": [{"publisher": "Aperture Intelligence", "title": "This Site’s Old URL Repair Log for 2026-09-14", "url": "https://github.com/milan9527/geo/blob/34b646e1f34d74c740020df4d9f59dd770449646/reports/legacy-url-repair-2026-09-14.md", "published_at": "2026-09-14", "source_type": "本站代码与复盘"}, {"publisher": "Aperture Intelligence", "title": "Implementation of Persistent Article Redirects and Database Safeguards", "url": "https://github.com/milan9527/geo/blob/34b646e1f34d74c740020df4d9f59dd770449646/backend/article_redirects.py", "published_at": "2026-09-14", "source_type": "本站代码与复盘"}, {"publisher": "Google Search Central", "title": "Site moves with URL changes", "url": "https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes", "published_at": "", "source_type": "Official documentation"}, {"publisher": "Google Search Central", "title": "How to specify a canonical URL", "url": "https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls", "published_at": "", "source_type": "Official documentation"}, {"publisher": "MDN Web Docs", "title": "301 Moved Permanently", "url": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/301", "published_at": "", "source_type": "Official documentation"}, {"publisher": "Google Search Central", "title": "Build and submit a sitemap", "url": "https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap", "published_at": "", "source_type": "Official documentation"}], "knowledge": {"question": {"en": "After article deduplication leaves old URLs returning 404, how should a site choose restoration or a relevant 301 redirect, preserve the mapping, and verify canonical URLs, sitemap entries, and navigation?", "zh": "文章去重后旧网址返回404，网站应如何选择原址恢复或相关301重定向、持久保存映射，并验证canonical、sitemap与导航？"}, "audience": {"en": "Content-site editors and engineers responsible for article consolidation, URL maintenance, publishing safeguards, and search accessibility.", "zh": "负责文章合并、网址维护、发布保护与搜索可访问性的内容网站编辑和工程人员。"}, "decision": {"en": "Review the old article's content, publication history, and sources before choosing restoration, a redirect to an adequately covering article, or a genuine 404. Then verify HTTP responses, destination content, canonical URLs, sitemap membership, machine interfaces, and browser navigation separately.", "zh": "先审核旧稿正文、发布历史与来源，再决定原址恢复、重定向到覆盖充分的文章，或保留真实404；随后分别验证HTTP响应、目标正文、canonical、sitemap条目、机器接口与浏览器导航。"}, "contribution": {"en": "A bounded repair case covering 13 old URLs on September 14, 2026: 11 permanent redirects and two articles restored at their original URLs. It connects content review with persistent database mappings and publishing protection, supplies curl checks, and reports validation of 24 public articles.", "zh": "复盘2026年9月14日针对13个旧网址的一次修复：11个永久重定向、2篇文章原址恢复。文章将内容审核与数据库持久映射、发布保护相衔接，提供curl检查命令，并报告24篇公开文章的验收结果。"}, "limitation": {"en": "The results establish the tested paths and rendering behavior at that time, not improved rankings or completed indexing. Newly discovered URLs and URL variants still require checks. The redirect example concerns public GET and HEAD access, not payment or write operations; shared content mappings do not remove interface-specific access requirements.", "zh": "结果仅证明当时受测路径与渲染行为符合目标，不证明排名提高或收录完成。新发现的网址及网址变体仍需检查。重定向示例针对公开GET和HEAD访问，不适用于直接照搬到支付或写操作；共享内容映射也不取消各接口自身的访问要求。"}, "nodes": [{"key": "n1", "kind": "entity", "name": {"en": "Aperture", "zh": "Aperture"}, "mention": "Aperture", "id": "entity-6f59cf9b31012122ebe1"}, {"key": "n2", "kind": "concept", "name": {"en": "301 permanent redirect", "zh": "301永久重定向"}, "mention": "301", "id": "concept-f5fe4e2ddfc04a09de5a"}, {"key": "n3", "kind": "concept", "name": {"en": "Review of core-question and valid-content coverage", "zh": "核心问题与有效内容覆盖审核"}, "mention": "覆盖其核心问题与有效内容", "id": "concept-219f11939660755b0da3"}, {"key": "n4", "kind": "concept", "name": {"en": "rel=canonical", "zh": "rel=canonical"}, "mention": "rel=canonical", "id": "concept-52e2cfe499d9823f5213"}, {"key": "n5", "kind": "concept", "name": {"en": "Sitemap", "zh": "sitemap"}, "mention": "sitemap", "id": "concept-6b0d1c558c93b0e25f36"}, {"key": "n6", "kind": "entity", "name": {"en": "article_redirects table", "zh": "article_redirects表"}, "mention": "article_redirects 表", "id": "entity-6b49bc12b8025a83ac5a"}], "edges": [{"source": "n1", "target": "n2", "relation": "uses", "stance": "reported", "citationRole": "direct", "explanation": {"en": "Aperture reports using 301 redirects for 11 old URLs in this repair batch. The cited repair record establishes the observed GET and HEAD responses, not a search-ranking outcome.", "zh": "Aperture报告在该批修复中为11个旧网址使用301重定向。所引修复记录直接支持GET和HEAD响应的验收结果，不支持搜索排名改善的结论。"}, "quote": {"en": "The September 14 validation record shows that GET and HEAD requests to 11 old URLs returned 301, while 24 public articles returned 200 and had a single H1 and the correct canonical; the article sitemap contained 24 articles and did not include redirect sources.", "zh": "9月14日的验证记录显示，11个旧网址的GET和HEAD返回301，24篇公开文章返回200并有单一H1及正确canonical；文章sitemap包含24篇，未包含重定向来源。"}, "citations": [1], "sourceId": "entity-6f59cf9b31012122ebe1", "targetId": "concept-f5fe4e2ddfc04a09de5a"}, {"source": "n2", "target": "n3", "relation": "depends_on", "stance": "analysis", "citationRole": "background", "explanation": {"en": "The original article's section on choosing URL actions makes adequate content coverage a prerequisite for an appropriate permanent redirect in article consolidation. This is an editorial decision rule, not a technical requirement of HTTP. Google's migration guidance supplies background on URL mapping and relevant destinations, rather than proving the author's application to article merging.", "zh": "原文“先判断内容关系，再选择网址动作”一节将充分的内容覆盖作为文章合并时适宜采用永久重定向的前提。这是编辑决策规则，不是HTTP的技术要求。Google迁移指南提供网址映射与目的地相关性的背景，而非证明作者对文章合并的具体推论。"}, "quote": {"en": "Only after confirming that an existing page covers its core question and valid content is it appropriate to permanently point the old URL to that page.", "zh": "只有确认已有页面覆盖其核心问题与有效内容时，才适合将旧网址永久指向该页。"}, "citations": [3], "sourceId": "concept-f5fe4e2ddfc04a09de5a", "targetId": "concept-219f11939660755b0da3"}, {"source": "n1", "target": "n6", "relation": "uses", "stance": "reported", "citationRole": "direct", "explanation": {"en": "Aperture stores reviewed source-to-target article mappings in article_redirects, including article IDs, content hashes, and review records. Web, article JSON, and Agent entry points read this shared mapping; the repair record and implementation directly document this arrangement.", "zh": "Aperture使用article_redirects保存经过审核的文章来源—目标映射，包括文章ID、内容哈希与审核记录。网页、文章JSON及Agent入口读取该共享映射；修复记录与实现代码直接记录了这一安排。"}, "quote": {"en": "This site stores source_slug, the original article ID, the target article ID, both content hashes, and review records in the article_redirects table. Web pages, article JSON, and Agent entry points read the same mapping, reducing the chance that different entry points lead to different content.", "zh": "本站把 source_slug、原文章ID、目标文章ID、双方内容哈希和审核记录保存在 article_redirects 表中。网页、文章JSON及Agent入口读取同一份映射，减少不同入口指向不同内容的机会。"}, "citations": [1, 2], "sourceId": "entity-6f59cf9b31012122ebe1", "targetId": "entity-6b49bc12b8025a83ac5a"}, {"source": "n2", "target": "n4", "relation": "compares", "stance": "reported", "citationRole": "direct", "explanation": {"en": "The article reports Google's classification of permanent redirects and rel=canonical as strong canonicalization signals. This comparison concerns signal strength, not functional interchangeability or a guarantee that Google will select the preferred page.", "zh": "文章转述Google将永久重定向与rel=canonical都列为较强规范化信号。这一比较针对信号强度，并不表示两者功能可以互换，也不保证Google选择网站首选页面。"}, "quote": {"en": "Google lists permanent redirects and rel=canonical as stronger canonicalization signals, and sitemap inclusion as a weaker signal; these methods can work together, but the search engine may ultimately still choose a canonical page based on other signals.", "zh": "Google 将永久重定向和 rel=canonical 列为较强的规范化信号，将 sitemap 包含关系列为较弱信号；这些手段可以相互配合，但最终搜索引擎仍可能根据其他信号选择规范页。"}, "citations": [4], "sourceId": "concept-f5fe4e2ddfc04a09de5a", "targetId": "concept-52e2cfe499d9823f5213"}, {"source": "n5", "target": "n4", "relation": "compares", "stance": "reported", "citationRole": "direct", "explanation": {"en": "Sitemap inclusion is reported as a weaker canonicalization signal than rel=canonical. Google's canonical-URL documentation directly supports this distinction; it does not establish that listing a URL guarantees indexing.", "zh": "文章指出，sitemap包含关系是比rel=canonical更弱的规范化信号。Google规范网址文档直接支持这一区分，但并不支持“列入sitemap即可保证收录”的结论。"}, "quote": {"en": "Google lists permanent redirects and rel=canonical as stronger canonicalization signals, and sitemap inclusion as a weaker signal; these methods can work together, but the search engine may ultimately still choose a canonical page based on other signals.", "zh": "Google 将永久重定向和 rel=canonical 列为较强的规范化信号，将 sitemap 包含关系列为较弱信号；这些手段可以相互配合，但最终搜索引擎仍可能根据其他信号选择规范页。"}, "citations": [4], "sourceId": "concept-6b0d1c558c93b0e25f36", "targetId": "concept-52e2cfe499d9823f5213"}]}, "knowledgeMap": "/knowledge", "license": {"model": "open", "price": 0.002, "currency": "USDC", "paymentProtocol": "x402", "network": "eip155:84532", "payTo": "0x23a885262A89c32eB582f4439184769dA22c467c", "variants": {"A": "/agent/v1/articles/preserve-article-urls-301-canonical-sitemap?lang=en", "B": "/agent/v1/articles/preserve-article-urls-301-canonical-sitemap/paid?lang=en"}}, "accessVariant": "A", "contentPolicy": {"citationAllowed": true, "attributionRequired": true, "trainingUse": "contact publisher"}}