Check the sitemap on a small business website

Understand the limited job of a sitemap

Google describes a sitemap as a file providing information about pages and other content. It can help discovery, particularly for a new site with few external links, but it does not guarantee crawling or indexing. A small site with thorough internal links may not need one for discovery.

Find the existing file before adding a plugin

Check your website builder's settings or ask the person who built the site for its sitemap address. Common addresses include /sitemap.xml and /sitemap_index.xml, but your platform may use something else. Open the actual address supplied by the platform rather than assuming a filename exists.

An index may link to several smaller sitemap files, such as pages and posts. Follow those links and inspect the listed URLs. You do not need to understand every XML tag to notice an old domain, a staging hostname, a broken page, or a service that was never published.

Use a keep-or-remove worksheet

Create columns for URL, purpose, public search destination, and action. Your main service page is usually a keep. A private client document is not a search destination. An old service URL that redirects belongs on your redirect inventory rather than your preferred public-page list. A duplicate tracking URL should not become a separate content priority.

Google's build guidance recommends complete URLs and the preferred canonical versions. It ignores priority and changefreq values; lastmod should reflect a significant, genuine update. That means a daily timestamp change is not a substitute for maintaining useful content.

Submit and diagnose the file

In the verified Search Console property for your website, open the Sitemaps report and submit the actual sitemap address. If your platform already manages submission, avoid creating a competing file without a reason. Save the address in your website handover notes so the next editor knows which file is authoritative.

If the report cannot fetch or parse it, open the sitemap in a signed-out browser. Check whether it requires a login, redirects unexpectedly, or returns a normal webpage rather than a sitemap. Share the exact address and reported error with the platform's support team or your developer. Guessing at the XML is usually slower than identifying the failing response.

Keep pages connected through navigation

A sitemap is not the place customers browse your offer. Our recommendation is to keep every priority service reachable from sensible menus or relevant pages as well. If the only record of a service is inside a technical file, fix the customer path too.

After a redesign or service change, check the sitemap again. For a five-page business site, a short manual review may be sufficient: open each listed page, confirm it is current, and compare it with your navigation. Investigate missing priority URLs and obsolete inclusions, while remembering that the file's job is to communicate your intended pages, not to force search placement.