NEWS

Google Changes More Structured Data Requirements via @sejournal, @martinibuster

Published

3 years ago

October 29, 2021

google structured data upda 617be3385aa3d sej

Google announced a change to several structured data types. This change affects the requirements for the HowTo, QAPage and the SpecialAnnouncement structured data. The guidance didn’t come with examples, which makes it a little difficult to understand but this article will walk through the changes.

The guidance provided by Google stated:

“Removed the following structured data fields from documentation, since they are unused by Google Search and Rich Result Test doesn’t flag warnings for them.”

In general, including structured data that isn’t required could be helpful if it helps describe a page better, even though that structured data won’t produce any visible results in Google’s search results pages in the form of rich results.

Google’s John Mueller has in the past commented on this:

“I think that’s one of the trickier questions with regards to all of the structured data, in that we have a lot of things that we use to try to understand a page and the content on the page that we don’t necessarily show directly in the search results.

But a lot of things help us to better understand the content and the context of a particular page.

And those are things within kind of like a general Schema.org markup which you can do various things.

And that’s kind of I’d say, almost a shame that we don’t highlight that in the rich results test.”

Continue Reading Below

Mueller then goes on to caution about going overboard with extra structured data.

With regard to the structured data properties that Google removed as being required, Google doesn’t warn against using them other than to say that the Rich Results test ignores it and that Google does not use it.

“…since they are unused by Google Search and Rich Result Test doesn’t flag warnings for them. “

HowTo Structured Data Changes

Google announced it has removed the “description” structured data field that pertains strictly to the HowTo data type. The “description” property can still be used in other properties of the HowTo data type, but it’s no longer needed in the HowTo part.

Here’s an example of how it used to be:

<script type="application/ld+json">
{ "@context": "https://schema.org", "@type": "HowTo", "name": "How to tile a kitchen backsplash",
"description": "Any kitchen can be much more vibrant with a great tile backsplash. This guide will help you install one with beautiful results, like our example kitchen seen here.", "image": { "@type": "ImageObject", "url": "https://example.com/photos/1x1/photo.jpg", "height": "406", "width": "305"
},

Here is the new way that omits the “description” property of the HowTo type:

<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "HowTo",
"name": "How to tile a kitchen backsplash",
"image": {
"@type": "ImageObject",
"url": "https://example.com/photos/1x1/photo.jpg",
"height": "406",
"width": "305"
},

It’s a little tricky at first because the documentation doesn’t explain it in depth.

The documentation simply states:

Removed the following structured data fields from documentation, since they are unused by Google Search and Rich Result Test doesn’t flag warnings for them:
HowTo: description.”

Continue Reading Below

See what I meant when I said that the documentation was a bit sparse?

Change to the QAPage Structured Data

The author property has been removed as a requirement when using the suggestedAnswer property, under the mainEntity property.

The suggestedAnsswer property is described as:

“One possible answer, but not accepted as a top answer (acceptedAnswer). There can be zero or more of these per Question.”

The purpose of the now removed author property was to name the author of the question.

The guidance from Google is written out like this:

mainEntity.suggestedAnswer.author

Kind of opaque, right?

Here is what the changed structured data used to look like:

"suggestedAnswer": [
{ "@type": "Answer", "text": "Are you looking for ounces or fluid ounces? If you are looking for fluid ounces there are 15.34 fluid ounces in a pound of water.", "dateCreated": "2016-11-02T21:11Z", "upvoteCount": 42, "url": "https://example.com/question1#suggestedAnswer1",
"author": {
"@type": "Person",
"name": "AnotherUser"
}

This is what it looks like now:

"suggestedAnswer": [
{ "@type": "Answer", "text": "Are you looking for ounces or fluid ounces? If you are looking for fluid ounces there are 15.34 fluid ounces in a pound of water.", "upvoteCount": 42, "url": "https://example.com/question1#suggestedAnswer1"
},

See the difference?

Everything after the URL part that pertains to the “author” property is gone.

These additional properties that are a part of the mainEntity property have also been removed

mainEntity.dateCreated
mainEntity.suggestedAnswer.dateCreated
mainEntity.acceptedAnswer.author
mainEntity.acceptedAnswer.dateCreated
mainEntity.author

SpecialAnnouncement Structured Data

The SpecialAnnouncement structured data is a Covid-19 structured data that is in Beta, meaning that it’s not super official yet. In fact, the SpecialAnnouncement structured data itself is still under development at Schema.org.

Google offered these examples of situations where the SpecialAnnouncement structured data is appropriate:

“Announcement of a shelter-in-place directive

Closure notice (for example, closing a school or public transportation)

Announcement of government benefits (for example, unemployment support, paid leave, or one-time payments)

Quarantine guidelines

Travel restrictions

Notification of a new drive-through testing center

Announcement of an event transitioning from offline to online, or cancellation

Announcement of revised hours and shopping restrictions

Disease spread statistics and maps”

The following properties have been removed for SpecialAnnouncement and are no longer required:

provider
audience
serviceType
address
category

Here’s an example of the “serviceType” and “provider” properties that are no longer required:

Continue Reading Below

Before:

"governmentBenefitsInfo": { "@type": "GovernmentService", "name": "Paycheck Protection Program", "url": "https://www.sba.gov/funding-programs/loans/coronavirus-relief-options/paycheck-protection-program-ppp",
"provider": {
"@type": "GovernmentOrganization",
"name": "US Small Business Administration"
},
"serviceType": "https://schema.org/BusinessSupport",
"audience": {
"@type": "Audience",
"name": "Small businesses"
}

After:

“governmentBenefitsInfo”: {
“@type”: “GovernmentService”,
“name”: “Paycheck Protection Program”
}

It’s a big difference without the structured data properties that are missing but it’s also simpler.

If in doubt or confused, I suggest reviewing the before and after versions of the structured data. You can find the before version at Archive.org

Citations

Google’s QA Page Structured Data Developer Page
https://developers.google.com/search/docs/advanced/structured-data/qapage

Google’s HowTo Structured Data Type Page
https://developers.google.com/search/docs/advanced/structured-data/how-to

Google’s SpecialAnnouncements Structured Data Help Page
https://developers.google.com/search/docs/advanced/structured-data/special-announcements

Google’s Changelog for Updates to their Documentation
https://developers.google.com/speed/docs/insights/release_notes

Searchenginejournal.com

NEWS

OpenAI Introduces Fine-Tuning for GPT-4 and Enabling Customized AI Models

Published

3 weeks ago

August 21, 2024

Max

OpenAI Introduces Fine-Tuning for GPT-4 and Enabling Customized AI Models

OpenAI has today announced the release of fine-tuning capabilities for its flagship GPT-4 large language model, marking a significant milestone in the AI landscape. This new functionality empowers developers to create tailored versions of GPT-4 to suit specialized use cases, enhancing the model’s utility across various industries.

Fine-tuning has long been a desired feature for developers who require more control over AI behavior, and with this update, OpenAI delivers on that demand. The ability to fine-tune GPT-4 allows businesses and developers to refine the model’s responses to better align with specific requirements, whether for customer service, content generation, technical support, or other unique applications.

Why Fine-Tuning Matters

GPT-4 is a very flexible model that can handle many different tasks. However, some businesses and developers need more specialized AI that matches their specific language, style, and needs. Fine-tuning helps with this by letting them adjust GPT-4 using custom data. For example, companies can train a fine-tuned model to keep a consistent brand tone or focus on industry-specific language.

Fine-tuning also offers improvements in areas like response accuracy and context comprehension. For use cases where nuanced understanding or specialized knowledge is crucial, this can be a game-changer. Models can be taught to better grasp intricate details, improving their effectiveness in sectors such as legal analysis, medical advice, or technical writing.

Key Features of GPT-4 Fine-Tuning

The fine-tuning process leverages OpenAI’s established tools, but now it is optimized for GPT-4’s advanced architecture. Notable features include:

Enhanced Customization: Developers can precisely influence the model’s behavior and knowledge base.
Consistency in Output: Fine-tuned models can be made to maintain consistent formatting, tone, or responses, essential for professional applications.
Higher Efficiency: Compared to training models from scratch, fine-tuning GPT-4 allows organizations to deploy sophisticated AI with reduced time and computational cost.

Additionally, OpenAI has emphasized ease of use with this feature. The fine-tuning workflow is designed to be accessible even to teams with limited AI experience, reducing barriers to customization. For more advanced users, OpenAI provides granular control options to achieve highly specialized outputs.

Implications for the Future

The launch of fine-tuning capabilities for GPT-4 signals a broader shift toward more user-centric AI development. As businesses increasingly adopt AI, the demand for models that can cater to specific business needs, without compromising on performance, will continue to grow. OpenAI’s move positions GPT-4 as a flexible and adaptable tool that can be refined to deliver optimal value in any given scenario.

By offering fine-tuning, OpenAI not only enhances GPT-4’s appeal but also reinforces the model’s role as a leading AI solution across diverse sectors. From startups seeking to automate niche tasks to large enterprises looking to scale intelligent systems, GPT-4’s fine-tuning capability provides a powerful resource for driving innovation.

OpenAI announced that fine-tuning GPT-4o will cost $25 for every million tokens used during training. After the model is set up, it will cost $3.75 per million input tokens and $15 per million output tokens. To help developers get started, OpenAI is offering 1 million free training tokens per day for GPT-4o and 2 million free tokens per day for GPT-4o mini until September 23. This makes it easier for developers to try out the fine-tuning service.

As AI continues to evolve, OpenAI’s focus on customization and adaptability with GPT-4 represents a critical step in making advanced AI accessible, scalable, and more aligned with real-world applications. This new capability is expected to accelerate the adoption of AI across industries, creating a new wave of AI-driven solutions tailored to specific challenges and opportunities.

GOOGLE

This Week in Search News: Simple and Easy-to-Read Update

Published

2 months ago

June 30, 2024

Entireweb News Bot

This Week in Search News: Simple and Easy-to-Read Update

Here’s what happened in the world of Google and search engines this week:

1. Google’s June 2024 Spam Update

Google finished rolling out its June 2024 spam update over a period of seven days. This update aims to reduce spammy content in search results.

2. Changes to Google Search Interface

Google has removed the continuous scroll feature for search results. Instead, it’s back to the old system of pages.

3. New Features and Tests

Link Cards: Google is testing link cards at the top of AI-generated overviews.
Health Overviews: There are more AI-generated health overviews showing up in search results.
Local Panels: Google is testing AI overviews in local information panels.

4. Search Rankings and Quality

Improving Rankings: Google said it can improve its search ranking system but will only do so on a large scale.
Measuring Quality: Google’s Elizabeth Tucker shared how they measure search quality.

5. Advice for Content Creators

Brand Names in Reviews: Google advises not to avoid mentioning brand names in review content.
Fixing 404 Pages: Google explained when it’s important to fix 404 error pages.

6. New Search Features in Google Chrome

Google Chrome for mobile devices has added several new search features to enhance user experience.

7. New Tests and Features in Google Search

Credit Card Widget: Google is testing a new widget for credit card information in search results.
Sliding Search Results: When making a new search query, the results might slide to the right.

8. Bing’s New Feature

Bing is now using AI to write “People Also Ask” questions in search results.

9. Local Search Ranking Factors

Menu items and popular times might be factors that influence local search rankings on Google.

10. Google Ads Updates

Query Matching and Brand Controls: Google Ads updated its query matching and brand controls, and advertisers are happy with these changes.
Lead Credits: Google will automate lead credits for Local Service Ads. Google says this is a good change, but some advertisers are worried.
tROAS Insights Box: Google Ads is testing a new insights box for tROAS (Target Return on Ad Spend) in Performance Max and Standard Shopping campaigns.
WordPress Tag Code: There is a new conversion code for Google Ads on WordPress sites.

These updates highlight how Google and other search engines are continuously evolving to improve user experience and provide better advertising tools.

FACEBOOK

Facebook Faces Yet Another Outage: Platform Encounters Technical Issues Again

Published

6 months ago

March 20, 2024

Max

Uppdated: It seems that today’s issues with Facebook haven’t affected as many users as the last time. A smaller group of people appears to be impacted this time around, which is a relief compared to the larger incident before. Nevertheless, it’s still frustrating for those affected, and hopefully, the issues will be resolved soon by the Facebook team.

Facebook had another problem today (March 20, 2024). According to Downdetector, a website that shows when other websites are not working, many people had trouble using Facebook.

This isn’t the first time Facebook has had issues. Just a little while ago, there was another problem that stopped people from using the site. Today, when people tried to use Facebook, it didn’t work like it should. People couldn’t see their friends’ posts, and sometimes the website wouldn’t even load.

Downdetector, which watches out for problems on websites, showed that lots of people were having trouble with Facebook. People from all over the world said they couldn’t use the site, and they were not happy about it.

When websites like Facebook have problems, it affects a lot of people. It’s not just about not being able to see posts or chat with friends. It can also impact businesses that use Facebook to reach customers.

Since Facebook owns Messenger and Instagram, the problems with Facebook also meant that people had trouble using these apps. It made the situation even more frustrating for many users, who rely on these apps to stay connected with others.

During this recent problem, one thing is obvious: the internet is always changing, and even big websites like Facebook can have problems. While people wait for Facebook to fix the issue, it shows us how easily things online can go wrong. It’s a good reminder that we should have backup plans for staying connected online, just in case something like this happens again.