SaleEvent Schema Example [2024]

Here’s an example for Black Friday:

It’s JSON format

{
  "@context": "http://schema.org",
  "@type": "SaleEvent",
  "name": "Black Friday Mega Sale",
  "startDate": "2024-11-29T00:00:00",
  "endDate": "2024-11-29T23:59:59",
  "eventAttendanceMode": "http://schema.org/OnlineEventAttendanceMode",
  "location": {
    "@type": "VirtualLocation",
    "url": "https://www.yourstore.com/black-friday-sale"
  },
  "offers": {
    "@type": "Offer",
    "url": "https://www.yourstore.com/black-friday-sale",
    "priceCurrency": "USD",
    "price": "199.99",
    "eligibleRegion": {
      "@type": "Place",
      "name": "United States"
    },
    "availability": "http://schema.org/InStock",
    "validFrom": "2024-11-29T00:00:00"
  },
  "organizer": {
    "@type": "Organization",
    "name": "Your Store",
    "url": "https://www.yourstore.com"
  }
}

It’s listed as schema type recongised by Google, and it shows on SERPs

saleevent

Source

Business Audience Schema Example [2024]



{
  "@context": "https://schema.org",
  "@type": "WebPage",
  "mainEntity": {
    "@type": "BusinessAudience",
    "audienceType": "Consumers",
    "description": "Middle-class residents of the United Kingdom interested in purchasing t-shirts.",
    "geographicArea": {
      "@type": "AdministrativeArea",
      "name": "United Kingdom"
    },
    "hasOfferCatalog": {
      "@type": "OfferCatalog",
      "name": "T-Shirts",
      "itemListElement": [
        {
          "@type": "Offer",
          "itemOffered": {
            "@type": "Product",
            "name": "T-Shirt"
          }
        }
      ]
    },
    "additionalType": "https://schema.org/Commerce",
    "audience": {
      "@type": "Audience",
      "audienceType": "Middle-class",
      "description": "Individuals with average to above-average income levels"
    }
  }
}

Here’s business Audience schema for a B2B business:

{
  "@context": "https://schema.org",
  "@type": "BusinessAudience",
  "audienceType": "Business",
  "numberOfEmployees": {
    "@type": "QuantitativeValue",
    "minValue": 50,
    "maxValue": 500
  },
  "yearlyRevenue": {
    "@type": "QuantitativeValue",
    "minValue": 1000000,
    "maxValue": 10000000
  },
  "geographicArea": {
    "@type": "AdministrativeArea",
    "name": "United States"
  }
}

Implementing Redirects with Filezilla and MTPutty (On a sonasi server)

This is our inhouse protocol, it might differ in normal places…

Open FileZilla – connect to M2 server (magento 2, rather than our magento 1 server)

Click domains folder –

Select relevant domain

Select Rewrites

Right Click – Config folder and click View/Edit – Open in a text editor like Sublime

Add redirects in the following format:

#Note to say who did redirects on what date

rewrite ^/rwl-x-la-new-member-starter-pack.html$ /gym-equipment.html permanent;
rewrite ^/rwl-x-la-ultimate-starter-pack-intermediate.html$ /gym-equipment.html permanent;
rewrite ^/rwl-x-la-new-member-dumbbell-pack.html$ /gym-equipment.html permanent;

- Save the file

This will redirect the URL example.com/rwl-x-la-new-member-starter-pack.html to example.com/gym-equipment.html

and so on…the other 2 below will also redirect to gym-equipment.html

Open MTPUTTY

Connect to relevant server – in my case – server 3

type in “ntest” and check for any error messages

if ok – type in “nreload”

That should be it!