Which URLs Belong in a Factory Website’s Sitemap? Admission Checklist
Tuohai editorial guide · Reviewed and published October 5, 2026. The worksheets are blank working templates, not client results.
A longer sitemap is not necessarily a better deliverable. Mixing current product pages, old paths, filter parameters and pages not intended for search makes the preferred version harder to explain.
Start with the intended purpose: which content should appear as an independent search result, and which URL should represent it? Decide why a URL belongs before checking the generated file.
Choose which URLs your sitemap should include
Google's sitemap documentation recommends listing URLs you want in search results and choosing a preferred version for duplicate content. Submission is a hint, not a guarantee of downloading, crawling or indexing.
For routine maintenance, use a practical admission rule: a production URL that is accessible, intended for indexing and represents the preferred version. This is an editorial quality gate, not a claim that one other-status URL makes an entire file invalid. Temporary migration or diagnostic lists need their own stated purpose.
A canonical URL is the preferred address representing content. Google's canonical guidance treats sitemap inclusion as a weaker signal. It does not override conflicting canonical declarations or redirects. Resolve those conflicts before choosing the listed version.
Admission is not deletion. A thank-you page may remain useful without needing search exposure; an old path may retain an appropriate redirect. Removing either from a sitemap does not make it inaccessible or prove its removal from Google's index.
Judge page types by their purpose
Write one purpose for each type: a model page explains suitability, a category supports comparison, and a technical article answers a specific question. Do not exclude categories merely because they are categories, or include similar copies merely because the product catalog is large.
| Page type | Reason to include | Reason to defer or exclude |
|---|---|---|
| Production model page | Genuine specifications, limits and distinct purpose | Name-only copy or unfinished template |
| Product category | Scope, selection guidance and useful product links | Empty category or automatic list without products |
| Technical article | Distinct buyer or usage question | Draft, placeholder or duplicate of a retained page |
| Tag or author archive | Clear retrieval purpose and indexing decision | Repeated list or intentionally excluded page |
| Filter or parameter URL | Distinct task and defined canonical strategy | Sorting, tracking or duplicated main content |
| Old or error URL | Prefer the production replacement in routine lists | Redirecting old path, 404 or missing useful body |
This is an editorial decision table, not Google's blanket prohibition on archives. Deferring inclusion does not require immediate deletion.
In a hypothetical example, a valve filter changes only list order, while an edited media-selection page answers a distinct question. Judge content and URL strategy, not the presence of a question mark. This is not client evidence.
Complete a URL admission worksheet
Sample each template, then document priority URLs individually. Add evidence and a check date; leave unknown fields unknown rather than accepting plugin defaults.
| Check | Record for this URL | Decision or task |
|---|---|---|
| Full production URL and type | ____ | ____ |
| Distinct task intended for search | ____ | ____ |
| Response and final destination | ____ | ____ |
| Crawl rules and indexing intention | ____ | ____ |
| HTML/header noindex directives | ____ | ____ |
| Canonical target and current state | ____ | ____ |
| Complete, non-duplicate body | ____ | ____ |
| Internal referring pages | ____ | ____ |
| Significant update date and basis | ____ | ____ |
| Include/defer/exclude and owner | ____ | ____ |
noindex expresses an instruction not to index a page. Google's page-level directive documentation covers HTML and HTTP headers, and says crawlers need access to read the rules. Visible body content alone does not establish the indexing configuration.
For routinely included pages, verify useful content, no accidental indexing exclusion and alignment between the preferred URL and actual destination. Passing this local check does not guarantee Google's selection or indexing.
Complete the internal-link field too. Sitemap inclusion is not a reason to leave content disconnected from relevant categories or articles.
Check generated child sitemaps and update dates
An editor setting does not prove the public file changed. Open the actual sitemap index and relevant article, product or category child file. Check that <loc> contains the full production address, not a preview or pre-redirect path.
Where caching is involved, record the public version, time and discrepancy before an authorized person changes caching or generation rules.
Give lastmod a defensible basis. Google uses accurate, verifiable values; significant changes to main content, structured data or links can qualify. Setting every page to today's date does not describe actual changes. Updating a copyright year is not a significant body update.
Google ignores priority and changefreq. Check missing production URLs, retained copies and consistent generation rather than repeatedly increasing a priority value.
Frequently asked questions
Does successful submission mean every URL is indexed?
No. Submission, file reading and individual indexing are separate records. Verify the file and admission rules, then observe priority pages independently.
Must all WordPress tag pages stay out?
No blanket conclusion follows. Check purpose, useful content and indexing intention. Defer pages without a clear reason, but do not delete existing pages just to empty a report.
Does removing a dead URL immediately remove its search result?
No. Confirm its actual response, replacement arrangement and indexing separately. A smaller sitemap is not proof of an updated search state.
Conclusion: keep a reason for every included URL
Decide which URLs belong in a sitemap through page-type rules and recorded evidence. Confirm the retained version, inspect public child files, and separate file acceptance from later crawling and indexing.
You can request Tuohai's free human SEO audit, in Chinese. The full human audit is free; scope, materials and scheduling are agreed separately. There is no guaranteed response time, indexing or ranking outcome.
Sources
Read on October 5, 2026. These links open Chinese-language official documentation. The tables are editorial tools for routine maintenance, not migration instructions.