site: add robots.txt and sitemap.xml - #4
Conversation
The nginx fallback served index.html for /sitemap.xml, so Search Console could not accept a sitemap for the site. One URL, the landing page.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 58a9c6cea9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| User-agent: * | ||
| Allow: / | ||
|
|
||
| Sitemap: https://floodwall.ai/sitemap.xml |
There was a problem hiding this comment.
docs tree
These files exist only under Vite's publicDir, while site/vite.config.ts builds the publishable output into the tracked docs/ directory and the CI workflow merely builds without deploying its ephemeral output. Because this commit adds neither docs/robots.txt nor docs/sitemap.xml, the production site continues serving its fallback HTML for these paths, so the Search Console problem described by the commit remains unresolved. Commit the generated docs files as previous site changes do, or add an actual build-and-deploy workflow.
Useful? React with 👍 / 👎.
1 participant
The nginx fallback served index.html for /sitemap.xml, so Search Console
could not accept a sitemap for the site. One URL, the landing page.