# Improve

> Use the content audit buckets, decay and refresh, the site pages crawl, internal link suggestions and outgoing link checks to decide what to fix next.

**In short:** The Improve hub tells you which existing pages to fix next, using your Search Console data and the results SerpDad already holds. Each page shows the numbers and the rule that placed it. SerpDad suggests next steps. It never promises a ranking change.

## Content audit

Open **Improve > Content audit**. The audit needs Search Console. See [Measure](../measure/).

It compares each page's last 28 synced days with the 28 days before. Every site page with data in the last 90 days lands in one bucket. Buckets are checked in this order:

| Bucket | Rule | Next step |
|---|---|---|
| Prune | No clicks in 90 days | Merge |
| Decay | Clicks down more than 25%, from at least 100 clicks before | Refresh |
| Quick win | Average position 4 to 10, with impressions rising | Optimize |
| Striking distance | Average position 11 to 20 | Optimize |
| Rework | At least 100 impressions, with fewer than 0.5% of them clicked | Optimize |
| Monitor | Clicks moved 10% or more, or the position moved more than 3 positions or 8% | None |
| Keep | Steady | None |

**Seasonal guard:** with 12 or more months of data, a dip that matches the same weeks last year goes to Monitor, not Decay.

Each page shows the Search Console rows that placed it. Lists show up to 150 rows. Select export to download every row.

## Decay and refresh

Open **Improve > Decay and refresh**, or select a Decay row in the audit.

For a decaying page, SerpDad shows the stored top 10 from before the drop and a fresh top 10, side by side. Changed rows are marked. SerpDad names what changed in the results:

- New AI Overview
- Format change
- New competitor
- Intent shift

These describe what changed in the results. They are not a claim about why the page lost clicks.

To refresh the page:

1. Read the estimate.
2. Start the refresh. SerpDad rebuilds the brief from the new results.
3. Only changed sections are drafted again. Unchanged signed sections stay signed. Changed sections need sign-off again.

The "Refresh pages that are losing traffic" job can find these pages every week. See [Jobs and workflows](../workflows/).

## Site pages

Open **Improve > Site pages** to crawl your site.

- The crawl runs on DataForSEO On-Page, on your own DataForSEO key. SerpDad's servers never crawl your site.
- The estimate shows before the crawl starts.
- An optional JavaScript rendering mode costs about 10 times more.
- One crawl stops at 10,000 pages.
- Estimated cost: about $0.00015 per page, or $0.0015 per page with JavaScript rendering.

The table shows each page's status, title, links in and links out, whether it matches a planned page, and its clicks.

## Internal links

Open **Improve > Internal links**. Each suggestion comes with its evidence:

- The two pages share top 10 results.
- The target is a secondary keyword of the source page.
- The two pages sit in the same hub.

A link that already exists in the crawl is never suggested. The page also lists broken internal links with a suggested replacement, orphan pages with two suggested source pages, and thinly linked pages. You can mark a suggestion as added, dismiss it or copy it.

### Link rules in briefs and drafts

The "Plan internal links" step adds an internal link plan to briefs and places links in drafts.

- Anchors come from each target page's own keywords.
- No anchor text is used twice in the project.
- By default, each page gets 3 to 5 contextual links.
- In drafts, a link is placed only where its anchor reads naturally.

## Outgoing links

Open **Improve > Outgoing links**. SerpDad checks every outgoing link in your pages, briefs and articles from its own servers. Private addresses are blocked.

| Rule | Value |
|---|---|
| Dead link | After three failed tries |
| Redirects | Followed up to 5 hops |
| Share links | Resolved to their final page |
| Order | Dead links behind a fact come first |

The page also shows your citation mix by source type.

## Next actions

**Home > Next actions** gathers what to do next across your projects, grouped as Decide, Plan and write, and Improve. Each item has a short reason, its source, a receipt and one button. You can snooze an item to a date or dismiss it. A dismissed item comes back only if a later run changes its numbers. Next actions never act for you.

## Related

- [Measure](../measure/)
- [Drafts and sign-off](../drafts-and-sign-off/)
- [Briefs](../briefs/)
- [Jobs and workflows](../workflows/)