If you’ve read that schema markup helps local businesses show up better in Google, but the idea of hand-coding JSON-LD makes your eyes glaze over, you’re not alone. The good news is you don’t need to touch a code editor to do this correctly.
Table of Contents
This guide walks through generating LocalBusiness schema with a free tool, adding it to your site through a plugin or simple paste-in method, and confirming Google can actually read it — all without writing a single line of code yourself.
Photo by Bibek ghosh on Pexels
Quick Answer
Use a free LocalBusiness schema generator to fill in a form with your business name, address, phone number, and hours, then paste the generated code into your site using an SEO plugin (like Rank Math) or your site builder’s custom code/header section — no manual coding needed. Afterward, verify it with Google’s Rich Results Test.
Step-by-Step: Generate and Add Your Schema
Start with a free LocalBusiness schema generator. Several exist (iLoveSchema, Localo, and LocalHQ are examples), and most work the same way: you fill in fields like business name, street address, city, phone number, business type, opening hours, and price range, and the tool outputs a ready-to-use block of JSON-LD code. Some generators can even pull details directly from your Google Business Profile listing, which saves re-typing information and reduces the chance of mismatches.
Once you have the generated code, you need to get it onto your site. If you run WordPress, the simplest route is an SEO plugin with a built-in schema builder — Rank Math, for example, includes a visual LocalBusiness schema generator under its Schema/Local SEO settings, so you fill in fields inside your WordPress dashboard and the plugin outputs the correct markup automatically, with no copy-pasting of raw code required.
If you’re not using a plugin with a built-in generator, you can still avoid hand-coding by pasting the generator’s output into a ‘custom HTML’ or ‘header/footer scripts’ section, which most modern site builders (and many WordPress themes) provide. Another no-code option is Google Tag Manager: create a Custom HTML tag, paste the JSON-LD snippet inside `
Cookie Consent
We use cookies to improve your experience on our site. By using our site, you consent to cookies.
This website uses cookies
Websites store cookies to enhance functionality and personalise your experience. You can manage your preferences, but blocking some cookies may impact site performance and services.
Essential cookies enable basic functions and are necessary for the proper function of the website.
Name
Description
Duration
Cookie Preferences
This cookie is used to store the user's cookie consent preferences.
30 days
These cookies are needed for adding comments on this website.
Name
Description
Duration
comment_author
Used to track the user across multiple sessions.
Session
comment_author_email
Used to track the user across multiple sessions.
Session
comment_author_url
Used to track the user across multiple sessions.
Session
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
SourceBuster is used by WooCommerce for order attribution based on user source.
Name
Description
Duration
sbjs_first
Traffic origin information for the visitor’s first visit to your store (only applicable if the visitor returns before the session expires)
session
sbjs_current
Traffic origin information for the visitor’s current visit to your store
session
sbjs_first_add
Timestamp, referring URL, and entry page for your visitor’s first visit to your store (only applicable if the visitor returns before the session expires)
session
sbjs_current_add
Timestamp, referring URL, and entry page for your visitor’s current visit to your store
session
sbjs_migrations
Technical data to help with migrations between different versions of the tracking feature
session
sbjs_session
The number of page views in this session and the current page path
30 minutes
sbjs_udata
Information about the visitor’s user agent, such as IP, the browser, and the device type