Next.js部署AWS Amplify后着陆页500错误及谷歌Ads索引问题求助

问题背景 #

• 基于Next.js开发的网站部署到AWS Amplify后，页面加载时返回500错误，但可视内容显示正常
• 关联谷歌Ads时，平台提示广告机器人无法抓取网站内容
• 仅修改了app.locale格式设置并添加语言切换按钮，未改动网站定位相关配置
• 查看.env日志仅显示本地机器变量，未找到环境变量变更记录；重新部署项目无效
• 网站链接：https://www.bocancorporation.com/es/landing/software
• 最新部署日志：

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:
git switch -c <new-branch-name>

Or undo this operation with:
git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at 8f16a14 Update page.jsx

[INFO]: Successfully cleaned up Git credentials
[INFO]: # Checking for Git submodules at: /codebuild/output/src3731319908/src/BocancorpPage/.gitmodules
[INFO]: # Retrieving environment cache...
[WARNING]: ! Unable to write cache: {"code":"ERR_BAD_REQUEST","message":"Request failed with status code 404"})}
[INFO]: ---- Setting Up SSM Secrets ----
[INFO]: SSM params {"Path":"/amplify/d2bxu2qqh4oj5l/main/","WithDecryption":true}
[WARNING]: !Failed to set up process.env.secrets
[INFO]: # No package override configuration found.
[INFO]: # Retrieving cache...
[INFO]: # Extracting cache...
[INFO]: # Extraction completed
[INFO]: # Retrieved cache
[INFO]: ## Starting Backend Build
## Checking for associated backend environment...
## No backend environment association found, continuing...
## Completed Backend Build
[INFO]: ## Starting Frontend Build
# Starting phase: preBuild
[INFO]: # Executing command: npm install
[INFO]: up to date, audited 439 packages in 3s
[INFO]: 135 packages are looking for funding
run `npm fund` for details
[INFO]: 9 vulnerabilities (4 moderate, 5 high)
To address issues that do not require attention, run:
npm audit fix
To address all issues, run:
npm audit fix --force
Run `npm audit` for details.

可能的原因分析 #

1. Git Detached HEAD状态：部署时处于分离头指针状态，可能导致Amplify无法正确追踪分支变更，破坏构建一致性
2. SSM Secrets加载失败：日志中Failed to set up process.env.secrets警告，可能导致服务端渲染阶段依赖环境变量的代码抛出未捕获异常，触发500错误（前端内容正常可能是因为客户端渲染降级生效）
3. Next.js国际化配置问题：修改app.locale后，服务端渲染(SSR/SSG)的语言路由处理可能出现逻辑错误，返回500状态码但客户端hydration后正常显示
4. 谷歌Ads机器人抓取问题：页面返回500状态码会直接被机器人判定为不可用，导致抓取失败

排查与解决步骤 #

1. 修复Git Detached HEAD状态 #

• 本地切换到部署用主分支：git switch main
• 同步远程分支：git pull origin main
• 重新推送代码触发Amplify构建，验证日志中是否不再出现detached HEAD提示

2. 排查环境变量与SSM Secrets问题 #

• 登录AWS Amplify控制台，进入项目环境变量配置页，检查所需变量是否正确配置
• 确认SSM参数路径/amplify/d2bxu2qqh4oj5l/main/存在且Amplify服务角色拥有ssm:GetParametersByPath权限
• 构建时添加环境变量日志：在next.config.js或构建脚本中加入console.log(process.env)，查看Amplify构建时的变量加载情况
• 若无需SSM Secrets，可在Amplify构建设置中禁用该功能或移除相关代码依赖

3. 修复Next.js国际化配置问题 #

• 检查app.locale相关代码，确保服务端组件未出现未捕获的undefined错误
• 验证app/[lang]/路由结构符合Next.js App Router国际化规范
• 本地模拟生产构建：npm run build && npm start，复现500错误后调试

4. 解决谷歌Ads机器人抓取问题 #

• 先修复500错误，确保页面返回200状态码（通过浏览器Network面板确认）
• 使用谷歌Search Console的URL检查工具验证页面可访问性
• 检查robots.txt，确保未禁止AdsBot-Google访问
• 确认页面lang属性、meta标签配置正确

补充信息需求 #

若以上步骤无效，请提供：

• Next.js版本号
• next.config.js中的国际化配置代码
• 浏览器Network面板的页面请求详情（状态码、响应头）
• Amplify项目的amplify.yml构建配置

内容的提问来源于stack exchange，提问作者SKILLEMPRESARIO