LocalBusiness schema, title and description templates, default social images, and the structured data every page emits automatically.
Loading the guide...
Did this answer your question?
Help us make the guides more useful.
0 helpful · 0 not helpful
LocalBusiness schema, title and description templates, default social images, and the structured data every page emits automatically.
Loading the guide...
Help us make the guides more useful.
0 helpful · 0 not helpful
Site-wide SEO lives mostly in the Technical tab: the business's address, the templates that fill in whatever individual pages leave blank, and the default share images. Set these once per client site and every page benefits.
Per-page controls (focus keyword, meta fields, canonical, noindex) are covered in Page SEO.
The Business Address & Location card on the Technical tab, plus three schema fields, describe the business behind the site. Business Type, Service Area and Hours of Operation are not on the Technical tab: set them in /admin, under Site Settings, SEO & Schema. A generated site takes its Business Type from the client's Google Business Profile category. They emit a single LocalBusiness node - the site's canonical organization entity - that the rest of the structured data references.
| Setting | What it feeds |
|---|---|
| Business Type | The schema type, from a list of local-business types across trades, health, beauty, food and drink, hospitality, automotive, professional services and retail, or a generic Local Business |
| Street Address / City / State / ZIP | The business's postal address. Leave the street blank for a service-area business with no public address |
| Latitude / Longitude | Optional geo coordinates |
| Service Area | The list of areas the business serves |
| Hours of Operation | Opening hours, for example "Mon-Fri 7am-6pm, Sat 8am-2pm" |
The business name, phone, and social profile links come from Site Settings (the social URLs become the entity's profile links).
This same data also powers the local-business content blocks - NAP, Hours, Service Area, and Service elements read it as their defaults. See Local Business Blocks.
Templates fill the search snippet for any page that has no meta title or description of its own. They take {{title}} (the page's title) and {{siteName}}, and the site's own merge tokens such as {{site.phone}} work in them too (see Merge Tokens).
| Template | Applies to |
|---|---|
| Meta Title Template | Pages and posts without a meta title |
| Meta Description Template | Pages and posts without a meta description, when no Default OG Description is set |
| Category / Author Title Template | Category, tag, and author archive pages |
| Category / Author Description Template | The same archive pages |
A typical title template: the page title, a separator, the site name. Set the templates once and stop hand-writing "About Us | Business Name" on every page.
A meta template can also carry an [AI-PROMPT] marker. On a template-path build, a template carrying the marker has its title or description written by the model per page, with your tokens resolved first and the output passing the same content gates as the rest of the generated copy. A template with tokens only resolves at render, and with no template at all the platform falls back to its standard title and description, so this is opt-in and changes nothing until you add the marker. A template page can also carry its own per-page meta prompt, which pages built from it inherit.
Two independent fallbacks in the Default OG / Social Sharing card:
Each cross-falls back to the other, so setting just one still covers both roles. The Default OG Title and Default OG Description fields cover pages missing those too, and the Default OG Description also stands in for a missing meta description.
With the business schema configured, the published site carries a coherent structured-data graph with no per-page work:
| Structured data | Where |
|---|---|
| LocalBusiness (the organization) | Site-wide, referenced by everything else |
| WebSite | Site-wide, published by the organization |
| WebPage + BreadcrumbList | Every page |
| Article markup (BlogPosting) | Every blog post, with headline, dates, image, and author |
| Person | Post authors - one consolidated entity per author across all their posts, plus profile-page markup on the author archive |
| FAQPage | Pages using the FAQ element |
| Service | Pages using the Service block, linked to the business as provider |
| Review + AggregateRating | Pages using the Reviews element, attached to the business |
Everything renders into the static output at deploy time - no client-side scripts involved. Per-page custom JSON-LD (see Page SEO) merges into this graph rather than fighting it.
A block you switch off in the builder is left out of the structured data as well, with one exception: JSON-LD you paste into an HTML element yourself stays until you delete the element.
The site's locale setting (for example en-US or es-ES, in /admin under Site Settings, Site language / locale) sets the page language attribute and the social-card locale for the whole site.
/admin