Guides · SEO & getting found

Schema basics for local businesses (without over-engineering)

Schema is not a ranking “hack”. It is machine-readable context. Errors or misleading types can create noise in Search Console and erode trust if your visible content contradicts the markup.

Where schema usually makes sense for NZ SMEs

  • Organisation / LocalBusiness on the homepage or contact page—with real address and phone if you publish them.
  • FAQPage only if FAQs are visible on the page and remain accurate.
  • Product for ecommerce">ecommerce with honest price and availability fields.

What to skip until you have a developer

Nested graph experiments, auto-generated FAQ on every page, and “aggregateRating” without verifiable reviews often cause more harm than help.

Validate before you celebrate

Use Google’s Rich Results test on a sample URL after deployment. Fix errors; warnings are hints, not always mandatory.

Frequently asked questions

Will schema fix poor rankings?

No—it can improve eligibility for some result types. You still need relevance, quality content, and technical health.

Should every page have schema?

No—use types that match real content. Irrelevant schema is clutter.

Putting this into practice on your NZ website

This guide sits in our SEO & getting found collection. The goal is practical advice you can act on without a computer science degree. Start with one change, measure whether enquiries or usability improve, then tackle the next item. Small businesses across Auckland, Wellington, Hamilton, Christchurch, and regional New Zealand face the same constraints: limited time, real customers, and a website that must earn its keep.

For Schema basics for local businesses (without over-engineering), the highest-leverage move is usually to align your live site with what the guide recommends, then fix anything that blocks Google from crawling pages or stops visitors from contacting you. If your site runs on WordPress, many of these tasks are configuration and content work rather than custom development.

Document your starting point: note current enquiry volume, average page speed from PageSpeed Insights, and any errors showing in Google Search Console. Without a baseline, improvements are guesswork. Revisit the same metrics after 90 days—SEO and UX changes rarely produce overnight miracles, but sustained progress should be visible in leads and user behaviour.

Share this guide with whoever maintains your site—an employee, a contractor, or your hosting support desk—so terminology and priorities align. The FAQ section on our main site answers common project questions if you are weighing a rebuild versus incremental fixes.

Before committing to changes, run your current site through our free website checker to see speed, mobile usability, and basic SEO signals in one report.

When to involve a web partner

Some tasks—migrations, checkout changes, security incidents, or a full redesign—benefit from experienced help. If you are comparing providers, look for clear scoping, realistic timelines, and measurement tied to business outcomes rather than vanity metrics. Our team builds and maintains business websites nationwide; explore relevant services below or request a quote when you are ready.

A good partner will ask about your customers, geography, and capacity to publish content—not only colour preferences. Review our recent website projects for examples of brochure, WordPress, and ecommerce work across New Zealand.

Related NZDH services

More guides in this topic

Browse the full SEO & getting found guide hub or return to the guides home.

Explore on NZDH.co.nz

Authoritative further reading

These independent resources complement this guide. Search engines and customers both reward accurate, helpful information—we link out where official documentation or regulators explain the topic better than a generic blog post could.