<b>The data-source freshness contract</b>

<b>The data-source freshness contract</b>

Every pSEO build runs on a feed. Treat the feed like a vendor with an SLA, in writing, before launch.

Define four numbers per source:

1. Refresh cadence — Owner: data lead. How often does the source update? Daily, weekly, never. Gate: documented or the source is rejected.

2. Staleness ceiling — Owner: SEO. Maximum age a value can show on-page before it must be hidden. Example: a "price" field older than 30 days renders as "check current" instead of a stale number.

3. Null-rate threshold — Owner: data lead. If more than 20 percent of rows are missing a required field, the template degrades to a reduced layout, not a blank slot.

4. Drift alarm — Owner: SEO. A daily job counts rows; a swing over 15 percent fires an alert before pages re-render.

— Stale numbers in titles get you a manual penalty faster than thin content does
— The staleness ceiling protects you when the vendor silently stops updating

Ship gate: don't publish until all four numbers are signed off.