Close the metadata and crawlability findings for one public surface
Missing titles, descriptions, and canonical links on a public surface, fixed and re-audited clean.
The ticket
Fix the metadata and crawlability findings on one public surface.
Acceptance criteria
- Every page has a unique title and description
- Canonical links are present and correct
- Structured data validates where it is used
- The audit is rerun and reports clean
What lands as proof
A clean re-run of the same audit, attached alongside the original findings.
Why teams defer it
- Nothing breaks, so it stays invisible until somebody looks at search performance.
- It is split across a framework's metadata layer and individual pages, so the fix is not in one place.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: fix the metadata and crawlability findings on one public surface. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means each finding fixed and the audit rerun clean, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- None is required before the run starts. Every claim this ticket makes can be checked by machine, so the agent works straight through and a person reviews the finished pull request like any other.