row_id,offer_name,tracking_url,expected_domain,source_mode,check_status,final_url,conclusion,error,skip_reason,last_checked,ready_for_ads
offer-001,Spring campaign,https://trk.example/a1,example.com,google_sheets,pending,,,,,,false
offer-002,Partner promo,https://trk.example/b7,partner.example,google_sheets,valid,https://partner.example/landing,valid,,,2026-05-26T00:00:00Z,true
offer-003,Paused offer,https://trk.example/c3,example.net,google_sheets,skipped,,,paused_by_operator,operator skipped before sync,,falseGoogle Sheets template
Copy a Google Sheets link audit template for verified redirect evidence.
This template gives spreadsheet-heavy teams a concrete row structure for link validation. It separates raw tracking input from final URL evidence, conclusion state, skip reasons, checked time, and readiness for downstream Google Ads scripts.
Direct answer
What columns should a Google Sheets link audit include?
A Google Sheets link audit should include stable row ID, offer name, tracking URL, expected domain, source mode, check status, final URL, conclusion, error, skip reason, last checked timestamp, and a script readiness flag.
Copyable artifact
Copy the sheet columns and sample rows.
Paste this CSV into a blank sheet or adapt the header row inside an existing workflow. Keep ready_for_ads false until rows have a valid conclusion and current final URL evidence.
Implementation steps
Turn a sheet into an auditable source, not hidden infrastructure.
The template is useful because every downstream decision can point to a visible row and a current conclusion.
01
Keep row_id stable
Do not depend on row number after sorting, filtering, imports, or manual cleanup.
02
Resolve before readiness
Set ready_for_ads only after final_url and conclusion are current.
03
Separate skip from failure
A deliberate operator skip should not look like a technical failure.
04
Protect script reads
Let scripts consume rows where conclusion is valid and ready_for_ads is true.
05
Upgrade when external triggers grow
Move recurring API-triggered work into platform API mode when Sheets becomes the bottleneck.
Internal links
Related operating pages
Templates work best when they are connected to the guide, integration, and tool pages that explain the surrounding workflow.
R1
Google Sheets integration
Use Sheets as the visible source while Link Peeler handles resolution and writeback.
R2
Google Sheets link operations guide
Learn the row identity and writeback discipline behind the template.
R3
Data Integration
Understand when to keep Sheets and when to move rows to hosted platform API mode.
Template FAQ
Questions about the Google Sheets template.
Can I add more columns?
Yes. Add campaign IDs, owner, schedule, or traffic source fields as needed, but keep result fields explicit and stable.
Why include ready_for_ads?
It gives campaign scripts a simple gate so they do not infer readiness from blank errors or partial data.
Should row_id be editable?
Treat row_id as stable identity. If it changes casually, writeback and audit trails become harder to trust.
Can Link Peeler write back into this structure?
Yes. The structure matches the kind of result state Link Peeler needs: final URL, conclusion, error or skip context, and checked time.