<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sitemap on DevOpsTales</title>
    <link>https://devopstales.github.io/tags/sitemap/</link>
    <description>Recent content in Sitemap on DevOpsTales</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Thu, 16 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://devopstales.github.io/tags/sitemap/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Hugo robots.txt Generation</title>
      <link>https://devopstales.github.io/hugo/hugo-robots-txt/</link>
      <pubDate>Thu, 16 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://devopstales.github.io/hugo/hugo-robots-txt/</guid>
      <description>Crawlers still look for /robots.txt before they dig through your tree. Hugo can generate that file at build time from a template, so the Sitemap URL always matches your baseURL and you can add allow/disallow rules without maintaining a hand-copied static file.
</description>
      <enclosure url="https://devopstales.github.io/img/hugo.webp" length="3684" type="image/png" />
    </item>
    
    <item>
      <title>Hugo SEO on a Multi-Section Blog</title>
      <link>https://devopstales.github.io/hugo/hugo-seo/</link>
      <pubDate>Fri, 10 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://devopstales.github.io/hugo/hugo-seo/</guid>
      <description>Search and social previews on a Hugo blog are mostly template work: consistent titles, a real summary, a thumbnail, Open Graph / Twitter tags, structured data, and a sitemap. DevOpsTales does that in layouts/_default/baseof.html plus a JSON-LD partial—no SEO plugin required.
</description>
      <enclosure url="https://devopstales.github.io/img/hugo.webp" length="3684" type="image/png" />
    </item>
    
  </channel>
</rss>
