Sure, here's an example of a valid XML sitemap for a hypothetical website with four URLs:

<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
    <url>
        <loc>https://www.example.com/</loc>
        <lastmod>2024-04-01</lastmod>
        <changefreq>weekly</changefreq>
        <priority>1.0</priority>
    </url>
    <url>
        <loc>https://www.example.com/about</loc>
        <lastmod>2024-03-15</lastmod>
        <changefreq>monthly</changefreq>
        <priority>0.8</priority>
    </url>
    <url>
        <loc>https://www.example.com/products</loc>
        <lastmod>2024-03-20</lastmod>
        <changefreq>weekly</changefreq>
        <priority>0.9</priority>
    </url>
    <url>
        <loc>https://www.example.com/contact</loc>
        <lastmod>2024-03-25</lastmod>
        <changefreq>monthly</changefreq>
        <priority>0.7</priority>
    </url>
</urlset>

In this example:

• <urlset> is the root element of the XML sitemap.
• Each <url> represents a URL on the website.
• <loc> contains the URL itself.
• <lastmod> indicates the last modification date of the page.
• <changefreq> specifies how frequently the page is likely to change (options include always, hourly, daily, weekly, monthly, yearly, and never).
• <priority> provides a hint to search engines about the relative priority of the URL compared to other URLs on the site (values range from 0.0 to 1.0).

You can replace the URLs, last modification dates, changefreq, and priorities with the actual details of your website's pages.