# 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.

Category: Audits and budgets
Source: https://letsship.ai/use-cases/close-metadata-and-crawlability-findings
Published: 2026-08-25

## Goal

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.

## Prompt

Copy this to an agent to open the ticket:

```text
Create a Linear issue in my team and assign it to the SHIP agent.

Title: Fix the metadata findings on {surface}

Description: 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

Before you create the issue, run a crawl audit against this repository's public pages and replace {surface} with the section with the most findings.
```

## 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.