Homepage Schema Reference

This outlines the recommended schema types and their key properties for a typical website’s homepage. This applies whether the site represents a business, an organization, a blog, or a personal website.

• WebPage: Describes the homepage as a page.
  • @type: WebPage
  • @id: [Homepage URL]#webpage (e.g., https://www.example.com/#webpage)
  • url: [Homepage URL] (e.g., https://www.example.com/)
  • name: [Website Name] - Homepage (or a similar title that includes your brand)
  • description: (The homepage’s meta description)
  • isPartOf: { "@type": "WebSite", "@id": "[Homepage URL]#website" } (Links to the WebSite schema)
  • publisher: { "@type": "Organization", "@id": "[Homepage URL]#organization" } (Links to the Organization schema)
  • mainEntity: Can point to the Organization schema, especially if the homepage is primarily about the organization/business. In some cases (like a personal blog), the mainEntity might be omitted, or might point to something else if there’s a more specific, primary entity represented on the homepage besides the organization. For most business websites, linking to Organization is best.
  • breadcrumb : Include the schema
• WebSite: Describes the overall website.
  • @type: WebSite
  • @id: [Homepage URL]#website (e.g., https://www.example.com/#website)
  • url: [Homepage URL] (e.g., https://www.example.com/)
  • name: [Website Name] (e.g., “Example Company”)
  • description: (A general description of the website – can be the same as, or different from, the homepage meta description)
  • potentialAction: (Optional, but highly recommended if you have site search) JSON{ "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "[Homepage URL]?s={search_term_string}" }, "query-input": "required name=search_term_string" }
• Organization: Describes the business/organization that the website represents.
  • @type: Organization (or LocalBusiness if it’s a single-location business – see note below)
  • @id: [Homepage URL]#organization (e.g., https://www.example.com/#organization)
  • url: [Homepage URL] (e.g., https://www.example.com/)
  • name: [Your Business Name] (The official business name)
  • description: (A concise description of your business)
  • logo: (With nested ImageObject, including URL, width, height, and caption)
  • image: (With nested ImageObject, including URL, width, height, and caption)
  • address: (Your business address, using PostalAddress schema)
  • telephone: (Your business phone number – use international format)
  • email: (Your business email address)
  • sameAs: (URLs of your business’s social media profiles – Facebook, LinkedIn, etc.)
  • contactPoint: (if applicable)
  • aggregateRating: (Only if you have verifiable aggregate rating data)
• BreadcrumbList
  • @type: BreadcrumbList
  • @id: [Homepage URL]#breadcrumb
  • itemListElement: For the homepage, this will usually be just one item: JSON"itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "[Homepage URL]" } ]

LocalBusiness vs. Organization on the Homepage:

• Single Location Business: If your business has a single physical location, and the homepage is primarily about that business/location, then using LocalBusiness instead of Organization on the homepage is perfectly acceptable (and often preferred).
• Multi-Location Business: If your business has multiple locations, it’s generally better to use Organization on the homepage (to represent the overall brand) and then use LocalBusiness on the individual location pages.
• Online-Only Business: If your business is purely online and doesn’t have a physical location where customers visit, use Organization.

What Not to Include on the Homepage:

• Person: Unless your homepage is specifically a personal profile page (which is rare for a business website), do not include a full Person schema on the homepage. Person schema belongs on “About” pages or author profile pages.
• Article/BlogPosting: These are for individual blog posts, not the homepage.
• Duplicate of any of the Schemas

Complete Example (Conceptual JSON-LD – Adapt to Your Specifics):

HTML

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "WebPage",
      "@id": "[Homepage URL]#webpage",
      "url": "[Homepage URL]",
      "name": "[Website Name] - Homepage",
      "description": "[Homepage Meta Description]",
      "isPartOf": {
        "@type": "WebSite",
        "@id": "[Homepage URL]#website"
      },
      "publisher": {
          "@type": "Organization",
          "@id": "[Homepage URL]#organization"
        },
      "mainEntity": {
        "@type": "Organization",
        "@id": "[Homepage URL]#organization"
      },
        "breadcrumb": {
        "@type": "BreadcrumbList",
        "@id": "[Homepage URL]#breadcrumb",
        "itemListElement": [
          {
            "@type": "ListItem",
            "position": 1,
            "name": "Home",
            "item": "[Homepage URL]"
          }
        ]
      }
    },
    {
      "@type": "WebSite",
      "@id": "[Homepage URL]#website",
      "url": "[Homepage URL]",
      "name": "[Website Name]",
       "description": "[Website Description]",
      "potentialAction": {
        "@type": "SearchAction",
        "target": {
          "@type": "EntryPoint",
          "urlTemplate": "[Homepage URL]/?s={search_term_string}"
        },
        "query-input": "required name=search_term_string"
      }
    },
    {
      "@type": "Organization", //  Or "LocalBusiness" if single-location
      "@id": "[Homepage URL]#organization",
      "url": "[Homepage URL]",
      "name": "[Your Business Name]",
      "description": "[Your Business Description]",
      "logo": {
        "@type": "ImageObject",
        "url": "[Logo URL]",
        "width": [Logo Width],
        "height": [Logo Height],
        "caption": "[Logo Caption]"
      },
        "image": {
        "@type": "ImageObject",
        "url": "[Logo URL]",
        "width": [Logo Width],
        "height": [Logo Height],
        "caption": "[Logo Caption]"
      },
      "address": {
        "@type": "PostalAddress",
        "streetAddress": "[Your Street Address]",
        "addressLocality": "[Your City]",
        "addressRegion": "[Your State/Province]",
        "postalCode": "[Your Postal Code]",
        "addressCountry": "[Your Country Code]"
      },
      "telephone": "[Your Phone Number]",
      "email": "[Your Email Address]",
      "sameAs": [
        "[Your Facebook URL]",
        "[Your LinkedIn URL]",
        "[Your Instagram URL]",
        // ... other social profiles
      ],
        "contactPoint": {
          "@type": "ContactPoint",
          "telephone": "[Your Phone Number]",
          "contactType": "customer service",
          "areaServed": "[Your Country Code]",
          "availableLanguage": "English"
        },
      "aggregateRating": { // ONLY if verifiably accurate
        "@type": "AggregateRating",
        "ratingValue": "[Your Rating]",
        "reviewCount": "[Number of Reviews]"
      }
      // Add other relevant Organization properties if needed.
    }
  ]
}
</script>

Key Placeholders to Replace:

• [Homepage URL]: The full URL of your website’s homepage (e.g., https://5dme.com.au/).
• [Website Name]: The name of your website (e.g., “5DME”).
• [Your Business Name]: The official name of your business (e.g., “5DME”).
• [Logo URL]: The URL of your website’s logo image.
• [Logo Width] and [Logo Height]: The actual dimensions of your logo image, in pixels.
• [Your Street Address], [Your City], [Your State/Province], [Your Postal Code], [Your Country Code]: Your business’s full, accurate address.
• [Your Phone Number]: Your business’s phone number (use international format: +61…).
• [Your Email Address]: Your business’s email address.
• [Your Facebook URL], [Your LinkedIn URL], etc.: The URLs of your business’s social media profiles.
• [Your Rating] and [Number of Reviews]: Only if you have a verifiable aggregate rating, include these values.

This provides a complete, generic template for homepage schema. Remember to adapt the placeholders to your specific website and business information, and always validate your schema using the Google Rich Results Test after implementation. This structure is suitable for a wide range of websites, providing clear and accurate information to search engines.