Some SEO signals still travel into assistant answers, but they travel as evidence, not as ceremony. The signal has to help a machine decide what the business is, where it fits, and why it can be trusted.
The Florence office had better local pages than its Venice office. Better photos, fresher reviews, tighter service text, a less confusing address block. Yet in assistant answers for English-speaking visitors, Venice was the branch that kept getting named. The reason was not obvious from a normal ranking view. A travel aggregator had written one clean paragraph about the Venice service boundary, and the assistant seemed to prefer that paragraph to the company’s own page.
This is a composite scenario from tourism-adjacent Italian businesses, not a single client file. I have seen the shape often enough to trust the pattern, while the details vary. A business ranks locally, has reviews, owns a tidy site, and still loses the citation to a directory, a list page, or a booking-style aggregator. The old signals did not vanish. They simply arrived at the assistant’s desk wearing different clothes.
The signal has to survive extraction
A signal survives citation checks when it remains useful after the page has been stripped of design, persuasion and search-result context. That is the shortest way I can say it. The assistant does not experience the page as a human does. It does not feel the nice spacing, the brand warmth, the tasteful photograph of a doorway in Florence. It sees text, structure, entities, links, source reputation, repeated claims and sometimes conflicting descriptions from elsewhere.
AI-citation signal is evidence that remains understandable after extraction, because it helps an assistant name, classify, locate or verify a business. That is the working definition I use with clients. It keeps the discussion away from mystical language. We are not asking whether a page “looks authoritative” in the abstract. We are asking whether the useful evidence survives the trip from page to answer.
Some classic SEO work still helps. Clear titles help. Internal links help. Specific service pages help. Location pages can help. Reviews can help indirectly, especially when they reinforce service and place. But the mechanism is not identical to ranking. A title tag may help a page appear in search results; a citable service sentence may help an assistant trust the page as a source. Those are cousins, not twins.
This is why I am cautious when someone asks for “the AI SEO signals.” The phrase invites a shopping list. Shopping lists get stale. It is more accurate to look at families of signals and ask which ones survive citation checks across repeated queries. In my notebooks, the surviving signals usually fall into four families: entity clarity, source corroboration, boundary language and query fit. I call them the four surviving shelves, because each one gives the assistant a place to put the business without dropping it.
Entity clarity is still the first shelf
A business that cannot be classified cleanly will be classified by someone else. That someone else may be a directory, an aggregator, an old profile, or a competitor page that names the category more plainly. Entity clarity sounds technical, but on the page it is quite ordinary. What is the business? What is the branch? What is the service? Which place does this page represent? Which audience does it serve?
For the composite tourism-adjacent company, the branch pages mixed several audiences in the same opening. English-speaking visitors, Italian partners, private groups, agencies, concierge desks, local collaborators. All of them mattered commercially. The page was trying to be hospitable to everyone at once, like a small hotel breakfast table with too many cups. Assistants do not reward that kind of hospitality when the query is specific.
If the query is “best private service in Venice for English-speaking visitors,” the page must make that branch-level fit easy to extract. The Venice office should not hide behind a national brand paragraph. The Florence office should not share the same text with only the city swapped. Each branch needs its own entity clarity: address, service area, languages, service boundaries, proof and the type of visitor or partner it is built for.
Search engines have long handled messy pages better than business owners deserve. Assistants are less forgiving in a different way. They may still find the name, yet choose a cleaner source to explain the name. That is the painful gap. The business is known, but not known in its own words.
A useful test is to read only the first screen and the main headings. If two branches could swap pages without making the text false, the entity signal is weak. If the page can only belong to that branch, because the service boundary and local proof are too specific to move, the signal is stronger.
Corroboration beats repetition
Old SEO habits often confuse repetition with evidence. Put the city in the heading. Repeat the service term. Add a few variants. That may still have some search value in ordinary contexts, though even there it can become clumsy. Citation checks are harsher. Repetition without corroboration looks like a person saying his own name louder in a railway station.
Corroboration means that different sources say compatible things about the business. The website says the Venice branch serves English-speaking visitors for a defined service. The Google profile or public listing does not contradict the address. A relevant directory uses the same category. Reviews mention the real service, not a vague “great experience.” Partner pages do not describe the business as something else. The assistant sees fewer reasons to hedge.
For Italian businesses serving both Italian and English queries, this is especially important. The English web often builds a second version of the business. Tourism pages, listicles and booking sites may describe the offer in simpler terms than the Italian site. Sometimes that simpler version is more citable. Sometimes it is wrong. Either way, it becomes evidence.
I do not think every business needs to chase every aggregator profile. That becomes a dirty hallway with no end. But the main public descriptions should agree on the basics: name, branch, category, place, service boundary and audience. When they disagree, the assistant may choose the source with the cleanest sentence, not the source with the deepest truth.
The imperfect detail is often small. A branch moved two streets away. An old listing still says “tour operator” while the site says “visitor service.” A review platform groups Florence and Venice under one page. These details do not always hurt ranking. They can poison citation because the assistant is trying to avoid a wrong recommendation.
Boundary language has become a serious signal
Boundary language is the unglamorous art of saying what you do and do not cover. It matters because assistant answers often respond to fit questions. “Which company handles this kind of visitor?” “Who is suitable for a small group?” “Which provider works in Venice, not only Florence?” The model needs boundaries to avoid naming the wrong business.
Many business pages avoid boundaries because they sound limiting. I understand the instinct. A service company wants to keep the door open. But a page with no boundaries becomes a soft lump. Assistants prefer edges. Edges let the answer say, “this provider fits this query.”
In the composite tourism scenario, the company’s own page said it handled “tailored experiences across Italy.” That phrase had a nice sweep. The aggregator said the Venice office handled “English-language support for visitors arranging local services in Venice and nearby islands.” The aggregator won the citation more often in teaching runs because it offered edges: language, visitor type, service type, place. It was not a deeper source. It was a cleaner shelf.
This does not mean the business should write like a form. It means the page needs at least a few hard edges near the main service explanation. “We serve English-speaking visitors in Venice and Florence” is a start. “The Venice office covers arrival support, local arrangements and partner coordination; it does not operate as a licensed tour guide service” is stronger, if true. That last clause may save the business from being misdescribed.
Boundary language also helps where Italian and English queries diverge. An Italian partner might search by formal service category. An English visitor might search by problem. The same branch can be relevant to both, but the page must not collapse the two into a cheerful cloud.
Query fit is stronger than broad authority
A familiar mistake is to treat authority as one large bucket. The strongest domain will win, the biggest site will be cited, the oldest page will dominate. Sometimes yes. But in citation checks I often see smaller sources win because they fit the query more exactly. The assistant may use a directory for a broad comparison, then a business page for a narrow branch-level question, then a review source for proof. Source choice shifts with the query.
This is where old keyword lists become blunt instruments. A page may rank for “Venice private service” and still not fit a question like “which Venice provider helps English-speaking visitors coordinate with Italian partners?” The assistant’s answer lives closer to the buyer’s phrasing. Citation signals therefore have to be checked against query shelves, not just keyword positions.
Query fit has a particular texture. The page uses the buyer’s category without stuffing it. It names the relevant place. It gives proof near the claim. It answers the condition inside the query. For a branch page, the condition might be language. For a software page, it might be sector. For a consultant, it might be regulatory context. If the condition is missing, the assistant must infer. Inference is where competitors enter.
I keep old SEO evidence in one notebook and citation evidence in another because the same signal can behave differently. A strong title may help both. A large blog archive may help rankings but do little for assistant selection. A clean branch paragraph may not move rankings much, yet it may change which source gets cited. The disagreement is not a bug in the audit. It is the thing worth studying.
The practical way to find surviving signals is dull but reliable. Run the same query shelf. Record named business, cited source, description, and whether the description matches the page. Then look backward at the source. What signal did it offer that the skipped business did not? Do that across enough checks and the surviving shelves become visible.
The Citation Ledger
Query shelf: “segnali citazione IA SEO for an Italian branch or service page.” Ranking residue: old reports still show position, titles, local visibility and traffic signals. Citation hinge: the signal must survive extraction as entity clarity, corroboration, boundary language or query fit. Next count: compare cited sources against your own page and mark which surviving shelf each source supplied better than you did.