The documentation section turns Link Peeler's public promise into implementation paths. Operators can start with the desktop client, connect Google Sheets, wire Google Ads Scripts, or trigger link fetch jobs through signed API Links.
Link Peeler documentation covers quickstart setup, desktop client linkage, Google Sheets row mapping, Google Ads Scripts consumption, and API Link authentication. Each document explains the source, execution, result, and safety boundary for one implementation path.
The documentation hub now behaves like an implementation console. Pick the system being connected and the page explains the setup boundary, proof state, and next document before the visitor jumps into a child doc.
Each mode maps a setup query to the implementation document, verification object, and downstream handoff that matters next.
Send them to quickstart when the account, desktop, source, first run, and review step all need to be understood together.
Create an account, download desktop, choose a source, run link resolution, and review verified state.
Open docInstall the local execution engine and understand how outbound polling, device state, and account linkage work.
Open docMap source rows, result fields, row identity, and writeback rules for spreadsheet workflows.
Open docLet scripts consume verified rows before final URL suffix updates touch campaign state.
Open docSign external requests with HMAC, timestamp, nonce, and idempotency controls.
Open docThe hub gives crawlers and operators a stable mental model: web identity, desktop execution, source state, result evidence, signed triggers, and campaign handoff are different responsibilities that must connect cleanly.
Login, membership, private downloads, billing, and account readiness live behind the same web boundary.
The desktop doc explains why local redirect resolution and cloud-side device state are both part of the architecture.
Sheets and platform API mode represent different source boundaries, but both need stable row identity and result fields.
Verified state should include final URL, conclusion, error or skip reason, checked time, and script readiness.
Google Ads Scripts should filter verified rows and keep failed, skipped, unknown, and stale rows out of mutation.
API Links docs make timestamp, nonce, HMAC, idempotency, quota, and desktop pickup explicit.
The connected system changes, but the workflow stays consistent: source rows enter, desktop execution resolves, result state returns, and external scripts consume verified evidence.
Set account boundary
Use the website for identity, membership, downloads, and plan state.
Attach desktop
Let the local client pull work outbound and resolve links with browser context.
Choose source
Start with Google Sheets or move to platform API mode when hosted state is needed.
Return evidence
Store final URL, conclusion, error, skip reason, and checked time.
Consume safely
Let scripts or API clients act only on verified state.
Docs pages should answer immediate setup questions while linking forward to the exact system boundary: account, desktop, Sheets, Ads Scripts, API Links, and first verified row state.
Use quickstart when the visitor needs the shortest path from web account to first verified link result.
Open quickstartUse desktop client setup when local execution, outbound polling, device state, and sign-in boundaries need explanation.
Open desktop docsUse Google Sheets setup when spreadsheets remain the operator-owned source and writeback surface.
Open Sheets docsUse Google Ads Scripts setup when campaign mutation must read only validated rows and readiness gates.
Open script docsUse API Links authentication when external systems need HMAC, nonce, idempotency, quota, and queue boundaries.
Open API docsUse the account center after login to connect docs to live readiness state.
Open accountDocumentation pages target setup queries that marketing pages usually cannot answer completely.
The hub repeats the most valuable setup questions in concise answer blocks while each child doc carries the deeper implementation detail.
It covers quickstart setup, desktop client linkage, Google Sheets row mapping, Google Ads Scripts consumption, and API Links authentication.
Create a web account, download and sign into desktop, connect a source, resolve a small batch, and review verified state before scripts consume it.
It pulls queued work outbound, follows tracking redirects locally, returns structured conclusions, and exposes device linkage to the account center.
Sheets should use stable row IDs, tracking URLs, expected context, final URL, conclusion, error or skip reason, checked time, and readiness fields.
Scripts should fetch verified rows, filter to current valid conclusions, dry-run campaign decisions, skip unsafe rows, and log each mutation source.
API Links use an API key, HMAC signature, timestamp, nonce, idempotency key, quota checks, and queueing for outbound desktop pickup.
Start with the quickstart, then open the setup doc for the source system that owns your rows today.
No. The docs explain the operating model. Pro becomes important for unlimited offers, hosted state, and production API Links.
No. Templates provide copyable artifacts. Docs explain the surrounding setup, safety gates, and operating decisions.
Public docs help operators, search engines, and AI assistants understand how the product is actually implemented.