A short story to start
Val runs a small home-decor shop. Her new website looks great, but Google is slow to show her pages. We check one simple thing: the XML sitemap. It is missing. We add it, submit it to Google, fix a few pages that should not be there, and set a clean structure. Two weeks later, more of her pages appear in search. Sales grow. This happens often. The sitemap is a small file with a big job.
What is an XML sitemap?
An XML sitemap is a machine-readable file that lists canonical URLs you want search engines to find. Each <url> can include metadata such as <lastmod>. Change frequency and priority exist in the protocol but Google ignores them; focus on accurate <lastmod>sitemaps.org+1
It tells Google and other search engines:
- which pages are important
- when a page was last updated
Where to find it: usually at https://yourdomain.com/sitemap.xml or https://yourdomain.com/sitemap_index.xml.
Simple view of a sitemap
sitemap_index.xml
├─ page-sitemap.xml
├─ post-sitemap.xml
├─ product-sitemap.xml
└─ category-sitemap.xml
A page entry looks like this:
<url>
<loc>https://example.com/about/</loc>
<lastmod>2025-09-01</lastmod>
</url>
- <loc> = the page URL
- <lastmod> = the date the page really changed
Ignore “priority” and “changefreq.” They do not help. Focus on correct URLs and true lastmod dates.
Why XML sitemap matters across the full website lifecycle
- During design and development: checks the site structure; shows if “extra” pages are being created by the CMS and keeps content types organized; ensure every intended template and content type resolves to clean, crawlable URLs. Catch “generated” URLs early (e.g., unstyled tag/author archives, default CPT archives) and exclude them before launch to protect crawl budget.– Google for Developers
- At launch: helps Google discover new pages faster.
- SEO: improves discoverability and reduces crawl waste by excluding thin, duplicate, or broken pages
- During maintenance: makes it easy to see what should be indexed and what should be hidden; supports ongoing audits, highlights gaps (e.g., posts not indexed or categories empty), and informs redirect decisions after changes.
How UPQODE uses sitemaps on real projects
We keep the sitemap small, clean, and honest. Only good pages go in. Everything else is either styled and kept or excluded. No broken links. No test pages. No duplicates.
Our 5-step workflow
| Plan: | PM and SEO define what page types we will have (pages, posts, products, categories). We align content/pages types with the sitemap index (posts, pages, custom post types) and keep each section clean. |
| Build: | Dev sets clean URLs and adds the sitemap tool (Yoast, Rank Math, platform generator, or custom). |
| Review: | QA checks the sitemap in staging. We remove junk pages (example: empty tag pages). |
| Launch: | SEO submits the sitemap in Google Search Console and checks for errors. |
| Maintain: | We watch the index status monthly and after every big change. |
How-to: creating and submitting an XML sitemap
WordPress (Yoast/Rank Math Pro)
Enable the sitemap in SEO plugin (Yoast or Rank Math Pro). Confirm /sitemap_index.xml loads and section sitemaps exist – https://upqode.com/page-sitemap.xml
In Search Appearance – Settings/Content Types (Yoast) , choose what to include:
- Include: Toggle per type core pages types, blog posts, useful category pages, well-designed archive pages with unique value. Confirm after cache clear.
- Exclude: Disable low-value post types and archives in the plugin “Search Appearance” settings. e.g., tag pages that have no design or content, author pages you don’t use, thin, duplicated, broken, test content. Confirm after cache clear.
Shopify/Webflow
Confirm platform sitemap path and sections; apply same include/exclude logic and verify in GSC.
Shopify quick path
Shopify auto-generates /sitemap.xml with child sitemaps for products, collections, pages, and blogs. You submit once, then monitor.
- Shopify auto-creates /sitemap.xml.
- Expect nested sitemaps for products, collections, pages, and blogs.
- Submit it in Google Search Console. Do not add filters or parameter URLs to sitemaps.
Webflow quick path
- Enable Auto-generate sitemap in Site Settings → SEO → Auto-generate sitemap: On.
- Exclude low-value pages (thank-you pages, tests).
- Publish, then submit in Google Search Console.
GSC + robots.txt
- Submit /sitemap_index.xml or /sitemap.xml in GSC.
- Reference sitemap in robots.txt. Track coverage deltas after changes.
Concrete scenario and how UPQODE handles them
Scenario: Content-heavy Website with messy archives
During an onboarding audit, we found numerous auto-generated archive pages (custom post types, author archives) that were unstyled and offered no SEO value. We removed these sections from the sitemap, retained only quality archive templates, and recommended either styling the remaining archives or eliminating page generation in the functionality to prevent crawl waste.
Result: a smaller, higher-quality sitemap and fewer indexation warnings.
Symptoms: Lot of tag pages, many empty or duplicative. Category pages unstyled.
Actions:
- Exclude tag archives from sitemap and from indexation until they’re styled and unique.
- Keep category archives only if they offer real value (curation, intro copy, internal links)
- Keep only well-designed page types.
- Add short intro text to categories. Watch index counts.
Result: Google spends time on pages that matter. Faster indexing of new posts.
Frequently Asked Questions
1. Do I need both XML and HTML sitemaps?
XML is for crawlers. HTML can help users and internal linking. Use both if the HTML version is well-designed.
2. Should I include categories/tags or author pages?
Only if they are designed, have unique text, and help users. Otherwise exclude.
3. Will removing archives hurt SEO?
Not if they have no traffic or links; check first, then decide.
4. Should I fill in <priority> and <changefreq>?
You can, but Google ignores them; prioritize clean inclusion and accurate <lastmod>.
5. Can I combine image, video, and hreflang in one file?
Yes. Declare the proper namespaces and follow each extension’s rules.
6. My site is small. Do I still need a sitemap?
Yes. It helps Google find pages faster, especially right after launch.
7. My shop has many color/size filters. Add them?
No. Keep only the main product and category URLs.
8. What if I change many URLs during a redesign?
Create a new sitemap with the new URLs. Add 301 redirects for old winners. Watch Google Search Console for one month.
9. My sitemap shows pages I don’t want in Google.
Remove them from the sitemap and set noindex if needed. Clear cache. Resubmit.
10. Is <priority> useful?
No. Focus on good pages and true <lastmod>.
11. Where should I put the sitemap link for Google?
Submit it in Google Search Console. Also add Sitemap: https://domain.com/sitemap.xml in robots.txt.
12. My multilingual site needs hreflang. Use the sitemap?
You can. Add hreflang pairs in the sitemap or in HTML. Keep consistent.
13. Do I need redirects when removing tag pages?
Check traffic and backlinks first. If none, remove without redirects. If some value, redirect to the best category or blog hub.
14. Can a broken page in the sitemap hurt me?
Yes. Remove broken URLs from the sitemap. Fix the page or keep it out.
15. How often should I resubmit the sitemap?
Normally once. Resubmit after large changes.
16. Can I use one sitemap for www and non-www?
List only the canonical host. Stick to HTTPS.
Need help cleaning up your sitemap?
A well-structured XML sitemap can speed up indexing, reduce crawl waste, and highlight the pages that truly matter. If you want support reviewing your sitemap, fixing indexation gaps, or aligning it with Google’s best practices, our SEO team is here to help.
Submit the form below and let us take care of it for you.
