Résumé clé

En SEO 2026, robots.txt décrit les règles d’exploration et sitemap.xml liste les URL canoniques. Les deux fichiers doivent rester cohérents.

Guide SEO 2026 pour robots.txt et sitemap.xml

robots.txt syntax: User-agent, Disallow, Allow, Sitemap

Use robots.txt at the root of the host, for example https://millionscode.com/robots.txt. The practical 2026 baseline is simple: open the parts that should be crawled, block low-value operational paths, and declare the sitemap with a full URL. A safe starting point is:

User-agent: *
Allow: /

Sitemap: https://millionscode.com/sitemap.xml

For a production site, treat Disallow carefully. A single Disallow: / can stop crawling of the whole host. That is useful on staging and dangerous on a live site. If admin pages, carts, search results, or temporary filters should not be crawled, block those paths only:

User-agent: *
Disallow: /admin/
Disallow: /search
Disallow: /cart
Allow: /blog/
Allow: /tools/

Sitemap: https://millionscode.com/sitemap.xml

robots.txt is not a security layer. It is a crawler instruction file. Sensitive data must be protected by authentication, and pages that must disappear from search need the right removal method rather than only a crawl block.

sitemap.xml structure

A sitemap lists canonical URLs that deserve discovery. Keep it clean:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://millionscode.com/tools/meta-checker</loc>
    <lastmod>2026-06-03</lastmod>
  </url>
  <url>
    <loc>https://millionscode.com/blog/post-mp90fbw1</loc>
    <lastmod>2026-06-03</lastmod>
  </url>
</urlset>

Do not mix canonical and non-canonical versions. Do not submit URLs blocked by robots.txt. Use /tools/meta-checker for metadata checks, /blog/post-mp90fbw1 for sitemap generation planning, /blog/api-mpj0hwex for indexing API workflow, and /blog/post-mpkfy95s for Search Console checks.

Submission: Search Console and Naver

In Google Search Console, verify the property and submit sitemap.xml or sitemap_index.xml in the Sitemaps report. Then check status, discovered URL count, fetch errors, and whether blocked URLs are accidentally present. In Naver Search Advisor, verify ownership, run robots.txt diagnosis, submit the sitemap, and watch collection requests separately. For Korean search traffic, Naver diagnostics should not be skipped.

Common mistakes

The first mistake is leaving a staging rule on production. The second is listing blocked URLs in the sitemap. The third is mixing www, non-www, http, and https versions. The fourth is changing lastmod every day without real content changes. The fifth is using robots.txt as an index removal tool. The reliable 2026 pattern is open crawl paths, submit only canonical URLs, and use console tools for diagnosis.

Note pratique

For small and mid-size websites, the most useful habit is consistency. The pages in sitemap.xml should also be reachable through internal links. New posts, key tools, category pages, and evergreen guides should reinforce one another instead of living as isolated URLs. Après chaque changement de routes, canonical, langues ou XML généré, vérifiez les deux fichiers et les rapports de diagnostic.

FAQ

robots.txt bloque-t-il seul l’indexation ?

Non. Il contrôle surtout l’exploration. Pour retirer ou protéger une page, utilisez noindex, authentification, outils de suppression ou bons codes HTTP.

Où placer Sitemap ?

Avec une URL complète, souvent en fin de fichier robots.txt.

Allow gagne-t-il toujours ?

La règle la plus spécifique gagne souvent. Testez avant production.

Faut-il toutes les URL ?

Non. Seulement les URL canoniques et indexables.

La soumission garantit-elle l’indexation ?

Non. Elle aide la découverte et le diagnostic.

Faut-il Naver ?

Oui si le trafic coréen compte.