A website manager reviews a list of page addresses

When to Update Your Law Firm’s XML Sitemap

Uncategorized

A solo lawyer publishes a new practice-area page, links to it from the site menu, and can open it without trouble. But the page is missing from the XML sitemap. Search engines may still find it through that menu link; the missing entry simply removes another way for crawlers to discover it. If your firm adds services, attorney profiles, or client guides over time, check the sitemap when those changes go live.

What an XML sitemap actually does

An XML sitemap is a machine-readable file listing URLs you want search engines to consider crawling. It often sits at /sitemap.xml, though a site may use another address or several sitemap files. Visitors normally find their way through menus and internal links, not the sitemap.

The file is especially useful for a new or reorganized site, or for pages that are hard to reach through links. It can also report when individual pages last changed. But a sitemap is a hint, not an instruction: listing a URL does not guarantee that a search engine will crawl it, index it, rank it, or show it in results.

Say a solo lawyer publishes a page about a flat-fee estate-planning service. A clear navigation link helps clients and crawlers reach it; a correct sitemap gives crawlers another route. Neither makes up for a page that fails to load, cannot be indexed, or does not answer clients’ questions.

A website manager reviews a list of page addresses

What goes into the file

Each entry identifies a URL, usually inside a <loc> element. An optional <lastmod> value can show when that page was last meaningfully changed. XML sitemaps support specialized information for certain types of content, but a small law firm usually needs a straightforward list of its public pages and articles.

The question is not just whether a page is published, but whether it belongs in the sitemap. A public attorney bio or substantive FAQ may belong there. A private client portal, internal search-results page, duplicate tracking URL, or temporary preview generally does not. List the preferred, working version of each page rather than every address the site can produce.

What a sitemap cannot fix

A sitemap cannot replace a sensible site structure. If a family-law service page has no link from the practice-area menu or another relevant page, clients may struggle to find it even when it appears in the XML file. A sitemap entry also cannot override a noindex directive.

Check the listed URLs themselves. A page that redirects elsewhere, returns a 404 error, requires a login, or names a different URL as its canonical version sends mixed signals. Search engines may sort some of that out, but the sitemap should clearly identify the address the firm considers primary.

That matters during a redesign. If /services/business-formation/ moves to /business-formation-lawyer/, put the new preferred address in the sitemap and arrange an appropriate redirect from the old one. Listing both addresses does not complete the move.

When to update your XML sitemap

Many content-management systems and SEO plugins generate sitemaps automatically. In that case, updating the sitemap usually means checking the result after publication, not editing XML yourself. A manually maintained file needs attention whenever the set of preferred public URLs changes.

  • After publishing a substantial new page: Check that a new practice area, location page, attorney profile, or client resource appears once it is public and intended for search.
  • After removing or consolidating pages: Remove obsolete URLs. If an old page has a useful replacement, handle the redirect separately.
  • After changing a URL: List the new preferred address, not the old one or both by default.
  • After changing indexability: Exclude a page you have made private or marked noindex. If a previously hidden page becomes public and indexable, check whether it belongs in the sitemap.
  • After a migration or redesign: Compare the sitemap with the new domain, URL structure, and published pages. A copied file can quietly retain old addresses.
  • After a meaningful page revision: Update its last-modified date if your setup can do so accurately. A rewritten service description or an update to a filing guide qualifies; a changed comma or site-wide footer usually does not.

There is no need to resubmit an automatically generated sitemap after every small edit if search engines already know where to find it. What matters is whether the file reflects the current site. For a modest practice website, check it after major publishing or structural work and periodically as part of routine maintenance, rather than refreshing it on a fixed daily schedule.

Use the last-modified date honestly

The <lastmod> field describes a change to an individual URL, not the day the sitemap was rebuilt. If software stamps every page with today’s date on each rebuild, the field stops being useful. Search engines may disregard dates that do not correspond to meaningful changes.

If a lawyer updates a guide to reflect a revised filing process, marking that guide as modified makes sense. Changing an office phone number in a shared footer does not mean every guide was substantively revised. If accurate per-page dates are unavailable, leave out <lastmod> rather than supply unreliable ones.

A page checklist beside a laptop during website maintenance

A practical check for a small law practice

You do not need to be fluent in XML. Open the sitemap in a browser and compare its entries with the public pages you expect to see. Some sites use a sitemap index that points to separate files for pages, posts, or categories; if yours does, open the relevant file.

  1. Find the current sitemap address. Check your website settings or ask whoever maintains the site. A familiar file name does not prove the file is current.
  2. Look for important URLs. Spot-check the homepage, core services, attorney profiles, and recent resources. Each should appear at its preferred public address.
  3. Look for URLs that should not be there. Watch for previews, test pages, private areas, outdated services, and duplicate addresses with tracking parameters.
  4. Open a few listed pages. They should load without a login or a chain of redirects. Check that pages intended for search are not marked noindex.
  5. Check dates if present. Compare a recently revised page with its <lastmod> value. If every entry shows today’s date despite no corresponding edits, ask how the dates are generated.
  6. Check search-console reporting. If you use a search engine’s webmaster tools, confirm that it can fetch the submitted sitemap and review any errors. A successful fetch does not mean every listed page was indexed.

A short page inventory can make the comparison easier. Record each URL, its purpose, whether it should appear in search, and whether it is in the sitemap. This helps when a firm has similar service or office-location pages: you can decide which are genuinely distinct before asking a developer to change the file.

Common situations that need different responses

The page is live but absent from the sitemap

First, confirm that the page is meant to be public and indexable. Then see whether the sitemap generator excludes that type of page, or whether the page is still a draft, password-protected, or marked noindex. If the omission is accidental, correct the setting or add the URL to a manually maintained sitemap. Give the page an appropriate internal link, too, so clients can find it.

The sitemap lists a deleted page

Remove the URL or correct the publishing setting that keeps adding it. Separately, decide what should happen when someone visits the old address. A relevant successor may call for a redirect; if there is no replacement, a not-found response may be appropriate. Leaving the dead URL in the sitemap does not preserve its value.

The sitemap lists pages the firm does not want indexed

Remove them, but do not mistake sitemap removal for privacy protection. Search engines may discover an omitted URL through links or other sources. Client information and confidential documents need proper access controls; pages intentionally excluded from search may also need suitable indexing directives. Check with your website administrator before changing settings on a client-facing portal.

A search engine reports a URL as not indexed

Do not assume the sitemap is broken. Check that the page is accessible, indexable, and identified as the preferred URL. Then look at whether it offers distinct, helpful information and has sensible links from the site. A search engine can choose not to index a valid sitemap URL; repeatedly resubmitting the same file is unlikely to fix an underlying page problem.

Who should maintain it?

It depends on how the website is run. On a managed platform, the firm owner may only need to check the results after publishing. On a custom site, a developer may maintain the generator or XML file. If a freelancer uploads articles, agree in advance whether their work includes checking that new pages are public, indexable, and listed.

A practical division of work is for the lawyer to approve publication and confirm that service and location pages remain accurate, while the website manager handles URL settings, redirects, and sitemap generation. For substantive legal-service descriptions, check current law and applicable professional rules in your jurisdiction. This website-maintenance guidance does not replace individualized legal or tax advice from a qualified professional.

Before signing off on a site change, ask for the sitemap address and spot-check the affected URL. If an office-location page was renamed, open its new address, test the redirect from the old one, and confirm that the sitemap lists the new address instead.