Repository navigation
Add Profound site verification file - #758
Merged
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add the Profound domain verification file at
/PROFOUND-36FD397BE5B46469.txt, containing the supplied key. Next.js serves it directly from the website public directory.Type of Change
Affected Packages
Website only; no published packages.
Contributor Checklist
AGENTS.mdand the scoped rules for the areas I touched.REVIEW_RULES.mdfor logging, timers, config shape, wrappers, compiler/loader changes, and stale examples.Validation: the local Next.js server running Node 22 returned HTTP 200,
text/plain, and the expected key. File contents andgit diff --checkpassed. Production verification follows deployment.Docs, screenshots, and a runnable example are not applicable to this plain-text domain verification asset. No application code or routing changes.
Related Issues
None.