Guide : Sitemaps

TL;DR — A sitemap is a fichier que listes lune pages on votre site so search engines peut trouver les. It helps Google and Bing découvrir votre content — but it doesn’t force les to index it. La plupart sites devrait have un (it’s cheap insurance), it devrait be generated automatically so it stays current, and vous submit it in Recherche Google Console and Bing Webmaster Outils.

Ce que a sitemap is

A sitemap is a fichier où vous liste l’URLs on votre site — and parfois votre images and videos — so moteur de recherches have a tidy inventory to fonctionner from à la place of having to découvrir everything by suivant liens. Google’s propre definition: “A sitemap is a fichier où vous provide information à propos de lune pages, videos, and autre fichiers on votre site, and the relationships entre les.” Evidence for this claim A sitemap supplies search engines with information about pages, videos, and other files on a site and their relationships. Scope: Google's general definition of sitemaps; supported formats and extensions have additional requirements. Confidence: high · Verified: 2026-07-14 Google Search Central: Learn about sitemaps

The la plupart courant kind is an XML sitemap, qui is written pour robots d’exploration plutôt que personnes. There’s aussi an HTML sitemap, qui is une page of liens meant pour human visitors. Ils solve différent problems.

Do vous en réalité besoin un?

Si votre site is petit (think a few hundred pages) and everything is bien lié from votre navigation, moteur de recherches peut usually trouver it tout on leur propre — Google dit vous may pas strictly besoin a sitemap in que cas. But it’s so cheap to have un que I’d generate un anyway. John Mueller put it bien: a sitemap fichier is “a minimal baseline for any serious website.” So my rule of thumb is simple: toujours have un, and let votre CMS or framework generate it automatically.

Vous surtout vouloir un si votre site is grand, brand nouveau with few liens pointing at it, or heavy on images, video, or news content.

The chose to comprendre up front

A sitemap helps discovery — it ne fait pas guarantee indexation. Putting une URL in votre sitemap doesn’t force Google to explorer it, and it definitely doesn’t force Google to index or rank it. Google dit it plainly: “A sitemap helps search engines découvrir URLs on votre site, but it doesn’t guarantee que tout the items in votre sitemap va be crawled and indexé.” Think of it as a utile liste, pas a magic “index me” button. Evidence for this claim A sitemap helps search engines discover URLs but does not guarantee that Google will crawl or index them. Scope: Google Search sitemap discovery; inclusion is not an indexing or ranking directive. Confidence: high · Verified: 2026-07-14 Google Search Central: Learn about sitemaps

How to trouver a site’s sitemap

La plupart sitemaps live at a predictable spot. Essayer:

• yoursite.com/sitemap.xml (the la plupart courant par défaut).
• Votre robots.txt fichier (yoursite.com/robots.txt) — sites souvent liste the sitemap là with a Sitemap: line.
• Recherche Google Console (votre propre site) sous the Sitemaps report.

Un chose worth knowing: pas every site advertises its sitemap. Some deliberately garder it out of robots.txt and submit it seulement à l’intérieur Search Console and Bing Webmaster Outils, so competitors can’t grab a clean liste of every URL ils publish. So “I can’t find it at the usual spot” doesn’t mean a site has aucun sitemap.

How to faire and submit un

La plupart platforms faire un pour vous automatically — WordPress, Shopify, Wix, Squarespace, and Webflow tout generate a sitemap out of the box (voir the Cheat Sheets tab pour the chemin on chaque un). Une fois vous have it:

1. Assurez-vous it listes seulement l’URLs vous en réalité vouloir indexé.
2. Submit it in Recherche Google Console and Bing Webmaster Outils.
3. Ajouter a Sitemap: line to votre robots.txt (unless you’re deliberately keeping it private).

Vouloir the complet version — the size limites, the tags Google ignores, how to trouver a site that’s hiding its sitemap, and the différent types? Switch to the Avancé tab.

TL;DR — A sitemap is a fichier listing votre URLs (and optionally images/videos) so engines peut découvrir les — a coverage and diagnostic outil, pas a discovery silver bullet, parce que submitting jamais guarantees exploration or indexation. A unique sitemap caps at 50 000 URLs or 50MB uncompressed (gzip is allowed; the cap is the uncompressed size); UTF-8; fully-qualified absolute URLs; entity-escape &, ', ", <, >. Google ignores <priority> and <changefreq> and seulement uses <lastmod> si it’s consistently accurate. Submit via Search Console, Bing Webmaster Outils, and the robots.txt Sitemap: line — the old ping endpoint has 404’d since Jan 2024, and IndexNow notifies Bing and others (pas Google). Construire it automatically, liste seulement canonical indexable URLs, and utiliser the submitted-vs-indexed signal in Search Console to trouver what’s manquant.

Ce que a sitemap is — and ce que it’s pour

Google’s definition is the correct anchor: “A sitemap is a fichier où vous provide information à propos de lune pages, videos, and autre fichiers on votre site, and the relationships entre les.” Evidence for this claim A sitemap supplies search engines with information about pages, videos, and other files on a site and their relationships. Scope: Google's general definition of sitemaps; supported formats and extensions have additional requirements. Confidence: high · Verified: 2026-07-14 Google Search Central: Learn about sitemaps It’s an inventory vous hand to moteur de recherches.

The la plupart important framing I peut give vous: a sitemap is a coverage and diagnostic outil, pas a discovery silver bullet. Google is explicit que “A sitemap helps moteur de recherches découvrir URLs on votre site, but it doesn’t guarantee que tout the items in votre sitemap va be crawled and indexé.” Submitting une URL doesn’t index it. The réel day-to-day payoff is the submitted-vs-indexed comparison in Search Console: split votre sitemaps by section or content type and vous pouvez voir qui partie of le site isn’t getting picked up. During a migration I’ll garder a sitemap of the old URLs autour pour a pendant que on objectif, specifically so I peut watch les drop out of the index in GSC.

Do vous besoin un? Resolving the contradiction

You’ll voir two pieces of advice que regarder comme ils conflict:

• Google’s threshold: vous probable don’t besoin a sitemap si le site is petit (autour 500 pages) and bien internally lié; vous probable do si it’s grand, nouveau with few backlinks, or media/News-heavy.
• Mueller’s baseline: “Making a sitemap fichier automatically seems comme a minimal baseline pour quelconque serious website, imo.”

Les deux are correct, and here’s how I reconcile les: a sitemap isn’t strictly requis pour a tiny, well-linked site, but it’s cheap insurance and it’s now the attendu baseline — so toujours generate un, automatically. Qui brings me to the un rule I won’t bend on.

Automate it, or it rots

Sitemaps devrait be generated automatically from lune pages vous en réalité have. Si someone hands me a manually-built sitemap, I déjà know it’ll fall out of date fast — somebody adds pages, nobody updates the fichier, and now it’s lying to Google. And there’s a subtler point: si you’re generating le sitemap from votre réel, crawlable pages anyway, moteur de recherches peut usually reach ceux pages on leur propre via liens. Le sitemap earns its garder by being current and complet, pas simplement by existing. Automation is ce que rend it current.

The types of sitemap

• XML sitemap — the workhorse, written pour robots d’exploration. A liste of <loc> URLs, optionally with <lastmod>. Ce is ce que personnes usually mean by “sitemap.”
• HTML sitemap — a human-facing page of liens. Utile pour utilisateurs and pour internal linking, but it isn’t the fichier vous submit to Search Console.
• Image sitemap — surfaces images moteur de recherches pourrait sinon miss (pour exemple, images chargé by JavaScript or served dynamically). Peut be a standalone fichier or image tags ajouté to an existing sitemap.
• Video sitemap — donne moteur de recherches the metadata ils besoin to comprendre and index votre videos (thumbnail, title, description, and the media or player URL).
• News sitemap — pour sites in Google News, listing recent articles.

And XML isn’t the seulement accepted format. Google aussi takes RSS/Atom feeds and a plain-text .txt fichier (un URL per line). RSS and text formats peut seulement liste page URLs — aucun image or video metadata — so XML is the la plupart versatile.

XML vs HTML

Ces obtenir confused constantly, so garder les separate: an XML sitemap is pour robots d’exploration — machine-readable, submitted to Search Console, the chose moteur de recherches parse. An HTML sitemap is pour personnes — a regular web page linking to votre sections, qui peut aussi aider maillage interne. Si vous seulement construire un, construire the XML sitemap; that’s the un moteur de recherches en réalité utiliser.

How to trouver a sitemap (and pourquoi some sites hide theirs)

To trouver a sitemap, essayer, in order:

• /sitemap.xml — the par défaut emplacement on la plupart platforms.
• robots.txt — a public sitemap is usually named ici with a Sitemap: line, qui is aussi how engines auto-discover it.
• site: operators / Search Console — pour votre propre property, the Search Console Sitemaps report is the authoritative view of what’s submitted and how it’s doing.

But here’s the partie la plupart guides skip: pas every sitemap is meant to be trouvé. Some sites deliberately omit the Sitemap: line from robots.txt and submit the fichier seulement via Search Console and Bing Webmaster Outils. A sitemap referenced in robots.txt is readable by anyone — notamment competitors who’d love a tidy liste of every URL vous publish (unlinked pages, nouveau launches, strategically pages importantes) and a façon to watch how fast vous ship. A sitemap submitted seulement via the consoles is effectively private. So si vous pouvez’t trouver a site’s sitemap at the usual paths, it may simplement be unlisted, pas absent.

The trade-off is réel, though: hiding le sitemap from robots.txt aussi signifie quelconque engine que relies on robots.txt auto-discovery won’t voir it unless you’ve submitted it in chaque console. Si vous go the private route, vous have to do the submission legwork everywhere vous care à propos de.

How to créer un

Almost every platform peut generate a sitemap pour vous — and on la plupart of les it’s automatic. I’ve put the per-platform paths (WordPress, Shopify, Wix, Squarespace, Webflow, Drupal, JS frameworks, and manual generators) in the Cheat Sheets tab so vous pouvez jump straight to yours. La version courte pour JS frameworks: search the framework nom plus “sitemap” (Par exemple, “Gatsby sitemap” or “Suivant.js sitemap”) — there’s almost toujours an existing module so vous don’t hand-roll it. Ce site runs on Astro and uses @astrojs/sitemap, configuré in astro.config.mjs.

How to submit it

The live méthodes:

• Recherche Google Console — le sitemaps report (and the Search Console API). The principal méthode.
• Bing Webmaster Outils — submit là aussi; Bing récupère it immédiatement, alors rechecks roughly daily.
• robots.txt Sitemap: line — fonctionne pour quelconque engine que reads robots.txt, and is how a public sitemap obtient auto-discovered. Utiliser the complet absolute URL.

What’s dead: the old standalone ping endpoint (google.com/ping?sitemap=). It’s been deprecated since 2023 and renvoie a 404 since January 2024 — Google killed it parce que the vast majority of submissions were spam. Si you’ve got a plugin or cron job encore hitting it, strip que out. Pour fast, URL-level notification of unique changements to Bing and others, utiliser IndexNow — but remarque Google ne fait pas participate in IndexNow, so it won’t speed up Google indexation. Bing’s propre framing is que the two are complementary: sitemaps pour comprehensive coverage, IndexNow pour fast per-URL pushes.

Submission problems

Quand something goes incorrect, the Search Console Sitemaps report va tell vous — but the error étiquettes aren’t toujours self-explanatory. I’ve put a complet error → meaning → fix table in the Cheat Sheets tab. The greatest hits: “Couldn’t fetch” (incorrect URL, robots block, or simplement pas processed yet — souvent transient), “Unsupported format” (vous submitted an HTML page au lieu de a réel XML/RSS/Atom/txt fichier), and “URL pas allowed” (the classic HTTP-vs-HTTPS / www mismatch, or URLs ci-dessus le sitemap’s propre chemin). A couple of non-error gotchas worth knowing: Google may serve vous a stale mis en cache copy, so changements aren’t instant, and submitting les deux the children and le sitemap index is harmless but unnecessary.

Meilleur practices — and “exclude ≠ noindex”

The rules que matter, tout from Google’s propre spec:

• Size: a unique sitemap holds at la plupart 50 000 URLs or 50MB uncompressed, whichever comes premier. Vous pouvez gzip it — the 50MB cap is the uncompressed size. Evidence for this claim Google limits a single sitemap to 50,000 URLs or 50 MB uncompressed. Scope: Google-supported sitemap files; larger inventories must be split across multiple sitemaps, optionally joined by an index. Confidence: high · Verified: 2026-07-14 Google Search Central: Build and submit a sitemap Over the limite, split into multiple sitemaps and tie les ensemble with a sitemap index.
• Encoding: UTF-8.
• URLs: fully-qualified, absolute URLs. Entity-escape &, ', ", <, and >.
• Tags Google ignores: <priority> and <changefreq> ne faites pashing — don’t bother with les.
• lastmod fait honestly: Google seulement trusts lastmod si it’s consistently and verifiably accurate. Définir it on significant updates (principal content, structured données, or liens) — pas a blanket copyright-year or “today” stamp on every URL. Lie à propos de it and Google arrête believing the field. Fait correct, an accurate lastmod genuinely helps re-crawling (Bing leans on it même harder que Google fait).
• Contents: liste seulement canonical, indexable, 200-status URLs. Aucun redirections, aucun non-URL canoniques, aucun noindex’d pages. Quelconque page vous vouloir indexé devrait be in le sitemap; nothing vous don’t.

Worked audit: valid XML, polluted inventory

A sitemap peut réussir XML validation and encore send contradictory discovery signals. Ce illustrative explorer joins chaque <loc> to its live réponse and index contrôle:

Le sitemap fichier itself is bien formed. The pollution apparaît seulement après comparing its inventory with status, canonical, robots, and lifecycle evidence. Fix the generator or source requête plutôt que deleting the même rows by hand every release.

Que dernier point hides the unique la plupart courant conceptual error: exclude ≠ noindex. Leaving une URL out of votre sitemap fait pas deindex it. Le sitemap is an advertisement, pas a gate — dropping une URL simplement arrête vous advertising it; it doesn’t supprimer it from Google. Si vous vouloir une page gone, autoriser exploration and utiliser noindex. The sitemap is the incorrect outil pour que job.

Où to go suivant

Ce page is the overview. Chaque of ces is its propre deep dive nested sous the discovery topic:

• XML sitemap — the format and anatomy: <urlset>, <loc>, <lastmod>, the ignored tags, ce que to inclure and exclude, and hreflang in sitemaps.
• Sitemap index — the “sitemap of sitemaps” pour grand sites, quand to split, and the math on how nombreux URLs vous pouvez cover.
• Image sitemap — surfacing images moteur de recherches pourrait miss, the current (pas deprecated) tag liste, and cross-domain rules.
• Video sitemap — the requis tags, accepted fichier types, and getting videos understood and indexé.

Sitemaps are un half of discovery — the autre half is exploration, qui is how engines en réalité récupérer l’URLs votre sitemap points to. Pour the whole picture, voir How Search Fonctionne. Every topic ci-dessus is in the sidebar aussi.

AI summary

A condensed prendre on the Avancé version:

• A sitemap is a fichier listing votre URLs (and optionally images/videos) so search engines peut découvrir les. Google: “a fichier où vous provide information à propos de the pages, videos, and autre fichiers on votre site.”
• Discovery, pas indexation. Submitting a sitemap doesn’t guarantee exploration or indexation — “it doesn’t guarantee que tout the items in votre sitemap va be crawled and indexé.” Its réel valeur is the submitted-vs-indexed diagnostic in Search Console.
• Do vous besoin un? Pas strictly pour tiny well-linked sites (Google’s ~500-page threshold), but Mueller calls it “a minimal baseline for any serious website.” Toujours generate un — automatically, or it rots.
• Types: XML (pour robots d’exploration), HTML (pour personnes), image, video, news; plus RSS/Atom and plain .txt formats (page URLs seulement).
• Finding un: /sitemap.xml, robots.txt, site: / Search Console. Some sites deliberately hide theirs (omit it from robots.txt, submit seulement in the consoles) to garder leur URL liste private — at the cost of losing auto-discovery.
• Limites: 50 000 URLs or 50MB uncompressed per sitemap (gzip allowed; cap is uncompressed); UTF-8; fully-qualified absolute URLs; entity-escape & ' " < >.
• Tags: Google ignores <priority> and <changefreq>; uses <lastmod> seulement si consistently accurate (significant updates, pas copyright-year).
• Submit via Search Console, Bing Webmaster Outils, and the robots.txt Sitemap: line. The ping endpoint 404s since Jan 2024. IndexNow notifies Bing/Yandex/others — pas Google.
• Exclude ≠ noindex. Leaving une URL out of le sitemap doesn’t deindex it; utiliser noindex pour que.
• Deep dives: XML sitemap, sitemap index, image sitemap, video sitemap.

Documentation officielle

Primary-source documentation from the moteur de recherches.

Google

• Sitemaps overview — ce que a sitemap is, do vous besoin un, and the pris en charge formats.
• Construire and submit a sitemap — the 50 000-URL / 50MB limites, UTF-8, absolute URLs, lastmod, and how to submit.
• Manage votre grand sitemaps with sitemap index fichiers — splitting big sitemaps and the index fichier.
• Image sitemaps — the current image tags and namespace.
• Video sitemaps — requis/optional video tags.
• Sitemaps report aider — every Search Console sitemap error and Ce que cela signifie.
• sitemaps.org protocol — the cross-engine XML sitemap standard.

Bing / Microsoft

• Keeping Content Discoverable with Sitemaps in AI-Powered Search (Jul 2025) — Bing’s current stance: XML preferred, lastmod matters, sitemaps + IndexNow are complementary.
• The Importance of Setting the lastmod Tag in Votre sitemap (Feb 2023) — Fabrice Canel on pourquoi lastmod is crucial.
• IndexNow / indexnow.org documentation — the push protocol pour instantly signaling modifié URLs (Bing, Yandex, and others — pas Google).

Quotes from the source

On-the-record statements from Google and Bing. Chaque lien is a deep lien que jumps to the quoted passage on the source page.

Google — ce que a sitemap is and ce que it fait

• “A sitemap is a file where you provide information about the pages, videos, and other files on your site, and the relationships between them.” — Recherche Google Central, sitemaps overview. Jump to quote
• “A sitemap helps search engines discover URLs on your site, but it doesn’t guarantee that all the items in your sitemap will be crawled and indexed.” Jump to quote

Google — discovery, pas a guarantee

• “submitting a Sitemap doesn’t guarantee the pages referenced in it will be indexed. Think of a Sitemap as a way to help Googlebot find your content … if the content is shallow, it may totally happen it will not be indexed at all.” — Gary Illyes, Google. Jump to quote
• “One part of sitemaps is that Google has to be keen on indexing more content from the site. If Google’s not convinced that there’s new & important content to index, it won’t use the sitemap.” — John Mueller, Google. Jump to quote

Google — do vous besoin un?

• “Making a sitemap file automatically seems like a minimal baseline for any serious website, imo.” — John Mueller, Google. Jump to quote

Google — the tags it ignores

• “we ignore those. It’s essentially a bag of noise.” — Gary Illyes, Google, on <priority> and <changefreq>. Jump to quote
• “Priority and change frequency doesn’t really play that much of a role with Sitemaps anymore … it is much better to just specify the time stamp directly.” — John Mueller, Google. Jump to quote

Google — lastmod fait honestly

• “setting today’s date in a sitemap file isn’t going to be something that works in favor of anyone, it’s just lazy.” — John Mueller, Google. Jump to quote
• “an update to the main content, the structured data, or links on the page is generally considered significant, however an update to the copyright date is not.” — Recherche Google Central, construire a sitemap. Jump to quote

Bing — lastmod and IndexNow

• “XML remains the preferred format for sitemaps, as it supports structured metadata like lastmod, which helps Bing assess content freshness and relevance more effectively.” — Microsoft Bing blog. Jump to quote
• “By combining sitemaps for comprehensive site coverage with IndexNow for fast, URL-level submission, you provide the strongest foundation for keeping your content fresh, discoverable, and visible.” — Microsoft Bing blog. Jump to quote

The standing KPIs pour sitemap health

A sitemap doesn’t have a ranking metric of its propre — its job is coverage, so the KPIs que matter track si it’s en réalité doing que job over temps, pas a one-off audit.

Submitted vs. indexé, per sitemap

• Metric — Of l’URLs in a donné sitemap, ce que share Google reports as indexé vs. non indexée.
• Ce que it indique vous — Si l’URLs you’re advertising are en réalité landing dans l’index. A ratio that’s fine overall but bad pour un sitemap (dire, a blog sitemap vs. a product sitemap) indique vous exactly qui section of le site has a problem — that’s the whole raison to split sitemaps by section in the premier placer.
• How to pull it — In Search Console, ouvrir Page Indexation (“Pourquoi pages aren’t indexé”) and filter by sitemap — que view splits indexé vs. not-indexed pour l’URLs in que spécifique fichier. The Sitemaps report itself seulement montre ce que was submitted and quand it was dernier lire, so the indexé/not-indexed split comes from Page Indexation, pas le sitemaps report. Spot-check individual URLs with the Google Index Checker quand vous besoin the observable signals (status, redirections, noindex, canonical) behind a unique URL’s non-indexing.
• Benchmark / realistic range — There’s aucun honest universal target — a site with lots of thin, near-duplicate, or genuinely low-value pages va jamais voir 100%, and that’s pas necessarily a bug. Establish votre propre baseline per section and watch the trend: a ratio that’s drifting bas is the signal, pas quelconque spécifique absolute number.
• Cadence — Monthly pour a stable site; weekly during a migration, a grand content push, or correct après vous restructure votre sitemaps, since that’s quand the ratio moves fastest.

Sitemap coverage completeness

• Metric — Share of votre réel canonical, indexable, 200-status URLs que are présent in the submitted sitemap(s).
• Ce que it indique vous — Si le sitemap is doing its job as a complet inventory, or si it’s rotted — manquant nouveau sections, encore listing redirigé or deindexed URLs, or drifting out of sync with ce que votre CMS en réalité generates. Ce is a data-quality vérifier on the fichier itself, pas on Google’s behavior.
• How to pull it — Récupérer and validate the live sitemap with the XML Sitemap Validator to obtenir the exact URL liste plus quelconque structural errors, alors comparer que liste contre votre site’s réel URL canonique définir (a explorer export, or votre CMS’s propre page liste) to trouver gaps in soit direction — pages manquant from le sitemap, or stale URLs encore in it que shouldn’t be.
• Benchmark / realistic range — Dépend entirely on how vous define “devrait be indexable” pour votre propre site, so there’s aucun defensible universal number ici soit — the correct bar is simply “fermer to 100% match, with quelconque gap explained” plutôt que a target percentage.
• Cadence — Whenever le sitemap is regenerated (ideally every deploy, si it’s automated) and as a manual spot-check après quelconque grand content migration or URL restructuring.

Ready-to-use AI prompts

Copy-paste starting points pour sitemap tasks. Treat the output as a draft to vérifier contre the réel sitemap fichier, Search Console, and Google’s propre sitemap docs — pas a final réponse.

Audit a sitemap fichier contre the spec

Ici is my sitemap XML [paste the fichier or the premier ~200 lines]. Vérifier it contre Google’s sitemap requirements: is it sous 50 000 URLs / 50MB uncompressed, UTF-8, en utilisant fully-qualified absolute URLs, and are &, ', ", <, and > correctement entity-escaped? Flag anything que semble comme a non-URL canonique, a redirection target, or a duplicate. Don’t flag <priority> or <changefreq> as errors — Google ignores ceux tags, they’re pas a validity problème.

Decide si to split into a sitemap index

My site has approximately [N] indexable URLs à travers ces sections: [liste sections, e.g. blog, product pages, category pages]. Fondé on Google’s 50 000-URL / 50MB-per-sitemap limite, tell me si I besoin a sitemap index, and si so, propose a sensible split by section (so I peut aussi diagnose submitted-vs-indexed per section in Search Console afterward).

Écrire a lastmod mettre à jour policy

I vouloir a lastmod policy pour my sitemap generator que seulement updates the date on genuinely significant changements (principal content, données structurées, or liens) — pas a blanket “today” or copyright-year stamp, since Google dit it arrête trusting lastmod une fois it’s inaccurate. Here’s how my CMS tracks edits [décrire: publish date, last-edited timestamp, version history, etc.]. Draft the logic pour quand lastmod devrait and shouldn’t modifier.

Decide si to garder le sitemap public or submit it privately

Here’s my situation: [décrire le site — competitive niche? nouveau unlinked pages vous don’t vouloir scraped? currently listing le sitemap in robots.txt?]. Walk me via the trade-off entre listing my sitemap in robots.txt (public, auto-discoverable by quelconque robot d’exploration) versus submitting it seulement via Recherche Google Console and Bing Webmaster Outils (private, but I lose auto-discovery pour quelconque engine I haven’t manually submitted to). Recommend un donné my situation and expliquer pourquoi.

Triage a submitted-vs-indexed export by section

Here’s a CSV export of my sitemap URLs joined with leur indexation status from Search Console [paste: URL, sitemap, indexé y/n, raison si pas indexé]. Groupe the “not indexed” URLs by probable causer (contenu pauvre, near- duplicate, blocked, pas yet crawled, deliberately low-value) and tell me qui sitemap section has the worst ratio, so I know où to focus premier.

Sitemap checklist

A réussir to confirmer votre sitemap is helping plutôt que rotting:

• A sitemap exists and is generated automatically (pas hand-maintained).
• It listes seulement canonical, indexable, 200-status URLs — aucun redirections, aucun non-URL canoniques, aucun noindex’d pages.
• URLs are fully-qualified and absolute, and special characters (& ' " < >) are entity-escaped.
• It’s UTF-8 encoded.
• Aucun unique sitemap exceeds 50 000 URLs or 50MB uncompressed — split + utiliser a sitemap index si it fait (gzip is fine; the cap is the uncompressed size).
• Vous haven’t bothered with <priority> or <changefreq> — Google ignores les deux.
• <lastmod> is seulement définir on significant updates and is genuinely accurate (pas a blanket copyright-year or “today” date).
• Submitted in Recherche Google Console and Bing Webmaster Outils.
• A Sitemap: line is in robots.txt (or it’s deliberately omitted to garder the sitemap private — in qui cas you’ve submitted it in every console).
• Aucun dead google.com/ping?sitemap= calls left in quelconque plugin or cron job (it 404s since Jan 2024).
• Vous periodically vérifier the submitted-vs-indexed numbers in Search Console to spot under-indexed sections.
• You’re pas en utilisant le sitemap to essayer to deindex anything — that’s noindex’s job.

The mental models

1. A sitemap is an inventory, pas a discovery silver bullet. It’s a coverage outil — a clean liste of ce que vous vouloir indexé. It fait pas force exploration or indexation. Si pages aren’t getting indexé, le sitemap is où vous notice the problem (submitted vs indexé), pas où vous fix it.

2. Exclude ≠ noindex. Leaving une URL out of le sitemap ne fait pas supprimer it from Google. Le sitemap is an advertisement, pas a gate. To supprimer une page, autoriser exploration and ajouter noindex — the sitemap is the incorrect lever entirely.

3. Automate it, or it rots. A manually-built sitemap goes stale the moment someone adds une page and forgets the fichier. Generate it from lune pages vous en réalité have so it stays current and complet. A sitemap’s valeur is in being accurate, pas in merely existing.

4. Submitted-vs-indexed is a diagnostic. Split votre sitemaps by section or content type and the Search Console coverage numbers tell vous qui partie of le site is under-indexed. That’s the réel, day-to-day payoff — far plus utile que the act of submitting itself.

5. Discovery has two halves. Sitemaps are the pull-inventory half of discovery; liens are the autre pull half, and push protocols (IndexNow, the Indexation API) are a separate channel. Si une page isn’t being trouvé, demander qui channel devrait be carrying it — and si anything liens to it at tout.

How to créer a sitemap, by platform

Chaque platform ci-dessous soit generates a sitemap automatically or has a standard module pour it. The two final steps are the même everywhere: (1) assurez-vous seulement the correct URLs are inclus (canonical, indexable seulement); (2) submit it in Search Console + Bing Webmaster Outils and ajouter the Sitemap: line to robots.txt (or deliberately omit que line to garder it unlisted).

Search Console sitemap errors → meaning → fix

Autre real-world gotchas: an HTTP-vs-HTTPS or www mismatch entre sitemap URLs and the verified property triggers “URL not allowed”; Google may serve a stale mis en cache copy so changements aren’t instant; and submitting children and the index is harmless but unnecessary.

Outils pour validating and diagnosing a sitemap

• Google Index Checker — spot-check a spécifique URL from votre sitemap pour the observable indexability blockers (code d’état, redirections, noindex, canonical signals) avant vous assume the sitemap itself is the problem. It routes vous to Search Console’s URL Inspection pour Google’s réel, authoritative réponse — ce outil seulement surfaces what’s visible from the outside.
• Recherche Google Console — Sitemaps report — où vous submit a sitemap and voir ce que Google dernier récupéré and quand; combine with the Page Indexation report (filtered by sitemap) to obtenir the indexed-vs-not-indexed split utilisé in the How to Mesurer tab ci-dessus.
• Bing Webmaster Outils — Sitemaps — the equivalent submission and status view pour Bing; submit ici en outre to Search Console, since the two engines track sitemaps independently.
• A robot d’exploration (Ahrefs Site Audit, Screaming Frog) — the façon to generate the “actual canonical URL list” vous comparer a sitemap contre quand checking coverage completeness — a sitemap validator confirms the fichier is well-formed, but seulement a réel explorer of votre site indique vous si the fichier is complet.

Ressources utiles

My connexe writing

• Enterprise SEO technique — où automated, current sitemaps fit into managing a grand site.
• Quand Devrait Vous Worry À propos de Budget d’exploration? — en utilisant le sitemap as a clean inventory of votre indexable définir.
• Webmigration de site: The Ultimate Guide — notamment keeping a sitemap of the old URLs autour to watch les drop out of the index.
• JavaScript SEO Problèmes & Meilleur Practices — quand sitemaps matter la plupart (JS-loaded content and framework sitemap modules).

My speaking

• How Search Fonctionne (SlideShare) — my walkthrough of exploration, rendering, indexation, and ranking, où sitemaps live on the discovery side. (Standing disclaimer: “This is my understanding of systems… not going to be 100% complete or accurate.”)

From others

• Google’s Sitemaps overview and build-a-sitemap docs — the principal source pour everything on ce page.
• The sitemaps.org protocol — the cross-engine standard XML sitemaps are construit on.
• Bing Webmaster Blog: Keeping Content Discoverable with Sitemaps in AI-Powered Search — Bing’s current prendre on XML format preference, lastmod importance, and sitemaps + IndexNow as complementary.
• Bing Webmaster Blog: The Importance of Setting the lastmod Tag in Votre sitemap — Fabrice Canel explique how Bing uses lastmod pour freshness assessment.
• IndexNow documentation — the push protocol pour instantly notifying Bing, Yandex, and others of modifié URLs (Google ne fait pas participate).
• Recherche Google Console Sitemaps report aider — complet référence pour every sitemap error and status in Search Console.
• Moteur de recherche Journal: Google Explique Pourquoi It May Pas Utiliser a Sitemap — covers John Mueller’s explanation of quand Google ignores submitted sitemaps.
• Moteur de recherche Roundtable: Google: XML Sitemaps Are A Minimal Baseline Pour Quelconque Serious Website — Barry Schwartz covering Mueller’s “minimal baseline” stance.

Testez vos connaissances: Sitemaps

Five rapide questions on ce que sitemaps do and ce que belongs in les. Pick an réponse pour chaque, alors vérifier.

Journal des modifications