An Extensible Markup Language (XML) sitemap gives search engines a structured list of the pages and files you want them to discover. For local search engine optimisation (SEO), that may include service pages, location pages, useful articles, images and videos.
We use an XML sitemap as a discovery and diagnostic tool. It can help Google and Bing find preferred Uniform Resource Locators (URLs), but it cannot force crawling, indexing or rankings. Google states that sitemap submission is only a hint.
The process still works heading into 2027. We now place more weight on clean canonical URLs, accurate update dates and clear measurement after submission.
Key Takeaways
- Use the XML sitemap for discovery. It gives search engines a direct list of preferred URLs. Google’s sitemap overview confirms that a sitemap does not guarantee crawling or indexing.
- List only pages you want eligible for search. We normally include canonical, indexable URLs that return a successful response. Redirects, broken pages and duplicate variants should stay out.
- Keep last modified data accurate. Google can use the value when it reflects a real page change. Google ignores priority and change frequency values.
- Check the website platform first. Many content management systems already create sitemaps automatically. We audit the existing output before adding another tool.
- Use Search Console to diagnose indexing patterns. Google’s Page indexing report can show repeated issues across submitted URL groups. We use those patterns to guide the next check.
- Keep sitemap work separate from local ranking work. Google’s local ranking guidance says local results mainly depend on relevance, distance and popularity. A sitemap can support discovery, but it cannot replace those signals.
What Is an XML Sitemap?
An XML sitemap is a machine-readable file that lists URLs a site owner wants search engines to know about. It can also carry information about page updates, images, videos, news content and alternate language versions. Google’s sitemap overview explains these supported uses.
Search engines can still discover pages through crawlable links. Google says sitemaps are especially useful for large sites, new sites with few external links and sites with substantial image, video or news content. A small site of about 500 pages or fewer may not need one when every important page is easy to reach through links.
For local businesses, the sitemap becomes more useful as the site grows. A clinic group may have branch pages, treatment pages and local guides. Our internal linking strategy guide explains how contextual links can support those same pages.
What an XML Sitemap Can and Cannot Do
The sitemap has a clear technical role. It supports discovery and reporting, but it does not turn weak pages into strong search results.
| An XML Sitemap Can | An XML Sitemap Cannot |
| Help search engines discover preferred URLs | Guarantee that every URL will be indexed |
| Supply accurate last modified information | Give a page an automatic ranking increase |
| Support image, video and news discovery | Replace internal links or site structure |
| Group URLs for indexing checks | Fix thin or duplicate location pages |
| Give search engines a stable discovery source | Force a page into local map results |
Google identifies relevance, distance and popularity as the main local ranking factors. We therefore treat sitemap work as one technical input. Local page quality and business signals still need separate attention.
Types of XML Sitemaps
Different sitemap formats serve different discovery and user-access needs. A Hypertext Markup Language (HTML) sitemap is not an XML file, but businesses often compare it with XML sitemaps because both can help people or crawlers find content.
1. Standard XML Sitemap
A standard XML sitemap lists the preferred URLs you want search engines to discover. For most local businesses, this is the main sitemap.
Typical entries include
- Service pages that answer real customer needs
- Unique location pages for branches or service areas
- Useful articles and evergreen guides
- Product or category pages with search value
- Important conversion pages intended for organic search
Each entry needs a location value. Google’s XML sitemap guidance also requires fully qualified absolute URLs.
2. HTML Sitemap
An HTML sitemap gives visitors another route to important site sections. It can help when menus or category pages do not make every page easy to find.
We would keep one only when it improves user access. It does not replace the XML sitemap. Better internal linking may solve the same problem on a smaller site.
3. Video Sitemap
A video sitemap gives Google extra information about videos on website pages. Google’s video sitemap documentation says video sitemap data can help it find and understand videos that normal crawling may miss.
It can suit property tours, service demonstrations, product walkthroughs and location videos. We would add one only when video supports a clear search goal.
4. Image Sitemap
An image sitemap can help Google discover images that normal crawling may miss. This can help restaurants, retailers, property firms and image-led businesses. Google’s image sitemap documentation explains the supported image fields.
Google no longer supports several former image sitemap tags, including caption, geographic location, title and licence. We would focus on crawlable image URLs and useful page context instead.
5. News Sitemap
A news sitemap serves eligible news publishers. Google’s news sitemap documentation says news-specific entries should cover recent articles from the previous two days.
Most local businesses do not need one for ordinary company announcements or standard blog posts. We would keep those URLs in the normal XML sitemap.
How to Pick the Right Sitemap for Local SEO
Most local businesses need only a standard XML sitemap. We add another format only when it solves a clear discovery or user-access problem.
Use this quick guide
- Standard XML sitemap for canonical pages you want search engines to discover
- HTML sitemap when users need another route through a large site
- Image sitemap when image discovery supports customer research
- Video sitemap when video is a meaningful search asset
- News sitemap only for eligible news publishers
For a multi-location business, we first check the quality of each location page. Repeated copy with only a place name changed creates more URLs without creating stronger local content.
Best Practices for XML Sitemaps in SEO
A useful XML sitemap should match the pages we want search engines to process. We focus on URL quality, technical consistency and clear reporting.
Include Only Canonical URLs
A canonical URL is the preferred version of a page when several URLs contain the same or very similar content. Google’s canonical URL guidance describes sitemap inclusion as a canonicalisation signal. It also warns against conflicting signals.
We normally remove
- Tracking variants
- Redirected URLs
- Duplicate parameter URLs
- Non-canonical filter pages
- Old protocol or hostname versions
Only the preferred version belongs in the sitemap. On larger sites, our crawl budget optimisation guide explains how duplicate patterns and sitemap clutter can make crawl analysis harder.
Keep the Sitemap Current
Add new eligible pages when they go live. Remove URLs that no longer belong.
Branch openings, closures, retired services and expired campaigns deserve regular review. A dynamic sitemap can handle routine changes, but we still audit it after migrations and large content cleanups.
Use Last Modified Dates Properly
Google says it uses the last modified value when it is consistently and verifiably accurate. The value should reflect a significant page update. Its current sitemap guidance cites main content, structured data and page links as examples.
Good reasons to update the date include
- A substantial rewrite of the main content
- An important service or product update
- A meaningful structured data change
- Significant changes to useful links
Do not refresh every date because the sitemap regenerated. Google says a copyright date change does not count as a significant page update.
Stop Using Priority and Change Frequency as Search Controls
Older sitemap guides often tell site owners to assign high priority values to important pages. Google’s XML sitemap documentation says it ignores both priority and change frequency values.
We put that effort into cleaner canonical URLs, useful content and stronger internal links. Important pages should receive stronger support through the site structure and page quality.
Respect Sitemap Size Limits
Google limits one sitemap to 50,000 URLs or 50 megabytes uncompressed. Larger sites should split URLs across several files and can group them with a sitemap index.
Segmentation can also improve reporting by page type. Include it especially when several site sections have separate owners.
Keep Low-Value URLs Out
A sitemap should contain pages that support the site’s indexing plan. Low-value URLs make the file harder to review.
We would normally exclude
- Redirects and 404 URLs
- Pages marked noindex
- Duplicate filter and parameter URLs
- Internal search results
- Login, account and staging pages
- Thin pages with no clear search purpose
Google’s Page indexing report lists several reasons pages can remain outside the index, including redirects, duplicate pages and noindex rules. We use those categories to group problems after sitemap submission.
For larger sites, our crawl budget optimisation guide covers sitemap pruning and other sources of crawl waste. We would not apply large-site crawl tactics to a small local website without evidence of a crawl problem.
Check Public URLs for Singapore Data Protection Risks
XML sitemaps are usually public files, so their URL paths can be easy to inspect. Singapore’s Personal Data Protection Act obligations require organisations to make reasonable security arrangements for personal data in their possession or under their control.
During an audit, we would flag public URLs that expose customer names, account identifiers or private document references. This is a website governance check, not a sitemap-specific legal rule.
Keep AI Search Expectations Practical
Artificial intelligence (AI) search does not require a special XML sitemap. Google’s AI features guidance says standard search requirements still apply to AI Overviews and AI Mode.
We would keep the sitemap focused on clean discovery and indexing signals. For generative engine optimisation, clear page structure, useful content and crawlable internal links still deserve more attention than unsupported sitemap additions.
Steps to Create an XML Sitemap for Local SEO
A sound sitemap workflow starts with the file the website already has. This avoids duplicate generators and keeps the work focused on real indexing problems.
Step 1. Check the Existing Sitemap
Start with the content management system, website platform and robots.txt file. Google’s sitemap overview notes that many platforms already generate sitemaps.
Check the current file before building anything new. If it is valid and aligned with the site’s canonical URLs, the task may only need an audit and cleanup.
Step 2. Select the URLs to Include
Choose pages you genuinely want eligible for organic search. For a local business, that often includes services, branch pages, useful articles and commercial pages with a clear search purpose.
Check each URL for
- A successful response
- Indexable status
- The correct canonical URL
- Useful page content
- Internal links from relevant pages
Remove redirects, broken URLs, duplicate variants and noindex pages. A sitemap cannot fix a weak location page simply by listing it.
Step 3. Generate or Configure the Sitemap
Use the site’s built-in sitemap feature when it gives enough control. Google’s ” Build and submit a sitemap” guide says a content management system can often create the file automatically. Larger sites can also generate sitemaps from their own site data.
Google requires UTF-8 encoding and fully qualified absolute URLs. Keep the preferred protocol and hostname consistent across every entry.
Step 4. Validate the Sitemap
Check that the file loads, uses the correct format and remains accessible to search engines. Then inspect the URLs inside it, not only the XML syntax. Review the following:
- URL format and response codes
- Canonical targets and indexability
- Redirect chains and obsolete pages
- Last modified values where used
A site crawl can reveal URLs that are technically valid but still do not belong in the sitemap. Use it to compare the live site with the submitted URL set.
Step 5. Submit the Sitemap Through Google Search Console
Submit the sitemap through Google’s Sitemaps report. The report shows the last read date, errors and discovered page counts.
Submission is still only a hint. If important URLs remain outside the index, check the page, canonical settings, internal links and content quality.
Step 6. Add the Sitemap to Robots.txt and Submit to Bing
Google can discover a sitemap from a Sitemap line in robots.txt. Bing can also use sitemaps, while IndexNow can notify participating search engines when URLs are added, updated or deleted.
We use the XML sitemap for broad URL coverage. IndexNow handles faster change notices on supported engines.
Step 7. Monitor Indexing and Act on Patterns
Use Google’s Page indexing report to compare submitted page groups with indexed pages. Look for patterns across URL types instead of checking every page in isolation.
Useful checks include:
- Location pages discovered but not indexed
- Old URLs still present after a migration
- Important pages missing from the sitemap
- Redirects still listed in the file
- Groups affected by noindex or access rules
If one page type repeatedly fails, fix the shared template, content or linking problem. Do not treat the sitemap as the cause without evidence.
How We Measure XML Sitemap Performance
A sitemap audit should show if the file represents the URLs we want search engines to know about. It should also show what happened after discovery.
| Check | What We Review | Action |
| Sitemap status | Successful fetch and no parsing errors | Fix access or format problems first |
| Submitted URLs | Canonical, indexable pages only | Remove redirects, errors and noindex pages |
| Indexed URLs | Important page groups entering the index | Inspect repeated exclusions by page type |
| Last modified data | Dates tied to real page changes | Fix systems that refresh dates without content changes |
| Internal support | Important URLs linked from relevant pages | Add useful contextual links to isolated pages |
For larger sites, our crawl budget optimisation guide gives a deeper process for reviewing crawl activity and sitemap waste. For smaller Singapore businesses, keep the sitemap accurate and fix repeated indexing problems that affect service or location pages.
Common XML Sitemap Mistakes to Avoid
The most useful sitemap checks focus on problems we can confirm through a crawl or search engine report. We prioritise URL conflicts, stale entries and signals that do not match the site’s indexing plan.
- Including duplicate or non-canonical URLs. Keep one preferred version of each page. Tracking variants and duplicate parameters make the file harder to audit.
- Leaving broken or redirected URLs in the file. Point the sitemap directly to the live destination. Clean it after migrations, branch closures and URL changes.
- Keeping noindex pages in the sitemap. A page marked noindex should not normally sit in a file that represents pages you want in search. Review the rule first.
- Faking freshness. Do not reset every last modified value when the sitemap regenerates. Keep the previous date when the page itself has not changed.
- Treating sitemap submission as a local ranking boost. Google’s local ranking guidance says local results mainly use relevance, distance and popularity. A sitemap helps with discovery, not local ranking placement.
- Relying on the sitemap instead of internal links. A sitemap lists a page, but it doesn’t show search engines why the page matters.
- Leaving low-value URLs in large sitemaps. Parameter, archive and duplicate URLs bury the pages you want crawled and make indexing reports harder to read.
Build Your XML Sitemap to Support Local Visibility
An XML sitemap remains useful for local businesses heading into 2027, but its role is specific. We use it to support discovery, keep preferred URLs organised and make indexing problems easier to diagnose.
For most Singapore businesses, keep the sitemap your website platform already generates. Remove conflicting URLs, use accurate last modified values and review the result in Google Search Console and Bing Webmaster Tools.
If the site has many branches, products or content groups, split sitemaps when that improves reporting. Pair the file with strong internal links and useful local pages because discovery is only the first stage of search visibility.
Businesses that need help with indexing, technical SEO or local visibility can talk to us about local SEO for Singapore businesses. We audit the sitemap as part of the wider site and prioritise changes that deliver clear search and business value.
Frequently Asked Questions
Should I submit my XML sitemap to Google and Bing?
Yes. Submission gives search engines a direct route to the sitemap and gives site owners reporting tools. It still does not guarantee that every listed URL will be crawled or indexed.
What pages should be included in an XML sitemap?
Include canonical, indexable pages that you genuinely want eligible for search. For a local business, that often means service pages, useful location pages, strong articles and selected commercial pages.
Can XML sitemaps include images and videos?
Yes. Google supports image and video sitemap extensions that can supply extra discovery information. We would use them when those media assets support a clear search goal.
How big can an XML sitemap be?
Google limits one sitemap to 50,000 URLs or 50 megabytes uncompressed. Larger sites can split URLs across several files and group them through a sitemap index.
Does having an XML sitemap guarantee higher rankings?
No. Google’s sitemap overview says a sitemap can help with URL discovery but does not guarantee crawling or indexing. Local rankings also depend on signals outside the sitemap.
How often should I update an XML sitemap?
Update the sitemap when eligible URLs are added, removed or materially changed. A dynamic sitemap can handle routine changes, but audit the file after migrations and major content updates.
