Website Content Collection to Google Sheets
A website content spreadsheet should show which page package a response describes and what the build team still needs. Copy approval, available images and completeness are separate facts. Receiving a row does not make a page ready to build or publish.
Use one submission per page package
Start with the Website Content Collection template. It asks for the page name and planned URL, purpose, copy-document link, approval status, image links, missing material and the content approver. Keep the version in the linked document or record so reviewers can identify the material they actually assessed.
The native Sheets connection creates a new spreadsheet with a Responses tab after authorization. Questions become columns automatically; you do not manually map them to an existing sheet. Save the form before connecting, then use Open spreadsheet from its Integrations card. Google Sheets is included on Zunoform Free.
A page package and its review record
Scroll sideways to read all three columns.
| Form input | Review task | Evidence to record |
|---|---|---|
| Page name and planned URL | Identify the page in the agreed site scope | Page reference and the relevant response ID. |
| Link to the copy document | Open the intended version and check access | Document version and the reviewer’s access result. |
| Copy approval status | Confirm which copy was approved | Named approver and version, rather than a blanket site approval. |
| Image links and permissions owner | Check whether usable assets and information are present | Missing item and person responsible for supplying it. |
| Missing material and build instructions | Decide whether the package can proceed | Reviewer’s readiness status and next action. |
Set up the receiving workflow
Finish the form
Use clear page and version instructions. A URL field validates an entry’s format, not whether the receiving team can open the document.
Connect and test
Save the form, authorize Google Sheets, enable the connection and submit fictional page details through a saved test form. Open the created spreadsheet and match the row to the saved response.
Add a Review tab
Record Source Response ID, Page reference, Reviewed version, Readiness, Missing item, Owner and Next check. These are internal columns maintained by your team, not fields the client must complete.
Review the actual package
Open source links with the access the delivery team will use. Check the agreed scope and version before marking the package ready.
Illustrative page review: a services page
A client submits /services with an approved copy document, a folder of draft images and a note that captions are missing. The response is successfully delivered. The reviewer records “Waiting for assets,” assigns the image owner and schedules a follow-up. The copy can be approved while the complete page package is still blocked.
If the client later supplies final images, use a new submission or a clearly recorded internal update. Link the new response to the same page reference and mark which package is current. Do not count two submissions for one page as two completed pages.
Protect the source tab from accidental changes
Responses is integration-managed. Its header follows the form’s current question labels and order, while existing data rows are not remapped when the form changes. Avoid renaming or reordering fields in a live collection workflow without a versioning plan. Keep your review columns and formulas in another tab.
Do not sort a single source column independently, because it separates values that belong to one response. Use a review view that preserves the Response ID relationship. The integration appends new rows; it does not fetch linked documents, inspect asset rights or publish website content.
Tests before the team relies on the queue
Scroll sideways to read all three columns.
| Test input | Expected source result | Manual check |
|---|---|---|
| A page with missing images | The submitted missing-item answer is present | Readiness remains a reviewer decision. |
| A second version of the same page | A separate response record appears | The current package is explicitly identified. |
| A source URL inaccessible to the reviewer | The URL text can still arrive | The access problem is recorded before build. |
| A saved response without a destination row | The source response remains the recovery reference | Inspect connection state and check duplicates before recovery. |
Start with the matching form
Questions people ask
Does Sheets check whether a page is complete?
No. The row contains submitted answers. A reviewer must check the actual files, access, scope and current version.
Can several pages share one response?
Use separate responses when pages have different source files, owners or readiness states. This makes each review record easier to identify.
Will previous responses backfill when I connect?
No automatic backfill is provided by the current connection. Any separate import needs a clear source reference and duplicate check.
Keep reading
Better forms.
Better data.
Start with a conversation, a document or a single page. Unlimited forms and 500 responses per month on Free. No card required.