Schema Markup for Small Business Websites: What to Add and What to Skip
Schema markup will not push your small business up the rankings, and anyone who sells it that way is overselling. What it does is tell Google, in a format a machine can read, who you are, where you are and what a page is about. That is worth an afternoon of work, and nothing more than that.
If you have been told you need schema markup for your small business website, here is what to add, what to ignore and where it goes wrong.
What schema markup actually is
Schema markup, also called structured data, is a block of code added to a page that labels its content. Your page might say "Atlas MKT, Manchester" in a footer. Markup says, explicitly, that this is an organisation, this is its name, and this is its address.
Google's own documentation describes it as providing "explicit clues about the meaning of a page". It is a clarification, not a ranking lever. Google states plainly that it does not guarantee structured data will show up in search results, even when the markup is correct.
So set expectations before you spend a pound. Markup makes a search feature possible. It does not make it certain, and it does not make a weak page rank.
The three types worth adding
Most small business sites need very little. Resist any quote that lists twenty schema types.
Organization or LocalBusiness on the homepage. This is the one that matters. Google's Organization markup guidance says it "can help Google better understand your organization's administrative details". There are no required properties, so you add what applies: name, url, logo, address, contactPoint and sameAs. If you serve a physical location, a more specific type such as LocalBusiness is the better fit.
Breadcrumbs on deeper pages. If your site has a clear hierarchy, such as Services, then Google Ads, then a specific page, breadcrumb markup describes that path. It is quick to add and low risk.
Article markup on blog posts. Useful if you publish regularly, because it labels the headline, author and dates. It is housekeeping rather than a growth tactic.
Everything else, including FAQ markup, review stars and product schema, depends on whether your content genuinely qualifies. Which brings us to the part most agencies skip.
What to leave out
Reviews you cannot show on the page. Google's guidelines say: "Don't mark up content that is not visible to readers of the page." If your homepage markup claims a 4.9 rating and no reviews appear on the page, you are inviting trouble.
Markup for content you do not have. Adding FAQ schema to a page with no FAQs, or Product schema to a service page, is exactly the sort of misleading markup that triggers a manual action. The consequence, per Google, is that the page loses rich result eligibility. It will not drop out of web search, but you will have wasted the work.
Plugin defaults you have not read. Many WordPress and Shopify themes inject markup automatically, sometimes with wrong addresses, duplicate organisation entries or placeholder logos. Check what your site already outputs before adding anything on top.
How to add it without breaking your site
Google recommends JSON-LD where your setup allows it, and so do we. It sits in a single script block in the page, separate from your visible content, which makes it easy to edit and easy to remove.
The process is short:
- Write the markup for your homepage with your real name, address, phone number and logo URL. Match the details exactly to your Google Business Profile and your footer.
- Paste it into the page head or the footer, depending on your platform.
- Run the page through Google's Rich Results Test, which the documentation calls "an easy and useful tool for validating your structured data".
- After launch, watch the rich result status reports in Search Console. Templates and plugin updates can silently break markup months later.
Google's own guidance adds a caveat worth remembering: the testing tools catch most technical errors, but not all, and they will not catch markup that is technically valid and misleading. Validation tells you the code parses. It does not tell you the markup is honest.
Where it fits in the bigger picture
Schema is a finishing touch on a technical SEO job, not the first step. If your title tags are vague, your pages are slow or your service pages say nothing specific, markup will not rescue them. Fix the fundamentals first, which is what our SEO work starts with.
It is also a build-time decision. Adding clean markup to a new site is trivial. Retrofitting it onto a tangle of plugins is where the hours go, which is why it belongs in the brief for any web development project from day one.
What to do this week
Check what your homepage already outputs. If it has an organisation entry with the right name, address and logo, you are largely done. If it has nothing, add one clean block. If it has three conflicting ones, remove two.
Then stop. A small business does not need a schema strategy, just accurate markup on the pages that matter.
If you want a second opinion on your site's technical foundations, get in touch and we will tell you what is worth fixing and what is not.
