WordPress Playground – A New Tool You Need To Try Right Now via @sejournal, @martinibuster

WordPress has been releasing innovative tools that helps users accomplish their goals and become more proficient users. One of the newest tools is called Playground, a tool that is designed to make a WordPress site instantly available for testing, learning and building.

Background On WordPress Playground

Playground is a tool that runs in your browser.

The official WordPress documentation for Playground suggests these uses:

  • Try a block, a theme, or a plugin
  • Build an entire site, save it, host it
  • Test your plugin with many specific WordPress and PHP versions
  • Embed a real, interactive WordPress site in your tutorial or course
  • Showcase a plugin or theme on your website
  • Build a native app running WordPress and put it in App Store
  • Preview pull requests from your repository

There is also a WordPress Plugin available, Playground By WordPress Contributors, that enables a user to clone their site to a private in-browser Playground version.

The WordPress plugin allows a user to create an exact website copy within a Playground instance, from which a user can do things like test a plugin or theme. Any changes made to the Playground instance do not affect the actual website. The cloned site is not uploaded to any cloud service, all the data remains private, residing within a user’s web browser, where it stays until the browser tab is closed.

Interview: Adam Zieliński, WordPress Playground Architect @ Automattic

I interviewed Adam Zieliński, the WordPress Playground Architect at Automattic, to learn more about what Playground is and how it can be useful for developers and regular users of WordPress.

The first thing I wanted to know is, what is Playground and why should anyone use it, what should people expect from it?

Adam Zieliński:

“Playground is WordPress in a single click. There are no tedious setup steps, webhosts account, or technical talk.

Playground is not the site at playground.wordpress.net. It is the groundbreaking technology that makes that site possible and also powers a new generation of interactive, single-click WordPress tools. There are interactive tutorials, QA (Quality Assurance) workflows, “try before you buy” previewers for plugins, collaboration tools, contribution workflows and so much more.

Here are two examples:

The site at playground.wordpress.net doubles as a QA tool – you can try the upcoming WordPress release, test your plugin or theme with five other plugins and then see how it performs on different WordPress and PHP versions. It proved useful for sourcing feedback during the WordPress 6.5 release cycle, the Font library call for testing, and more.

As a WordPress plugin, Playground can clone your existing WordPress site, including all content, plugins, and themes, inside a private Playground instance. This gives you a way of testing changes, new plugins, or updates before pushing them live and without needing a separate hosting.

The next example is a bit more technical but I’ll still go with it. Playground can be embedded on websites. There are companies out there showcasing a live version of their plugin or theme using a live WordPress Playground site embedded inside their actual site. That’s highly useful for their future customers – even if they have no clue about what Playground is.”

I followed up with a question asking how he would describe Playground to someone who uses WordPress but doesn’t dabble in the development part.

Adam Zieliński:

“Playground is a version of WordPress that runs directly on your device, not on a webhost. You can open Playground on your phone, turn off the internet, and continue using it.”

I next asked if it’s useful for migrating to a new template or testing plugin updates.

Adam Zieliński:

“Absolutely. You can clone your site using the Playground WordPress plugin and try the new template or the updated plugin there first without risking breaking your production site. That plugin also adds a “preview now” button to the plugins search in wp-admin so you can “try them on” before committing to installing one on your live site.”

Zieliński next recommended the following resources to view and read more about Playground:

WordPress Playground: the ultimate learning, testing, & teaching tool for WordPress

How to use WordPress Playground for interactive demos

How to start using WordPress Playground

Does Playground help regular WordPress users become familiar with developing sites themselves, is it a hands-on way to learn how to use WordPress?

Adam Zieliński:

“Playground makes a great learning tool. You can just hop on playground.wordpress.net and start exploring WordPress, whether that means creating your first post or installing fifteen plugins and building an entire site.

The experience is very self-guided today, which is useful in classes, workshops and meetups where an instructor can give you directions.

We’re also exploring an interactive and guided tutorials. Imagine visiting WordPress.org, clicking on, say, “I want to build my first WordPress site”, and getting clear directions and an interactive WordPress site to work on. That’s what we’re building towards.

And this doesn’t have to be a distant future. Anyone can start creating these interactive learning experiences today with the Playground Block – it’s a single-click way of embedding Playground in your WordPress content. You can play with that block right now if go to the plugin page and by click the Live Preview button. Oh, and that live preview? It’s also powered by WordPress Playground!”

Is Playground compatible with popular WordPress website builders?

Adam Zieliński:

“I haven’t tested Divi. Elementor mostly works, although there’s a technical issue in the onboarding flow that needs to be fixed in Elementor fix before it’s fully functional.”

Playground has a feature called Blueprints, configuration setting files. I asked Adam how he would describe Blueprints and how is it useful to users.

Adam Zieliński:

Blueprints are guidelines for Playground on how to create the WordPress site for you.

Blueprints are also like puzzle pieces. In fact, at WCEU 2024, you’ll build real WordPress sites with physical puzzle pieces. We’ve printed puzzle pieces representing site configuration steps like installing a plugin or changing the site name and attendees will be able to collect and scan them with an app that will load Playground with the configuration (Blueprint) they put together.

See also: What are Blueprints, and what can you do with them?

About the usefulness of Blueprints – there are two sides to that. You can either use a Playground site created based on an existing Blueprint, or you can create a new Blueprint.

If you just want to enjoy Playground-based tools, you don’t even need to know what Blueprints are. All you’ll experience is a button that opens a WordPress site preconfigured to do anything at all. It could help you test a theme, contribute a documentation page, or even build a slide deck and export it to PDF.

If you want to build new Blueprints, today you need to get your hands dirty and write some JSON code. Blueprints 101 and Technical Introduction to Playground will walk you through the steps and you can also preview the examples in the Blueprints Gallery. It’s worth noting we’re working on a visual tool where you’ll be able to just assemble these steps like puzzle pieces without any coding knowledge.”

Is this a way to create a site and then save or share the demo?

Adam Zieliński:

“Yes! Playground sites are temporary by default but there’s many ways to save and share them. On playground.wordpress.net there’s a settings button where you can tell Playground to save your site in your web browser. Once you do that and refresh the page, you’ll return right to your site. You can also synchronize the site with a directory on your computer and all the Playground changes will show up there. Then you can also export your site as a zip file or to GitHub.

There are two ways of sharing a site with others.

The first one, is to create a Blueprint – so write down all the step by step instructions for Playground to recreate that site. You could then include that Blueprint in a link and share it with the world.

Blueprints are powerful but not always convenient, so there’s also a second way. A Playground site can be exported as a zip file. You can host that zip file, for example on GitHub, and create a Playground link to load it.”

Someone from the WordPress developer community passed this question along:

“Site builders often have one or more “starter sites”, which seem to squarely line up with blueprints, though they usually include premium themes and plugins. Drupal has “Distributions,” which are basically pre-configured starter sites often with a niche focus.

Imagine a preconfigured install of core, a theme, a membership plugin, and payment setup (waiting for gateway API keys). If you want a membership site then just install this and start adding content. Or a preconfigured help desk system and so on.

So, I’m wondering if the vision is that Blueprints will provide something similar?”

Adam Zieliński:

“Blueprints enable just that. Live previews in the WordPress plugin directory are an example – every time you get an identical site pre-configured for a particular plugin. It always installs a fresh WordPress and the latest versions of all the co-existing plugins and themes. You can prepare a Blueprint for your particular setup and work with it in the browser, or you can also use the Playground CLI tool to work with these starter sites on your local computer. We’re building a PHP library to enable webhosts to support Blueprints – template sites may then become a common feature in the WordPress hosting landscape.”

WordPress Playground

A playground is a place that is designed for and encourages activities. That’s exactly what WordPress Playground is about. Anyone who uses WordPress should give Playground a try or at the very least become familiar with it because knowledge broadens perspectives, aids in problem solving, and makes one a more effective competitor and business person.

Featured Image by Shutterstock/Leszek Czerwonka

Core Web Vitals: WordPress, Wix, Squarespace, Joomla, Duda, & Drupal via @sejournal, @martinibuster

The Core Web Vitals technology report shows that five out of six of the most popular content management systems performed worse in April 2024 when compared to the beginning of the year. The real-world performance data collected by HTTPArchive offers some clues about why performance scores are trending downward.

Core Web Vitals Technology Report

The rankings for Core Web Vitals (CWV) are a mix of real-world and lab data. The real-world data comes from the Chrome User Experience Report (CrUX) and the lab data is from an HTTP Archive public dataset (lab data based on the websites included in the CrUX report).

The data is used to create the Core Web Vitals technology report which can be sliced and diced to measure the mobile and desktop performances for a wide variety of content management systems in any combination, as well as provide data on JavaScript, CSS HTML and image weight data.

The data reported in the Search Engine Journal articles are based on measurements of mobile data. The scores are in the form of percentages which represent the percentages of website visits that resulted in a good Core Web Vitals (CWV) score.

This is the background on the HTTP Archive scoring for CWV:

“Core Web Vitals
There may be different approaches to measure how well a website or group of websites performs with CWV. The approach used by this dashboard is designed to most closely match the CWV assessment in PageSpeed Insights”

This is the background information about the HTTP Archive lab data:

“HTTP Archive measures individual web pages, not entire websites. And due to capacity limitations, HTTP Archive is limited to testing one page per website. The most natural page to test for a given website is its home page, or the root page of the origin.”

Source of quotes, HTTP Archive.

Top Core Web Vitals Performance

The highest performing content management system (CMS) of the six CMS under comparison is Duda, a closed-source website builder platform that is used by agencies and developers for creating and managing large portfolios of client sites. 71% of website visits resulted in a good core web vitals score. Duda’s score is 13 percentage points ahead of the second place winner, Squarespace, another closed source website building platform.

Sites built with Duda consistently have higher CWV performance rates than any other CMS, by a wide margin. Squarespace, Drupal and Wix are bunched together with similar performance scores, with the Joomla and WordPress scoring in fifth and sixth place.

WordPress Is Faster But Other Factors Slowing It Down

Although WordPress is ranked in sixth place, it’s performance did not drop as much as the other leading content management systems, quite possibly reflecting the many performance improvements in
present in each new version of WordPress. WordPress 6.5, released in early April 2024, featured over 100 performance improvements to the backend and the front end.

The performance score for WordPress was slightly lower in April 2024 than in the beginning of the year, but less than one percentage point. However, that percentage drop is lower than the top ranked CMS, Duda, which experienced a drop of 5.41 percentage points.

Chrome Lighthouse is an automated tool for measuring website performance. The Lighthouse scores for WordPress in January of this year was 35%, which means that 35% of measured WordPress sites had a good Lighthouse CWV score. The CWV score took a dip in February and March but it zipped back to 35% in April, perhaps reflecting the many performance improvements in WordPress version 6.5.

The scores for the average Page Weight is likely where the performance lagged. Page Weight is the average number of bytes sent over the network, which could be compressed. The average Page Weight of WordPress sites started out at 568.48 in January and increased to 579.92, an increase of 11.44.

The average download size of images when compared from January to April 2024 increased by 49.5 Kilobytes but that’s something that has more to do with how publishers use WordPress and not how WordPress is being used. These could be contributing to the essentially flat performance change this year. But again, virtually no change in performance is better than what’s going on with other content management systems which experienced larger drops in their performance rates.

Top CWV Performance By CMS

The list of CWV performance represents the percentage of sites using a given CMS that has a good CWV score. Here is the list of the top performers with their respective percentage rates:

  1. Duda 71%
  2. Squarespace 58%
  3. Drupal 54%
  4. Wix 52%
  5. Joomla 43%
  6. WordPress 38%

Performance Drops By CMS

Comparing the performance drop by CMS shows a weird trend in that four out of six content management systems had relatively high drops in performance. The following is a comparison of performance drops by percentage points, indicated with a minus sign.

List By Performance Change

  • Wix -7.11
  • Duda -5.41
  • Joomla -2.84
  • Drupal -2.58
  • WordPress -0.71

As can be seen above, WordPress had the lowest drop in performance. Wix and Duda had the steepest drops in performance while Squarespace was the only CMS with an increase in performance, with a positive score of +3.92.

Core Web Vitals Scores – Takeaways

Duda is clearly the Core Web Vitals performance champ, outscoring every content management system in this comparison. Squarespace, Wix and Drupal are close behind in a tight pack.  Out of the six platforms in this comparison only Squarespace managed to improve their scores this year.

All of the other platforms in this comparison scored less well in April compared to the beginning of the year, possibly due to increases in page weight, particularly in images but there might be something else that accounts for this anomaly that isn’t accounted for  in the HTTP Archive reports.

The WordPress performance team continues to score notable improvements to the WordPress core and the slight performance drop of less than one percent may be because of how publishers are using the platform.

It’s safe to say that all the platforms in this comparison are winners because all of them show steady improvements in general.

Explore the HTTP Archive Core Web Vitals report here.

Featured Image by Shutterstock/Roman Samborskyi

WordPress Releases Way To Build Sites On A Windows Desktop via @sejournal, @martinibuster

Last month WordPress released a way to create or test WordPress sites on the desktop but the app was limited to Apple Mac devices. This month WordPress announces that WordPress Studio is now available for Microsoft Windows.

According to WordPress, Microsoft Windows users account for over 25% of WordPress developers. But it’s possible that non-developers who use WordPress for their websites may account for many more people who use WordPress and would like to learn how to create with it.

WordPress Studio is an easy to use development platform that will help developers who use Microsoft Windows as well as non-developers who want to learn how to use WordPress without messing anything up on a live website.

The official WordPress announcement explained:

“We recently launched Studio, our free and open source local WordPress development environment, for MacOS, and we’re happy to share that the Windows version of Studio is now available!

As a reminder, we’ve built Studio to be the fastest and simplest way to build WordPress sites locally.”

Local WordPress Development

Local development is a way to work on a website from the desktop (local) as opposed to working on the site on a webhost. There are many reasons to work on a website locally, with convenience being at the top of the list. Working on a website directly on a desktop environment makes it unlikely for a mistake that could cause the site to go public and causing unintended ranking consequences for the actual site that’s live on the web, which is a second reason why local development is popular.

A third reason for local development is that it’s cheaper, faster and for those with less development skills, it’s generally easier than creating an online testing site for the purpose of testing new plugins to verify they won’t break a site or simply for creating a demo site for sharing with a client or a team.

Until now, the downside of local development is that many of the most popular local development platforms have a steep learning curve which is inconvenient for publishers and SMBs who don’t have the time to devote to learning yet another skill. I know about the learning curve because I’ve used a few local development platforms in the past.

WordPress Studio

WordPress has now released a solution to the problem of local WordPress development that’s specific to WordPress and makes it easier for WordPress users to test, develop and learn how to become more comfortable with WordPress. It’s easy to break a WordPress site and until now there was never an easy way to test WordPress plugins without additional expense or to just plain old learn how to use WordPress.

WordPress lists the following benefits:

  • Demo sites
    Forget Ngrok-like tunnels—share interactive snapshots of your local sites with clients or colleagues, powered by WordPress.com.
  • Superfast WordPress installation
    Regardless of how many sites you’re working on, you can create unlimited local sites in Studio.
  • Dependency-free building
    Build lightweight and reliable local WordPress sites, powered by WordPress Playground, without the hassle of Docker, NGINX, Apache, or MySQL.
  • One-click admin
    Spend less time wrangling passwords—open WP Admin for each site with just one click.
  • Open your site anywhere
    Develop your sites your way. Open your site’s code in your favorite IDE, CLI, or file browser to fit your workflow.
  • Built by the biggest contributor to WordPress core
    With 109 active contributors, we know WordPress inside and out.

Create And Share A Demo Site

One of the fantastic features of WordPress Studio is the ability to share your demo sites with others on your team or with clients, to get feedback and iteratively improve the website. A user first needs to create a WordPress.com account and connect the local Studio desktop app to the WordPress account. Users are able to host five demo sites for free on a temporary domain (WP.build). Free demo sites last for 7 days after the last update to the demo site so if you need it to stay longer just update the demo site.

All demo sites can be manually deleted from the hosted demo and also on the desktop.

Screenshot Of How To Delete A Website In Studio

Support For Exporting A Theme

The WordPress Studio local development environment has the functionality for exporting a theme. Users can create a theme on their desktop environment and then select to export the theme. The Studio app will export the theme as a zip file which can then be uploaded to a live site (or a staging environment) online.

Full instructions on how to use Studio is available on WordPress.com. Judging by the instructions, using Studio appears to be a lot easier to use compared to other local development solutions that in general are made to accommodate a wide range of websites, not just WordPress sites. The learning curve appears to be relatively gentle compared to other local development environments.

Read more about the Windows version of WordPress Studio:

Studio: Now Available for Windows

Download a Windows or Mac version of Studio, both versions are free:

Build Fast, Ship Faster with Studio

Doubts Emerge Over Alleged Google Data Leak via @sejournal, @martinibuster

Many SEOs are coming to the conclusion that the alleged Google data leak was not a leak, did not contain ranking algorithm secrets, was five years out of date and it did not show anything new. While that’s not how everyone feels about it, SEOs in general don’t tend to agree about anything.

As SEJ reported yesterday, there were signs that this was not a ranking algorithm data dump and that there were many unanswered questions.

Our take about the alleged leak was:

“At this point in time there is no hard evidence that this “leaked” data is actually from Google Search… and not related in any way to how websites are ranked in Google Search.”

At this point we have more information and many SEOs are saying that the information is not an algorithm data dump.

Some SEOs Urged Caution

While many in the search community were quick to accept the claims of a data leak at face value, others who care about actual facts cautioned to slow down and think first and to be open minded to all possibilities.

Tweet By Ex-Googler Pedro Dias

Tweet with the following words: There's nothing worse than information without context. Also, there’s no point in trying to explain anything to someone that only accepts what aligns with their predefined assumptions and biases.

Ryan Jones was the first to offer a modest note of caution, advising people in a tweet to view the information objectively and without preconceived ideas.

Ex-Googler Pedro Dias tweeted:

“Have no issues with the shared data. And advising caution on the interpretation of some items.”

Pedro followed up with another tweet to explain why he couldn’t comment on specifics:

“I can only speak for me. I think you understand why I can’t just correct specific items. What I’m saying is that context is needed and room should be given for interpretation.”

Someone tweeted that Pedro’s response didn’t add anything to the discussion.

Pedro responded:

“I didn’t say that. All I’ve been saying is please be careful jumping to conclusions. If you think that’s not helpful, than I’m sorry.”

The ex-Googler later tweeted about the importance of having discussions:

“Let’s remind everyone:
– It’s healthy to bring logical arguments to a discussion.

– It’s not healthy to expect everyone to buy opinions without discussing. Especially when it comes from data sources lacking context.”

Search marketing expert Dean Cruddance tweeted:

“There isn’t anything that gives away the secret sauce.”

To which ex-Googler Pedro Dias responded:

“100%
But the impact of this, fuels a lot of tinfoil hattery and simplistic takes on search, which is suboptimal.

In the end, I believe it’s more detrimental than beneficial. Not for the information it contains, but by how it’s gonna be spun and interpreted.”

This SEO Is Not Buying It

As the day passed more and more SEOs began openly doubting the leak. Twenty-year search marketing expert Trevor Stolber (LinkedIn profile) posted his observations about the alleged leak, indicating that he wasn’t “buying it.”

Some of what he posted on LinkedIn:

  • “It’s from a deprecated code base (still very interesting – but old and not used)
  • It’s not actually from their ranking algorithm, it is an API used internally
  • We already knew most of the things that are in there
  • Good production code documentation would specify ranges and values – I see none of that here
  • Google doesn’t use DA (Domain Authority) – DA is an analog to PR (Page Rank) which was Google’s stand-out differentiator – I am not sure why so much attention is being paid to these nuances.”

Kristine Schachinger, another SEO who I personally know to be an expert, commented in that discussion that the information in the so-called leak dated from 2019.

“I have been reading the raw dump and they are all dated 2019 and there is literally nothing you can gather from 90% of the pages — I so agree. “

Others in that discussion openly questioned if it was actually a leak and most everyone agreed that there was nothing new in it and advised it was better to focus on Google’s new AI Overviews, particularly because AI doesn’t follow ranking factors.

This Was Not A Leak?

Out of all the people in SEO, the person who can most be described as the father of modern SEO is Brett Tabke. He is the founder of PubCon search marketing conference and also the founder of WebmasterWorld, which in the early days of SEO was the largest and most important SEO forum in the world. Brett is also the person who coined the acronym SERPs (for search engine results pages).

Brett devoted five hours to studying the data leak and then posted his observations on Facebook.

Among his observations (paraphrased):

  • This is not a leak
  • There is zero in it that’s directly algorithm related but rather they are API calls.
  • He found nothing that points to how any of the data could be used as part of a ranking algorithm.

Ash Nallawalla, an enterprise SEO with over 20 years experienced commented:

“Like I said a few times, it is merely an API document with a list of calls and not an algo code dump. At the most, we can learn some more internal Google terminology.”

Google Data Leak: Where Are The Facts?

It’s sinking in within the SEO community that this wasn’t the Google algorithm data leak that some expected it to be. In fact, it wasn’t even a leak by a Googler. And far from being algorithm secrets many are agreeing that there is nothing new in there and that it’s just a distraction.

Google Data Leak Clarification via @sejournal, @martinibuster

Over the United States holidays some posts were shared about an alleged leak of Google ranking-related data. The first posts about the leaks focused on “confirming” beliefs that were long-held by Rand Fishkin but not much attention was focused on the context of the information and what it really means.

Context Matters: Document AI Warehouse

The leaked document shares relation to a public Google Cloud platform called Document AI Warehouse which is used for analyzing, organizing, searching, and storing data. This public documentation is titled Document AI Warehouse overview. A post on Facebook shares that the “leaked” data is the “internal version” of the publicly visible Document AI Warehouse documentation. That’s the context of this data.

Screenshot: Document AI Warehouse

Screenshot

@DavidGQuaid tweeted:

“I think its clear its an external facing API for building a document warehouse as the name suggests”

That seems to throw cold water on the idea that the “leaked” data represents internal Google Search information.

As far we know at this time, the “leaked data” shares a similarity to what’s in the public Document AI Warehouse page.

Leak Of Internal Search Data?

The original post on SparkToro does not say that the data originates from Google Search. It says that the person who sent the data to Rand Fishkin is the one who made that claim.

One of the things I admire about Rand Fishkin is that he is meticulously precise in his writing, especially when it comes to caveats. Rand precisely notes that it’s the person who provided the data who makes the claim that the data originates from Google Search. There is no proof, only a claim.

He writes:

“I received an email from a person claiming to have access to a massive leak of API documentation from inside Google’s Search division.”

Fishkin himself does not affirm that the data was confirmed by ex-Googlers to have originated from Google Search. He writes that the person who emailed the data made that claim.

“The email further claimed that these leaked documents were confirmed as authentic by ex-Google employees, and that those ex-employees and others had shared additional, private information about Google’s search operations.”

Fishkin writes about a subsequent video meeting where the the leaker revealed that his contact with ex-Googlers was in the context of meeting them at a search industry event. Again, we’ll have to take the leakers word for it about the ex-Googlers and that what they said was after carefully reviewing the data and not an informal comment.

Fishkin writes that he contacted three ex-Googlers about it. What’s notable is that those ex-Googlers did not explicitly confirm that the data is internal to Google Search. They only confirmed that the data looks like it resembles internal Google information, not that it originated from Google Search.

Fishkin writes what the ex-Googlers told him:

  • “I didn’t have access to this code when I worked there. But this certainly looks legit.”
  • “It has all the hallmarks of an internal Google API.”
  • “It’s a Java-based API. And someone spent a lot of time adhering to Google’s own internal standards for documentation and naming.”
  • “I’d need more time to be sure, but this matches internal documentation I’m familiar with.”
  • “Nothing I saw in a brief review suggests this is anything but legit.”

Saying something originates from Google Search and saying that it originates from Google are two different things.

Keep An Open Mind

It’s important to keep an open mind about the data because there is a lot about it that is unconfirmed. For example, it is not known if this is an internal Search Team document. Because of that it is probably not a good idea to take anything from this data as actionable SEO advice.

Also, it’s not advisable to analyze the data to specifically confirm long-held beliefs. That’s how one becomes ensnared in Confirmation Bias.

A definition of Confirmation Bias:

“Confirmation bias is the tendency to search for, interpret, favor, and recall information in a way that confirms or supports one’s prior beliefs or values.”

Confirmation Bias will lead to a person deny things that are empirically true. For example, there is the decades-old idea that Google automatically keeps a new site from ranking, a theory called the Sandbox. People every day report that their new sites and new pages nearly immediately rank in the top ten of Google search.

But if you are a hardened believer in the Sandbox then actual observable experience like that will be waved away, no matter how many people observe the opposite experience.

Brenda Malone, Freelance Senior SEO Technical Strategist and Web Developer (LinkedIn profile), messaged me about claims about the Sandbox:

“I personally know, from actual experience, that the Sandbox theory is wrong. I just indexed in two days a personal blog with two posts. There is no way a little two post site should have been indexed according to the the Sandbox theory.”

The takeaway here is that if the documentation turns out to originate from Google Search, the incorrect way to analyze the data is to go hunting for confirmation of long-held beliefs.

What Is The Google Data Leak About?

There are five things to consider about the leaked data:

  1. The context of the leaked information is unknown. Is it Google Search related? Is it for other purposes?
  2. The purpose of the data. Was the information used for actual search results? Or was it used for data management or manipulation internally?
  3. Ex-Googlers did not confirm that the data is specific to Google Search. They only confirmed that it appears to come from Google.
  4. Keep an open mind. If you go hunting for vindication of long-held beliefs, guess what? You will find them, everywhere. This is called confirmation bias.
  5. Evidence suggests that data is related to an external-facing API for building a document warehouse.

What Others Say About “Leaked” Documents

Ryan Jones, someone who not only has deep SEO experience but has a formidable understanding of computer science shared some reasonable observations about the so-called data leak.

Ryan tweeted:

“We don’t know if this is for production or for testing. My guess is it’s mostly for testing potential changes.

We don’t know what’s used for web or for other verticals. Some things might only be used for a Google home or news etc.

We don’t know what’s an input to a ML algo and what’s used to train against. My guess is clicks aren’t a direct input but used to train a model how to predict clickability. (Outside of trending boosts)

I’m also guessing that some of these fields only apply to training data sets and not all sites.

Am I saying Google didn’t lie? Not at all. But let’s examine this leak objectionably and not with any preconceived bias.”

@DavidGQuaid tweeted:

“We also don’t know if this is for Google search or Google cloud document retrieval

APIs seem pick & choose – that’s not how I expect the algorithm to be run – what if an engineer wants to skip all those quality checks – this looks like I want to build a content warehouse app for my enterprise knowledge base”

Is The “Leaked” Data Related To Google Search?

At this point in time there is no hard evidence that this “leaked” data is actually from Google Search. There is an overwhelming amount of ambiguity about what the purpose of the data is. Notable is that there are hints that this data is just “an external facing API for building a document warehouse as the name suggests” and not related in any way to how websites are ranked in Google Search.

The conclusion that this data did not originate from Google Search is not definitive at this time but it’s the direction that the wind of evidence appears to be blowing.

Featured Image by Shutterstock/Jaaak

Google Search Leak: Conflicting Signals, Unanswered Questions via @sejournal, @MattGSouthern

An apparent leak of Google Search API documentation has sparked intense debate within the SEO community, with some claiming it proves Google’s dishonesty and others urging caution in interpreting the information.

As the industry grapples with the allegations, a balanced examination of Google’s statements and the perspectives of SEO experts is crucial to understanding the whole picture.

Leaked Documents Vs. Google’s Public Statements

Over the years, Google has consistently maintained that specific ranking signals, such as click data and user engagement metrics, aren’t used directly in its search algorithms.

In public statements and interviews, Google representatives have emphasized the importance of relevance, quality, and user experience while denying the use of specific metrics like click-through rates or bounce rates as ranking-related factors.

However, the leaked API documentation appears to contradict these statements.

It contains references to features like “goodClicks,” “badClicks,” “lastLongestClicks,” impressions, and unicorn clicks, tied to systems called Navboost and Glue, which Google VP Pandu Nayak confirmed in DOJ testimony are parts of Google’s ranking systems.

The documentation also alleges that Google calculates several metrics using Chrome browser data on individual pages and entire domains, suggesting the full clickstream of Chrome users is being leveraged to influence search rankings.

This contradicts past Google statements that Chrome data isn’t used for organic searches.

The Leak’s Origins & Authenticity

Erfan Azimi, CEO of digital marketing agency EA Eagle Digital, alleges he obtained the documents and shared them with Rand Fishkin and Mike King.

Azimi claims to have spoken with ex-Google Search employees who confirmed the authenticity of the information but declined to go on record due to the situation’s sensitivity.

While the leak’s origins remain somewhat ambiguous, several ex-Googlers who reviewed the documents have stated they appear legitimate.

Fishkin states:

“A critical next step in the process was verifying the authenticity of the API Content Warehouse documents. So, I reached out to some ex-Googler friends, shared the leaked docs, and asked for their thoughts.”

Three ex-Googlers responded, with one stating, “It has all the hallmarks of an internal Google API.”

However, without direct confirmation from Google, the authenticity of the leaked information is still debatable. Google has not yet publicly commented on the leak.

It’s important to note that, according to Fishkin’s article, none of the ex-Googlers confirmed that the leaked data was from Google Search. Only that it appears to have originated from within Google.

Industry Perspectives & Analysis

Many in the SEO community have long suspected that Google’s public statements don’t tell the whole story. The leaked API documentation has only fueled these suspicions.

Fishkin and King argue that if the information is accurate, it could have significant implications for SEO strategies and website search optimization.

Key takeaways from their analysis include:

  • Navboost and the use of clicks, CTR, long vs. Short clicks, and user data from Chrome appear to be among Google’s most powerful ranking signals.
  • Google employs safelists for sensitive topics like COVID-19, elections, and travel to control what sites appear.
  • Google uses Quality Rater feedback and ratings in its ranking systems, not just as a training set.
  • Click data influences how Google weights links for ranking purposes.
  • Classic ranking factors like PageRank and anchor text are losing influence compared to more user-centric signals.
  • Building a brand and generating search demand is more critical than ever for SEO success.

However, just because something is mentioned in API documentation doesn’t mean it’s being used to rank search results.

Other industry experts urge caution when interpreting the leaked documents.

They point out that Google may use the information for testing purposes or apply it only to specific search verticals rather than use it as active ranking signals.

There are also open questions about how much weight these signals carry compared to other ranking factors. The leak doesn’t provide the full context or algorithm details.

Unanswered Questions & Future Implications

As the SEO community continues to analyze the leaked documents, many questions still need to be answered.

Without official confirmation from Google, the authenticity and context of the information are still a matter of debate.

Key open questions include:

  • How much of this documented data is actively used to rank search results?
  • What is the relative weighting and importance of these signals compared to other ranking factors?
  • How have Google’s systems and use of this data evolved?
  • Will Google change its public messaging and be more transparent about using behavioral data?

As the debate surrounding the leak continues, it’s wise to approach the information with a balanced, objective mindset.

Unquestioningly accepting the leak as gospel truth or completely dismissing it are both shortsighted reactions. The reality likely lies somewhere in between.

Potential Implications For SEO Strategies and Website Optimization

It would be highly inadvisable to act on information shared from this supposed ‘leak’ without confirming whether it’s an actual Google search document.

Further, even if the content originates from search, the information is a year old and could have changed. Any insights derived from the leaked documentation should not be considered actionable now.

With that in mind, while the full implications remain unknown, here’s what we can glean from the leaked information.

1. Emphasis On User Engagement Metrics

If click data and user engagement metrics are direct ranking factors, as the leaked documents suggest, it could place greater emphasis on optimizing for these metrics.

This means crafting compelling titles and meta descriptions to increase click-through rates, ensuring fast page loads and intuitive navigation to reduce bounces, and strategically linking to keep users engaged on your site.

Driving traffic through other channels like social media and email can also help generate positive engagement signals.

However, it’s important to note that optimizing for user engagement shouldn’t come at the expense of creating reader-focused content. Gaming engagement metrics are unlikely to be a sustainable, long-term strategy.

Google has consistently emphasized the importance of quality and relevance in its public statements, and based on the leaked information, this will likely remain a key focus. Engagement optimization should support and enhance quality content, not replace it.

2. Potential Changes To Link-Building Strategies

The leaked documents contain information about how Google treats different types of links and their impact on search rankings.

This includes details about the use of anchor text, the classification of links into different quality tiers based on traffic to the linking page, and the potential for links to be ignored or demoted based on various spam factors.

If this information is accurate, it could influence how SEO professionals approach link building and the types of links they prioritize.

Links that drive real click-throughs may carry more weight than links on rarely visited pages.

The fundamentals of good link building still apply—create link-worthy content, build genuine relationships, and seek natural, editorially placed links that drive qualified referral traffic.

The leaked information doesn’t change this core approach but offers some additional nuance to be aware of.

3. Increased Focus On Brand Building and Driving Search Demand

The leaked documents suggest that Google uses brand-related signals and offline popularity as ranking factors. This could include metrics like brand mentions, searches for the brand name, and overall brand authority.

As a result, SEO strategies may emphasize building brand awareness and authority through both online and offline channels.

Tactics could include:

  • Securing brand mentions and links from authoritative media sources.
  • Investing in traditional PR, advertising, and sponsorships to increase brand awareness.
  • Encouraging branded searches through other marketing channels.
  • Optimizing for higher search volumes for your brand vs. unbranded keywords.
  • Building engaged social media communities around your brand.
  • Establishing thought leadership through original research, data, and industry contributions.

The idea is to make your brand synonymous with your niche and build an audience that seeks you out directly. The more people search for and engage with your brand, the stronger those brand signals may become in Google’s systems.

4. Adaptation To Vertical-Specific Ranking Factors

Some leaked information suggests that Google may use different ranking factors or algorithms for specific search verticals, such as news, local search, travel, or e-commerce.

If this is the case, SEO strategies may need to adapt to each vertical’s unique ranking signals and user intents.

For example, local search optimization may focus more heavily on factors like Google My Business listings, local reviews, and location-specific content.

Travel SEO could emphasize collecting reviews, optimizing images, and directly providing booking/pricing information on your site.

News SEO requires focusing on timely, newsworthy content and optimized article structure.

While the core principles of search optimization still apply, understanding your particular vertical’s nuances, based on the leaked information and real-world testing, can give you a competitive advantage.

The leaks suggest a vertical-specific approach to SEO could give you an advantage.

Conclusion

The Google API documentation leak has created a vigorous discussion about Google’s ranking systems.

As the SEO community continues to analyze and debate the leaked information, it’s important to remember a few key things:

  1. The information isn’t fully verified and lacks context. Drawing definitive conclusions at this stage is premature.
  2. Google’s ranking algorithms are complex and constantly evolving. Even if entirely accurate, this leak only represents a snapshot in time.
  3. The fundamentals of good SEO – creating high-quality, relevant, user-centric content and promoting it effectively – still apply regardless of the specific ranking factors at play.
  4. Real-world testing and results should always precede theorizing based on incomplete information.

What To Do Next

As an SEO professional, the best course of action is to stay informed about the leak.

Because details about the document remain unknown, it’s not a good idea to consider any takeaways actionable.

Most importantly, remember that chasing algorithms is a losing battle.

The only winning strategy in SEO is to make your website the best result for your message and audience. That’s Google’s endgame, and that’s where your focus should be, regardless of what any particular leaked document suggests.

Google To Shut Down Business Profile Chat Feature via @sejournal, @MattGSouthern

Google has announced that it will discontinue the chat feature in Google Business Profiles.

The wind-down process will start on July 15, and the functionality will complete on July 31.

The news was emailed to businesses, acknowledging the potential difficulty of the decision and emphasizing Google’s commitment to remaining a helpful partner in business management.

Google’s email to businesses reads:

“We are reaching out to share that we will be winding down Google’s chat feature in Google Business Profile on July 31, 2024. We acknowledge this may be difficult news – as we continually improve our tools, we occasionally have to make difficult decisions which may impact the businesses and partners we work with. It’s important to us that Google remains a helpful partner as you manage your business and we remain committed to this mission.

Google will stop creating new conversations after July 15, and chat functionality will fully end on July 31. Please note, customers will still be able to find and contact your business via Google Search and Maps – and learn more information about you from your website links, business description, photos, and anything else you share on your Business Profile.”

Impact On Businesses & Customers

Starting July 15, customers can no longer initiate new chat conversations with businesses through Google.

Customers currently engaged in chat conversations will receive notifications informing them of the upcoming phase-out of the chat feature.

However, customers will still be able to locate and contact businesses using Google Search and Maps and access information through website links, business descriptions, photos, and other elements shared on Business Profiles.

Google’s Decision To Discontinue Business Chat

Google says the decision to wind down the chat feature is part of ongoing efforts to streamline its offerings.

To assist businesses in the transition, Google has provided guidance on the next steps:

  1. Chat History Download: Businesses that wish to retain a record of their past Business Profile chats can download their chat history of customer conversations using Google Takeout.
  2. Alternative Chat Solutions: Google suggests that businesses invite customers to alternative chat solutions to continue conversations seamlessly.

Background & Context

Google Business Profile, formerly known as Google My Business, is a free tool for businesses to manage their online presence across Google, including Search and Maps. The chat feature enabled customers to communicate directly with companies through their Business Profiles.

While the chat functionality will no longer be available, Google remains committed to providing a platform for companies to manage their online presence and connect with customers.


Featured Image: Vladimka production/Shutterstock

New WordPress Plugin Solves Site Navigation Problem via @sejournal, @martinibuster

Joost de Valk, the creator of Yoast SEO plugin, has created a new (and free) plugin for solving a site architecture problem that can silently diminish a website’s ability to rank.

Site Architecture

Site architecture is an important SEO factor because a well-organized website with clear navigation helps users quickly get to the content and products they’re looking for. Along the way it also helps Google find the most important pages and rank them.

The normal and common sense way to organize a website is by topic categories. While some newbie-SEOs believe that organizing a site by topic is an SEO strategy, it’s really just plain old common sense. Organizing a site by topic categories organizes a site in a way that makes it easy to drill-down and find specific things.

Tags: Contextual Site Navigation

Another way to organize a website is through contextual navigation. Contextual navigation is a way to offer a site visitor links to more webpages that are relevant to the webpage and to their interests in the moment. The way to provide a contextual link is through the concept of Tags. Tags are strongly relevant links to content that site visitors may find interesting.

For example, if someone is on a webpage about a new song by a pop star they may in that moment may be interested in reading more articles about that singer. A publisher can create a tag which links to a page that collects every article about that specific pop singer. Ordinarily it doesn’t make sense to create an entire category for hundreds of musical artists because that would defeat the purpose of a hierarchical site navigation (which is to make it easy to find content).

Tags solve the problem of making it easy to navigate to more content that one site visitor is specifically interested in at that moment. It’s contextually relevant navigation.

Too Many Good Things Isn’t Always Good

Creating a long-range plan for organizing a website can be undone by time as a website grows and trends wane. An artist that was trending several years ago may have dropped out of favor (as they often do) and people lose interest. But those tags remain, linking to content that isn’t important anymore, defeating the purpose of internal site navigation, which is to link to the most important content.

Joost de Valk researched a (very small) sample of WordPress sites and discovered that about two thirds of the websites contained overlapping tags, multiple tags linking to the same content while also generating thin content pages, which are webpages with little value.

A blog post sharing his findings noted:

“Tags are not used correctly in WordPress. Approximately two-thirds of WordPress websites using tags are using (way) too many tags. This has significant consequences for a site’s chances in the search engines – especially if the site is large. WordPress websites use too many tags, often forget to display them on their site, and the tag pages do not contain any unique content.”

The sample size was small and a reasonable argument can be made that his findings aren’t representative of most WordPress sites. But the fact remains that websites can be burdened by overlapping and outdated tags.

Here are the three main tag navigation problems that Joost identified:

1. Too Many Tags
He found that some publishers add a tag to an article with the expectation that they will add more articles to that tags when those articles are written which in many cases doesn’t happen, resulting in tags that link to just a few articles, sometimes only to one article.

2. Some Themes Are Missing The Tag Functionality
The next issue happens when websites upgrade to a new theme (or a new version of a theme) that doesn’t have the tag functionality. This creates orphaned tag pages, pages that site visitors can’t reach because the links to those tag pages are missing. But because those pages still exist the search engines will find them through the autogenerated XML sitemaps.

3. Tag Pages Can Become Thin Content
The third issue is that many publishers don’t take the time to add meaningful content to tag pages, they’re just pages of links with article excerpts that are also reproduced on category pages.

Use Fewer Tags

This is where Joost de Valk’s new WordPress plugin comes in handy. What it does is to automatically remove tags that aren’t linking to enough pages, which helps to normalize internal linking. This new plugin is called, The Fewer Tags WordPress Plugin. There’s a free version and a paid Pro version.

The free version of the plugin works automatically to remove all tag pages that contain less than ten posts, which can be adjusted to remove pages with five posts or less.

Added functionality of the Pro version allows greater control over tag management so that a publisher can merge tag pages, automatically create redirects or send a 404 Page Not Found server response.

These are the list of benefits for the Pro version:

  • “Merge & delete unneeded tag pages quickly & easily.
  • Creates redirects for removed tag pages on the fly, in your SEO plugin of choice.
  • Includes an online course in which Joost explains what you should do!
  • Fix a site’s tag issues long-term!
  • Uninstall the plugin when you’re done!”

Where To Download Fewer Tags Plugin

The free version of the plugin can be downloaded here:

Fewer Tags Free By Joost de Valk

Read more about the Pro version here.

Featured Image by Shutterstock/Simple Line

Google Is Now Indexing EPUB Files via @sejournal, @martinibuster

Google announced that it is now indexing .epub documents, a format commonly used to print books for e-readers. Google is already showing EPUB books in the search index.

EPUB File Format

EPUB is an XML-based eBook publishing format based on a standard developed by the International Digital Publishing Forum, which in 2016 was subsequently merged with the World Wide Wide Web Consortium (W3C). The goal of the merger was to bring together electronic book publishing with the Internet so that they would mutually enrich each other.

Google Indexing EBUB Content

The intent of merging e-publishing with the Internet aligns with Google’s decision to index (and at some point presumably rank) EPUB content. The only surprise should be that it took eight years to do so. The changelog notes that EPUB file format was added to Google’s documentation of indexable file types and offers no other details.

Google’s official changelog offers a matter of fact notation:

“Adding epub to indexable file types

What: Added EPUB to the list of indexable file types.

Why: Google Search now supports epub.”

Does Google Rank EPUB Content?

I did a site:search for EPUB content, noted the title of a scientific research about eating contaminated fish in Lake Ontario (“Consumption of Contaminated Lake Fish and Reproduction”) that was hosted on the journals.lww.com domain.

I next searched for that document in the regular search using the exact match keyword phrase and a variation of the keyword phrase (“Consumption of Contaminated Fish in Lake Ontario”) and Google didn’t surface the EPUB document but it did surface the webpage that contained the download to the EPUB document.

Screenshot Of EPUB Download Page

Google’s official indexable file type documentation only notes that the listed filetypes are indexable. At this time it’s fair to say that Google isn’t ranking EPUB documents but Google will surface them with a filetype:epub search.

Read Google’s official documentation:

File types indexable by Google

Featured Image by Shutterstock/Simple Line

Google’s AI Overviews Shake Up Ecommerce Search Visibility via @sejournal, @MattGSouthern

An analysis of 25,000 ecommerce queries by Bartosz Góralewicz, founder of Onely, reveals the impact of Google’s AI overviews on search visibility for online retailers.

The study found that 16% of eCommerce queries now return an AI overview in search results, accounting for 13% of total search volume in this sector.

Notably, 80% of the sources listed in these AI overviews do not rank organically for the original query.

“Ranking #1-3 gives you only an 8% chance of being a source in AI overviews,” Góralewicz stated.

Shift Toward “Accelerated” Product Experiences

International SEO consultant Aleyda Solis analyzed the disconnect between traditional organic ranking and inclusion in AI overviews.

According to Solis, for product-related queries, Google is prioritizing an “accelerated” approach over summarizing currently ranking pages.

She commented Góralewicz’ findings, stating:

“… rather than providing high level summaries of what’s already ranked organically below, what Google does with e-commerce is “accelerate” the experience by already showcasing what the user would get next.”

Solis explains that for queries where Google previously ranked category pages, reviews, and buying guides, it’s now bypassing this level of results with AI overviews.

Assessing AI Overview Traffic Impact

To help retailers evaluate their exposure, Solis has shared a spreadsheet that analyzes the potential traffic impact of AI overviews.

As Góralewicz notes, this could be an initial rollout, speculating that “Google will expand AI overviews for high-cost queries when enabling ads” based on data showing they are currently excluded for high cost-per-click keywords.

An in-depth report across ecommerce and publishing is expected soon from Góralewicz and Onely, with additional insights into this search trend.

Why SEJ Cares

AI overviews represent a shift in how search visibility is achieved for ecommerce websites.

With most overviews currently pulling product data from non-ranking sources, the traditional connection between organic rankings and search traffic is being disrupted.

Retailers may need to adapt their SEO strategies for this new search environment.

How This Can Benefit You

While unsettling for established brands, AI overviews create new opportunities for retailers to gain visibility without competing for the most commercially valuable keywords.

Ecommerce sites can potentially circumvent traditional ranking barriers by optimizing product data and detail pages for Google’s “accelerated” product displays.

The detailed assessment framework provided by Solis enables merchants to audit their exposure and prioritize optimization needs accordingly.


FAQ

What are the key findings from the analysis of AI overviews & ecommerce queries?

Góralewicz’s analysis of 25,000 ecommerce queries found:

  • 16% of ecommerce queries now return an AI overview in the search results.
  • 80% of the sources listed in these AI overviews do not rank organically for the original query.
  • Ranking positions #1-3 only provides an 8% chance of being a source in AI overviews.

These insights reveal significant shifts in how ecommerce sites need to approach search visibility.

Why are AI overviews pulling product data from non-ranking sources, and what does this mean for retailers?

Google’s AI overviews prioritize “accelerated” experiences over summarizing currently ranked pages for product-related queries.

This shift focuses on showcasing directly what users seek instead of traditional organic results.

For retailers, this means:

  • A need to optimize product pages beyond traditional SEO practices, catering to the data requirements of AI overviews.
  • Opportunities to gain visibility without necessarily holding top organic rankings.
  • Potential to bypass traditional ranking barriers by focusing on enhanced product data integration.

Retailers must adapt quickly to remain competitive in this evolving search environment.

What practical steps can retailers take to evaluate and improve their search visibility in light of AI overview disruptions?

Retailers can take several practical steps to evaluate and improve their search visibility:

  • Utilize the spreadsheet provided by Aleyda Solis to assess the potential traffic impact of AI overviews.
  • Optimize product and detail pages to align with the data and presentation style preferred by AI overviews.
  • Continuously monitor changes and updates to AI overviews, adapting strategies based on new data and trends.

These steps can help retailers navigate the impact of AI overviews and maintain or improve their search visibility.


Featured Image: Marco Lazzarini/Shutterstock