Hey, Finfao! Welcome

Could you make sure your sitemap.xml is placed in the correct location. In Next.js, static files should be placed in the public folder? Your sitemap.xml should be at public/sitemap.xml.

Yes, I do see in the build logs that sitemap is generated. But the newer one is not visible. I even tried with postman. I tried everything that forums have.

Hi @live-play1, thanks for sharing more context. When you run the build locally, is the new sitemap.xml file generated and placed in the public/ folder?

If you need more help, please share your public repo or a minimal reproducible example. That will let us all work together from the same code to figure out what’s going wrong.

Hi, @oo-ng! Welcome to the Vercel Community

I've moved your discussion topic here as it seems related.

Do you have any error messages that you can share with us?

I am using static sitemap, so sitemap.xml is already in the public folder. Should I use dynamic or ts file to generate sitemap ?

This what I get when I build it locally, however I don't see sitemap.xml or public folder in my dist folder. I have next-sitemap.config.js if it is relevant.

1
/** @type {import('next-sitemap').IConfig} */
2
module.exports = {
3
    siteUrl: process.env.SITE_URL || 'https://liveplay.in',
4
    generateRobotsTxt: true,
5
}

Should I use sitemap.ts and genrate the sitemap, or should I have a sitemap.xml which has all the relevant things ?

On vercel it shows sitemap-0.xml as well, I have sitemap.xml which points to sitemap-0.xml and it has all the xml data. But when build is run loclly I dont see nything of that sorts.

Hi @live-play1, thanks for sharing more details.

Let's take it step by step:

1. If you're using a pre-generated sitemap.xml and keep it in the /public/sitemap.xml then that's a correct approach and should work. If that's what you're doing let's debug this.
2. If you're using the next-sitemap package, then we will have to debug it differently.

So, don't change the approach just yet. Can you confirm which method were you using initially?

hi, I see this discussion was nipped, but I'm getting a similar issue. I have a sitemap.ts that generates a sitemap xml for me, and a robots.txt that directs the robots to the correct sitemap location. The sitemap xml is available via the browser, validate-xml-sitemap gives me "no issues detected", and I get a 200 and corerct headers via a curl command. However, when I submit the sitemap to the Google Search Console, I get "Sitemap could not be read". I tried generating a static xml and saving in public/sitemap.xml, but hit the same error; I even tried generating a simple xml sitemap with just three links - public/test-sitemap.xml - but got the same error on GSC. I suspect the issue might be with Vercel accidentally blocking the crawlers? I see DDoS mitigation instances in the project's firewall (I didn't set up any firewall rules), which might be the crawlers being blocked by vercel (?..). Can you help? What should I do now?

@sfkislev Welcome to the Community!

Funnily enough I actually did this myself over the weekend for a project, and it worked fine.

Sharing my configuration, in case it's helpful:

1
import type { MetadataRoute } from "next/types"
2

3
const SITE_URL = "URL"
4

5
export default function robots(): MetadataRoute.Robots {
6
  return {
7
    rules: {
8
      userAgent: "*",
9
      allow: "/",
10
    },
11
    sitemap: `${SITE_URL}/sitemap.xml`,
12
  }
13
}
14

1
import type { MetadataRoute } from "next/types"
2

3
const WORDPRESS_API_URL = "URL"
4
const SITE_URL = "URL"
5

6
// Define types for WordPress content
7
interface WordPressPost {
8
  id: number
9
  slug: string
10
  date: string
11
  modified: string
12
  link: string
13
}
14

15
// Fetch posts from WordPress
16
async function fetchPosts(page = 1, perPage = 100): Promise<WordPressPost[]> {
17
  try {
18
    const res = await fetch(
19
      `${WORDPRESS_API_URL}/posts?page=${page}&per_page=${perPage}&_fields=id,slug,date,modified,link`,
20
      { next: { revalidate: 3600 } },
21
    )
22

23
    if (!res.ok) {
24
      throw new Error(`Failed to fetch posts: ${res.status}`)
25
    }
26

27
    const posts = (await res.json()) as WordPressPost[]
28
    const totalPages = Number.parseInt(res.headers.get("X-WP-TotalPages") || "1", 10)
29

30
    if (page < totalPages && page < 10) {
31
      // Limit to 10 pages to avoid too many requests
32
      const nextPagePosts = await fetchPosts(page + 1, perPage)
33
      return [...posts, ...nextPagePosts]
34
    }
35

36
    return posts
37
  } catch (error) {
38
    console.error("Failed to fetch WordPress posts:", error)
39
    return []
40
  }
41
}
42

43
// Fetch pages from WordPress
44
async function fetchPages(): Promise<WordPressPost[]> {
45
  try {
46
    const res = await fetch(`${WORDPRESS_API_URL}/pages?per_page=100&_fields=id,slug,date,modified,link`, {
47
      next: { revalidate: 3600 },
48
    })
49

50
    if (!res.ok) {
51
      throw new Error(`Failed to fetch pages: ${res.status}`)
52
    }
53

54
    return (await res.json()) as WordPressPost[]
55
  } catch (error) {
56
    console.error("Failed to fetch WordPress pages:", error)
57
    return []
58
  }
59
}
60

61
// Create a URL that uses the main domain
62
function createUrl(wpUrl: string): string {
63
  try {
64
    // Extract the path from the WordPress URL
65
    const urlObj = new URL(wpUrl)
66
    const path = urlObj.pathname
67

68
    // Create a new URL with the main domain
69
    return `${SITE_URL}${path}`
70
  } catch (error) {
71
    console.error("Error creating URL:", error)
72
    return wpUrl
73
  }
74
}
75

76
export default async function sitemap(): Promise<MetadataRoute.Sitemap> {
77
  // Fetch all posts and pages
78
  const [posts, pages] = await Promise.all([fetchPosts(), fetchPages()])
79

80
  // Create sitemap entries for posts
81
  const postEntries = posts.map((post) => ({
82
    url: createUrl(post.link),
83
    lastModified: new Date(post.modified || post.date),
84
    changeFrequency: "weekly" as const,
85
    priority: 0.6,
86
  }))
87

88
  // Create sitemap entries for pages
89
  const pageEntries = pages.map((page) => ({
90
    url: createUrl(page.link),
91
    lastModified: new Date(page.modified || page.date),
92
    changeFrequency: "monthly" as const,
93
    priority: 0.8,
94
  }))
95

96
  // Add homepage and feed
97
  const staticEntries = [
98
    {
99
      url: SITE_URL,
100
      lastModified: new Date(),
101
      changeFrequency: "daily" as const,
102
      priority: 1.0,
103
    },
104
    {
105
      url: `${SITE_URL}/api/feed`,
106
      lastModified: new Date(),
107
      changeFrequency: "daily" as const,
108
      priority: 0.8,
109
    },
110
  ]
111

112
  // Combine all entries
113
  return [...staticEntries, ...pageEntries, ...postEntries]
114
}
115

116

It could be helpful to look at your current set up!

hi, thanks for sharing. Here's the sitemap.ts, here's the robots.ts, and here's the resulting sitemap.xml . It's in public/sitemap.xml . Not sure how you attached the code so nicely - sorry about the links.

TL;DR: Working fine for me

I'm using next-sitemap 4.2.3 right now with no issues. My config:

1
/** @type {import('next-sitemap').IConfig} */
2
module.exports = {
3
  siteUrl: process.env.NEXT_PUBLIC_SITE_URL || "https://bestcodes.dev",
4
  generateRobotsTxt: true,
5
};

This generates public/sitemap.xml and public/sitemap-0.xml files, which are mostly empty since I recently rebuilt my website and haven't migrated all the old pages, but they work:

https://bestcodes.dev/sitemap.xml https://bestcodes.dev/sitemap-0.xml

My site is deployed with Vercel with no issues (using Next.js 15.3.0).

Logs:

next-sitemap logs from my last deployment

1
$ rm -rf public/sitemap*.xml public/robots.txt && next-sitemap
2
✨ [next-sitemap] Loading next-sitemap config: file:///vercel/path0/next-sitemap.config.js
3
✅ [next-sitemap] Generation completed
4
┌───────────────┬────────┐
5
│ (index)       │ Values │
6
├───────────────┼────────┤
7
│ indexSitemaps │ 1      │
8
│ sitemaps      │ 1      │
9
└───────────────┴────────┘
10
-----------------------------------------------------
11
 SITEMAP INDICES 
12
-----------------------------------------------------
13
   ○ https://bestcodes.dev/sitemap.xml
14
-----------------------------------------------------
15
 SITEMAPS 
16
-----------------------------------------------------
17
   ○ https://bestcodes.dev/sitemap-0.xml

Questions for people using next-sitemap:

• Are the sitemap files git-ignored? (They should be)
• What version of next-sitemap are you using?
• Do you remove current sitemap files (if they exist) before running next-sitemap? (You should)

thanks for your response! I’m not using next-sitemap, but the native MetadataRoute.Sitemap . The resulting sitemap looks fine, I think (it’s attached above). It’s quite large, at ~15k entries. I’ve also downloaded it and put it in /public, so that it behaves like a static file.

There’s a promising sign: the test-sitemap.xml I created and submitted yesterday, with only 3 entries, got a “couldn’t fetch” yesterday, and is now a green “success” at the Google Search Console, which might indicate that the “couldn’t fetch” is Google’s confusing way of saying “wait”?..? However, in the vercel firewall settings, looking at yesterday, I see 213 deinals and 588 challenges, all DDoS mitigation, and coming from the same IP (154.83.103.202 challenged, 154.83.103.113 deined). These seem like the crawlers of either the GoogleBot or the Ahref’s site audit I’ve attempted to generate, being blocked. (?)

I think the original poster, @live-play1, was using next-sitemap, so my post was to him.

As far as the “couldn't fetch” error on Google Search Console, ignore it. I get the same error every time I upload a sitemap. Just wait a few minutes and reload the page.

+1, seen this myself. What's the update today, @sfkislev? Sounds like you made some progress here.

I don't see how this could be the case given your robots file is permissive.

well.. that's confusing, and I saw it happening with my smaller test file: still, I'm about 24 hours on, and I still see a "couldn't fetch" message on the Google Search Console for my sitemap. On the Vercel firewall dashboard I still see DDoS mitigation deinals from today (though only ~150, compared to yesterday's ~2k, and to the ~15k sitemap...). I strongly suspect that this mitigation is blocking the crawlers. Don't you?