An XML sitemap is a structured file listing a site's URLs along with optional metadata (last modified date, priority, change frequency) to help search engines discover and index content efficiently, particularly useful for large sites, new sites, or pages not well-linked internally.
Quick Answer
An XML sitemap is a structured file listing a site's URLs along with optional metadata (last modified date, priority, change frequency) to help search engines discover and index content efficiently, particularly useful for large sites, new sites, or pages not well-linked internally.
How XML Sitemap Works
An XML sitemap is a file in XML format that lists all the URLs on your website you want search engines to crawl and index, along with optional metadata about each URL. Submitted through Google Search Console and Bing Webmaster Tools, a well-maintained sitemap ensures your most important pages are discoverable without relying solely on crawling your internal link structure.
Why XML Sitemap Matters for B2B Marketing
For most websites under 500 pages with strong internal linking, an XML sitemap is not strictly necessary, Google can discover all pages via crawl. However, sitemaps become critical in several scenarios: (1) new sites with few external backlinks that crawlers might not discover otherwise, (2) large sites where new content should be indexed quickly, (3) sites with content that isn\'t well-linked internally (e.g., a news site where articles are only linked from date-based archive pages), and (4) sites with rich media content (video, images) that benefit from separate media sitemaps.
XML Sitemap: Best Practices & Strategic Application
A well-structured XML sitemap should include: all canonical URLs (never include pages you don\'t want indexed), no URLs that return non-200 status codes or have noindex tags, and last-modified dates that are accurate (inaccurate lastmod dates are ignored by Google). For large sites, sitemaps should be split by content type (pages sitemap, posts sitemap, video sitemap) and referenced in a sitemap index file.
Agency Perspective: XML Sitemap in Practice
Submit your sitemap to Google Search Console (Settings > Sitemaps) and to Bing Webmaster Tools. After submission, monitor the "Submitted" vs. "Indexed" count disparity, a large gap between submitted and indexed URLs is a signal of indexing issues (thin content, canonical problems, noindex tags, or low authority pages that Google has deprioritized).
Frequently Asked Questions: XML Sitemap
An XML sitemap is a structured file listing a site's URLs along with optional metadata (last modified date, priority, change frequency) to help search engines discover and index content efficiently, particularly useful for large sites, new sites, or pages not well-linked internally.
Your CMS should generate and update the sitemap dynamically whenever content is published or updated. For WordPress sites, plugins like Yoast SEO, RankMath, or All in One SEO manage this automatically. For manually maintained sitemaps, update them whenever you add, remove, or substantially update pages. After major updates, ping Google and Bing by resubmitting the sitemap URL in Search Console and Webmaster Tools to accelerate re-crawling.
No, only include URLs you want indexed. Exclude: pages with noindex tags, redirected URLs, duplicate content pages, utility pages (login, checkout, search results), and low-quality thin pages. Including poor-quality URLs in your sitemap wastes crawl budget and can signal to Google that your site has a high proportion of low-quality content. A sitemap with 200 high-quality pages is better than one with 2,000 pages including thin or duplicate content.
MV3 Marketing helps B2B companies apply these strategies to drive measurable pipeline growth. Our team executes technical seo audit for technology, SaaS, and professional services companies.
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
