πŸ› οΈ Website Studio Source and OTTO Schema

Camilo Aponte

Camilo Aponte

Last updated on Nov 17, 2026

πŸ“¦ Export the currently published source

** Open the relevant project in Website Studio and, in the preview toolbar’s download menu, choose Download ZIP (source). Save the ZIP as a baseline and compare its contents with the published site or known deployment version. Inspect the ZIP for the React/Vite files and src/lib/useFormSubmission.ts; if the file is missing, do not assume it is available in this project.

Keep the original export unchanged as your baseline. Record the project name, export date, published version, and deployment status so the baseline can be restored if needed.

✏️ Edit only the form submission file

Make the requested change only in src/lib/useFormSubmission.ts. Do not modify generated files, package versions, routing, styling, environment settings, or other source files unless the change specifically requires it.

Before publishing, review the file change and confirm that existing form fields, validation, success messages, error handling, and tracking behavior remain intact. Test the form in a staging or preview environment when available.

πŸš€ Publish safely and restore the baseline

  1. Save the untouched export as the rollback baseline.
  2. Apply the limited change to src/lib/useFormSubmission.ts.
  3. Build or preview the project and test a successful submission and a failed submission.
  4. Publish only after the preview passes.
  5. Verify the live form, browser console, network request, and confirmation behavior.

** To restore a Website Studio project, use Version History to select and restore the appropriate earlier version. Confirm the restore completes, publish or republish if needed, and verify the live form afterward. Keep the original exported ZIP separate from any modified copy.

🧩 Back up Header Embeddings separately

** Before changing Header Embeddings, copy and label the current contents from the project’s settings separately from the source ZIP. Record the project and where the code is intended to run, and verify the live site after making changes.

Restore Header Embeddings separately from the Website Studio rollback. A source redeploy does not necessarily remove or restore embedding records, and restoring an embedding does not restore application source.

πŸ” Find the authoritative OTTO schema record

** For WordPress page 1622, confirm the page’s public and canonical URLs in WordPress and on the live page. In the relevant OTTO project, find the matching URL and review its page-level and sitewide Schema Markup, including the available source and approval information. Check any available deployment history and compare it with the rendered page; involve support if the needed record details are not visible.

** Do not assume a copied JSON-LD block, browser cache, Website Studio file, WordPress revision, or OTTO record is the source of the markup without checking. Confirm the page’s canonical and public URLs, then compare the rendered markup with the relevant OTTO page-level and sitewide schema and other possible sources. Do not guess the URL from the page title or edit an unrelated record.

🧹 Stop recurring 24-hour care schema

** Compare the rendered page with the relevant OTTO schema and other possible sources, such as WordPress plugins, templates, and injected scripts. Identify which source is actually producing the inaccurate 24-hour care markup, then correct or disable it using that source’s controls. Publish or redeploy the change and clear caches as appropriate for the source.

** Recheck the rendered page and structured-data testing results after the correction and again after enough time for any relevant cache or scheduled process to run. If the schema returns, review the available OTTO deployment information and page-level and sitewide schema, along with WordPress plugins, templates, and injected scripts, rather than editing the generated markup alone. **Code references:** Website Studio’s source-download label is in landing-page-studio/next\_js\_service/app/components/PreviewToolbar.tsx:523–526; Version History is in app/components/VersionHistoryModal.tsx:124–125; and Header Embeddings is a settings text field in app/components/SettingsTabContent.tsx:220–230. OTTO’s page-level and sitewide schema associations and fields are defined in content-assistant/app/ca/models/otto\_schema.py:146–196.

βœ… Recommended evidence

  • Untouched Website Studio source export and modified-file diff.
  • Deployment or rollback version and verification date.
  • Separate Header Embeddings backup.
  • Canonical URL and WordPress page ID 1622.
  • OTTO schema record ID, status, source, and update history.
  • Before-and-after rendered HTML or structured-data test results.

If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Was this article helpful?