Business Profile

What Business Profile controls

Business Profile is the trusted source for your site's business identity. Hiveality uses it for local SEO, generated JSON-LD schema, AI writing context, email defaults, reviews, business hours, and shared contact details.

For most websites, you do not need to paste custom JSON-LD schema into Custom Code. Add the business facts here, keep structured data enabled, and Hiveality generates the technical schema automatically from saved site data.

Set up Business Profile

Which service delivery should I choose?

• In-person: clients visit a public clinic, office, store, or other location. Address, map, and hours matter for local SEO.
• Hybrid: clients can visit a public location and you also serve clients virtually or across a wider service area. Address, map, hours, and service area all matter.
• Virtual: you do not have a public location for clients to visit. Service area, website, phone or email, logo, and social profiles matter; Hiveality will not penalize the profile for missing a street address or hours.

If you connect a public business listing, Hiveality starts with that listing's facts. You can still change service delivery if the listing does not fully describe how you serve clients.

Fields to review

• Business name: the public business name shown in schema and defaults.
• Category: a plain-language category such as "Naturopathic clinic" or "Physiotherapy clinic." This helps AI context and schema selection.
• Description: a short factual summary of what the business does and who it serves.
• Phone, email, and website: contact details used in business schema and defaults.
• Address and map data: required for in-person and hybrid local SEO when a public location exists.
• Service area: useful for hybrid and virtual businesses. Add the actual city, region, country, or "Worldwide" area served.
• Business hours: used for local SEO and JSON-LD. These hours do not control booking availability.
• Social profiles: add one full URL per line. These can become sameAs links in structured data.
• Price range: optional. Use a short range such as CA$70-CA$280 when public service prices are available.

Manual edits are protected from future syncs. If you change a synced field by hand, Hiveality keeps your manual value unless you edit it again.

How schema works

When structured data is enabled, Hiveality generates JSON-LD automatically from Business Profile and page content.

• Indexable website pages can include WebPage and BreadcrumbList.
• The homepage can include WebSite and Organization, LocalBusiness, or a more specific business type when enough facts are available.
• Blog posts can include BlogPosting.
• Team profiles can include Person.
• Product pages can include Product and Offer.
• Visible FAQ or accordion content can include FAQPage when questions and answers are actually shown on the page.

Hiveality does not invent addresses, hours, reviews, ratings, or service areas. It also does not promise rich results. The goal is valid, eligible structured data that accurately reflects the published site.

Preview and test schema

Open Website Settings -> SEO & AI Visibility and review the schema area when you want to inspect generated structured data.

• Schema Health shows detected schema types and missing profile facts.
• Preview JSON-LD shows the generated homepage structured data.
• Open Rich Results Test opens Google's testing tool for the published site URL.

Google testing tools may show optional warnings such as missing price range or image. Optional warnings do not always mean the page is broken. Add the missing fact if it is accurate and useful for the business.

Should I paste custom JSON-LD?

Usually, no. Use Business Profile and Hiveality's schema controls for normal business, page, blog, team, product, and FAQ structured data.

Custom JSON-LD is still available for advanced cases, such as an unsupported schema type or a verified custom snippet. If you paste JSON-LD into Custom Code, Hiveality validates it and renders it safely, but duplicate or conflicting schema can confuse testing tools. Remove old custom business schema once Business Profile is set up unless you have a specific advanced reason to keep it.