OOmnistu

Blog / Web & Ecommerce

Web & Ecommerce

Sitemaps for a new blog: what to include and how to check them

Build a sitemap from published canonical URLs, keep drafts out and check discovery without mistaking submission for guaranteed indexing.

OOmnistu
Reviewed 2026-11-16 · 4 min read

A sitemap lists URLs you want search engines to discover. For a new blog, it is a useful companion to navigation and internal links, especially when few other sites link to the new articles. It is not a way to force Google to crawl, index or rank every post.

Google's sitemap overview makes that distinction explicit. A technically valid file can help discovery while an individual article still does not appear in search results.

Do small blogs need a sitemap?

Google can usually discover most pages on a well-linked site by following links. A small site with clear navigation may not strictly need a sitemap. Google's guidance nevertheless identifies new sites with few external links as a case where one can help.

Our practical recommendation is to generate one automatically when launching a blog, but not to treat it as a substitute for a usable article index. A visitor and a crawler should both be able to reach the important posts through links.

A launch with five useful articles needs a sitemap for those published URLs, not a file advertising a hundred drafts that readers cannot yet use.

Start with a publication list, not a directory scan

A sitemap generator should know which articles are actually public. If it blindly lists every file or route in a project, it may include drafts, preview pages and old duplicates.

For a straightforward blog, use an explicit publication state and a consistent URL field. Then generate the article index, category listings and sitemap from the same approved set. This is a suggested implementation pattern, not a requirement of the sitemap protocol.

Before adding a URL, check:

A sitemap is a discovery hint, not an access-control system. Omitting a private document does not protect it; keep private material behind appropriate access controls.

Use absolute canonical URLs

Google's build guide says to use fully qualified absolute URLs. A sitemap entry should include the scheme and hostname rather than only /blog/article/.

Choose one preferred version when the same content is reachable through several URLs. The sitemap, internal links and canonical element should support the same choice. Listing every tracking-parameter variation does not make the article more discoverable in a useful way.

If you are changing a site's routes, review old and new URLs separately. Updating the sitemap alone is not a migration plan.

Format, size and location

Google supports XML, RSS/Atom and text sitemap formats, with different capabilities. XML is useful when the site needs additional information or extensions. A simple text sitemap can list HTML and other indexable page URLs, one per line.

The build guide specifies these limits and rules:

Item Rule
Single sitemap size No more than 50 MB uncompressed
URLs per sitemap No more than 50,000
Encoding UTF-8
URL form Fully qualified, absolute URLs
Larger collections Split into multiple sitemaps; a sitemap index is optional

Google recommends placing a sitemap at the site root. Unless submitted through Search Console, its location limits its scope to descendants of its parent directory. Your implementation may have additional hosting considerations, so verify the generated file where it is served, not only in the source project.

For a small launch, these limits are rarely the hard part. Keeping the list accurate as articles are added, renamed or withdrawn is the more immediate maintenance task.

Make the sitemap discoverable, then inspect the result

Google documents several submission methods, including Search Console and a Sitemap: line in robots.txt. Submitting through Search Console also lets the owner inspect processing errors and when Google accessed the file.

Submission is still a hint. Do not label an article "indexed" merely because the sitemap was submitted or accepted for processing.

Our suggested launch check is:

  1. Open the served sitemap and confirm it contains the intended public URLs.
  2. Open a sample of those URLs and compare the actual page with the sitemap entry.
  3. Check that navigation and category pages link to the same preferred URLs.
  4. Submit through an authorized Search Console property, if available, and review processing feedback.
  5. Investigate page-level indexing separately when a particular article is missing.

Common questions

Should every rebuild change the update date?

No. If you supply modification information, keep it tied to a genuine relevant update. A build running again is not, by itself, proof that the article changed. Google's guide says modification information should be consistently and verifiably accurate.

Does the order of articles matter in the file?

Google says the order of URLs in a sitemap does not matter to it. Arrange your public article index for readers instead of using sitemap order as an imagined ranking control.

Can a sitemap fix weak content?

No sitemap guarantees indexing. Check that an article answers a real reader question and is useful in its own right. Discovery infrastructure and editorial quality are separate responsibilities.

By Omnistu. Reviewed against Google Search Central guidance on 16 November 2026. This article concerns Google Search, not every search engine's implementation.

Sources

Previous
Moving or redesigning a website: reducing search visibility risks