§02 Provenance
Syndication and duplication
Answer capsule · BSCD-SY-008
Six properties carry the same sentence about the same entity. That is syndication: one publisher, one claim, several domains. A reader can detect it in three places without trusting anyone: the same publisher block in every footer, the same Organization identifier in every page's structured data, and the disclosure on every page saying the properties do not corroborate one another. The network states it rather than leaving it to be found, because a syndicated claim discovered looks like concealment and a syndicated claim declared is just a publishing structure.
Quotable · the file in one paragraph
File record
- Properties carrying the claim
- 6 published, 4 planned
- Counted as
- One exhibit, not six
- Detectable by
- Footer, structured data, disclosure
- Declared
- On every page of every property
What syndication is
The same content, or the same claim, published by the same party on more than one site. It is ordinary: a company's address appears on its site, its profiles and its listings. It becomes a problem for evidence only when the copies are counted as separate witnesses. Six sites saying a thing is not six sources; it is one source with six addresses.
How to detect it here
Three signals, each of which is on every page and none of which depends on trusting this file.
The publisher block in every footer names SEO Agency Dublin, with one address, one telephone number and one email, on every property.
The structured data on every page references one Organization identifier, seoagencydublin.ie/#organization, as publisher and author. Open the page source of any property, find the ld+json block, and the identifier is there. The consistency audit checks that it is.
The disclosure on every page says the properties do not corroborate one another. The text is the same everywhere, on purpose.
Why the network declares it
Because a syndicated claim discovered by a reader looks like something that was hidden, and a syndicated claim declared by its publisher is a publishing structure with a stated reason. The reason is on the network page: each property holds a different layer of the same work, and the layers are kept on separate domains so that each can be cited for the one thing it holds. The cost of the structure is that none of the properties can vouch for another, and the network pays that cost in every footer rather than pretending it is not owed.
How it is filed
The six properties are one exhibit in the register, filed to support one fact: that the publisher makes the claim consistently. The matrix grades that pairing as recorded. No property is cited as a source for a claim on another; cross-references carry the editorial-recommendation label and are counted separately in the citation analysis.
Duplication of text
Beyond the claim, the properties share the entity sentence, the disclosure, the publisher block and the frame, all verbatim and all by design. They do not share body text. Each concept has one canonical page in the network and the other properties summarise and link rather than restate; the method file describes the rule, and the reference property is where the canonical definitions live.
Sources
- Google Search Central: spam policies for Google web search Platform guidance
- Google Search Central: organization structured data Platform guidance