Chris Long

So yet another company joining the party in lawsuits against Google's anti-competitive behavior.

It seems unlikely that this one will prove successful (especially if there's precedent for featured snippets).

As part of the statement, Chegg mentioned that their non-subscriber traffic is down -49% in January 2025.

This is compared to a -8% decline in Q2 2024 (this is quarter that Google launched AI Overviews).

In Chegg's official statement, they provide three arguments:

1. Reciprocal Dealing

2. Monopoly Maintenance:

3. Unjust Enrichment

Google sued by Chegg over AI Overviews hurting traffic and revenue Will other companies follow suit and go after Google for sending less traffic to sites and publishers with these new AI Overviews?

This was a story that was was written by CNBC and reported on by @rustybrick.com in Search Engine Land.

Yesterday, Chegg officially launched a lawsuit against Google, specifically citing their AI Overviews and the impact on their business.

searchengineland.com/google-sued-...

Big SEO News: Chegg is suing Google over AI Overviews.

They claim that AIOs have had a "profound impact on Chegg’s traffic, revenue, and workforce":

Using @id in Schema.org Markup for SEO, LLMs, & Knowledge Graphs | Momentic The complete guide to using @id for SEO and Knowledge Graphs

Very in-depth article on a niche aspect of structured data that I haven't explored too much before.

Also big shout out to @aleyda.bsky.social for including this in her newsletter: momenticmarketing.com/blog/id-sche...

6. He also gives best practices when using the "@id" property.

Some of these include using descriptive fragments ("Organization", not "ID1"), using the same format across pages and testing markup through the Rich Results Tool.

5. In a very interesting snippet, he talks about using the "@graph" property of structured data when connecting multiple entities on the same page.

You define the "@graph" property at the top of the structured data, then define each subproperty's "type" and connect them by using "@id".

4. Tyler also recommends paring "@id" properties with "sameAs" schema. The "sameAs" schema can be used to reference external profiles (author pages, social profiles, Wikipedia).

This helps pair your internal ID function with external references that Google can easily connect.

3. Tyler recommends that to reference entities cross-pages, it's best to pair an "@id" property with a URL. This allows for a more explicit connection between the two properties.

The URL would be formatted as a URL, while the ID would be formatted as as fragment.

2. The "@id" property acts as a "variable" that you define in one place and reference in other aspects of your site. For example, you could link your website to an "Organization" ID property.

In another markup, you reference that "Organization" variable when defining the Publisher of an article.

1. The "@id" property can be used to uniquely identify nodes in your site's data graph.

It is actually an INTERNAL reference system for your site, generally using URL or URL fragments.

Using @id in Schema.org Markup for SEO, LLMs, & Knowledge Graphs | Momentic The complete guide to using @id for SEO and Knowledge Graphs

This is a super interesting article from @tylereinberger.com on the benefits of the "@id" structured data property.

By using this property in your structured data more, you're able to created strong + more direct connections between your site's entities: momenticmarketing.com/blog/id-sche...

Advanced Schema SEO: This article showcases how to use "@id" schema to create powerful connections between your site's entities:

We're also seeing trends that sites that limit the use of JavaScript tend to perform better in the commerce results.

For the record, loading content through JavaScript isn't necessarily bad.

However, it means you need to double check the indexation of those sections to be 100% sure Google is seeing it properly.

You'll then want to verify the indexation. Perform some "site:" searches for the content to see if Google actually records the content in it's index.

Or utilize the Rich Results Tool to ensure Google can render the whole page.

Understand JavaScript SEO Basics | Google Search Central  |  Documentation  |  Google for Developers Discover how Google Search processes JavaScript and explore best practices for improving JavaScript web apps for Google Search.

From an SEO perspective, we know that Google can have trouble indexing JavaScript - especially if there's a lot to process or it creates major conflicts between the raw HTML.

developers.google.com/search/docs/...

You'll be able to assess the sections most "at risk" from an SEO perspective.

Web Developer - Chrome Web Store Adds a toolbar button with various web developer tools.

For this reason, it's critical to analyze any commerce site with JavaScript turned off. You'll be easily able to visualize the content that requires JS in order to load.

You can use the Web Developer extension to do this: chromewebstore.google.com/detail/web-d...

During my time in SEO, I've found that retail sites are the biggest culprits of using JavaScript to load content.

There are just so many technologies that use it nowadays to insert content. Review platforms, headless CMS, personalization software and more.

Ecommerce SEO Tip: Always analyze your product and category pages with JavaScript turned off.

You'll easily spot content that's JS-dependent:

Also worth noting that I was quoted in this along with some other great SEOs such as @Michael King, Crystal Carter and Kevin Indig

So the biggest takeaway to me is that A LOT more people have the "Search" function turned on than what I thought.

This means that there's a ton of opportunities for SEOs as the search feature is the one you can control the most.

7. Finally, they analyzed the site's that are most likely to get traffic from ChatGPT Search.

They found that Online Services, Education and Mass Media were the biggest industries. Entertain, travel and real estate were at the bottom of the list.

6. They also analyzed websites that were more likely to get traffic from ChatGPT than Google. They found that a lot of AI-related sites (AIPRM, RANKIQ were cited) are more likely to get traffic.

5. When it came to transactional queries, Google and ChatGPT had similar ratios of about 8% of searches.

4. They also compared the intents of ChatGPT interactions against Google searches. They found that 52.2% of ChatGPT prompts had "Informational" intent when compared to Google's 36.4%.

3. When using ChatGPT Search, prompts tend to much shorter. They averaged only 4.2 words, compared to 23 words with Search turned off.

2. They also looked whether users had the "Search" feature turned on our off.

They found that 46% of people use ChatGPT with Search turned on. This is a lot more people than I would have thought.

1. ChatGPT is rapidly expanding as a search referrer. In July 2024, Semrush found that ChatGPT sent traffic to less than 10,000 domains in a day. In November 2024, that increased to 30,000+ domains.