LocalBusiness Schema.

JSON-LD is the format Google explicitly recommends for structured data, which is the main reason this tool produces it. The big practical advantage is separation: JSON-LD lives in a single self-contained script block, usually in the head of your page, and describes your business as a tidy block of data without tangling itself into your visible HTML. Microdata and RDFa, the older alternatives, work by sprinkling extra attributes throughout your page markup, wrapping your name, address and phone number in special tags, which means every time you redesign the page you risk breaking the structured data. Because JSON-LD sits apart from the layout, it is far simpler to maintain, easier to read, and easier to debug in Google Rich Results Test. For a small business owner who is not a developer, that matters: you update the schema in one place without touching the rest of the site. So while all three formats are valid, JSON-LD is the cleanest, most future-proof choice, and the one Google prefers.

Paste the generated JSON-LD inside the head section of your homepage HTML, where structured data is conventionally placed and where Google reliably reads it. How you do that depends on your platform. On most modern site builders, including Neweb, you add it through a custom code or script block in the page or site settings, so you do not edit raw files at all. On WordPress, the easiest routes are your SEO plugin, many of which have a dedicated field for custom schema, or a lightweight header-insertion plugin that injects code into the head sitewide. On a hand-built static site, you simply place the script tag in the head of your HTML file. The key points are that it belongs in the head rather than the body, that you paste the complete script block including its opening and closing tags, and that you do it on your homepage. After pasting, run the page through Google Rich Results Test to confirm the schema is detected and error-free.

No, and it is important to be clear-eyed about this. Adding valid LocalBusiness schema makes your business eligible for enhanced search appearances and helps Google understand exactly who you are, where you are and how to reach you, but it does not guarantee that rich results, star ratings, knowledge panels or enhanced listings, will actually show. Whether Google displays them is at Google discretion and depends on many signals beyond the markup, including your overall site authority and trust, whether you have genuine reviews, the quality of your content, and how well your information matches other sources like your Google Business Profile. In other words, schema is necessary but not sufficient: it is the structured foundation that makes rich results possible, while the surrounding factors decide whether Google grants them. The right way to think about it is that correct schema removes the technical barrier and gives you the best chance, and you improve your odds by keeping details accurate and earning real reviews.

For LocalBusiness schema, the homepage is the primary and most important place, since it is the page Google most strongly associates with your business identity. It is also sensible to add it to a small number of other directly relevant pages, most notably your Contact page, where your address, phone and hours naturally live, and sometimes your About page. What you should not do is paste the same LocalBusiness block onto every single page of your site, including blog posts and unrelated content, because indiscriminate duplication looks like schema bloat, adds no value, and can muddy how cleanly Google reads your structured data. The guiding principle is to place the markup where the business-information context genuinely fits, the pages a customer visits to learn who you are and how to reach you, rather than scattering it everywhere. Keep the details identical across the few pages where it appears, and let your homepage carry the canonical version that Google treats as authoritative for your local business.

The quickest way to get your exact latitude and longitude is through Google Maps. Open Google Maps in a browser, find your business or its precise location, then right-click directly on the map pin or the exact spot. The first item in the menu that appears is the latitude and longitude pair, shown as two decimal numbers; click it to copy the pair to your clipboard, then paste it into this tool. Accuracy matters, so right-click on your actual building entrance rather than a rough area, because the coordinates feed the geo data in your schema and influence how precisely you are placed on maps. On the Google Maps mobile app the gesture differs slightly, but you can drop a pin and read the coordinates from the place details. If your business is already verified on Google Business Profile, its coordinates there will match, which is a useful consistency check, since you want the same precise location across your schema, your profile and your website.

If your business keeps set opening hours, including them in your structured data is worthwhile, because hours are one of the details customers most want to see and Google often surfaces them directly in local results, so accurate hours can be the difference between someone visiting and someone moving on. In schema terms, opening hours are expressed through an openingHoursSpecification block that lists the days and the open and close times. This tool currently generates the core LocalBusiness schema, your name, address, phone and location, and adding the openingHoursSpecification is on the roadmap, so for now you would append that block manually if you want it immediately. In the meantime, keep your hours correct and consistent on your Google Business Profile, which is where most local searchers actually read them and which Google weights heavily. When the hours field arrives in the tool, keep the schema hours identical to your profile hours, since conflicting times confuse both customers and Google.

Yes, but multi-location businesses need a slightly different structure than a single shop. The recommended pattern for a chain or a business with several branches is to use one Organization schema to represent the overall brand, and then a separate LocalBusiness schema for each individual location, with each location schema placed on its own dedicated location page rather than all bundled together. That way Google can understand both the parent brand and each physical outlet, with its own address, phone, hours and coordinates, which is how local search wants to index a chain. This tool generates a single LocalBusiness block, so for a multi-location business the practical approach is to run it once per branch, entering that branch specific details each time, and place each generated block on the matching location page. Keep every location page genuinely distinct, with its own address and unique content, since thin duplicate pages can hurt rather than help.

No, nothing you enter is sent anywhere; the entire schema generation runs locally in your browser. The business details you type, your name, address, phone number, coordinates and the rest, are assembled into JSON-LD right on your own device, with no request carrying that information to us or to any third-party server. That keeps your business data private and means there is no copy of it sitting on someone else system, which is the same privacy-first approach we take across these tools. Because the work happens on-device, the tool is also instant, with no waiting on a server round trip, and you can generate and regenerate the markup as many times as you like while you fine-tune the details. The only thing to remember is that, since nothing is stored for you, you should copy the generated JSON-LD and paste it into your site, or save it in your own files, before you close the tab.