Unique Data Input Audit (Onboarding)

Unique Data Input Audit (Onboarding)

1. 01

   Inventory the client's structured data sources before any template is built

   List every database, spreadsheet, or API that holds product, location, pricing, or review data. The goal is to confirm the client has unique inputs that AI filler cannot replicate.

2. 02

   Assess data freshness and update frequency for each source

   Check whether inventory, pricing, or review feeds update daily, weekly, or monthly. Stale data produces pages that lose trust with both users and search engines.

3. 03

   Identify which data fields are truly differentiating versus generic

   Compare the client's data against what competitors publish. Unique fields like real-time availability or local pricing justify programmatic pages; generic descriptions do not.

4. 04

   Map each data field to a specific page template slot

   Define exactly which field populates the headline, body, schema markup, and meta description. This prevents the thin-content trap where every page reads the same.

5. 05

   Flag any data that requires legal or compliance review

   Pricing, reviews, and location data can carry usage restrictions. Confirm the client has rights to publish each field before automation begins.

6. 06

   Document the data pipeline and ownership in the client handoff

   Record who maintains each source, how often it refreshes, and what happens if an API breaks. This becomes the operating manual for the delivery team.