NAP, opening hours, service areas, services with schema markup, click-to-call, breadcrumbs, maps with location pins, and embed blocks.
Loading the guide...
Did this answer your question?
Help us make the guides more useful.
0 helpful · 0 not helpful
NAP, opening hours, service areas, services with schema markup, click-to-call, breadcrumbs, maps with location pins, and embed blocks.
Loading the guide...
Help us make the guides more useful.
0 helpful · 0 not helpful
Seedly Sites ships a pack of blocks purpose-built for local business sites - the plumbers, landscapers, and clinics most agencies serve. Several of them emit structured data automatically, and the Map and Hours blocks can read from the Locations you set up once, so those stay accurate across every page.
The NAP block renders the business name, address, phone, and email as a card with schema.org PostalAddress markup, which is exactly what local search wants to see rendered consistently.
Fields: Business Name, Street, City, Region / State, Postal Code, Country, Phone, Email. The block shows exactly what you type: a field left empty is left out of the card and its markup, and nothing is filled in from Site Settings. Fill in every field you want shown, and keep them identical to the business details used elsewhere on the site. Consistent NAP across your site (and the web) is a local SEO fundamental.
The current editor helper text mentions inheriting empty fields from siteConfig.business. The published NAP renderer reads the block's saved fields only, so enter every detail you need on the block.
An opening-hours table. Its Source is Custom by default: an inline weekly schedule you type on the block, one open and close time per day. Switch it to Site to use the hours captured on your primary Location, for example from its Google Business Profile; a Site-sourced block with no captured hours shows nothing. Options include a Heading, a heading level, and a Show Open / Closed badge toggle. The badge is worked out when the site is deployed, so on the live site it shows the status at the time of the last deploy, not the visitor's current time.
For service-area businesses that travel to customers: a heading, description, and region list, with an optional map (Show map + Map Zoom). Regions are an inline, comma-separated list on the block, and the map needs an Address to center on.
One named service the business offers: Service Name, Description, Area Served, and an optional Link CTA. The block emits schema.org Service structured data linked to the site's LocalBusiness as the provider - so a services page built from Service blocks describes itself to search engines properly. Use one Service block per service, not one block listing everything.
A phone call-to-action: a Label, the Phone number, an optional Icon, and a button Style (Default, Primary, Secondary, Danger, Text, Link), plus Show phone number and Full width toggles. Always fill in Phone; an empty one is not filled in from Site Settings. It renders as a real tel: link, so tapping it on a phone starts the call. For a call bar that stays on screen on phones, put one in a Mobile only Row of your header and set the sticky header to Mobile only - see Header and Footer.
A visible breadcrumb trail (Home / section / page) for content pages. It renders the same trail as the page's BreadcrumbList structured data, which the page already emits - the block adds the visible navigation without duplicating markup.
An icon + title + body cell. Drop several into a Grid to build a feature list; it is a leaf block that does not host children. Grid Items cover most of the same ground, so use whichever reads better in your layout.
A pull quote: Content, optional Attribution, an optional Cite URL, and a style select. For customer reviews with ratings, prefer the Reviews element, which carries review markup.
An interactive map with brand-colored location pins and get-directions popups. No API key is required. Corner Radius rounds the map's frame and Shadow lifts it off the page; a border, if you want one, is a one-line custom CSS concern.
A pin you switch off (its Status) is left off the map. If every pin is switched off, the map treats it as having no pins and shows all of the site's locations, so to hide a map, switch off the Map block itself. Zoom applies to a single pin; with several pins the map fits them all in view.
Manage the underlying locations in the portal's Locations area; pins that reference them update when the location record changes.
The map loads lazily (it only initializes when scrolled into view), so it does not slow down page load.
The escape hatch for third-party embeds: review widgets, booking widgets, iframes, and custom snippets. Paste markup into HTML / Embed Code and it renders verbatim on the published site - iframes load and embed scripts execute. A Max Width select constrains the embed's width.
This block is also how you embed an external form from your CRM - see Forms for the full pattern, including UTM tracking into the embed.
Treat embed code with care: only paste snippets from providers you trust, since the block renders exactly what you give it.
| Block | Structured data | Reads shared data |
|---|---|---|
| NAP | PostalAddress | No, it shows exactly what you type |
| Hours | - | Your primary Location's hours, when Source is Site |
| Service Area | - | No, regions are typed on the block |
| Service | Service | - |
| Click to Call | Telephone | - |
| Breadcrumb | (page already emits BreadcrumbList) | - |
| Feature Item | - | - |
| Quotation | - | - |
| Map | - | Uses tenant Locations |
| HTML / Embed Code | - | - |
All of these go live on the next manual Deploy.
A block you switch off (its Status) is hidden on the live site and also left out of the page's structured data, and switching off a Section does the same for everything inside it. The one exception is structured data you pasted yourself into an HTML / Embed Code block: it still publishes while the block is switched off, so remove the code if you want it gone.