Why is your schema markup not showing up in search results?

If you have implemented structured data and your rich results aren’t appearing, you are likely falling into one of the common traps that plague small business websites. While schema markup (JSON-LD) is a critical signal for helping search engines understand your content, it is frequently misunderstood. Many business owners believe adding a few lines of code will instantly boost rankings or force Google to display star ratings. The reality is more nuanced: schema is a semantic layer, not a magic ranking button.

At Eikeland SEO, we see a distinct pattern in how Calgary businesses approach structured data. Some ignore it entirely, missing out on clarity for both users and algorithms. Others over-engineer it, adding types that Google no longer supports for rich results, creating noise rather than signal. This guide breaks down what actually works, what has changed, and how to implement production-ready schema without wasting resources.

Which schema types are actually worth your time?

Not all schema types are created equal. Google supports a specific subset of Schema.org types for rich results, and many types that were popular in 2018 or 2019 have been deprecated or restricted. Implementing unsupported types won’t harm your site, but it adds maintenance overhead with zero SEO benefit.

The high-value types for local businesses

  • LocalBusiness: Essential for any brick-and-mortar or service-area business. It helps Google map your NAP (Name, Address, Phone) data to your Google Business Profile.
  • Service: Critical for trades like plumbing, electrical, or consulting. It allows you to define the specific areas served and the type of service offered.
  • Product: Mandatory for e-commerce. Without it, you are invisible to Google Shopping.
  • Article: Standard for blogs and news. Helps establish authorship and publication dates.

The overhyped or restricted types

Some guides recommend FAQPage and HowTo schema for rich snippets. This is outdated advice.

Google significantly reduced FAQ rich results in 2023. Today, they are primarily displayed for well-known, authoritative government and health websites. For a local Calgary bakery or a plumber, adding FAQ schema is unlikely to result in visible accordion results in search. It may help Google understand your content, but do not expect the visual boost.

Similarly, Review schema is subject to strict eligibility rules. Self-serving reviews on your own website typically do not qualify for star ratings in search results. Google prioritizes reviews from third-party sources or those aggregated from a verified business profile. Adding review markup to a testimonial page you control is often ignored by the algorithm for rich result purposes.

What are the most common mistakes in implementation?

The most frequent error we see is structural. Developers often place JSON-LD in the <head> or, worse, in a hidden footer that doesn’t reflect the visible page content. Schema must be present on the page where the content exists. If you have a "Contact Us" page with your address, the LocalBusiness schema must be on that page, or linked via the site-wide footer if it applies globally.

Mistake 1: Inconsistent or incomplete opening hours

Businesses often use placeholder values or incorrect property names. The property is openingHoursSpecification, not hours or openingHours. Furthermore, if you are closed on Sundays, you should omit the Sunday entry entirely rather than setting it to null or zero. Including null values can confuse parsers.

What most guides don’t tell you: If your business has variable hours (e.g., different lunch breaks or holiday hours), you need multiple openingHoursSpecification objects. Most small business sites fail to handle this, resulting in Google showing outdated hours during holidays.

Mistake 2: Ignoring the "SameAs" property

The sameAs property is an array of URLs that identify the same entity. This includes your social media profiles, Google Business Profile, Yelp, and other authoritative directories. This helps Google consolidate your brand’s identity across the web. Missing this link often results in Google seeing your website and your Facebook page as separate, unconnected entities.

How do you implement production-ready LocalBusiness schema?

Below is a robust, production-ready example for a local service business. This example avoids common pitfalls like missing coordinates or incorrect property naming.


<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "@id": "https://www.yourbusiness.com/#organization",
  "name": "Eikeland SEO Example",
  "url": "https://www.yourbusiness.com",
  "telephone": "+1-403-555-0199",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Main Street SW",
    "addressLocality": "Calgary",
    "addressRegion": "AB",
    "postalCode": "T2P 1A1",
    "addressCountry": "CA"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 51.0447,
    "longitude": -114.0719
  },
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": [
        "Monday",
        "Tuesday",
        "Wednesday",
        "Thursday",
        "Friday"
      ],
      "opens": "09:00",
      "closes": "17:00"
    }
  ],
  "image": "https://www.yourbusiness.com/logo.png",
  "sameAs": [
    "https://www.facebook.com/yourbusiness",
    "https://www.linkedin.com/company/yourbusiness",
    "https://maps.google.com/?cid=123456789"
  ],
  "priceRange": "$$"
}
</script>

Key Implementation Notes:

  • Coordinates: Ensure latitude and longitude are accurate. A small error here can place your business in the wrong neighbourhood.
  • DayOfWeek: Use the full day name ("Monday"), not an abbreviation ("Mon").
  • Time Format: Use 24-hour format (HH:MM). Do not use AM/PM.
  • Price Range: This is a textual description of price range ($, $$, $$$, etc.). It does not affect rankings but adds context.

How do you implement Service schema for trades?

For service businesses, Service schema is often more important than generic LocalBusiness schema because it allows you to specify what you do, not just where you are. This is critical for ranking for specific intent queries like "emergency plumber Calgary."


<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Service",
  "serviceType": "Plumbing",
  "areaServed": {
    "@type": "City",
    "name": "Calgary"
  },
  "provider": {
    "@type": "LocalBusiness",
    "@id": "https://www.yourbusiness.com/#organization"
  },
  "description": "Emergency plumbing services in Calgary, including leak repair, drain cleaning, and pipe replacement."
}
</script>

What most people get wrong: They list areaServed as a string ("Calgary") instead of a City or State object. Using a simple string is less precise and may not be parsed correctly for local intent. Always use the structured object type.

Can schema markup directly improve rankings?

Google’s documentation suggests that structured data helps them understand the content of your page, which can lead to enhanced listings (rich results). However, it is crucial to understand that schema is not a direct ranking factor in the traditional sense. It does not give you a "boost" over competitors who also have valid schema.

Instead, schema improves the click-through rate (CTR) of your existing rankings. If you are ranked #3 and your competitor is #2, but you have a rich result snippet while they do not, you may capture more clicks. This increased engagement can indirectly influence rankings over time, but it is not a guarantee.

Furthermore, if your page content is poor, adding perfect schema will not save you. Schema describes content; it does not replace it. A page with thin content and perfect schema will still struggle to rank against a page with comprehensive content and basic schema.

What is the priority list if you can only do one thing?

If you are short on time or budget, and you can only implement one type of schema, here is the hierarchy of value for a small business:

  1. LocalBusiness: If you have a physical location or serve a specific area, this is non-negotiable. It connects your website to your Google Business Profile and ensures your NAP data is consistent. This is the foundation of local SEO.
  2. Service: If you are a service provider (plumber, lawyer, consultant), implement this on your core service pages. It clarifies your offering and area served.
  3. Article: If you have a blog, implement this on all posts. It helps Google understand authorship and dates, which is crucial for freshness signals.
  4. BreadcrumbList: If you have a complex site structure, this helps Google display your site hierarchy in search results. It improves navigation for users and can slightly improve CTR.

Do not prioritize FAQPage or Review schema unless you are a large, authoritative brand with third-party review aggregation. The effort-to-reward ratio is low for most small businesses in 2026.

How do you validate your implementation?

Never rely on intuition. Use the Schema Markup Validator to check for syntax errors. Then, use the Google Rich Results Test to see if Google detects the eligible types. Note that the Rich Results Test will tell you if you are eligible for a rich result, not if you will definitely get one. Eligibility depends on many factors, including site authority and relevance.

At Eikeland SEO, we build structured data into our custom website services from day one, ensuring it is validated and monitored. If you are unsure whether your schema is helping or hurting, a quick review can clarify the path forward.

Schema markup is a powerful tool for clarity, but it is not a shortcut. Use it to describe your business accurately, keep it updated, and focus on the high-value types that matter for your industry. For most Calgary businesses, getting LocalBusiness and Service schema right is the single most impactful step you can take.