Sitemap Checker

A sitemap is an XML file listing every URL you want search engines to crawl and index. It lives at yoursite.com/sitemap.xml and acts as a directory for crawlers, especially useful for large sites, new sites with few backlinks, or sites with deep navigation where pages sit five or more clicks from the homepage. Sitemaps do not guarantee indexing. Google still decides whether a page is worth indexing based on quality and duplication. Without a sitemap, Google relies on internal links and external backlinks to find pages, which can take weeks or even months for new content. With a sitemap, you tell Google the page exists and when it was last updated, which speeds up discovery and helps prioritize fresh content. Our sitemap checker fetches your sitemap.xml, parses the structure, validates XML syntax, checks HTTP status codes for every listed URL, flags duplicates, and detects orphan pages (pages in your sitemap but unreachable via internal links). Use it after launching a new site, after a migration, or quarterly to catch regressions.

Try three places. First, append /sitemap.xml to your domain (yourdomain.com/sitemap.xml) and see if it loads. Most CMSes generate a sitemap at this path automatically. If you see XML with a list of URLs, that is your sitemap. Second, check robots.txt at yourdomain.com/robots.txt for a line starting with Sitemap: followed by a URL. Many sites declare their sitemap location here. Third, log into Google Search Console, go to Sitemaps under Index, and see what sitemap URLs you submitted. This is the authoritative list Google uses to prioritize crawling. If you find a sitemap URL, paste it into our Sitemap URL field to validate structure, confirm all URLs return 200 status codes, and spot duplicates or orphans. If none of these methods finds a sitemap, you likely do not have one. That is fine for sites under 50 pages but a problem for larger ones. Generate one using your CMS plugin (Yoast, Rank Math, next-sitemap), then submit it to Search Console to speed up indexing.

The three types are XML sitemaps (for search engines), HTML sitemaps (for users), and visual sitemaps (for designers). XML sitemaps are machine-readable files in XML format that list URLs, last modification dates, update frequency, and priority. Search engines use them to discover and prioritize pages. They live at /sitemap.xml and are not meant for human browsing. HTML sitemaps are human-readable pages with links to every major section of your site, organized hierarchically. They help users navigate large sites and provide internal links. They live at URLs like /sitemap and are often linked from the footer. Visual sitemaps are diagrams (in Figma, Miro, Sketch) that map out page hierarchy, user flows, and navigation before a site is built. They are planning artifacts, not live pages. Most sites need an XML sitemap (required for SEO) and benefit from an HTML sitemap if over 100 pages. Visual sitemaps are for the design phase. Our checker validates XML sitemaps only. Most CMSes generate them automatically. For static sites, use next-sitemap or astro-sitemap.

Validating a sitemap means checking XML structure, URL accessibility, metadata accuracy, and protocol limits. First, confirm the XML is well-formed with proper namespace declaration (xmlns attribute pointing to sitemaps.org). Malformed XML causes parsers to reject the entire file. Second, verify every URL returns a 200 status code, not a 301, 404, or 5xx error. Search engines may still crawl redirecting or broken URLs, but they deprioritize them. Third, check that URLs use absolute paths (https://example.com/page, not /page) and match your canonical domain (www or non-www, not mixed). Fourth, confirm file size is under 50 MB uncompressed with fewer than 50,000 URLs. If you exceed either, split into multiple sitemaps and use a sitemap index file. Fifth, validate lastmod dates use W3C format (YYYY-MM-DD or ISO 8601). Our tool automates all five: paste your Sitemap URL, pick crawl depth (index only, all referenced sitemaps, or sample), and we return status codes, duplicates, missing lastmod warnings, and a CSV export of problems.

Google used to offer a sitemap generator (Google Sitemap Generator) for Apache and IIS, but it was deprecated years ago. You no longer need it. Nearly every modern CMS and static framework generates sitemaps automatically. WordPress (via Yoast SEO, Rank Math, or core sitemap since 5.5), Shopify (built-in), Webflow (built-in), Squarespace (built-in), Wix (built-in), Next.js (via next-sitemap), Astro (via astro-sitemap), Gatsby (via gatsby-plugin-sitemap), and Hugo (built-in) all create and update XML sitemaps without manual work. For custom sites, use open-source libraries like sitemap.js (Node.js), django-sitemap (Python), or a build script. Once you have a sitemap, submit it to Google Search Console under Sitemaps. Google will crawl it periodically. You can ping Google manually after adding URLs by sending a GET request to google.com/ping?sitemap=yoursitemapurl, though most CMSes do this automatically. Use our sitemap checker to validate the sitemap before submitting to Search Console.

Update your sitemap every time you publish, unpublish, or significantly edit a page. Most CMSes and static generators handle this automatically. WordPress plugins regenerate the sitemap on every post publish, Shopify updates it when products change, and static frameworks rebuild the sitemap during every deploy. If managing manually (rare on custom sites), regenerate it weekly or after content batches. The lastmod field tells search engines when a page changed, which helps them prioritize fresh content over stale. If you never update lastmod or set the same date for every URL, search engines ignore it and fall back to link discovery and crawl budget. For daily publishers (news, blogs, e-commerce with inventory changes), dynamic sitemaps that regenerate on publish are essential. For monthly or quarterly publishers, a static sitemap regenerated on deploy is fine. Do not let your sitemap list URLs that 404, redirect, or are blocked by robots.txt. That wastes crawl budget and signals poor site quality. Use our checker after major changes (migration, URL restructure, bulk content changes).

Robots.txt tells crawlers which parts of your site they are allowed or disallowed from accessing. A sitemap tells crawlers which pages you want them to prioritize crawling. They serve different purposes and work together. Robots.txt lives at yourdomain.com/robots.txt, uses plaintext syntax with User-agent, Allow, and Disallow directives, and blocks or permits access to paths, files, or directories. It declares where your sitemap lives via a Sitemap: directive. Robots.txt is crawled first. If you accidentally disallow your entire site, crawlers stop immediately and never see your sitemap. A sitemap lives at yourdomain.com/sitemap.xml, uses XML syntax, and lists URLs you want crawled with metadata like lastmod and priority. It does not control access. It suggests what to crawl. Crawlers can ignore your sitemap if they find pages via links, but they cannot bypass robots.txt. Use robots.txt to block admin panels, staging environments, and unwanted crawlers. Use a sitemap to list every indexable page.

A sitemap does not directly improve rankings, but it removes discovery friction, which indirectly helps SEO by ensuring new and updated pages get crawled faster. Without a sitemap, Google relies on internal links and external backlinks to find pages, which can take weeks for new content, especially on large sites or sites with weak internal linking. With a sitemap, you tell Google the page exists and when it was last updated, which speeds up indexing. This is important for new sites with few backlinks, sites with deep page hierarchies (pages buried five clicks from the homepage), sites with orphan pages, and sites that publish frequently (blogs, news, e-commerce). A sitemap helps with crawl budget efficiency. Instead of discovering pages via link crawling, Google reads your sitemap and knows what to prioritize. However, a sitemap cannot force Google to index low-quality, duplicate, or thin pages. If a page is in your sitemap but still not indexed, the issue is usually content quality, canonicalization, or robots meta tags.

A sitemap should only list URLs you want indexed, so exclude anything blocked by robots.txt, tagged with noindex, redirecting to another URL, returning 404 or 5xx errors, or canonicalized to a different URL. Including these wastes crawl budget and signals poor site maintenance. Do not include admin pages, login pages, checkout pages, or user account dashboards (usually blocked by robots.txt or noindex). Do not include parameter URLs (like ?sort=price or ?page=2) if you use canonical tags to consolidate them. Do not include staging or test environments. Do not include URLs that redirect (301 or 302). List the final destination instead. Do not include URLs with noindex meta tags or X-Robots-Tag headers. Do not include paginated URLs unless each page has unique content worth indexing. Most e-commerce sites should only include page 1, with rel=next/prev or canonical tags handling the rest. Do not include duplicate content URLs. Use canonical tags to consolidate duplicates, then only list the canonical version.

Sitemap errors fall into three buckets: structural (malformed XML, wrong namespace, file too large), URL-level (404s, redirects, noindex pages), and metadata issues (missing lastmod, incorrect date formats). Fix structural errors first. They prevent crawlers from parsing the file. Open your sitemap in a browser or XML validator, confirm it starts with the correct XML declaration and namespace (xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"), and check that every opening tag has a matching closing tag. If your sitemap exceeds 50 MB or 50,000 URLs, split it into multiple files and create a sitemap index file. Fix URL-level errors by removing or replacing broken entries. Delete any URL that returns 404, replace redirecting URLs with their final destination, remove URLs with noindex tags, and confirm every URL matches your canonical domain (www or non-www, not mixed). Fix metadata issues by ensuring lastmod dates use ISO 8601 format (YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS+00:00). Remove lastmod entirely if your CMS cannot keep it accurate. After fixing, revalidate with our tool and resubmit to Google Search Console.