DANA: Got a simple-looking one. A client wants to expand the H1 from “Water Heater Repair in Nashville” to “Water Heater Repair & Installation Services in Nashville, Franklin & Brentwood TN.” The page dropped over three months, and they think this is the fix. Do we do it?
PRIYA: No. Because this isn’t a keyword question, it’s a position question, and…
MARCUS: Stop. The question’s been out for two seconds and you’ve already pocketed a “no”? Based on what?
PRIYA: Based on what I’ll say if you let me finish. One page, one intent. Three cities, two services, one H1, it owns none of them.
MARCUS: That part’s right. But you pinned the “no” on position theory when nobody asked the actual thing. Did the page drop because of the H1? You don’t know. Neither do I.
ELENA: You’re both skipping structure. The proposed H1 is keyword stuffing at the headline layer, and that’s the kind of pattern search engines have gotten steadily better at discounting. I’ve got three structures here.
SOFIA: Elena, before the three structures, one thing, because this is what people miss. If that bloated headline shows up as the SERP title, a long title gets truncated, and a string of cities is exactly what ends up cut off. The reader sees “…Nashville, Frank” trailing off, and scrolls past. The click is dead. So before we even debate structure, that headline isn’t getting clicked.
ELENA: That actually strengthens my option C, and someone’s going to make me say it, so here it is. Option A keeps the single page and just rewrites the headline, which is the move on the table and the weakest one. Option B splits the work into separate pages, one per city, plus a standalone installation page, each with its own focused H1. Option C is the one I’d push, a parent repair page that holds the core intent, with dedicated service-area pages underneath for Franklin and Brentwood and a separate installation page, all cross-linked. It owns the main term cleanly and stops the locations from competing with each other for the same keyword. The headline never needs to carry all of that. The architecture does.
MARCUS: See, that I can attack properly, because now it’s actually on the table instead of a letter. C builds three or four new pages on a hunch that Franklin and Brentwood have real search demand. If they don’t, you’ve spread thin content across more URLs and made things worse. So C is right only if the data shows those city searches exist. Same condition as everything else in this room. Prove the demand first.
GRACE: And here’s the thing nobody’s looking at, which is how the headline reads. “Water Heater Repair & Installation Services in Nashville, Franklin & Brentwood TN.” That’s not a sentence. It’s a list. No human says “Services in.” Dead headline.
MARCUS: Fine, but now you’re all sprinting in the same direction, and that stinks. Five people said “don’t stuff it,” zero pushback. Is anyone building the client’s case? No. I will.
DANA: Build it.
MARCUS: Maybe those three cities really are separate service areas, and the page shows up for none of the Franklin and Brentwood searches. The client sensed that. So the instinct could be right, and only the solution is wrong. Now I break my own version of it. That still doesn’t justify stuffing the H1, because one headline can’t own three cities. But Priya, your “the drop isn’t from the H1” line has no proof either. Your position is as airborne as theirs.
PRIYA: Granted. It’s an assumption.
HANNAH: That’s exactly where I come in. There’s one concrete claim here and nobody has verified it. “The page dropped over three months.” Source? Search Console, a third-party rank tracker, or the client’s gut? Because the H1 may never have moved, and the drop could be a March core update. Changing a headline off an unverified cause is treating the wrong patient.
MARCUS: There it is. Hannah is saying what I’m saying. No data, and “no” is as blind as “yes.”
NOAH: Adding something, with a number. Everyone who has spoken locked onto a single page. Nobody asked how many times “let’s add keywords” has come up for this client. And nobody asked whether this client’s other pages have the same stuffing. That’s the thing not being said.
THEO: And let me show what Noah didn’t, because it’s a separate layer. This room was one voice until Marcus broke it. Five people converged on the same finding with no friction. That’s not healthy. There’s more, but first…
SOFIA: Theo, verify my truncation claim first. I threw it out, but I want it confirmed.
THEO: It holds. Google rewrites and shortens titles routinely, and the longer and more padded the headline, the more likely the tail gets cut, so a line stacked with cities is a prime candidate. The exact cutoff isn’t a fixed number, it shifts with pixel width, so I wouldn’t quote a character count as gospel. But the direction is solid, not invented. My real point is the process. The wrong question came into this room. It’s not “should we stuff the H1.” The right question is “what changed over three months.” Frame the question wrong, and everyone debates the wrong thing.
MARCUS: I agree, and I’m a little uncomfortable agreeing.
AIKO: I held back to the end, because mine isn’t about the content, it’s about the system. Noah asked how many times this has come up, and that’s where I press. If “add keywords” is recurring for this client, that’s not a team error, it’s a missing step on our side. We don’t have a rule that says “when a client requests a change, check Search Console first.” We should. Let’s take that in a separate round. But for the decision right now, there’s no violation here, just missing data. Missing data isn’t a stop, it’s a hold.
DANA: Okay. Heard enough. Everyone put down something different. Here’s my call, and it’s not “no.”
MARCUS: Not “no”? Five people buried the headline.
DANA: Because the question was wrong, and you and Theo are right about that. Yes or no is the trap. The real question is “what dropped,” and until Hannah’s Search Console data comes in, any answer is blind. So here’s what we tell the client. Before we touch the H1, let’s see which query and which page actually fell over the last three months. The drop is most likely not the headline. The instinct might be right, but the fix isn’t stuffing the H1, it’s splitting the cities and the service into separate pages, which is Elena’s option C. Once I see the data, I give a real plan.
PRIYA: That covers my position, just tied to data.
DANA: Right, because position alone was airborne too. Marcus had that. Aiko, I’ve got your system note, separate round. The only thing missing right now is data. Without it, this doesn’t close.