SEO

Sitemaps for small business websites: what to include and check

Understand how a sitemap helps discovery, choose suitable URLs and check it after important site changes.

By Graphic Core   /   Published
Monthly guide series: August 2021

Blank cards arranged as a branching tree and connected with thread.

What a sitemap can and cannot do

A sitemap is a machine-readable list of URLs you want search engines to discover and consider. It can help communicate the preferred addresses for useful public pages, particularly when a site changes or some content is less easy to find. It does not replace navigation, internal links, accurate content or a functioning website.

Submitting a sitemap is a hint, not a guarantee that a search engine will fetch, index or rank every URL. A small site with well-connected pages may already be discoverable without a separate submission. Use the file as one part of a clear site structure and review what happens after major changes.

Choose pages you want people to find

Start with the intended final addresses for the homepage, relevant services, useful location pages and articles you want search engines to consider. Each included page should load successfully, provide a clear purpose and be available to the intended audience. Review whether an almost identical page adds distinct value before treating it as a separate priority.

Avoid listing staging URLs, private account pages, deleted pages, redirect aliases or pages intentionally marked noindex as though they were preferred search destinations. A page’s inclusion does not make it canonical by itself; keep your sitemap, internal links and canonical signals consistent with the page you actually want people to use.

Let the platform generate the file

Many content management systems and SEO tools can generate a sitemap automatically. Identify the system responsible before installing another extension, since several overlapping generators can create confusion. Ask who maintains the settings, which content types are included and whether the file updates when pages are added, removed or changed.

A static website may need a build process that writes the sitemap from its actual public pages. Check that the file uses the correct production domain and secure protocol. It is more reliable to generate from maintained page data than to paste a list once and forget it after the site changes.

AT A GLANCE

Sitemap review route

  1. SelectChoose useful public URLs
  2. GenerateUse a maintained source
  3. CheckTest a representative sample
  4. MonitorReview reports after changes
A sitemap supports discovery but does not guarantee indexing.

Check addresses and responses

Open the sitemap and sample URLs from different sections of the site. They should lead directly to the intended final pages rather than through avoidable redirects. Check that an included page is not blocked by a login, an unintended noindex instruction or a server error. Review unusual parameters and duplicated variations with the person responsible for the site.

The order of URLs does not determine their importance in Google Search. A last-modified date should represent a meaningful change when used, not be refreshed automatically to suggest that unchanged content is new. Do not alter publication dates simply because you want a page to appear more recent.

Submit and use the report

If you use Google Search Console, verify the relevant property and submit the sitemap address using its Sitemaps report. You can also identify a sitemap in the site’s robots.txt file. Follow Google’s current instructions and ensure you have appropriate access before changing settings. Keep the sitemap itself publicly accessible if it is intended for public search engines.

A successful submission indicates that the file was processed or received; it is not proof that every page is indexed. Review reported errors, inspect a representative page and give changes time to be discovered. If a page remains absent, investigate its status and usefulness rather than repeatedly submitting the same file.

An illustrative review

Imagine a small Hertfordshire business replaces two service pages with one more useful page. Its sitemap should point to the final page, while appropriate redirects guide visitors from the old addresses. The owner checks that the new page is accessible and that internal navigation uses the final URL.

A team member also finds a private staging path listed in an older sitemap and removes it from the generated set while reviewing access controls. This example is illustrative, not a client case. The right decisions depend on the actual website, the destinations available and how its pages are maintained.

Use the sitemap alongside ordinary links

A page listed in a file can still be difficult for a visitor to discover if nothing on the site links to it. Check that important services are reachable from navigation or another relevant page and that articles connect to genuinely useful next steps. A directory can help people browse coverage, but it should not imply services or offices that do not exist.

If the site has many similar local pages, review their content and purpose individually. A sitemap does not make pages valuable or ensure they will be selected by a search engine. Keep the list aligned with the pages you are willing and able to maintain.

When a report shows a problem

If a sitemap report flags an address, open the precise URL and record what happens: does it return an error, redirect, require a login or point to a different domain? Check the generator configuration before editing the file by hand, since an automatic build may overwrite manual corrections.

Fix the underlying page or generation rule, rebuild if needed and then review the report again after it has had time to refresh. Keep the original error and resolution in a small change log. Submitting the file repeatedly without addressing the cause does not improve the page itself.

When the site has several content types, sample a service, an article and a location page separately. Confirm that the listed address is the one used by the site itself and that it does not first send visitors through an unnecessary chain. If a team member adds pages through a visual editor, ask whether those pages are included automatically. The answer can differ between a published page and a draft or private page, so verify the actual output.

Keep the file in step with the site

Review the sitemap after a redesign, domain change, content retirement or a change to indexing rules. Assign an owner for checking automated output and dealing with reported errors. A brief periodic sample is often enough to catch a generator pointing at an old domain or including unintended routes.

For each sample, ask: is the page genuinely useful, public, accessible, indexable and the preferred final version? Does it receive a sensible internal link? If the answer is unclear, resolve the page’s purpose before relying on the sitemap. Good discovery starts with pages people can find and use.

YOUR NEXT MOVE / 01

Ready to make
more of your business?

Tell us about your website, your services and where you want to grow.

START A CONVERSATION