semantic entity analyzer featured
AI

How Gemini Built Me an AI Model: The Semantic Entity Analyzer (NPL)

Gemini 3.1 built me an AI powered SEO Semantic Entity Analyzer. This isn’t clickbait and isn’t just a story about “using AI.” It’s a story about the 2 nights I spent arguing with a chatbot, the panic of breaking my site installation, and the breakthrough moment when I realized that software development has fundamentally changed.

Some days ago, I was staring at a “Topical Authority” report from a traffic checking third party site, it looked great, but it didn’t tell me how it reached its conclusions. It felt like a black box. I wanted to see the raw data: the entities, the salience, the connections, that Google’s own NLP (Natural Language Processing) sees.

🚀 See the result before the story

No credit cards, no sign ups. Use the SEO Semantic Entity Analyzer here →

The Anatomy of the The Semantic Entity Analyzer 3

The Anatomy of the The Semantic Entity Analyzer

When I first sat down with Gemini, I didn’t want a “toy.” I wanted a tool that could hold its own against the giants. We weren’t just building a word counter; we were building an AI powered Semantic Intelligence Engine, and to my suprise, he seemed eager to start, even adding upon my ideias to make the tool more advanced.

You can read the full jorney if you want, but before continuing here is the breakdown of the AI model “we” created and its capabilities:

1. The Multi-Layered Extraction Engine

Most basic scrapers just grab text and look for capitalized words. That’s useless for SEO. The online tool needed to understand Category Labels. I spent hours refining the logic so it could distinguish between:

  • ORG (Organization): Identifying brands like “Google” or “Nike” as corporate entities.
  • PERSON: Spotting authors and influencers who contribute to E-E-A-T.
  • GPE (Geopolitical Entity): Identifying locations that establish local relevance.
  • PRODUCT & CONCEPT: This was the hardest. Distinguishing a specific service from a general idea is where most NLP models trip up. We had to build a specific mapping system to ensure the data stayed clean.

2. The Salience Algorithm (Where the AI Model Shines)

This is where the AI gets “smart.” If you mention “Marketing” 50 times in an article about “Apples,” a dumb tool would say your article is about marketing. This SEO visualizer calculates Salience. It looks at where the word appears (headers vs. body), its relationship to other entities, and its structural frequency.

Why it was needed: I needed to know if my “Anchor Entity” was actually being recognized by the AI as the primary topic. If your salience score for your main keyword is under 50%, you’re going to have a hard time ranking.

3. Authority Mapping & Visualization

Data is boring if you can’t see it. We integrated Chart.js to create a live-updating bar chart. As soon as the scan finishes, the AI builds a “Semantic Map.” It shows you the top 10 entities in order of impact.

The Capability: This allows an SEO to instantly spot “Outliers.” If you’re writing about “Vegan Recipes” but “Meat” shows up as a top-3 entity because you spend too much time talking about what you’re not eating, the map will catch it.

why entities rule in seo

The End of Keyword Stuffing: Why Entities Rule SEO in 2026

For the last decade, we’ve been trained to think in “strings.” You want to rank for “organic dog food,” so you put that exact string of letters in your H1, your H2, and your meta tag description. But search engines haven’t worked that way for a long time.

Google is now an “Entity-First” engine. It doesn’t just see the word “Apple” and count it. It looks at the surrounding text to decide if you are talking about the fruit (The Apple entity) or the company (The Apple Inc. entity). This is what SEOs call the knowledge graph.

If you want to rank for high-competition topics in 2026, you can’t just spam keywords. You have to satisfy the “Entity Requirement.” You have to mention the brands, people, and locations that define that topic’s “neighborhood.”

And why I’m telling you this? I needed a free service to tell me if I was hitting those marks. Since I couldn’t find a free one that didn’t look like a computer science project from 1995, I decided to build it (with help).

ai is progressing at fast pace

The “Initial Spark”: Can AI Code Better Than I Can Explain?

I started by throwing a massive, vague prompt at Gemini. I said, “Build me a tool that extracts SEO entities from a URL.”

The AI’s first mistake? It tried to give me a Python script.

“I can’t use Python on a standard WordPress host,” I typed back, feeling that familiar spark of frustration. “I need this to be on my web tools page.”

This was the first lesson in building with AI: You have to be the Project Manager. If you are vague, it will give you the easiest path for it, not the best path for you.

We eventually moved forwared and I hosted the Python script on a separate server and gemini spent the next two hours architecting the NPL backend and sorting out issues I pointed out.

Then on my own server I needed a script that could reach out to a URL, scrape the text, and send that text to the NLP model to categorize it. We ran into a wall almost immediately with “CORS” errors, essentially website security blocks that stop scripts from grabbing data from other media sites.

Gemini suggested a PHP proxy. I didn’t know what that meant, so I asked it to explain it like I’m five.

“Think of it like a middleman,” Gemini told me. “Your browser can’t talk to the other site directly, so your server does it for you.” Once we had the “brain” of the tool, I uploaded it to my server via FTP, feeling like a hacker in a movie. I hit “refresh.”

Blank screen. Error 500.

The Anatomy of the The Semantic Entity Analyzer 2

Architecting the Semantic Entity Analyzer AI Brain

The script was crashing because the text I was feeding it was too long. The NLP model had a “token limit.” I had to go back to Gemini and argue.

“Nothing works” I told it. “This code broke my site, we need a solution.” Not very helpful response I know, but Gemini was undeterred.

In just 2 prompts it fixed the PHP script and I finally had my server connected to the NPL backend. Just like magic.

Gemini (with my laymen instructions) then spent the next hours refining the NPL AI Model, focusing on the core workflow of entity extraction:

  • Identification: Finding names, locations, and organizations in the noise.
  • Classification: Categorizing those findings so search engines can disambiguate “Apple” the tech giant from “apple” the fruit.
  • Salience Calculation: Determining which entities are the “stars” of the page and which are just “extras.”

After that was done we added logic to strip out navigation menus, footers, and sidebar leaving only the “meat” of the content. This wasn’t a “meta-moment” of brilliance, it was a tedious grind of copying code, uploading it, seeing it fail, and asking why.

Product Page Design Struggles

Once the data was flowing, the design looked… well, it looked terrible. It was white text on a gray background with basic buttons.

I wanted something that felt 2026. I’m a fan of the modern aesthetic: dark modes, subtle glows, and semi-transparent layers. I told Gemini. I wanted that look and to research the best pratices to make a modern design. I also asked for a SEO optimized meta description to optimize SERP search results and to add other important code to the page, like canonical tags, correctly labeled meta robot tags etc.

The CSS Centering Hell: I wanted the “SEO Semantic Entity Analyzer” title perfectly centered between the description and the search box. Gemini kept giving me code that looked fine on desktop but collapsed into a mess on mobile.

I had to take screenshots and describe exactly what was wrong. “The H1 is too close to the badge. The spacing between the input box and the title feels cramped. Move it 20 pixels down.” Was half expecting the AI to start cussing me off at this point but the tasks were all completed and you can see the result here:
https://webtraffic.blog/web-tools/seo-semantic-entity-analyzer/

Some key changes Gemini made:

  • backdrop-filter: This is what gives the “glass” look.
  • Radial Gradients: To make the background feel deep and layered instead of flat.
  • Progress Bars: Instead of just showing a “Salience Score” as a number (0.85), I wanted a visual “Power Bar.” It makes the data “glanceable.” If the bar is full, that entity is the king of the page.
what the tool actually does

What the Semantic Entity Analyzer Actually Does

So, what did we (Gemini) actually build? The SEO Semantic Entity Analyzer does three things that your standard keyword research service won’t:

1. It Identifies “Entity Neighborhoods”

When you scan a URL, the analyzer gives you a list of every Organization, Brand, Person, Location, and Concept it found. But more importantly, it categorizes them. If you are trying to rank for “Real Estate,” but the tool shows your top entities are “Beach” and “Vacation,” you have an entity mismatch. You’re in the wrong neighborhood.

2. It Calculates “Salience Impact”

Not all entities are created equal. Salience is a measure of how central an entity is to the page. If “The Beatles” are mentioned once in a 2,000-word article about space, the salience will be low. If the article is about them, it will be 90%+. This analyzer visualizes this so you can see if your “Anchor Entity” is actually the strongest node on the page.

3. It Bridges the “Knowledge Graph Gap”

We added a “Strategic Insights” tab. This was a late-night addition. I wanted the analyzer to act like a consultant. It looks at the top two entities and says, “Hey, your second entity is weak. Consider linking to an authoritative source for this concept to boost your E-E-A-T.

Building it Changed My Mindset

Building this changed how I think about my blog.

In the past, I was a content creator. I wrote articles and hoped people would find them. Now, I’m a Founder-Operator. I can identify a problem in my workflow (like the need for entity analysis) and build a solution for it in a weekend.

The barrier to entry for creating high-value software has vanished. You don’t need a $20,000 development budget anymore. You need:

  1. A Vision: A clear idea of what problem you want to solve.
  2. Patience: The ability to iterate through the “Messy Middle” of debugging.
  3. Communication: The skill to describe your vision to an AI with technical precision.

It’s Live & 100% Free to Use

The SEO Semantic Entity Analyzer is live, it’s free and it’s a testament to what happens when you stop treating AI like a search engine and start treating it like a lead developer.

Google is only getting smarter. No more easy knowledge graph, things are only getting more complex. If you are still just “stuffing keywords” and hoping for the best, you are playing a losing game.

Export your data to CSV. Study your competitor’s semantic footprint. And most importantly, realize that you have the power to build the programs you need to win, and the power to increase website traffic with creative ideias.

Join the discussion

  1. INFLUENCERS

    Hi there, always i used to check webpage posts here in the early
    hours in the morning, since i enjoy to find out more and more.

Leave a Reply

Your email address will not be published. Required fields are marked *

back to top
We use cookies to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners. View more
Cookies settings
Accept
Decline
Privacy & Cookie policy
Privacy & Cookies policy
Cookie name Active

Who we are

Our website address is: https://webtraffic.blog.

Comments

When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection. An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.

Media

If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.

Cookies

If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year. If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser. When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select "Remember Me", your login will persist for two weeks. If you log out of your account, the login cookies will be removed. If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.

Embedded content from other websites

Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website. These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.

Who we share your data with

If you request a password reset, your IP address will be included in the reset email.

How long we retain your data

If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue. For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.

What rights you have over your data

If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.

Where your data is sent

Visitor comments may be checked through an automated spam detection service.

Save settings