Yes. Let's take your **`sitemap-events.xml`** as an example. ## 1. Example `sitemap-events.xml` Suppose your website has these event pages: ```text https://example.com/events/annual-conference-2026 https://example.com/events/national-meeting-2026 https://example.com/events/womens-day-programme ``` Your `sitemap-events.xml` could be: ```xml https://example.com/events/annual-conference-2026 2026-08-18 https://example.com/events/national-meeting-2026 2026-08-15 https://example.com/events/womens-day-programme 2026-08-10 ``` That's enough. --- # 2. What is `priority`? You may see examples like this: ```xml https://example.com/events/annual-conference-2026 2026-08-18 0.8 ``` `priority` is an **optional sitemap field** that historically allowed you to indicate the relative importance of one URL compared with other URLs on the same site. It ranges from: ```text 0.0 → 1.0 ``` For example: ```xml 1.0 ``` could mean: > "This is extremely important relative to my other URLs." while: ```xml 0.3 ``` could mean: > "This page is relatively less important." ### But here's the important part: **You don't need it.** Search engines don't need you to assign priorities for them to crawl and index your site. In fact, I would generally **leave `` out** of your sitemap. --- # 3. Why? Imagine you have: ```text Homepage priority 1.0 News priority 0.9 Circulars priority 0.8 Events priority 0.8 Individual news priority 0.7 Individual event priority 0.6 ``` It looks sophisticated. But it doesn't mean: > "Google will rank my 1.0 page higher than my 0.6 page." That's **not how priority works**. It isn't a ranking score. It isn't: ```text priority = Google ranking ``` Instead, historically it was intended as a **relative crawling hint within your own site**. So: ```text example.com/page-A → 0.8 example.com/page-B → 0.4 ``` means roughly: > "I consider A more important than B." It does **not** mean: > "Google should rank A twice as high." --- # 4. What about `changefreq`? You'll also encounter this: ```xml weekly ``` For example: ```xml https://example.com/events/annual-conference-2026 2026-08-18 weekly 0.7 ``` Older sitemap tutorials frequently recommend: ```xml daily 0.8 ``` everywhere. I **wouldn't build your sitemap that way**. The more useful information is the actual modification date: ```xml 2026-08-18 ``` rather than telling Google: ```xml daily ``` when the page doesn't actually change daily. --- # 5. So what should your sitemap contain? For your website, I'd keep it clean: ```xml https://example.com/events/annual-conference-2026 2026-08-18 https://example.com/events/national-meeting-2026 2026-08-15 https://example.com/events/womens-day-programme 2026-08-10 ``` **`loc` → essential** **`lastmod` → useful** **`priority` → optional; I'd omit it** **`changefreq` → optional; I'd omit it** --- ## 6. Your architecture would then look like this ```text https://example.com/sitemap.xml │ │ ▼ sitemap index │ ┌───────┼────────┐ │ │ │ ▼ ▼ ▼ News Events Circulars XML XML XML │ │ │ ▼ ▼ ▼ Article Event Circular URLs URLs URLs ``` And your master `sitemap.xml`: ```xml https://example.com/sitemaps/sitemap-news.xml https://example.com/sitemaps/sitemap-events.xml https://example.com/sitemaps/sitemap-circulars.xml ``` That's the architecture I'd recommend rather than trying to put **title, description, priority, category, tags, etc.** into the sitemap. The sitemap's job is primarily to provide a structured list of **canonical URLs and useful modification dates**.