Add next-sitemap configuration

[naheel0]

🚀 BΞYTΞFLʘW | Pull Request Protocol

PR Type: (Choose one: feat | fix | refactor | docs | perf)
Issue Link: Fixes #

---

📝 System Summary

Provide a concise brief of the changes introduced to the stream.

🛠️ Technical Changes

• Logic change in ...
• New UI component added: ...
• Database schema updated: ...

🧪 Quality Assurance (QA)

• Linting: Code style matches the BeyteFlow grid.
• Build: npm run build executed without errors.
• Testing: New logic has been verified and tested.
• Dark Mode: UI is high-contrast and neon-optimized.

🖼️ Visual Evidence

If this PR affects the UI, drop a screenshot or GIF below:

---

📡 Developer Authorization

• I have performed a self-review of my code.
• My changes generate no new warnings in the console.
• I have updated the documentation (if applicable).

Authorized by: @Yourusername
Timestamp: {{ date }}

---

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
readme-gen-ai	Ready	Preview, Comment	Mar 5, 2026 7:14pm

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: fd406458-3cfa-4149-a62f-fc79ab748b94

📥 Commits

Reviewing files that changed from the base of the PR and between d0a21c2 and 0dc9525.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (2)

• next-sitemap.config.js
• public/google36b5ffdfc990e6cb.html

✅ Files skipped from review due to trivial changes (2)

• public/google36b5ffdfc990e6cb.html
• next-sitemap.config.js

---

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Build now automatically generates XML sitemaps to improve search engine discoverability and keep indexes up to date.
  • Site verification file updated to ensure continued recognition by search providers.

Walkthrough

Added a postbuild script to run next-sitemap, added next-sitemap as a devDependency, fixed siteUrl string quoting in next-sitemap config, and corrected the google site verification line in the public verification HTML.

Changes

Cohort / File(s)	Summary
Build / Sitemap package.json	Added "postbuild": "next-sitemap" script and next-sitemap ^4.2.3 to devDependencies.
Sitemap config next-sitemap.config.js	Normalized quoting for siteUrl (single to double quotes); no semantic change.
Public verification public/google36b5ffdfc990e6cb.html	Removed a leading dash from the verification line to correct the verification file content.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• add google html page #63 — edits to the same public/google36b5ffdfc990e6cb.html verification file.
• add nextjs #2 — earlier package.json/project setup changes related to adding Next.js and dependencies.

Suggested labels

enhancement

Suggested reviewers

• adithyanmkd
• jaseel0

Poem

🐰 I nibble scripts beneath the moon,

Postbuild maps hum a sitemap tune,
Lines tidy, URLs in line,
Crawlers hop and indexes shine.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description is a template with placeholders that does not provide actual details about the changes made or their rationale, though it uses the BeyteFlow protocol format.	Replace the template with concrete information about the next-sitemap configuration changes, implementation details, and rationale for the modifications.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Add next-sitemap configuration' directly matches the main change in the changeset: adding next-sitemap package and configuration files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch google

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@package.json`:
- Line 7: The package.json currently runs "npx next-sitemap" inline in the
"build" script and treats "next-sitemap" as a regular dependency; move the
"next-sitemap" package from dependencies to devDependencies and remove the
inline npx call from the "build" script (keep "next build" only), then add a new
"postbuild" script that runs "next-sitemap" so CI uses the installed
devDependency instead of npx. Update references to the "build" script and ensure
a new "postbuild" script exists, referring to the "next-sitemap" package name.
- Line 17: Update package.json to move the "next-sitemap" dependency from
"dependencies" into "devDependencies": remove the "next-sitemap" entry under
dependencies and add the same version string under devDependencies so the build
script ("build": "next build && npx next-sitemap") continues to work but the
package is not included in production runtime dependencies.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: fd338c91-abff-48b4-a00b-44ab23abb11d

📥 Commits

Reviewing files that changed from the base of the PR and between f16bd47 and c5558c8.

📒 Files selected for processing (1)

• package.json

[jaseel0]

@copilot
Verify each finding against the current code and only fix it if needed.

In @package.json at line 7, The package.json currently runs "npx next-sitemap"
inline in the "build" script and treats "next-sitemap" as a regular dependency;
move the "next-sitemap" package from dependencies to devDependencies and remove
the inline npx call from the "build" script (keep "next build" only), then add a
new "postbuild" script that runs "next-sitemap" so CI uses the installed
devDependency instead of npx. Update references to the "build" script and ensure
a new "postbuild" script exists, referring to the "next-sitemap" package name.
Verify each finding against the current code and only fix it if needed.

In @package.json at line 17, Update package.json to move the "next-sitemap"
dependency from "dependencies" into "devDependencies": remove the "next-sitemap"
entry under dependencies and add the same version string under devDependencies
so the build script ("build": "next build && npx next-sitemap") continues to
work but the package is not included in production runtime dependencies.

[Copilot]

@jaseel0 I've opened a new pull request, #69, to work on those changes. Once the pull request is ready, I'll request review from you.

[jaseel0]

@copilot
Run npm ci
npm error code EUSAGE
npm error
npm error npm ci can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with npm install before continuing.
npm error
npm error Missing: next-sitemap@4.2.3 from lock file
npm error Missing: @corex/deepmerge@4.0.43 from lock file
npm error Missing: @next/env@13.5.11 from lock file
npm error
npm error Clean install a project
npm error
npm error Usage:
npm error npm ci
npm error
npm error Options:
npm error [--install-strategy <hoisted|nested|shallow|linked>] [--legacy-bundling]
npm error [--global-style] [--omit <dev|optional|peer> [--omit <dev|optional|peer> ...]]
npm error [--include <prod|dev|optional|peer> [--include <prod|dev|optional|peer> ...]]
npm error [--strict-peer-deps] [--foreground-scripts] [--ignore-scripts] [--no-audit]
npm error [--no-bin-links] [--no-fund] [--dry-run]
npm error [-w|--workspace [-w|--workspace ...]]
npm error [-ws|--workspaces] [--include-workspace-root] [--install-links]
npm error
npm error aliases: clean-install, ic, install-clean, isntall-clean
npm error
npm error Run "npm help ci" for more info
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2026-03-05T18_56_16_093Z-debug-0.log
Error: Process completed with exit code 1.

Run npm ci
npm error code EUSAGE
npm error
npm error npm ci can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with npm install before continuing.
npm error
npm error Missing: next-sitemap@4.2.3 from lock file
npm error Missing: @corex/deepmerge@4.0.43 from lock file
npm error Missing: @next/env@13.5.11 from lock file
npm error
npm error Clean install a project
npm error
npm error Usage:
npm error npm ci
npm error
npm error Options:
npm error [--install-strategy <hoisted|nested|shallow|linked>] [--legacy-bundling]
npm error [--global-style] [--omit <dev|optional|peer> [--omit <dev|optional|peer> ...]]
npm error [--include <prod|dev|optional|peer> [--include <prod|dev|optional|peer> ...]]
npm error [--strict-peer-deps] [--foreground-scripts] [--ignore-scripts]
npm error [--allow-git <all|none|root>] [--no-audit] [--no-bin-links] [--no-fund]
npm error [--dry-run]
npm error [-w|--workspace [-w|--workspace ...]]
npm error [--workspaces] [--include-workspace-root] [--install-links]
npm error
npm error aliases: clean-install, ic, install-clean, isntall-clean
npm error
npm error Run "npm help ci" for more info
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2026-03-05T18_55_27_296Z-debug-0.log
Error: Process completed with exit code 1.

fix it

[Copilot]

@jaseel0 I've opened a new pull request, #70, to work on those changes. Once the pull request is ready, I'll request review from you.