<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Neil Fox</title>
    <description>The latest articles on DEV Community by Neil Fox (@northfoxdigital).</description>
    <link>https://dev.to/northfoxdigital</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4250596%2F110aaf8f-3e01-4d40-b7b4-d696d7cd0eb3.png</url>
      <title>DEV Community: Neil Fox</title>
      <link>https://dev.to/northfoxdigital</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/northfoxdigital"/>
    <language>en</language>
    <item>
      <title>Local SEO for Small Businesses: Add LocalBusiness Schema the Right Way</title>
      <dc:creator>Neil Fox</dc:creator>
      <pubDate>Tue, 17 Nov 2026 21:23:15 +0000</pubDate>
      <link>https://dev.to/northfoxdigital/local-seo-for-small-businesses-add-localbusiness-schema-the-right-way-56m6</link>
      <guid>https://dev.to/northfoxdigital/local-seo-for-small-businesses-add-localbusiness-schema-the-right-way-56m6</guid>
      <description>&lt;p&gt;Local SEO for small businesses is often described as a content problem, but a chunk of it is markup: search engines can only trust your location facts when the visible page and the machine-readable data say the same thing. This walkthrough shows how to add a single &lt;code&gt;LocalBusiness&lt;/code&gt; (or a more specific subtype) JSON-LD block to a small-business website, how to test it, and how to avoid the errors that create a second, conflicting NAP.&lt;/p&gt;

&lt;p&gt;I build and review sites for local service businesses. I also run North Fox Digital. The example below is fictional. Do not copy the names, phone numbers, or coordinates onto a live site.&lt;/p&gt;

&lt;p&gt;You only need one canonical JSON-LD graph on the templates that represent the business as a whole, usually the homepage and the contact page. You do not need a unique &lt;code&gt;LocalBusiness&lt;/code&gt; blob on every blog post. If you already have Open Graph tags, leave them; they do not replace schema.&lt;/p&gt;

&lt;h2&gt;
  
  
  A JSON-LD recipe you can adapt
&lt;/h2&gt;

&lt;p&gt;Prefer JSON-LD in a &lt;code&gt;&amp;lt;script type="application/ld+json"&amp;gt;&lt;/code&gt; tag over microdata sprinkled through the HTML. JSON-LD is easier to review in a pull request, and you are less likely to break it when a designer edits the header.&lt;/p&gt;

&lt;p&gt;Start with the most specific type Google documents for the business. &lt;code&gt;LocalBusiness&lt;/code&gt; is the safe parent. A dental office can use &lt;code&gt;Dentist&lt;/code&gt;, a shop can use &lt;code&gt;Store&lt;/code&gt;, a trades firm can use &lt;code&gt;HomeAndConstructionBusiness&lt;/code&gt; or a narrower subtype. Do not pick a type because it “sounds stronger.” If no subtype fits, stay with &lt;code&gt;LocalBusiness&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Here is a compact example for a fictional service-area plumber. The &lt;code&gt;@id&lt;/code&gt; values let the organization, the website, and the owner node point at each other without duplicating the telephone number in three disconnected objects.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;"@context"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://schema.org"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"@graph"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
    &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="nl"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"HomeAndConstructionBusiness"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"@id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://example-plumbing.example/#business"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Example Plumbing"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"url"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://example-plumbing.example/"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"telephone"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"+1-407-555-0142"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"email"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"hello@example-plumbing.example"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"image"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://example-plumbing.example/images/van.jpg"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"priceRange"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"$$"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"areaServed"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
        &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"City"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Orlando"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"AdministrativeArea"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Orange County"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
      &lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"openingHoursSpecification"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
        &lt;span class="p"&gt;{&lt;/span&gt;
          &lt;span class="nl"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"OpeningHoursSpecification"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
          &lt;span class="nl"&gt;"dayOfWeek"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"Monday"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"Tuesday"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"Wednesday"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"Thursday"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"Friday"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
          &lt;span class="nl"&gt;"opens"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"07:30"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
          &lt;span class="nl"&gt;"closes"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"17:00"&lt;/span&gt;
        &lt;span class="p"&gt;}&lt;/span&gt;
      &lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"sameAs"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
        &lt;span class="s2"&gt;"https://www.facebook.com/exampleplumbing"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="s2"&gt;"https://maps.google.com/?cid=0000000000"&lt;/span&gt;
      &lt;span class="p"&gt;]&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="p"&gt;]&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A storefront business should add a &lt;code&gt;PostalAddress&lt;/code&gt; under &lt;code&gt;address&lt;/code&gt;, with &lt;code&gt;streetAddress&lt;/code&gt;, &lt;code&gt;addressLocality&lt;/code&gt;, &lt;code&gt;addressRegion&lt;/code&gt;, &lt;code&gt;postalCode&lt;/code&gt;, and &lt;code&gt;addressCountry&lt;/code&gt;. If the business is service-area only and hides the street address on the public profile, do not invent a public street in JSON-LD to look more complete. Use &lt;code&gt;areaServed&lt;/code&gt; for the cities or counties the crew actually covers, and keep that list short and true. Listing every city in a metro area will not create a branch office.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;telephone&lt;/code&gt; should be the public customer number in international format, not a tracking number that differs from the number on the contact page. &lt;code&gt;sameAs&lt;/code&gt; should list official profiles you control, not directories you have not claimed. If you do not have a given profile, omit it.&lt;/p&gt;

&lt;p&gt;Common implementation mistakes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Two generators, two stories.&lt;/strong&gt; A theme plugin emits one &lt;code&gt;LocalBusiness&lt;/code&gt; block, a marketing plugin emits another, and the footer still shows a retired phone number. View source and keep a single graph.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Markup that does not match the page.&lt;/strong&gt; If the visible heading says “Example Plumbing” and the JSON-LD says a different legal name, fix the source of truth first. Schema is not a place to try a keyword variation.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Coordinates for places you do not occupy.&lt;/strong&gt; Do not drop a &lt;code&gt;GeoCoordinates&lt;/code&gt; pin on a city you merely hope to rank in. If you have a real premises, use the real lat/long.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;AggregateRating&lt;/code&gt; you did not earn on that page.&lt;/strong&gt; Do not hard-code star ratings. If you later add review markup, it has to follow the current rich-result rules and represent reviews that are actually present.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Copy-pasted opening hours.&lt;/strong&gt; A holiday exception that exists on the Google Business Profile but not in JSON-LD (or on the contact page) is a contradiction. Update the facts in one place, then regenerate the script.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;When the script is in a staging build, validate it before you merge. I use three checks, in this order:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The Schema.org Validator at validator.schema.org, to confirm the JSON is valid and the types exist.&lt;/li&gt;
&lt;li&gt;Google’s Rich Results Test at search.google.com/test/rich-results, to see whether the page is eligible for any documented rich result. A valid &lt;code&gt;LocalBusiness&lt;/code&gt; graph can still produce “not eligible,” which is fine; you are aiming for accurate entity data, not a decorative badge.&lt;/li&gt;
&lt;li&gt;A visual diff of the rendered homepage and contact page against the JSON-LD: name, phone, hours, and area served must match.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If the site is a static or server-rendered app, generate the JSON from the same configuration file that prints the footer. That is the whole trick. In a Next.js or similar project I keep a &lt;code&gt;business.json&lt;/code&gt; module and serialize it into the layout, so a hours change cannot land in the footer and miss the graph.&lt;/p&gt;

&lt;p&gt;Local SEO for small businesses also depends on work that schema cannot do: service pages that name the offer clearly, a contact path that works on a phone, and public listings that repeat the same facts. Markup is the consistency layer, not a substitute for those pages. If you want a non-code walkthrough of &lt;a href="https://northfoxdigital.com/guides/understand-local-seo" rel="noopener noreferrer"&gt;the basic parts of local search visibility&lt;/a&gt;, that explanation is written for owners who will approve the facts you are about to encode.&lt;/p&gt;

&lt;p&gt;Ship the script, run the three checks, and then leave it alone until a fact changes. A quiet, accurate &lt;code&gt;LocalBusiness&lt;/code&gt; block is more useful than a quarterly rewrite of the same JSON.&lt;/p&gt;

</description>
      <category>seo</category>
      <category>webdev</category>
      <category>schema</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
