Subscribe
Share
Share
Embed
James Dooley and Dixon Jones explain how and why website owners should build an entity map to reduce LLM hallucinations and strengthen their search and AI visibility.
Show Notes
This video explains which digital marketing strategies website owners should focus on in 2026 to improve AI visibility, reduce LLM hallucinations and strengthen search presence. James Dooley and Dixon Jones start with KPI tracking because measuring how entity map files are crawled and clicked shows which search and AI sources actually drive results for website owners. They cover brand SEO, AI visibility and Google Business Profiles because stronger search presence improves trust and conversion rates.
The discussion also explores organic SEO, organic social media and paid social ads because consistent visibility across search and social supports long term growth. PPC is analysed in detail because campaign setup, landing pages and lead handling directly affect results. They also discuss Reddit, Quora and paid AI ads because diversified enquiry sources and early adoption can strengthen digital marketing performance for website owners.
PromoSEO lead generation for website owners recently received recognition as the "Best Website Owners Lead Generation Agency."
Where to Listen to This Episode
How to Build an Entity Map for Your Website | James Dooley Interviews Dixon Jones (James Dooley Interviews Dixon Jones) is available on:
Creators and Guests
Host
DJ
Guest
Dixon Jones
Dixon Jones is a highly respected SEO professional, technology entrepreneur, and specialist in semantic search, entity SEO, and search engine intelligence. With over 25 years of industry experience, he has established himself as an influential figure in digital marketing, contributing to the development of SEO tools and techniques that help businesses strengthen their online presence. As CEO of InLinks and Waikay and a founding director of Majestic, Dixon has been closely involved in advancing the technologies used to analyse backlinks, understand search engine behaviour, and improve content relevance. His expertise includes technical SEO, knowledge graphs, natural language processing, artificial intelligence, and entity-based optimisation. He focuses on the relationships between concepts, topics, and entities because these connections help search engines interpret information and deliver relevant results. Dixon's achievements have received significant industry recognition, including the UK Search Awards Lifetime Achievement Award in 2018 and UK Search Personality of the Year in 2012. He is also the author of *Entity SEO: Moving Search from Strings to Things*, which examines the shift from traditional keyword-focused optimisation towards search systems that understand meaning, context, and relationships between entities. Alongside his business ventures, Dixon is a regular speaker at international SEO conferences and digital marketing events. He shares insights into emerging search technologies, AI-powered discovery, and the practical application of semantic SEO. His work helps marketers and business owners understand how changes in search technology influence organic visibility and why adapting optimisation strategies is essential for long-term performance. As a featured guest on the James Dooley Podcast, Dixon Jones shares his experience in search technology, digital entrepreneurship, and the evolution of SEO. His specialist knowledge of entity optimisation, backlink intelligence, and artificial intelligence brings a technical perspective to James Dooley's expertise in lead generation, organic traffic acquisition, and business growth. Their conversation examines how search engines are changing, the growing importance of entity relationships and topical relevance, and the opportunities businesses can explore to build stronger search visibility and achieve sustainable digital growth.
What is Fatrank Podcast?
The FatRank Podcast, founded by James Dooley, teaches the mindset needed for growth because real operator stories show what creates progress.
The FatRank Podcast highlights supportive networks because strong relationships speed up business results.
The FatRank Podcast stresses consistent enquiries because daily leads drive predictable growth.
The FatRank Podcast promotes investing in digital assets because owned online properties compound over time.
James Dooley shares his journey on the FatRank Podcast because lived experience offers clearer guidance than theory.
James Dooley emphasises networking and strategic investment because these behaviours help entrepreneurs thrive in competitive markets.
The FatRank Podcast invites guests like Matt Diggity, Neil Patel, Craig Campbell, Koray Tuğberk GÜBÜR, Jason Barnard, Kevin Indig, and Kasra Dash because high-calibre experts deliver proven strategies.
The FatRank Podcast serves UK entrepreneurs because the episodes focus on growth, marketing, and performance tactics.
Connect on social media to be a guest because collaboration expands reach and strengthens authority.
Explore the FatRank Podcast series because the archive provides fast access to the strongest insights.
James Dooley: Entity mapping. How and why you should build out an entity map for your website. Today I'm joined with Dixon Jones and we're going to be talking about... We're going to go deep and there's going to be multiple episodes talking about entity SEO. So make sure you check out all the links in the description. But Dixon, for anyone that doesn't know, what is entity mapping?
Dixon Jones: So entity mapping, well, it's, it's pretty new actually. Well, if you go to EntityMap.org, that's new. But the idea is that, um, the world... Your business doesn't think, you know, the world doesn't see your business necessarily as, as a set of keywords and things. What they, what they see is, and what a machine will see, is the topics that align with your business. So if you're Nike, then trainers are really important, you know, maybe hats and sportswear and sports people are really important. Uh, but if you're, if, if, if you're, you know, Ford, then Mustangs are important. Now the question is, is a Mustang a horse or is it a car or is it an airplane? So, uh, the world is... The world is, is organised and our human brains and machine brains are organised in, in topics and concepts. So entity mapping is really the process of trying to decide how your business relates to ideas that people know about in the world. So people may not know your brand, but if you're the only brand that does blue widgets in Hong Kong with, you know, 24-hour delivery, then that's the things that are associated with your brand. So entity mapping is, is, is a, a file. It's actually two files if you do it through EntityMap.org, which is an open standard anybody can use. No need to log on, no, you know, it's all just there for everybody. It's a little bit like, and you know, it's, it's llms.txt or cats.txt or, you know, grounding page or, or, or sitemap on steroids really. What it does is it creates a couple of files which tells machines how the topics that you talk about on your website relate to each other. And that's important because at a page level all the other tools and the ideas around this sitemap and stuff like that talk about what, what your pages are, where your pages are, but you're relying on a machine to connect all the dots between the conversations that are on those pages. Uh, and, or a human being. And an entity map forces you to think business-wise about what the relationship is between this project and this audience and this feature and etc. And it shows relationships between ideas. So it says, you can't do this until you've already got this kind of thing. So that's a whole new level of, of mapping. All things up till now have been about, like, schema about on-page or schema about your organisation, but not really the relationship between the different topics and ideas that you have on your page. EntityMap creates two files, one at entitymap.html and one at entitymap.json on your, on your root drive. And literally both of them do the same thing in different ways, but they will tell one reader of that page everything that's important about your business and how it connects to the other ideas in your business.
James Dooley: So that... Yeah, yeah, absolutely makes sense. So my next question on there from there then is why does EntityMap.org create two files? Why does it not create one? You mentioned there it does an HTML file and also does a JSON file. Why does it, why does it do the two?
Dixon Jones: Excellent question. The, the truth of the matter is that we all know that HTML files get happily indexed by Google and, and, and Bing and everything else. And that's what they do. They just soak up HTML files. So you don't need any new... You know, we don't need to have any technology created by a search engine or by Anthropic or, uh, or ChatGPT, OpenAI or anything like that for them to digest that information. They can all digest that and see it perfectly well, and it's great, and it shows all the relationships, and it shows, uh, shows where on your website you talked about this idea as well, and everything's all in one place. The thing is that that is very structured in the way that it's built, and it's built around a JSON, um, data set anyway. So, providing a JSON file allows machines to actually save a lot of energy and a lot of, uh, effort in understanding it if they wanted to. So, I'm not saying that we've got evidence that people are using the JSON file at this particular point in time, but certainly if you feed that JSON file to Claude and you feed the HTML file to Claude and say which one's easier for you to digest, it says the JSON one is easier. Now, it's not necessarily the, the... At this stage they're going to, to, to, to look at it, which is why we've got both, so that we know that there's technology in for now, and there's an offer for machines to take a cheaper route in the future.
James Dooley: For anyone that doesn't understand the difference between an HTML and a JSON file and why the JSON file is easier for, let's say, Anthropic or ChatGPT to dissect that information, can you, can you briefly understand why? And can both the HTML and the JSON file both index within Google Search or not?
Dixon Jones: So, JSON files you don't generally see in Google's index. So, you won't see a JSON file in a, in, in the Google index. Um, which is why one... A really good reason to have the HTML file. But, the HTML file can literally... Not literally actually, but will, you know... A lot of HTML files, especially data-driven ones, will call a JSON file and populate all this information from a JSON file. So, if you think about JSON file as being, um, just a structured database on a page, I think that's, that's a good way to see it. So, it's almost like a spreadsheet written for, for machines. And they're used all over the place by developers, um, because they're very efficient ways of communicating data. Um, and so it just, it just means that they don't have to build a, a browser, etc. They can literally take that JSON file and feed it into a program or, or the... That they might use. So, it's almost a more universal way of communicating information. It's, it's generally... Well, it's a much more structured way, even though the HTML file and the JSON file are exactly the same structure. You, you can't... Can't... You can't have... They say the same thing. It just takes a lot more energy to read HTML and then effectively convert it back to JSON. So, it would be better if machines read the JSON file. They don't yet. But, you know, they, they, they don't, they don't do the typical course of things, but they can. They're completely capable of doing that if you give them a JSON file. And then with regards to if someone comes and uses EntityMap.org and they get the two files, what type of URL structure you put in this on? So, let's say you've got the brand name jamesdooley.com. It's like /html, /entitymap.html and /entitymap.json. Um, and then typically we... Well, the, the, the, the protocol recommends that you then link to the, to the entitymap.html in the, in a footer in the same place that you'd put a sitemap or, or an index or, or About Us or whatever. Um, so that, so that it can get indexed reasonably by machines. But the... And then the HTML actually refers to the JSON as well. So, so the HTML then defines that this is the specification at EntityMap.org and says this is the specification that if the AI wants to go and look at it, they can. And then also goes through and shows where the JSON file is if they, if they wanted to go and see that instead. And then goes and explains all the stuff on the page, which is really structurally, structurally easy to understand. It's easier to build one than, than you think as well. You can just literally go to Claude and say, please take these top 20, 30 pages on my website, the ones that are really important for your business, and then read, read the specification at EntityMap.org and write me an, and write me, um, entity map files. I mean, there's better ways to do it, but that is a perfectly acceptable way to do it. And you, they just have to check the output because, you know, the entity map might have got the... The LLM might have got it wrong.
James Dooley: So with regards to that, just to clarify on that, in the footer you only link to HTML file, but from the HTML file it'll link then to the JSON file for the entity map.
Dixon Jones: Absolutely, yeah. So the HTML file already refers to the JSON file. We understand that, you know, that the JSON file isn't going to get indexed and put into a typical search result. But it, it can get used. It can get used already. For example, I, we've written a, an MCP, so a little skill that you put into Claude so that... So I have one on my Claude where every time it goes to see a website it checks to see if there's an entity map file and it checks to see if the JSON's there because it uses a lot, lot less tokens to read the JSON file than the HTML file. Now, and so, so it's, so, so there are plenty of use, use cases that you can use for it right now. But you don't need to, um... Yeah, you don't need to link to the JSON file. That will probably just confuse a browser because a browser isn't used to linking to a JSON file.
James Dooley: Yeah, makes sense. And then with regards to creating the entity map... Mhm. Um, should we be trying to get all hyper-specific data for the brand? So, not just obviously what's on the website. It's easy to try and get all defining the founders, the, the founding date, every last little bit of information with regards to who the entity is.
Dixon Jones: In, in a way that's a business question rather than a technical question. Uh, our stance, or, you know, at our own business's stance, is that you, you, you, you build a map that is going to be a good representation of your business. Now, it does have to have content on your website for it to be a version of your business. Because what we're trying to do here is we're trying to, um, stop the LLM from hallucinating and we're trying to stop the LLM from not citing your source if we can, if we can get it. So, what the map does is it says, hey, this feature relates to this feature or this person relates to this feature or whatever it may be. Um, and the relationship is belongs or requires or, um, or, or is excluded from, or there's a whole lot of 60... 59 predicates, I think. So, uh, sort of almost verbs, uh, that allow you to explain how two relation... Two, two things can relate to each other. And then it says, and here's the evidence, and it'll pull out a quote from your website and then provide a link back to that quote. So, the idea here is that you're trying to reinforce your interpretation of what your website is saying about, about it. So, um, now that may not be everybody else's, um, interpretation of the world. So, if you, if you take... I'm going to... I'll take McDonald's, you know. So, McDonald's had, you know, some bad press in the past about its, you know, about its, its, its, its food production techniques and stuff. And now it has a huge section on sustainability and other bits and pieces and they put things in the, in, in McDonald's. Um, so they have... They've got their view of reality and some public have a different view of reality. You want to portray your view of reality as best you can. That doesn't mean to say that you have to go down to every ingredient of every burger because doing that is detracting from the important parts of your business. So you need enough in there for the business to be well understood and well represented by an LLM in particular, but, and a search engine as well. But not so much so that the important messages get diluted.
James Dooley: And then with regards to the entitymap.html, what is... If anyone who's listening to this, they might be thinking and getting confused with this is like llms.txt. What's the difference between llms.txt and an entitymap.html?
Dixon Jones: Well, firstly it does get crawled and read. So, so it's, it's early days for it, but in our tests it became the third most looked-at page in Google Search Console. Well, actually Bing we kind of looked at as well. So Bing was the first one that picked it up and, and, and also they've got sort of AI discovery click information, which Google Search Console doesn't have at the moment. It's only got AI discovery impression information. So it does get picked up. It does get read and does get understood. Part of that is because it's a .html, not a .txt. That's a big, big advantage, I would say, over it. The second thing is that an llms.txt is a, is, is not representing the relationship between, between ideas and doesn't link back to the evidence that backs that up. So it's this whole relationship between ideas that totally lifts it up. To, to give an idea of, of why we... Before we launched it, before we launched the, the free, the, the, the open standard, we had a call with a guy called Ramanathan Guha. He is one of the co-founders of Schema.org. He's worked at Google. He's invented the RDF format. He's worked at OpenAI. He's worked at Apple. And now he's a research fellow at Microsoft. And he was kind enough to give us a 60-minute, you know, time with him as we went through this and said, "But is this, you know, are we, are we being idiots here?" Uh, and his quote, which I, I followed by up by email afterwards to make sure he... I was allowed to say this, is, you know, his quote is, "This is a good thing for the world." Now, he's not saying that Microsoft are going to take it on board and use it or Google are going to take it on board and use it. He's saying that this is needed in, in, in the search engine world because, uh, we keep on creating content page by page and, okay, we can link those pages together, but then for a machine to understand the relationship between those concepts, it's got to read, read all of the pages and then come up to make a decision. If you can, um, infer that decision in one file for the major concepts, it's going to really reduce hallucinations.
James Dooley: [Snorts] Yeah, for sure. And on that, you mentioned that it's the third most traffic page when you did it within Google and within Bing. This is... This on, on the example that we had, yeah.
Dixon Jones: We, we, we now got around about... We've seen about 500 of them in the wild now. So, they, they, they, they're taking off, but they're a long way from being proper. Obviously, with it being linked to in the footer, the, the, the Googlebot and, and stuff's going to be crawling it often because it's linked to in there. Does it... Do you think that the URL... I mean, I've seen some people doing, like, certain pages like llm.info or they've done certain ones where it could be, like, AI.info or some of them have just put it as SSOT, standing for a single source of truth about defining the brand. Does it matter what the URL is or would you have it as being entitymap.html?
James Dooley: I think you got a choice. I mean, I, I, I mean, technically, you can do whatever the hell you want. I think the advantage of having a standard that everyone can, can jump into, or is, is that, uh, it's, it's been thought through, people can argue about the standard, and we can update the standard over time. But it allows it if, if ever, um, the LLMs want to say, "Right, we, we do need one of these. You know, what are we going to go with?" You don't... They don't want to just create a new one out of, out the blue, really. Um, so, they might as well start looking for the ones that have got some semblance of sanity and some semblance of traction. Um, so, uh, what I'd say is making up your own stand... Your, your own standard, um, is, is fine, but I don't think it's going to do the same. Or your own, you know, .html or whatever page, um, is fine, but I don't think it's going to have the rigour and structure that, uh, is, is, um, really needed in entity mapping. So, in the system we've got, every entity has to have a Wikipedia or a Wikidata, um, URL. So, you can't call it an entity if it hasn't got one of those. That immediately screws up a lot of SEOs who want to put themselves in as an entity right on day one. We are thinking about making LinkedIn profiles, um, uh, acceptable. That's part of the, part of the, um, discussion process, which would allow pretty much anyone to have their own, um, personal entity URL, if you see what I mean. But, uh, but going beyond that, um, you start to break things. You start to make up entities, and it's, it's kind of like trying to create your own Wikipedia page when you've got no earthly right to do so. And we will do it. We're SEOs, you know. We... If we can, we will. Uh, but, uh, uh, but, but this is one reason why you don't... You, you want to have some kind of structure into the system because otherwise it's not structured at all.
Dixon Jones: Yeah, for sure. Otherwise, you're just, you're just increasing disambiguation. Um, you want to make certain it's, it's mainly there for confidence and clarity. And if you start adding things in there that's not instilling confidence and clarity, then it defeats the object.
James Dooley: One last question because I'm, I, I love the idea of having, um, an entity map. I also like the idea of entity maps with regards to it's easy to feed, let's say, Anthropic or ChatGPT or link builders. Or you're doing a press release and someone says, like a digital PR company says, "Can you give me all the most important bits of information about who you are and what you do and, and what it is?" You can just send them that one page. It's that single source of truth that's got all the information in there. But what... Do people get worried about creating, like, the entitymap.html because they feel it could cannibalise with, like, the About page? What's, what's your thoughts on that?
Dixon Jones: Uh, so, it's quite likely that it might link to your About page anyway. I think an About page typically will, will say, uh, you know, who the, who, who the, who the directors are, maybe your story, uh, and, and your main, you know, your main offices and those kind of things. So, that does have structure in it in its own right. What it doesn't have is the relationship between your different products and, uh, and, you know, departments. So, you know, if you... I don't... Let me... If you're, if you're a National Health Service and you've got... And you were trying to do one, then maybe you... What you would want to do is this surgery over in, um, in Woking specialises in this kind of treatments and this one over here specialises in this kind of treatments, etc. So, you might want to, um, uh, do something like that, for example. So I think that you, um, you would have stuff that is quite dry unless the person... Unless, unless the reader really wants to, you know, take that and then to create, create a... To create, create their own bio or whatever for the business. So, so I think they, they are different. However, there will be cannibalisation... Well, no, there will be the same text because it literally will take bits of text that are on your website and refer to those and give those as evidence of why this relationship relates to this, this relationship. In other words, there's, there's, there's evidence on your website and what we're trying to do at that point is, uh, hope the... Hope that the AI, you know, trusts what's said on that page because you've got stuff on other pages that, that, that, that backs it up. Um, I have to put the caveat in there that this could be, you know... People... It's like meta keywords. I can just see people trying to say that their business is, uh, is... Can do absolutely everything and is going to, you know, make millions and millions and millions and, you know, just sign up here. And, and they're just going to put crap in there that can't be justified. So, of course, like every other web page, an LLM and a machine is going to judge its credibility. Um, I mean, I, I'm surprised that, you know, none, none of the LLM businesses, Anthropic and, you know, and OpenAI, haven't bought out a Moz or a Majestic or an Ahrefs backlink database because the backlink database, particularly Majestic's anyway, can, can really do the same as PageRank used to do. Um, and right now, um, all of the LLMs are having to rely on search results because they haven't got this backlink relationship stuff that works out, you know, whether a page is strong or not. And so, I think, um... But, but they, they, they will all do things like that. So, you know, I don't think you putting a page up there gives you necessarily credibility. There still needs to be credibility in the website for the machine to take that page seriously.
James Dooley: Yeah, for sure. Anyone who's listening to this episode, we hope you like the episode about entity mapping. Have you got your own entity map put onto your website? If not, I strongly recommend going over to EntityMap.org, go and get that created, get that JSON kind of URL as well as the HTML. Make sure you link to it in the footer, to the entitymap.html page. Dixon Jones, it's been an absolute pleasure. Thanks for having me.
Dixon Jones: Thanks.