Keep canonical metadata in the document head - #1287
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
5 Skipped Deployments
|
🦋 Changeset detectedLatest commit: aa42fcf The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
Pull request overview
This PR updates the status.app Next.js configuration to prevent metadata (notably rel="canonical") from being streamed into the <body> for bot user agents, keeping canonical and other SEO-critical tags consistently in the document <head> to address Search Console canonical detection issues (refs #1262).
Changes:
- Configure Next.js
htmlLimitedBotsto disable streaming metadata behavior for bot requests. - Add a changeset to ship the
status.apppatch release.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| apps/status.app/next.config.mjs | Adds htmlLimitedBots config to keep SEO metadata (e.g., canonical) in <head> for bots. |
| .changeset/calm-bots-listen.md | Declares a patch changeset for status.app describing the SEO metadata behavior change. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Refs #1262
What changed
Next.js can stream metadata into
<body>for some bots. Search Console then missed the canonical URL on some pages.This PR disables metadata streaming for all bots, so canonical and other SEO tags stay inside
<head>.Related docs:
htmlLimitedBots