There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes.

https://community.vercel.com/t/debugging-404-errors/437

Vercel Community

Debugging 404 Errors

Sometimes things don’t go as expected when deploying a website. If you see a 404 on your site, that means the page or resource couldn’t be found. There are...

A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

Hey! The issue is that your sitemap.ts is trying to fetch dynamic data at build time, which might be failing on Vercel. Here’s how to fix it:

Option 1: Force Dynamic Rendering Add this to the top of your sitemap.ts file to make it render at request time:

1
export const dynamic = 'force-dynamic'

Option 2: Add Error Handling Wrap your data fetching in try/catch to prevent build failures:

1
export default async function sitemap(): Promise<MetadataRoute.Sitemap> {
2
  const domain = process.env.NEXT_PUBLIC_SITE_URL;
3
  
4
  try {
5
    const audioList = await getBayaanSlug();
6
    const audioSitemap = audioList?.items?.map((audio: any) => ({
7
      url: `${domain}/audio/${audio?.slug}`,
8
      lastModified: audio?.sys?.publishedAt,
9
      changeFrequency: 'yearly' as const,
10
      priority: 0.8,
11
    })) || [];
12
    
13
    return [
14
      {
15
        url: domain || '',
16
        lastModified: new Date(),
17
        changeFrequency: 'monthly',
18
        priority: 1,
19
      },
20
      ...audioSitemap,
21
    ];
22
  } catch (error) {
23
    console.error('Failed to fetch audio data for sitemap:', error);
24
    // Return at least the homepage
25
    return [{
26
      url: domain || '',
27
      lastModified: new Date(),
28
      changeFrequency: 'monthly',
29
      priority: 1,
30
    }];
31
  }
32
}

Also check that your getBayaanSlug() function works correctly in production - it might need environment variables or API endpoints that aren’t available during build time.

updated sitemap with the try catch blcok. check below deployment logs.

BUILD LOGS

1
Route (app)
2

3
┌ ƒ /
4

5
├ ○ /_not-found
6

7
├ ○ /about
8

9
├ ● /audio/[slug]
10

11
│ ├ /audio/how-to-become-close-to-allah
12

13
│ ├ /audio/why-dont-we-see-the-promise-of-allah
14

15
│ ├ /audio/hashar-hisaab
16

17
│ └ [+71 more paths]
18

19
├ ○ /robots.txt
20

21
└ ƒ /sitemap.xml

ISSUE

navigating to sitemap still gives 404 page not found. I cant even see the path being logged on vercel. I tried npm run build locally. Sitemap is working fine except on vercel

@anshumanb any idea. can it be an issue on vercel itself because you can't even see log of the sitemap being acess. The build logs shows sitemap but acessing gives 404. All env variables and endpoints seems to work correctly.

It's worth trying this: https://community.vercel.com/t/unable-to-access-sitemap-xml-and-robots-txt/3673/4?u=pawlean

Vercel Community

Vercel Community

Connect, learn, share projects, and get community support

I'm having the same issue and need a solution that does involve adding code as I don't have access to that either.

@pawlean @anshumanb any suggestions ?

Hey, @oumeir-rengony!

I dug into the repo and the deployed site a bit more, and this no longer looks like a dynamic-data-fetch problem.

What I found:

• app/sitemap.ts exists and Vercel is recognizing it during build as ƒ /sitemap.xml
• robots.txt is working fine in production
• but https://www.ulama-moris.org/sitemap.xml is being served as Vercel’s /404
• there’s no obvious middleware, vercel.json, rewrite, redirect, or route conflict in the repo that would explain only sitemap.xml failing
• the project was also upgraded from next 14.2.35 to next 16.2.0 on April 15, 2026, which makes a framework regression feel plausible

Because of that, my strongest recommendation is to avoid the metadata file route for this case and replace:

app/sitemap.ts

with:

app/sitemap.xml/route.ts

and return the XML manually from a GET() handler.

Why I think this is the safest workaround:

• it keeps the sitemap dynamic
• it bypasses the Next metadata-route pipeline entirely
• it gives you a normal route handler, which is much easier to debug on Vercel

So in short: I don’t think the main issue is the dynamic fetch itself anymore. I think the issue is specifically with how app/sitemap.ts is being served in production for this app/version combination.

What that would look like:

Create app/sitemap.xml/route.ts, like:

1
import { getBayaanSlug } from '@/services/bayaans/bayaan.service';
2

3
export const dynamic = 'force-dynamic';
4

5
function escapeXml(value: string) {
6
  return value
7
    .replace(/&/g, '&')
8
    .replace(/"/g, '"')
9
    .replace(/'/g, ''')
10
    .replace(/</g, '&lt;')
11
    .replace(/>/g, '&gt;');
12
}
13

14
export async function GET() {
15
  const domain = process.env.NEXT_PUBLIC_SITE_URL || 'https://www.ulama-moris.org';
16

17
  try {
18
    const audioList = await getBayaanSlug();
19

20
    const urls = [
21
      {
22
        loc: domain,
23
        lastModified: new Date().toISOString(),
24
        changeFrequency: 'monthly',
25
        priority: '1.0',
26
      },
27
      ...((audioList?.items || []).map((audio: any) => ({
28
        loc: `${domain}/audio/${audio?.slug}`,
29
        lastModified: audio?.sys?.publishedAt || new Date().toISOString(),
30
        changeFrequency: 'yearly',
31
        priority: '0.8',
32
      }))),
33
    ];
34

35
    const xml = `<?xml version="1.0" encoding="UTF-8"?>
36
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
37
${urls
38
  .map(
39
    (url) => `  <url>
40
    <loc>${escapeXml(url.loc)}</loc>
41
    <lastmod>${url.lastModified}</lastmod>
42
    <changefreq>${url.changeFrequency}</changefreq>
43
    <priority>${url.priority}</priority>
44
  </url>`
45
  )
46
  .join('
47
')}
48
</urlset>`;
49

50
    return new Response(xml, {
51
      headers: {
52
        'Content-Type': 'application/xml; charset=utf-8',
53
        'Cache-Control': 'public, s-maxage=3600, stale-while-revalidate=86400',
54
      },
55
    });
56
  } catch (error) {
57
    console.error('Failed to generate sitemap.xml:', error);
58

59
    const fallbackXml = `<?xml version="1.0" encoding="UTF-8"?>
60
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
61
  <url>
62
    <loc>${escapeXml(domain)}</loc>
63
    <lastmod>${new Date().toISOString()}</lastmod>
64
    <changefreq>monthly</changefreq>
65
    <priority>1.0</priority>
66
  </url>
67
</urlset>`;
68

69
    return new Response(fallbackXml, {
70
      headers: {
71
        'Content-Type': 'application/xml; charset=utf-8',
72
      },
73
    });
74
  }
75
}

And remove or rename app/sitemap.ts so there isn’t any conflict.

Hey, @iggy888-6163! This seems like a separate issue. Feel free to create a new post in #v0 :)

The same issue. i do think this is a regression with nextjs itself. for now im manually adding a script to add the sitemap after the build.