Built with Chinaski

Organization Settings

The Organization tab is your site’s business card — one logo file, a public phone number, links to your social profiles, and your postal address. Nothing here has layout opinions: the values are baked into schema.org structured data on every built page (the “Organization” block search engines read for identity, logo, contact, and profile information) and handed to your theme as plain variables.

The fields

Section Field What it feeds
Logo Logo File — a filename like logo.png Copied to the site root on every build; referenced by your theme’s header and the structured-data logo. Important: this is a file in the app’s assets/ directory, not a media-library item — upload/place it there first. The build log warns “not found in assets/, skipping” when the file’s missing
Contact Phone Reachable as org_phone in templates and telephone in the structured data
Social profiles LinkedIn / Facebook / Instagram / X (Twitter) Four URL fields; each becomes a sameAs link on the Organization node; blank per-field to omit
Address Street / City / Region·State / Postal Code / Country Emitted as a schema.org PostalAddress — the block appears as soon as a street or a city is set

Only a site_url (General tab) makes any of this appear in the built pages, since the structured-data node derives its identity URL from it — the same rule as canonical URLs and sitemaps. The tab is per-site, not per-language: one identity for the site.

Where each value lands on the built site

  • Logo: placed at the site root with your chosen filename; the built-in header references it there. The file must physically exist in the app’s assets/ directory — the build log warns and skips if it doesn’t, so check the build output if the logo vanishes.
  • Phone: telephone in the Organization structured data (worth filling any hours/region info in page copy yourself; there’s no hours field).
  • Social profiles: the four URLs become sameAs — the standard structured-data way to say “this site belongs to these other profiles,” used for knowledge-graph and entity matching.
  • Address: a schema.org PostalAddress behind your Organization — emitted only when street or city is present. Filling region/postcode/country but neither of those produces nothing, so at minimum fill street or city.
  • Email: there is no email field on this tab — a value set through the config CLI or a data import flows through as the Organization email in structured data, but the form itself doesn’t offer one (see the audit notes for the verified gap).

What the tab is not

  • Not the site’s name or tagline — those live on the General tab (the Organization node picks up the name from there).
  • Not the visible “about us” page — no layout decisions are made here. The values are handed to templates as flat variables (org_phone, the social URLs, and so on), and stock themes use only the logo; anything else you display is up to your theme.
  • Not the X @handle used in the social meta tags — that’s a separate setting on the Integrations tab (meta-tag attribution). This tab’s X URL feeds the JSON-LD sameAs list instead. Two X references, two different outputs.

Practical notes

  • Structured data only emits when there’s a real value — the builder skips every empty field rather than emitting "telephone": "".
  • The logo file’s name becomes part of the site root’s URL path (https://yoursite.com/logo.png) — pick a stable name; changing it after search engines have read it is a rename like any other (a build copy updates the file only when the name matches the setting).
  • The country field takes a country code (the placeholder suggests US), matching the schema.org convention for addressCountry.
  • The Reset Organization button clears only this tab’s values (with a confirm dialog) — the rest of Settings is untouched.

The short version

Type your org’s identity once — logo filename, phone, social URLs, address — and the builder turns it into the structured-data Organization block plus template variables — while site name and URL keep living on General, and anything that appears in a chip-previews flow is handled by the analytics and social tabs instead.