404 error in production, working fine in dev (Nuxt 3)

// nuxt.config.js

export default {
  modules: [
    '@nuxtjs/sitemap'
  ],

  sitemap: {
    routes: async () => {
      try {
        const { data } = await axios.get('https://api.example.com/routes');
        let routes = [];
        data.forEach((page) => {
          let route = { url: page.url, lastmod: page.lastModified };
          routes.push(route);
        });
        return routes;
      } catch (error) {
        console.error(error);
        return []; // Handle the error appropriately
      }
    }
  }
}

By ensuring the correct configuration and implementing the routes function correctly, you can resolve the issue of sitemap generation failures or missing routes.

Problem 2: Incorrect Sitemap XML Styling or XSL URL

Description: Another common problem with the sitemap-module is related to the styling of the sitemap XML or the XSL URL. The sitemap XML may not be properly formatted or styled, or the XSL URL may be incorrect or inaccessible.

Solution: To address this issue, review the sitemap XML formatting and styling to ensure it meets the required specifications. Double-check the content and structure of the generated XML to ensure it conforms to the sitemap protocol. Additionally, verify the XSL URL in the configuration to ensure it points to the correct location and the XSL file is accessible.

Here’s an example of specifying the XSL URL correctly in the nuxt.config.js file:

// nuxt.config.js

export default {
  modules: [
    '@nuxtjs/sitemap'
  ],

  sitemap: {
    xslUrl: '/sitemap_style.xsl',
    // ... other configuration options
  }
}

Ensure that the sitemap_style.xsl file exists in the specified location and is accessible from the defined URL. Correcting any formatting or styling issues with the sitemap XML and ensuring the correct XSL URL will resolve the problem of incorrect sitemap XML styling.

Problem 3: Sitemap Not Being Generated Automatically

Description: Sometimes, the sitemap is not automatically generated when running the Nuxt.js application, even though the @nuxtjs/sitemap module is installed and configured correctly.

Solution: To resolve this issue, it may be necessary to manually trigger the sitemap generation process. Nuxt.js provides a built-in command, nuxt generate, that generates the static files for the application, including the sitemap.

Execute the following command in the terminal to generate the sitemap manually:

nuxt generate

This command will run the static site generation process and include the sitemap generation as part of the build process. Once the command completes successfully, the sitemap should be generated and available at the specified URL.

By manually triggering the sitemap generation process using the nuxt generate command, you can ensure that the sitemap is generated correctly, even if it is not being generated automatically.

// Example configuration for generating sitemap.xml
export default {
  modules: [
    '@nuxtjs/sitemap'
  ],

  sitemap: {
    // Configuration options for URL inclusion, priority, etc.
  }
}

// Example dynamic route generation in sitemap configuration
export default {
  modules: [
    '@nuxtjs/sitemap'
  ],

  sitemap: {
    routes: async () => {
      // Fetch data from API or database
      const posts = await fetchPosts();

      // Generate routes based on fetched data
      const routes = posts.map((post) => ({
        url: `/posts/${post.id}`,
        lastmod: post.updatedAt
      }));

      return routes;
    }
  }
}