How to use a Righthand with Squarespace

Quick answer

Use Righthand to build a Squarespace content inventory from a limited export and approved page links. Do not treat that export as a complete portable website.

Start with a reviewable deliverable, keeping Squarespace as the accepted home for its records. This guide uses an explicitly approved snapshot or browser read; it does not assume that every provider API action is exposed by your Righthand connection.

Evidence and access

Squarespace documents exporting certain site content to XML, with limitations. See the official Squarespace reference. Provider capabilities and Righthand's available tools are separate checks.

Scope the input to one site and its approved page list, navigation map, and current asset versions; avoid account-wide assumptions. Verify the required tools and owner-approved scope through Righthand integrations; use the supplied packet when a native read is unavailable.

Define the objects and authority

Include these fields in the working input: page URL, content type, title, export ID, linked image, current public status. These are the requested review columns, not a promise that every provider endpoint returns them under those exact names.

Layouts, commerce settings, and excluded material need separate assessment. The site owner decides migration and publishing scope.

Illustrative first-run brief

Use the owner-provided Squarespace snapshot or approved read-only view. Compare the XML list with twenty approved URLs. Identify absent content, uncertain image links, and titles needing review. Prepare an inventory only. Run once for the agreed sample, using America/Los_Angeles for the review deadline and preserving source timestamps separately. Return the draft in this conversation by Friday at 3 PM Pacific for the site owner to review. Include source references and missing fields. Do not write records, spend money, change permissions, or send external messages. Stop and report an unavailable source rather than substituting another account.

Expected result and verification

An exported article appears in the inventory; a page outside export scope is marked manual review, not deleted.

Check one included page and one omitted page to verify the export boundary. Record the source cutoff, applied filters, and items excluded from the sample. The reviewer should be able to follow each consequential finding back to an original object. A well-written summary is not evidence that a proposed action happened. If a later write is authorized, verify its specific result separately before changing the task's status.

Illustrative input and draft output

These synthetic entries show the requested review, not live account results or a provider field schema.

Common failure and recovery

Linked assets can remain externally hosted. Record original URLs and request approved copies before describing a migration as complete.

If the supplied screenshot cannot identify a page version, ask the site owner for a dated reference and mark the copy comparison provisional.

FAQ

What should the reviewer verify first?

Verify the page's intended navigation location and actual destination. A page listed in a packet may still be hidden or linked incorrectly.

How should a repeat run be scoped?

For every site review, retain page references, navigation state, and screenshot date. Recheck changed links and visibility rather than treating yesterday's menu as current.

For connection and permission details, use Righthand Docs. Review Pricing alongside any separate provider charges before expanding the workflow.