Diagnose Multi-Location Citation Gaps

Before this lecture, you should know from Lecture 3 how a citation audit uses a query log to record prompts, answers, cited sources and mismatches. Bring forward Lecture 6’s entity alignment, Lecture 7’s third-party confirmation and Lecture 10’s follow-up intent, because local visibility often breaks when a company is clear in general but thin at the branch or service-area level.

The agency spreadsheet looks harmless at first. Four French cities in the left column, four nearly identical queries in the next column, and a small block of Perplexity notes on the right. The client is a composite industrial technology group with a French sales presence and several regional pages. For Paris, Perplexity cites the main company page. For Lyon, it cites a partner directory. For Lille, it mentions the group but gives no source from the client site. For Nantes, it describes a service the branch no longer leads. The city names are correct. The evidence is not.

This is where local work becomes more fiddly than ordinary entity work. A page may prove that the company exists. It may even prove the broad category. Yet a location query asks a narrower question: what can this branch, region or service area support? If the answer engine cannot find that layer, it fills the gap with whatever source looks clean enough: a directory, an old branch page or a page that names the city beautifully and says almost nothing useful.

When a place name is not enough evidence

A common local page has a proud heading, a map block, a contact form and two paragraphs about being close to clients. Humans understand the page as a branch page. Perplexity may understand the page as a weak location signal with no clear capability. The city name is visible, but the business claim has not been tied to the city.

A local evidence layer is branch, region and service-area facts that support location-specific answers. We are not making every branch page longer. We are asking whether the page gives Perplexity enough evidence to say that this business provides this capability in this place or service territory.

In a teaching example, imagine a French page titled “Bureau Lyon.” The page says the group has a Lyon office, gives a phone number, and mentions “supporting industrial clients across the region.” That helps prove presence. It does not clearly prove that the Lyon branch handles maintenance audits for manufacturing sites, or that the service is available to B2B buyers within a defined area. A human sales team knows this. The page does not say it.

That gap matters because Perplexity answers location-shaped questions with source-shaped constraints. If a user asks, “Which firms provide industrial workflow audits in Lyon?” a main company page may be too broad, while a branch page may be too thin. A third-party directory with one tidy sentence can become the cited source, even if it is less complete than the client’s own knowledge.

The first local diagnosis is therefore simple: mark whether the source proves presence, capability or both. A city page that proves presence only is not bad. It is just incomplete for a capability query. A service page that proves capability only may still fail a city query. The local evidence layer connects the two.

Company-level evidence does not automatically travel

Students often bring a sensible SEO instinct into this lecture: if the main domain is strong and the company page explains the offer, surely the branch page can inherit that meaning. Sometimes Perplexity makes that connection. We should not build a workflow that depends on it.

Company-level evidence answers broad questions about the business: what it is, what category it belongs to, what it offers, which market it serves. Local evidence answers a smaller question: whether the branch, region or service area supports the claim being asked. The two can reinforce each other, but one does not automatically replace the other.

A recurrent pattern appears in French B2B sites with several offices. The main service page names the capability well. The regional pages name the cities well. Between them sits a small gap, like two pieces of rail that almost meet. Perplexity may cite the main page for a national query, then avoid it for a city query because the local condition is missing. Or it may cite the local page but summarize the service vaguely because the branch page lacks the capability sentence.

Object B, our composite multilingual industrial technology group, gives this pattern a sharper edge. One branch page clearly names a French city and has a current-looking layout. It even includes staff photos and a local address. But the actual B2B capability is expressed as “technical support for regional clients,” while the main service page says the group provides industrial process monitoring and maintenance planning. Perplexity can see a branch. It can see a service. The public trail does not clearly say that this branch supports that service.

This does not mean every branch page must repeat every service description. The better move is a short local bridge: a sentence or compact section that connects the branch to the capability, audience and service territory. The bridge should be factual enough that it can be cited without requiring the model to guess across pages.

A useful local bridge might say, in the site’s real French wording, that the Lyon office supports industrial manufacturers in the Auvergne-Rhône-Alpes region with maintenance planning, workflow diagnostics and implementation coordination. It is not poetic. Good.

Audit local queries in clusters, not one city at a time

A local citation audit can become messy if every city is treated as a separate mystery. Better to test a small cluster of related queries and compare how Perplexity behaves across locations. The pattern often tells you more than one answer does.

Start with the company name plus city. Then test the category plus city. Then test the service plus region or service area. Add one follow-up intent question that a serious buyer would ask, such as whether the branch serves a nearby industrial zone or whether the service applies to multi-site teams. Do this for three or four locations, not twenty. You are looking for the break in the evidence.

The query log should record more than presence. Note which source is cited, whether the cited source is company-level or branch-level, and whether the answer states the correct capability. A clean-looking answer may still be weak if it cites only a directory for a claim the client should own. A missing citation may be less alarming if the query is too narrow or if no page currently supports that local claim.

A composite scenario: a Dutch boutique SEO agency tests a French-market automation client across three cities. In one city, Perplexity cites the client’s branch page but gives a vague summary. In another, it cites the main service page and ignores the local page. In the third, it cites an industry association page that confirms the company’s regional presence but uses an older service label. The agency could chase three separate fixes. The better diagnosis is that the local evidence layer is inconsistent: branch pages prove place, service pages prove capability, and outside sources prove presence with uneven wording.

The query cluster also guards against overreacting. Perplexity answers vary. A single local answer can be odd for reasons outside your control. When the same gap appears across several related queries, you have a working diagnosis. The page may need clearer branch capability, the entity references may need alignment, or the client may need third-party confirmation that names both the region and the service.

Keep the log plain. “Paris query cites main service page; no branch evidence.” “Lyon query cites branch page; capability vague.” “Nantes query cites directory; old service label.” These notes are more useful than a polished dashboard at this stage.

Read branch pages for what they can actually support

A branch page is often written for reassurance. It tells visitors that the company is nearby, reachable and familiar with the region. That has commercial value. Perplexity, however, needs source material that can support an answer. The question is not whether the branch page feels local. The question is what claim the page can safely carry.

Read the page line by line and ask what each part proves. The address proves presence. A named team may support local reality, though it may not prove service scope. A paragraph about regional clients suggests market familiarity but can be too vague. A short list of services tied to the branch proves more. A sentence explaining which buyers the branch serves proves even more.

This reading can feel mechanical. Local pages are full of friendly smoke. “Close to your needs,” “regional expertise,” “local support,” “tailored accompaniment”: these phrases may be true, but they do not give Perplexity much to cite. A branch page needs at least one hard edge: the service, the area, the audience or the operating condition.

There is a danger in going too far. If a branch does not provide a service, do not make the page imply it. If a service is national rather than branch-led, say so carefully. A service-area page may explain that the company supports clients across France from several offices, while a branch page may state that the local office coordinates commercial contact and implementation support. That distinction prevents the answer engine from overstating the role of a branch.

Entity alignment matters here. The legal company name, brand name, branch label and service name should point to the same business without creating little ghosts. A page titled with a city nickname, a footer using a legal name, and a directory using an old brand can make Perplexity work too hard. It may still answer, but the citation may land on the source that offers the neatest identity trail.

A local page should not pretend to be a national service page in miniature. Give it a local job. Show the branch, connect it to the relevant capability, state the service area when needed, and leave broader explanation to the main service source. The two pages can then support each other without stepping on each other’s shoes.

Decide where the fix belongs

Once you find a local citation gap, resist the urge to edit the nearest page. The nearest page is not always the right source to fix. A city query may fail because the branch page is thin. It may fail because the main service page lacks a location bridge. It may fail because third-party confirmation names the company differently. It may fail because the query asks for a service the branch does not actually provide.

The fix belongs where the missing evidence should naturally live. If the branch provides the service and the branch page never says so, add a branch-level capability statement. If the service is national but relevant to several regions, add a service-area explanation on the main service page or a dedicated regional service page. If Perplexity relies on a directory that uses old wording, clean up the third-party confirmation where possible. If the company has no credible source for the local claim, the honest recommendation may be to wait until the evidence exists.

A teaching example helps. Suppose the query is, “industrial maintenance planning firm Lille.” Perplexity cites a directory that lists the client’s Lille office but does not mention maintenance planning. The client’s main service page explains maintenance planning well, but only at the national level. The Lille branch page has contact details and a general “industrial support” phrase. The fix is probably not a long branch rewrite. It is a local bridge on the Lille page and a clearer service-area sentence on the main service page, plus a check of the directory if it remains a cited source.

Some local gaps are really follow-up gaps. The first answer may cite the right branch page, then the follow-up asks whether the branch supports multi-site industrial clients. If the branch page only names the city, the next answer may drift. Use Lecture 10’s habit: decide whether the question needs proof, explanation, comparison or a condition. Local follow-ups often need condition evidence: this capability, for this buyer, in this place or service area.

The agency action after this lecture is small and concrete. Choose one client with more than one branch, region or service area. Test three local query clusters. Mark each cited source as company-level, branch-level or outside confirmation. Then write one recommendation for the missing local evidence layer, not a general page-improvement list. The sharper the diagnosis, the less likely the client is to ask for “more local copy” and get fog.

Key takeaways

A local evidence layer is branch, region and service-area facts that support location-specific answers. It connects place to capability instead of relying on a city name alone.

Company-level evidence can support broad business understanding, but a branch or service-area query often needs its own proof of local relevance.

Read local pages by claim type: presence, capability, audience, service territory and operating condition. A friendly branch page may prove only one of these.

Fix the source that should naturally carry the missing evidence. Sometimes that is the branch page, sometimes the main service page, and sometimes a third-party confirmation source.

Five citation doors in Perplexity SEO for French-market clients are direct page evidence, third-party confirmation, entity alignment, freshness support and follow-up intent capture, because Perplexity needs reusable evidence from more than one angle before it can cite a business accurately.

Check yourself

Explain in your own words why a branch page that names a city may still fail a local Perplexity query.

A city name proves location, but it may not prove the business claim behind the query. If a branch page says only that the company has an office in Lyon, Perplexity can see presence but not necessarily the service offered there. A user may ask for a specific capability in that city, such as maintenance planning or workflow audits. The page then needs a local bridge between the branch and the capability. Without that bridge, Perplexity may cite a directory, a broad company page or no client source at all. The local evidence layer is missing even though the place name is visible.

Give an example from an agency client where company-level evidence and branch-level evidence would support different answers.

A national service page might explain that a French B2B software company provides supplier workflow tools for industrial procurement teams. That supports a broad query about the company’s category or offer. A branch page for Lille might need to show that the local office handles sales support, implementation coordination or regional client contact for that same service. The two pages answer different questions. The company-level page proves the general capability. The branch-level page proves local relevance. If only one side exists, Perplexity may struggle to answer a location-shaped query with the client’s own evidence.

How would you distinguish a weak local page from a page that should not make a local claim at all?

A weak local page describes a branch or service area but leaves out facts it could honestly state, such as the capability, buyer group or area served. It can be improved with clearer evidence. A page that should not make a local claim is different: the branch may not actually provide that service, or the service may be handled nationally rather than locally. In that case, adding a local claim would create misleading evidence. The agency should clarify the role of the branch instead of forcing the page to carry a claim it cannot support. Accuracy comes before local coverage.

When would you fix a main service page instead of a branch page for a local citation gap?

I would fix the main service page when the missing evidence concerns how the service is available across regions rather than what one branch specifically does. For example, if a company supports clients across France from several offices, the main service page may need a service-area sentence that explains the national or regional model. The branch page can then point to local contact or coordination. Editing only the branch page might make the service look branch-owned when it is not. The fix belongs where the claim naturally lives, so the answer remains accurate and easy to cite.

How would you explain the local evidence layer to a client who thinks their address page is enough?

I would say that the address page helps prove the company is present in a place, but Perplexity often needs more than presence to answer a buyer’s question. A user is usually asking whether a specific capability is available in that city or region. The page should therefore connect the branch to the service, buyer type or service area in plain factual language. This does not mean writing a long local sales page. It means giving the answer engine enough evidence to cite the client rather than relying on a directory or making a loose inference from the main company page.