What should a small business expect from schema?

Use schema to explain your page clearly. Structured data is a standard way to label information so a search engine can understand what it describes. LocalBusiness is the type used to describe a local business location. Google's introduction and local business guide explain these roles.

A rich result is a search result with additional features beyond a basic text listing. Structured data can make supported features possible, but a successful test does not guarantee that Google will display them. Set expectations using Google's appearance guidelines.

Choose a concrete first deliverable

Ask your website provider for one accurate location page, matching markup, and a completed test. Avoid making “more visibility” the only acceptance criterion. You need something you can inspect before judging any later search performance.

For a hypothetical repair shop, start with the page customers use to find the premises. Ask the owner to confirm the address and opening hours. Do not begin by adding every property found in an online generator.

Google Business Profile vs schema markup

Keep your profile review and website markup review as separate tasks. Schema in this guide is information embedded in your website page, as described in Google's implementation explanation. Do not sign off the website task merely because someone checked the business profile.

Put the business name, address and phone number side by side during that review. Use the NAP consistency guide to organize the comparison. Assign someone to resolve disagreements before the developer receives the details.

Which business details should you collect first?

Collect the name and physical address first. Google lists both as required for its LocalBusiness feature. It also lists useful recommended properties, including the main telephone number, location URL and opening hours. The table below follows Google's property definitions.

Create a short worksheet with three columns: detail, confirmed value and person responsible. Leave unresolved values blank during preparation. Send the developer the approved worksheet, rather than asking them to reconcile several old emails.

If you cannot provide a suitable physical address, do not invent one to satisfy a validator. Google's LocalBusiness requirements specifically call for a physical location. Review the appropriate business type before proceeding. Check the address requirement here.

Handle branches individually

Google says to describe each local business location separately. For several branches, prepare an individual worksheet for each and keep its telephone, hours and page URL together. Google's location guidance supports this approach.

For example, imagine two hypothetical shops with different Saturday schedules. Make the branch name prominent on each worksheet before anyone copies the hours. The multi-location local SEO guide can help you plan the related pages.

How do you adapt a LocalBusiness JSON-LD example?

JSON-LD puts the information in a separate data block. Microdata places labels within HTML elements. Google supports both and generally recommends JSON-LD when the site's setup allows it. See its supported formats explanation.

This is a teaching template, not a business listing ready to publish. Replace every bracketed value with verified information. The country field needs the appropriate two-letter country code; do not leave the instruction text inside the final markup.

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "[Your actual business name]",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "[Street and building or unit]",
    "addressLocality": "[City]",
    "addressCountry": "[Country code]"
  }
}

Choose the business type deliberately

The @type value identifies what you are describing. Google recommends the most specific suitable LocalBusiness subtype, such as Restaurant or HealthClub. Check your choice against the LocalBusiness type guidance before installing the template.

Keep the field names as written. Replace the values with your information, then test the small version before extending it. Ask your developer to add the confirmed telephone number, location URL and schedule from your worksheet.

Treat opening hours as a separate check

For a hypothetical salon, write the weekly schedule in ordinary language first. If Saturday differs from weekdays, show that difference in the worksheet. Have the manager approve it before converting it into code.

Google's examples show separate opening-hours entries for different schedules, including hours that cross midnight. Use the relevant pattern from the official opening-hours examples. Check the visible schedule against the finished data line by line.

Where should you install the markup?

Choose a page that describes the location. Google allows LocalBusiness data on your site and suggests a business information page as a sensible place. JSON-LD can sit in the page's head or body. See the placement guidance and JSON-LD format definition.

Give your developer the approved data and ask them to place it inside a <script type="application/ld+json"> block. Keep the corresponding business information readable on the page itself. Google requires markup to represent visible page content. Review the content rules.

Check existing website settings first

A CMS is the system used to manage your website content. Google notes that platforms such as WordPress, Wix and Shopify may offer search settings or plugins for structured data. The exact route depends on the site. Google explains the CMS options here.

Before installing anything, ask whoever maintains the website to show what it already generates. Compare the existing output with your worksheet. Choose one clear place to maintain the location details and document who can change them.

• Identify the page receiving the markup.
• Record the setting, plugin or template responsible.
• Keep a copy of the approved business details.
• Ask for the live page and test result at handover.

How should you test before and after publishing?

Use the Rich Results Test for validation, then URL Inspection to check Google's view of the live page. Google recommends fixing critical errors before proceeding and checking that access is not blocked. Follow its build, test and release process.

1. Open the test. Follow the Rich Results Test link from Google's documentation.
2. Check the draft code. Test the prepared block and note which fields need attention.
3. Fix critical problems. Supply missing required details using the approved worksheet.
4. Review warnings. Add useful information only when it is accurate and available.
5. Test the published URL. Check what the website actually serves after installation.
6. Inspect the page. Use URL Inspection in Search Console to review Google's access.

A non-critical warning is different from a critical error. Google recommends considering those improvements, but says fixing every non-critical issue is not necessary for rich result eligibility. Use the validation guidance to prioritize the work.

Search Console is Google's site monitoring service; URL Inspection is the tool used here to examine a page. Check for login requirements, robots.txt restrictions and noindex instructions. Google's access rules cover these barriers; the noindex guide explains that particular setting.

Do the checks software cannot complete for you

Ask a staff member to read the page as a customer would. Then compare the name, address and hours with the worksheet. Check accented characters, unit numbers and any branch-specific wording carefully.

Automated testing cannot reliably establish every quality requirement. Google explicitly separates technical checks from its broader quality rules. A valid result therefore still needs a factual review. See the quality guidelines.

Keep this review inside your regular website SEO audit. Store the page tested, the issues found and the person responsible for corrections. That gives the next person a useful starting point.

How do you keep the implementation useful?

Attach markup maintenance to changes in business details. Google requires current information that accurately represents the page. Whenever hours, contact details or premises change, review both the visible text and the structured data. Google's content rules explain this requirement.

Give the manager a simple change form: what changed, when it applies, who approved it and which location is affected. Ask the website maintainer to return a checked page. Avoid treating a verbal instruction as a completed update.

Do not add ratings simply to pursue stars for your own business. Google's LocalBusiness documentation recommends review and aggregateRating properties for sites collecting reviews about other local businesses. Check the property restrictions and the related search star ratings guide before considering review markup.