{
  "locale": "en",
  "group": "squarespace-seo",
  "manualOnly": true,
  "providerRequests": 0,
  "fictional": true,
  "verified": false,
  "title": "Squarespace SEO: a practical website launch review",
  "notice": "Fictional website review, not a Squarespace account audit. Example observations are not measured rankings, traffic or indexing results.",
  "diagram": {
    "title": "Squarespace SEO: a practical website launch review",
    "caption": "Fictional website review, not a Squarespace account audit. Example observations are not measured rankings, traffic or indexing results.",
    "relationLabel": "Source and destination relationships",
    "nodes": [
      {
        "id": "home",
        "title": "Homepage",
        "body": "Introduces the studio and links to the current workshop."
      },
      {
        "id": "old",
        "title": "Old /classes path",
        "body": "An obsolete leaflet address, not the current page."
      },
      {
        "id": "workshop",
        "title": "Workshop destination",
        "body": "/workshops/printmaking contains the class and booking route."
      }
    ],
    "relations": [
      {
        "id": "internal",
        "from": "home",
        "to": "workshop",
        "label": "Relevant internal navigation"
      },
      {
        "id": "redirect",
        "from": "old",
        "to": "workshop",
        "label": "Permanent redirect after the old page is disabled"
      }
    ]
  },
  "exampleCode": "/classes -> /workshops/printmaking 301",
  "columns": [
    "Inspection step",
    "Example observation",
    "Evidence to record",
    "Action if it differs"
  ],
  "rows": [
    {
      "id": "home",
      "title": "Homepage /",
      "values": [
        "Generic studio description in the example",
        "Saved homepage description and rendered page",
        "Describe the studio distinctly; do not reuse the workshop summary"
      ]
    },
    {
      "id": "workshop",
      "title": "Workshop page",
      "values": [
        "Useful class details and a homepage link",
        "Title, description, visible heading and booking route",
        "Resolve mismatched dates or unavailable booking before promotion"
      ]
    },
    {
      "id": "privacy",
      "title": "Booking confirmation",
      "values": [
        "Customer details should remain private",
        "Signed-out access test and chosen access control",
        "Restrict access; a search-hiding toggle is not privacy protection"
      ]
    },
    {
      "id": "redirect",
      "title": "Old /classes URL",
      "values": [
        "Leaflet still uses the obsolete path",
        "Old response, 301 destination and final enabled page",
        "Disable or remove the old page, add mapping, update owned links"
      ]
    },
    {
      "id": "sitemap",
      "title": "Sitemap",
      "values": [
        "Check the intended current workshop URL",
        "Primary-domain sitemap and review date",
        "Investigate missing eligible pages; do not record inclusion as indexing proof"
      ]
    }
  ],
  "example": "Our fictional printmaking studio uses studio.example. Its homepage links to /workshops/printmaking, while an old leaflet points to /classes. The launch worksheet assumes that the workshop has a useful title and description but the homepage still has generic copy. A booking confirmation page contains customer details and must not become a public resource. The five rows below record observations and corrective actions; they are an exercise you can replace with your own dated evidence.",
  "decision": "Keep customer information behind appropriate access controls. Hiding a page from search results requests exclusion; it does not authenticate visitors or make a known URL secret. For a permanent move, Squarespace URL mappings use the old path, an arrow, the new path and 301. The old page must be deleted or disabled for that mapping to work; confirm the destination is enabled first. Our escaped example changes nothing here. Also update the homepage and any links you control to the new URL. A 301 redirect does not guarantee unchanged search rankings.",
  "checklist": [
    "Record the platform version and exact page type before following an editor path.",
    "Write different descriptions for the homepage and the workshop.",
    "Test restricted pages while signed out; keep customer data out of the review export.",
    "Verify the old path, one intended redirect and the final booking destination.",
    "Recheck the sitemap after changes; record indexing separately in your own Search Console."
  ],
  "reviewRecord": "On a public, non-trial site, inspect /sitemap.xml on the primary domain. Squarespace generates the sitemap; it is not a file you manually rewrite. Compare the intended workshop URL with the list, and investigate page availability or search-hiding settings when it is missing. A sitemap entry helps discovery but does not prove Google indexed the page. Record the reviewed URL, setting, public response, reviewer and date; use your own verified Search Console property later for indexing evidence.",
  "limitations": "After launch, check the actual visitor path from homepage to workshop and from the old leaflet URL to the current page. Test signed out and on a narrow screen; confirm that the booking action still works without exposing private information. Search engines may choose different title or snippet text and may take time to revisit changes. This guide provides a repeatable editorial and technical review, not an expert-services engagement, a live account scan or a guarantee of first-page rankings."
}