docs(evidence): close out canonical-URL finding 6631c0ab0454 against current main and live - #38
Conversation
…current main and live The code-side fix (PR #29) and CI enforcement (the 'Canonical URLs (dogfood)' guard in scripts/check-site.mjs) for dogfood finding 6631c0ab0454 ('Missing canonical URL on home') are already merged in origin/main. This lane re-verified the guarantee still holds after the subsequent page edits (internal-link cleanup, App Store citation, sitemap): - npm run check passes on all five public pages: each carries exactly one canonical link in its head, non-empty href, pointing at the absolute https://tinystudio.io address the page is served under (the .html form), no duplicates across pages. - Fresh live measurement of the deployed pages in real Chromium confirms the same: exactly one canonical link per page in head and full document, HTTP 200, production CSP, no console errors — including the home page the finding flagged (https://tinystudio.io/). Nothing further to change; the receipt now records the closeout on the current head so the finding cannot be re-opened by tracker drift.
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
|
Warning Review limit reached
Next review available in: 11 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Comment |
![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: dc1f7884d8
ℹ️ 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".
| page is served under (the `.html` form; the worker also serves extensionless | ||
| twins, and the `.html` forms 307-redirect to them — so the canonical is the | ||
| single unambiguous address for the page). It also added a source-string CI |
There was a problem hiding this comment.
For /audit, /agents, /pricing, and /specimen, this paragraph acknowledges that each .html URL returns a 307 redirect to the extensionless URL, yet calls the redirecting .html URL canonical. The measurement itself navigates the clean final URLs, and the sitemap and internal links also use those URLs, so the canonical tags point away from the resolved address and send crawlers conflicting signals. The receipt and CI guard should use the final extensionless URLs before declaring these canonicals valid.
Useful? React with 👍 / 👎.
| 3. Assert: status 200, `inHeadCount === 1`, `inDocCount === 1`, a non-empty | ||
| `href`, no console or page errors, and the `href` is unique across the five | ||
| pages. |
There was a problem hiding this comment.
When any page contains a distinct but incorrect canonical—such as another host, an unrelated path, or a relative URL—this documented verification still passes because it checks only that href is non-empty and unique. That does not reproduce the claimed guarantee that each link points to the page's canonical absolute address; add an expected URL per input page and assert exact equality.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f7f700bbb8
ℹ️ 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".
| `public/index.html` — and every other public page — served zero | ||
| `<link rel="canonical">` tags (verified against the parent of the fix commit |
There was a problem hiding this comment.
When this receipt is used as the historical baseline, the claim that every other public page served zero canonical tags is false: at a163327^, public/agent-desk.html:18 already contains a canonical link, and src/worker.js:46-47 exposes that page at /agent-desk.html and /agent-desk. Narrow this statement to the other four scoped pages or account for the Agent Desk so the closeout does not overstate the original defect.
Useful? React with 👍 / 👎.
1 participant
What
Closes dogfood finding 6631c0ab0454 ("Missing canonical URL on home", audit 20260808T074205Z-msk2fl3n) against the current head and the deployed site. The code-side fix (PR #29) and CI enforcement (the "Canonical URLs (dogfood)" guard in
scripts/check-site.mjs) were already merged; this lane records the closeout so the finding cannot be re-opened by tracker drift.Verification
npm run checkpasses on all five public pages: exactly one canonical link per page, inside<head>, non-empty href, pointing at the absolutehttps://tinystudio.ioaddress (the.htmlform), no duplicates across pages./): 1 canonical link in head and full doc, hrefhttps://tinystudio.io/, HTTP 200, CSP present, no console errors/audit,/agents,/pricing,/specimen: same — 1/1, correct.htmlhrefs, 200, CSP, no console errorsChange
docs/evidence/canonical-urls-2026-08-09.md: closeout receipt (method, results table, reproduction steps, limitation, closeout), following the meta-descriptions receipt format.Nothing further to change on the code side.