Entities Are Not a Strategy

Every few months, SEO finds a new word and starts acting as if the whole job has changed.

At the moment, it’s entities.

Search has moved beyond keywords. Google needs to understand the people, places, businesses, products and ideas behind the words. We need to build entity authority, connect the graph, stack Google properties and make sure the machine knows exactly who we are.

Some of that is sensible. Some of it is old advice in a new coat. And some of it is a service page looking for a technical-sounding reason to exist.

I don’t want to write another article explaining what an entity if you want to. If you work in or around SEO, you have probably read several already. And if you haven’t, Google will find you one. This is my opinion about the gap between a useful idea and the performance built around it—and where I think the effort should actually go.

The useful idea

Search engines need to work out what a page is about and how it relates to the rest of the world, Sounds obvious but as we all know when something seems obvious its often ignored.

If a page mentions Apple, does it mean the fruit or the technology company? Is a business the same one that appears in a map listing, a trade directory and a news article? Is a person an author, a founder, an expert, or just a name in the footer?

Clear, consistent information helps. So does a website that explains what a business does, who it serves, where it operates and how its services fit together. Structured data can help describe information on a page in a format search engines can process. Good internal linking can make the relationships between pages clearer to people and crawlers alike.

None of this is magic. It’s the ordinary work of making a business and its website easier to understand. The sort of work that doesn’t always get a shiny new name or a conference talk, but still needs doing.

That is the bit I like about thinking in entities. It can make us ask better questions. Are we clear about the organisation behind this site? Do we describe the same service consistently? Does the page explain the connection between the product, the problem and the people it helps?

Those are worthwhile questions whether or not we use the word entity.

Then the idea gets a head of steam

The trouble starts when a useful way of describing search becomes a promise about rankings.

Now we have entity audits, entity authority, entity profiles and entity stacks. The pitch often goes something like this: create a set of properties on Google-owned platforms, connect them together, point them at the website and strengthen the business’s entity signals.

It sounds tidy enough. Google owns the properties. The properties are trusted. The links point to you. The signals reinforce one another. Lovely. Stick it in a diagram, give it a name and put it on the proposal.

But what, exactly, has been proved?

Google’s own spam policies define link spam as creating links primarily to manipulate search rankings. They don’t give a special exemption to a link because it lives on a Google product. If the purpose of a web of documents and profiles is to manufacture ranking signals, calling it an entity stack doesn’t change what the tactic is trying to do. (Google’s spam policies)

That doesn’t prove every Google stack has no effect. Search is too complicated for that kind of certainty, and an observed ranking change rarely tells you exactly which bit caused it. It does mean we should be careful about turning a plausible story into a reliable SEO method.

“Google can understand entities” and “this stack improves rankings” are two different claims.

The first is a useful way to understand search. The second needs evidence and im pretty sure if i opened up the comment abillity on this post i will get anecdotal comments from people that swear by the this idea.

A Google property isn’t a shortcut to trust

The name Google entity stacking does a lot of the heavy lifting.

It makes a collection of Google Sites, Drive files, profiles or other properties sound like a coherent technical system. It hints that because Google owns the platforms, Google must value the links between them.

That’s a leap. A fairly big one, actually.

A page hosted by Google is not automatically an endorsement by Google. A document does not become authoritative because it sits in Drive. A link does not become a meaningful vote because the destination happens to be a Google property. And publishing the same business details in a dozen places does not necessarily make those details more true or more useful.

There can be legitimate reasons to use those services. A business might publish a useful document, host a video or keep a public profile. If people need the material, publish it where it serves them.

But if the main reason for creating it is to pass ranking signals around a loop, I want to know why that should work—and what happens when Google decides those links are just links made to manipulate rankings.

The fact that a tactic is easy to sell doesn’t make it a sound investment. It just means somebody has got good at selling it.

Facts, guesses and sales copy

This is where entity SEO gets muddy. Three very different things get lumped together and presented with the same confidence.

What we can observe: Google Search can connect information and return results about people, organisations, places, products and other things. Search results sometimes display panels or other features built from information Google has gathered.

What is a reasonable practice: make the business’s identity and services clear across its site; use accurate structured data where it fits; keep important public information consistent; earn relevant coverage and references; explain relationships that matter to customers.

What still needs proving: that a prescribed set of interlinked Google properties creates a dependable ranking advantage, or that a particular “entity authority” score measures something Google uses.

The first two don’t automatically validate the third.

I keep seeing this pattern in SEO. There’s a real observation, then a plausible explanation, then a product built as if the explanation were settled fact. By the time it reaches a conference slide, all the uncertainty has buggered off. We’re no longer talking about an experiment. We’re talking about a must-have strategy.

And that’s how a good idea becomes the only thing anyone wants to talk about.

Where I would put the effort

If a business is hard to understand online, I wouldn’t start by building a stack. I’d start by looking at the bloody business.

I would start with the business itself.

Can a customer tell what it does? Are its services explained in plain language? Do the important pages show evidence, useful detail and a clear connection to the problems people are trying to solve? Do the site’s navigation and internal links help people move between related subjects? Is the business represented accurately on the platforms that matter to its customers?

Then I would look at the search results and the competition. Which pages are visible for the searches that matter? What do those pages explain that ours doesn’t? Are credible, relevant websites talking about the business? Are there technical problems stopping useful pages from being found or understood?

That work may include structured data. It may include fixing inconsistent business information. It may include earning legitimate mentions and links. It may even include a Google-hosted resource if that resource has a job beyond existing as another node in a diagram.

But each thing needs a reason that survives outside the framework used to sell it. If the only answer is “it strengthens your entity signals”, I’m going to keep asking questions.

I would rather have one genuinely useful reference from a relevant organisation than a folder full of empty assets. I would rather make the service page clearer than add another layer of SEO theatre around it. And I would rather spend time building evidence that the business is real, capable and relevant than manufacturing a pattern that merely looks like one.

This sounds like im saying straighten up and fly right and maybe i am to an extent but as we know from my last post a few weeks ago on Old-School SEO Never Really Went Away playing by the rules is a broad spectrum. I know this can be frustrating your working really hard daily to get to the top and it feels like your not winning so its easy to look at some strategies and think thats the answer and maybe it it is but most of the time its a distraction from the real work the hard work that we have to do shortcuts may exist but nothing beats getting it right.

Entities are a lens, not the destination

I don’t think entities are nonsense. Search needs to understand things and their relationships. Helping it do that is part of making a good website and representing a business accurately.

I do think the industry has a habit of taking a real concept, wrapping it in confident language and selling the wrapper as the strategy. We did it with all sorts of things before this. We will do it again next month with something else.

The useful question is not “Have we built an entity stack?”

It is “Can a person—and, as far as we can reasonably tell, a search engine—understand what this business is, what it offers, and why it is relevant?”

If the answer is no, fix that.

If the answer is yes, don’t keep adding properties just because somebody has drawn more boxes and arrows. The diagram isn’t the work. And a stack isn’t a strategy just because it has a name.

Entities matter. The hype around them still has to prove itself.