XML Sitemap Strategy: Index, Partition, News and Image Sitemap

Sending 50,000 URLs to Google in a single XML file is like trying to hold a 500-page book together with a staple. Technically possible but not practical. In 2023, when adding 79,000 doctor profiles to doktorbul.com, this was my first mistake: I crammed all URLs into a single sitemap.xml file. When Google's bot tried to download the file, the server timed out, and indexing was delayed by 3 weeks. Since that day, I've been using an index sitemap + partition structure in every project.

In this article, I'll explain XML sitemap architecture in four layers: basic index structure, partition strategy, news sitemap rules, and image sitemap integration. Not just theory—you'll see real examples and error scenarios from FUTIA projects. If you have a site with 10,000+ pages or produce daily content, don't expect Google to index at full capacity without setting up this structure.

Index Sitemap: The Main Organization File

An index sitemap works like a table of contents that lists other sitemap files. You submit a single file to Google Search Console, and that file references 10-50 separate sitemaps.

A simple index sitemap example:

<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap>
    <loc>https://ornek.com/sitemap-posts.xml</loc>
    <lastmod>2025-01-15</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://ornek.com/sitemap-pages.xml</loc>
    <lastmod>2025-01-10</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://ornek.com/sitemap-products.xml</loc>
    <lastmod>2025-01-14</lastmod>
  </sitemap>
</sitemapindex>

I always separate by content type: blog posts, static pages, products, categories in separate files. On doktorbul.com, there were 6 different sitemaps: doctors, clinics, articles, city pages, disease pages, general pages. Each had its own update frequency.

Advantages of Index Sitemap

• Selective updates: When only blog posts change, you update the blog sitemap, without touching the 50,000-URL product sitemap
• Error isolation: If one sitemap breaks, others continue working
• Crawl budget optimization: Google crawls priority content more frequently
• Maintenance ease: Instead of searching for errors in a 50,000-line file, you search in 10 files of 5,000 lines each

italyanmutfagi.com has 618 recipe pages. Initially, I used a single sitemap; every time a new recipe was added, the entire file was regenerated. After switching to an index structure, new recipes went into sitemap-recipes-new.xml, old recipes stayed in sitemap-recipes-archive.xml. Google crawls the new file 3-4 times a day, the archive file once a week.

Partition Strategy: Breaking Large Sites into Pieces

Google's limit per sitemap is 50,000 URLs and 50MB. But in practice, file management becomes difficult after 10,000 URLs. I use 5,000-URL partitions.

Partition Methods

1. Date-based partition (for blog, news sites):

• sitemap-2025-01.xml
• sitemap-2024-12.xml
• sitemap-2024-11.xml

kamupersonelhaber.com publishes 50+ announcements daily. I use monthly partitions; each month's sitemap "freezes" at the end of that month and never changes again. Only the current month's file gets updated.

2. Category-based partition:

• sitemap-category-teknoloji.xml
• sitemap-category-saglik.xml
• sitemap-category-egitim.xml

memuratamalari.com has 40,400 monthly organic searches. Content is divided into 12 main categories, each with its own sitemap. Google immediately sees which category has new content.

3. Number-based partition (for e-commerce, directory sites):

• sitemap-products-001.xml (1-5000)
• sitemap-products-002.xml (5001-10000)
• sitemap-products-003.xml (10001-15000)

I used this method on doktorbul.com. I divided 79,000 doctor profiles into 16 files. Each file contains exactly 5,000 profiles, the last file has 4,000.

Partition Automation Code (Python)

I automated partition creation in FUTIA:

def create_partitioned_sitemaps(urls, partition_size=5000):
    partitions = []
    for i in range(0, len(urls), partition_size):
        chunk = urls[i:i+partition_size]
        partition_num = (i // partition_size) + 1
        filename = f"sitemap-part-{partition_num:03d}.xml"
        create_sitemap_file(filename, chunk)
        partitions.append(filename)
    create_index_sitemap(partitions)

This code runs every night; as new URLs are added, partitions are automatically updated. No manual intervention whatsoever.

News Sitemap: Special Structure for Fresh Content

News sitemap works differently from regular sitemap. It's required to get into Google News, but just being a "news site" isn't enough.

News Sitemap Rules

• Contains content published within the last 2 days
• Contains maximum 1,000 URLs
• Uses special XML namespace: xmlns:news="http://www.google.com/schemas/sitemap-news/0.9"
• Publication name, language, publication date are mandatory

Example news sitemap structure:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:news="http://www.google.com/schemas/sitemap-news/0.9">
  <url>
    <loc>https://ornek.com/2025/01/yapay-zeka-haberi</loc>
    <news:news>
      <news:publication>
        <news:name>Örnek Haber</news:name>
        <news:language>tr</news:language>
      </news:publication>
      <news:publication_date>2025-01-15T10:30:00Z</news:publication_date>
      <news:title>Yapay Zeka Sektöründe Yeni Gelişme</news:title>
    </news:news>
  </url>
</urlset>

I use news sitemap on kamupersonelhaber.com. Announcements from the ilan.gov.tr API drop into the news sitemap within 2 hours, Google typically indexes within 4-6 hours. With regular sitemap, this would take 2-3 days.

Common Mistakes in News Sitemap

1. Adding content older than 2 days: Google ignores this content, the file bloats 2. Publication name inconsistency: If you write "Örnek Haber" in one article and "Ornek Haber" in another, Google gets confused 3. Wrong date format: ISO 8601 format is mandatory (2025-01-15T10:30:00Z), UTC not Turkey time 4. Title-content mismatch: If the title in the sitemap differs from the H1 on the page, Google doesn't trust it

I update the news sitemap hourly in every project. Content older than 2 days is automatically deleted, new content is added. This system has been running flawlessly on kamupersonelhaber.com for 18 months.

Image Sitemap: Visual Content Indexing

If you want to appear in Google Images, image sitemap isn't mandatory but very effective. It makes a difference especially on e-commerce, recipe, portfolio sites.

Image Sitemap Structure

There are two methods: separate image sitemap or adding image tags to existing sitemap. I prefer the latter, less file management.

Adding images to existing sitemap:

<url>
  <loc>https://ornek.com/makarna-tarifi</loc>
  <image:image>
    <image:loc>https://ornek.com/images/makarna-1.jpg</image:loc>
    <image:caption>Ev yapımı makarna tarifi</image:caption>
    <image:title>Makarna Tarifi</image:title>
  </image:image>
  <image:image>
    <image:loc>https://ornek.com/images/makarna-2.jpg</image:loc>
    <image:caption>Makarna sosu hazırlama</image:caption>
  </image:image>
</url>

italyanmutfagi.com has 3-8 images per recipe page. Before using image sitemap, images were indexed in Google in 2-3 weeks. After adding image sitemap, this time dropped to 3-5 days. Recipe images appear in top positions for searches like "makarna tarifi", "tiramisu yapımı".

Important Details for Image Sitemap

• Maximum 1,000 images per URL (20-30 is sufficient in practice)
• Use caption and title: Google reads these texts, uses them in image searches
• High resolution: Minimum 300x300px, ideal 1200x800px
• Alt text must be on page: Caption in sitemap should match alt text on page

I use image sitemap for product images on diolivo.com.tr. Each product has 4-6 images, all in the sitemap. Part of the 340% traffic increase in 6 months comes from Google Images.

Sitemap Update Strategy and Automation

Static sitemap files are stuck in the 2010s. If you're producing dynamic content, sitemaps should be dynamic too.

Update Frequencies

I use different frequencies depending on content type:

• News sitemap: Hourly (kamupersonelhaber.com)
• Blog sitemap: Daily (italyanmutfagi.com)
• Product sitemap: Every 6 hours (diolivo.com.tr)
• Static page sitemap: Weekly (all projects)
• Archive sitemap: Monthly (unchanging old content)

memuratamalari.com produces 10-15 pieces of content daily with Claude Haiku API. Every time content is published, the sitemap is automatically updated and Google is pinged.

Sitemap Ping Mechanism

When you publish a new sitemap, you must notify Google:

import requests

def ping_google(sitemap_url):
    ping_url = f"http://www.google.com/ping?sitemap={sitemap_url}"
    response = requests.get(ping_url)
    return response.status_code == 200

I run this code after every sitemap update. Google typically crawls the new sitemap within 2-4 hours.

Sitemap Error Monitoring

Check the "Sitemaps" section in Google Search Console once a week:

• Submitted URL count: Total URLs in sitemap
• Indexed URL count: URLs indexed by Google
• Error count: 404, 500, timeout errors

On doktorbul.com, in the first months I submitted 79,000 URLs, Google indexed 52,000. I examined the remaining 27,000: 12,000 were duplicate content, 8,000 were thin content, 7,000 were technical errors. After fixes, 74,000 were indexed.

Large Site Sitemap Architecture: Real Case Study

FUTIA's largest project was doktorbul.com. 79,000 doctor profiles, 15,000 clinic pages, 8,000 disease pages, 3,000 blog posts. Total 105,000 URLs.

The sitemap architecture I built:

Index sitemap (sitemap.xml):

• sitemap-doctors-index.xml
• sitemap-clinics-index.xml
• sitemap-diseases-index.xml
• sitemap-blog.xml
• sitemap-pages.xml
• sitemap-news.xml

Doctor sitemaps (sitemap-doctors-index.xml):

• sitemap-doctors-001.xml (5,000 profiles)
• sitemap-doctors-002.xml (5,000 profiles)
• ...
• sitemap-doctors-016.xml (4,000 profiles)

Clinic sitemaps (sitemap-clinics-index.xml):

• sitemap-clinics-istanbul.xml
• sitemap-clinics-ankara.xml
• sitemap-clinics-izmir.xml
• ...

Each city has a separate sitemap because we were doing city-based updates. When a new clinic is added in Istanbul, only the Istanbul sitemap is updated.

Update system:

• Doctor profiles: Weekly (profiles rarely change)
• Clinics: Daily (address, phone updates)
• Diseases: Monthly (static content)
• Blog: Daily (new posts)
• News: Hourly (current health news)

Thanks to this architecture, Google crawled 2,000-3,000 pages daily. Organic traffic increased 180% within 3 months.

Sitemap Performance Metrics

How do you know if your sitemaps are working?

Metrics I Track

1. Indexing rate: Submitted URLs / Indexed URLs. Below 70% is problematic. 2. Average indexing time: Time between adding to sitemap and indexing. Target: 3-7 days. 3. Crawl frequency: How often Google crawls a sitemap. Visible in Search Console. 4. Error rate: Rate of URLs returning 404, 500 errors. Above 5% is a serious problem.

On diolivo.com.tr, the indexing rate was 62% in the first 3 months. I cleaned up duplicate product pages, noindexed thin content pages, the rate rose to 91%.

On italyanmutfagi.com, average indexing time was 12 days. I added news sitemap, time dropped to 4 days for new recipes. Still 10-12 days for old recipes, no problem.

Sitemap Size Optimization

Large sitemap files create server load. Optimization techniques:

• Gzip compression: 5MB sitemap drops to 500KB
• CDN usage: Host sitemaps on CDN, Google downloads faster
• Remove unnecessary tags: <priority> and <changefreq> don't matter to Google, don't use them
• Lastmod only on real changes: If you update lastmod every day, Google doesn't trust it

I use gzip + CDN in all projects. On doktorbul.com, there were 16 sitemaps of 5MB each, after gzip each became 400-500KB. Google's crawl time decreased 40%.

If you have a large site and your sitemap structure is complex, managing it alone can be difficult. At FUTIA, we set up sitemap architecture and build automation systems. Partition strategy, news sitemap integration, image sitemap optimization, all included. You can reach us via WhatsApp: +90 532 491 17 05. Or write to info@futia.net for detailed information, let's plan your sitemap structure together.