Create an XML Sitemap That Reflects the Real Website in Edina

An XML sitemap should describe the public website the business actually wants discovered.

It should not become a dump of every URL the software can generate.

Start with canonical public pages

The sitemap should focus on URLs that are:

• public;
• canonical;
• intended for discovery;
• valid;
• part of the current website.

That usually means real service pages, useful articles, location pages, and other public content the business intends to maintain.

Exclude URLs that should not be there

A sitemap generally should not list URLs that are only:

• redirects;
• error pages;
• marked noindex;
• duplicate parameter variations;
• staging or development pages;
• obsolete or retired content;
• alternate versions that are not the canonical URL.

Including a URL does not make it a good discovery target.

Keep generation tied to publishing

A sitemap is easier to trust when it updates from the same source that controls the public site.

New canonical pages can be added when published, and retired pages can disappear when they are removed or redirected.

Manual sitemap files often drift out of sync when nobody remembers to update them.

Use modification dates honestly

A last-modified value is useful only if the system can maintain it accurately.

Do not rewrite dates on every build merely to make pages look fresh.

If the publishing system cannot provide trustworthy modification dates, it is better not to manufacture them.

Verify the sitemap itself

The file should be reachable, valid, and parseable.

Review the generated URLs and make sure they resolve to the intended public pages.

A sitemap can be technically valid while still containing the wrong URLs.

Submitting or exposing a sitemap does not guarantee indexing or rankings.

Compare the sitemap with the site structure

A sitemap audit should compare the listed URLs with the site's actual public content inventory.

If a canonical service page exists but is missing, that deserves investigation.

If the sitemap contains retired URLs, duplicates, or paths that only exist because of old software behavior, remove them at the generation source.

This comparison is especially useful after migrations and redesigns, when old and new URL structures can coexist temporarily and automated sitemap generation may still reflect outdated rules.

A sitemap should be reviewed again whenever the site's URL rules change materially.

That review should include newly published pages as well as URLs that have been retired.

For a related next step, see Why a Business Website Does Not Appear in Google Search in Downing and Fix Important Website Pages That Are Not Being Indexed in Kahoka.

For authoritative guidance on this subject, see Google's SEO Starter Guide.

See Also

• Improve Search Visibility After a Website Redesign in Wayland

Switchboard can help Edina and Northeast Missouri businesses generate and maintain XML sitemaps that reflect the real public website instead of every technically reachable URL.