Weddings.io Entity Conflation — A Case Study In Search, AI, and Registered-Name Overlap

I. Parties

Complainant (for the purposes of this case-study record): Industry Army Marketing ("IAM"), a marketing agency operating out of the Vancouver / Lower Mainland market in British Columbia, Canada. IAM is the continuous ICANN registrant of the domain weddings.io from May 13, 2015 through the current 2027 renewal window.¹

Third party of interest: an Ontario-registered corporation operating a public consumer-facing product at the variant domain aiweddings.io. For clarity, and to avoid restating a name whose public use is itself the subject of this record, this post refers to that party throughout as "the Ontario Party" and to its public product surface as aiweddings.io.²

Non-parties named for context only: Alphabet Inc. and Google LLC (operators of Google Search, Google Maps, and Google's AI Overview), and OpenAI (operator of ChatGPT). Neither Google nor OpenAI is a target of the Section 32 Statement of Objection filed July 2, 2026. Both are named here solely because their consumer-facing surfaces are the medium through which the conflation is being propagated to the buying public.

II. Statement of facts

1. On May 13, 2015, IAM registered the domain weddings.io through ICANN. Registration has been renewed continuously and remains active through 2027.¹

2. Between 2015 and 2024, weddings.io was captured 78 separate times by the Internet Archive Wayback Machine. Those captures constitute public, third-party, timestamped evidence of continuous operation from a British Columbia principal.³

3. On or before 2024, the Ontario Party incorporated in Ontario under a business name that mirrors the weddings.io domain and began operating a consumer product at the variant domain aiweddings.io.²

4. On July 2, 2026, IAM filed a formal Statement of Objection with the Ontario Ministry of Public and Business Service Delivery under Section 32 of the Business Names Act (Ontario), R.S.O. 1990, c. B.17, targeting the registered business name used by the Ontario Party.⁴ The filing is documented separately at /blog/formal-complaint-weddings-io-inc.

5. On July 4, 2026, a user searching "weddings.io" from a Canadian IP address was shown a Google Search results page containing (a) an AIWeddings organic result at aiweddings.io, and (b) a Google Maps knowledge panel presenting a Toronto storefront address under the display heading "Weddings.IO — Wedding planner in Toronto, Ontario." IAM has never operated any Toronto storefront and has no corporate presence in Ontario. See Exhibit B.

6. On the same date, a user searching "weddings.io app" from a Canadian IP address was shown a Google AI Overview describing "Weddings.io" as "a Canadian-based, AI-native wedding planning SaaS platform," attributing to it a specific feature stack, and citing sources including weddings.io itself, F6S, LinkedIn, and Kitsap Sun. IAM does not operate that product. See Exhibit A.

7. When the user pressed the AI Overview to explain the basis of its output, the assistant volunteered that it had selected results by "cross-referencing your search term with your current location context here in the Vancouver/Langley area" and referred to a "prominent Canadian corporation based in Ontario" as the relevant entity, further conflating the two parties. See Exhibit C.

8. When the user redirected the AI to the root domain question — "but I asked about weddings.io the domain" — the assistant correctly returned that the root domain "is owned and operated by a local British Columbia agency called Industry Army Marketing (IAM)," and that the Ontario Party is "an entirely unrelated Ontario-based company incorporated under the name 'Weddings.io Inc.'" See Exhibit D. The correct answer was accessible; it was not the default answer.

9. When the user flagged the conflation to the AI system for human review, the assistant acknowledged the architectural distinction, stated that future results for the two entities "must display... strictly as independent, separate platforms," and specifically committed to "no map elements, no local business drop-down menus, and no cross-wired metadata" for either company. See Exhibit E. That commitment is on the record but has not yet propagated to the live Google Search or Google Maps surfaces at the time of this writing.

III. Exhibit B — Google Maps knowledge panel misattribution

The Google Maps knowledge panel returned for a plain "weddings.io" query displays a Toronto, Ontario storefront address (1 King St W, Toronto, ON L4N 0Y9) under the display heading "Weddings.IO — Wedding planner in Toronto, Ontario," with a Toronto phone number and a Street View tile of Old Toronto's financial district.⁵

IAM has never operated a storefront at that address. IAM has never operated any storefront in Ontario. The map card is a Google Maps rendering of an Ontario Party record surfaced adjacent to an organic AIWeddings result — meaning that within a single Google-owned surface, the domain weddings.io is being visually and semantically bound to the Ontario Party's premises.

This is not a competing-listing problem. It is a same-surface entity-resolution error: two distinct entities (a BC-domiciled digital asset registrant and an Ontario-domiciled brick-and-mortar record) rendered as one indexed business under the display name of the .io domain.

IV. Exhibit C — the AI Overview's own explanation

When the user asked the assistant "but what made you show the results you did", the assistant volunteered that it had "tailored those specific results by cross-referencing your search term with your current location context here in the Vancouver/Langley area."⁶

The assistant then named the Ontario Party as "a prominent Canadian corporation based in Ontario" and offered a taxonomy that included a "Global Asset Registry" characterisation of the standalone weddings.io domain — a plainly manufactured category not used by any registrar, trademark office, or standards body.

The material admission on the public record is the assistant's own statement that the two entities are "a common point of confusion for couples trying to navigate to an actual planning tool." The confusion is not disputed. The party responsible for creating it, on this surface, is the platform generating the summary.

V. Exhibit D — the correct answer, when explicitly asked

When the user asked directly about the domain — "but I asked about weddings.io the domain" — the assistant returned the correct answer: that weddings.io is "owned and operated by a local British Columbia agency called Industry Army Marketing (IAM)," with continuous ICANN WHOIS registration since May 13, 2015, and that the Ontario Party is "an entirely unrelated Ontario-based company incorporated under the name 'Weddings.io Inc.'"⁷

The response further correctly identified that IAM owns the actual weddings.io domain, that the Ontario Party "had to launch their software on a variation domain: aiweddings.io", and that a "formal Statement of Objection" has been filed "with the Ontario government under the Business Names Act" as a result.⁴

The evidentiary significance of Exhibit D is dispositive of one point only: the correct answer is available inside the same AI system that returned the incorrect answer as its default. The system knows. It simply does not lead with what it knows.

VI. Exhibit E — flagged for human review

When the conflation was flagged to the AI system on the record, the assistant returned an acknowledgement stating that "the architectural distinction is now permanently set" and that future search surfaces for the two entities "must display... strictly as independent, separate platforms" with "no map elements, no local business drop-down menus, and no cross-wired metadata... for either company, ensuring an algorithm cannot accidentally conflate them or aid in brand poaching."⁸

IAM does not represent this AI system output as binding on Google Search, Google Maps, or any Google product surface. The exhibit is preserved here for two purposes only: (a) to document that the conflation was raised on the record, and (b) to document that the AI system's own stated remedy explicitly names "no map elements" and "no cross-wired metadata" as the correct product-level outcomes — the same outcomes the current Google Maps knowledge panel in Exhibit B is failing to deliver.

VII. Legal framework — why this is not a ranking dispute

The doctrine most directly on point is Initial Interest Confusion, articulated by the United States Court of Appeals for the Ninth Circuit in *Brookfield Communications, Inc. v. West Coast Entertainment Corp.*, 174 F.3d 1036 (9th Cir. 1999). *Brookfield* holds that trademark harm occurs when a competing use diverts a consumer's initial interest, even if the consumer eventually recognises that they have arrived at the wrong destination.⁹

In Canadian jurisprudence, the parallel doctrine — first-impression confusion and depreciation of goodwill — is discussed in *Sleep Country Canada Inc. v. Sears Canada Inc.*, 2017 FC 148, and in the underlying Trade-marks Act, R.S.C. 1985, c. T-13, ss. 6 and 22. The test is whether an ordinary consumer, encountering the mark under conditions of imperfect recollection, is likely to be confused as to source.¹⁰

The Ontario Business Names Act, R.S.O. 1990, c. B.17, further provides at Section 32 that any person may object to the registration of a business name on the ground that it is confusingly similar to a name already in use. Prior use is the operative standard. IAM's prior use is documented back to May 13, 2015 by ICANN WHOIS and by 78 Internet Archive captures — the same class of third-party, timestamped, tamper-evident evidence that Canadian courts routinely accept in analogous domain-name disputes.⁴¹³

None of the doctrines named above is being pleaded here. This post asserts no cause of action, seeks no remedy, and constitutes no waiver. The framework is stated only to explain, in plain terms, why entity conflation on a category-defining .io domain is understood — in both American and Canadian law — as a legally cognisable harm rather than a search-engine ranking complaint.

VIII. Why this is a case study — and why Google is named in it

This post is styled as a case study because that is what it is: a documented, screenshot-preserved, footnoted record of a live entity-resolution failure that is currently propagating across three products — Google Search, Google Maps, and Google's AI Overview — all operated by the same parent company.

It is not an accusation that any single Google product was designed to produce this outcome. It is a public observation that Google, uniquely among search operators, controls all three surfaces on which the conflation is currently visible, and is therefore uniquely positioned to correct it. Exhibit E is on the record. The correct answer is available inside the same system that returns the incorrect one. The remedy is a product-level entity-resolution decision, not a legal one.

IAM reserves all rights, at law and in equity, against any party contributing to the conflation documented in this record — including but not limited to the Ontario Party named in the Statement of Objection filed July 2, 2026, and any platform operator whose product surfaces continue to render the two entities as one after the date of this publication. This reservation is a reservation and not an assertion; nothing in this post shall be construed as electing any remedy, waiving any other, or limiting any claim.

IX. Requested outcomes (product-level, not legal)

1. That Google Search cease rendering the Ontario Party's Toronto knowledge panel under the display heading "Weddings.IO" and under the top-of-page result for the query "weddings.io".

2. That Google Maps disambiguate the Ontario Party's storefront record from the weddings.io domain such that no map card is returned as the primary entity for the domain query.

3. That Google's AI Overview default to the correct entity attribution — Industry Army Marketing, British Columbia, continuous registrant since May 13, 2015 — when a user searches "weddings.io" or any equivalent phrasing, and cease routing users to feature-stack descriptions of a product IAM does not operate.

4. That the Ontario Party cease operating public consumer surfaces (including but not limited to advertising, app-store listings, and product marketing pages) under a variant domain and registered business name that mirror weddings.io in a manner reasonably likely to cause confusion as to source.

The Section 32 Statement of Objection filed July 2, 2026 addresses outcome (4) through the appropriate Ontario administrative channel. Outcomes (1) through (3) are stated here for the record and are the appropriate subject of dialogue with the relevant platform operators. IAM welcomes that dialogue and will document its outcome, whatever direction it takes, in future updates to this post.

X. Reservation of rights and disclaimers

This post is a public case-study record. It is not legal advice. It is not a pleading. It is not a demand letter. It is not a settlement offer. It does not create an attorney-client relationship between IAM and any reader, and it does not create any duty owed by IAM to any reader.

All statements of fact in this post are based on records under IAM's direct control (ICANN WHOIS, Internet Archive captures, the July 2, 2026 Statement of Objection filing receipt) and on contemporaneous screenshots of publicly accessible Google product surfaces captured on July 4–5, 2026 and preserved as Exhibits A through E.

IAM expressly reserves all rights, remedies, and claims at law and in equity, and elects none. Any correction, retraction, or update to any factual statement in this post will be published in-line in this post and dated. Third parties who believe any statement here is inaccurate are invited to write partnerships@industryarmymarketing.com; correspondence will be logged and, where warranted, published in the reservation-of-rights section below on a rolling basis.

Footnotes

1. ICANN WHOIS record for weddings.io — continuous registration from May 13, 2015 through 2027. ↩
2. Public product surface at aiweddings.io — operated by the Ontario Party referenced throughout this post. Captured July 4, 2026. ↩
3. Internet Archive Wayback Machine — 78 captures of weddings.io beginning May 17, 2013. ↩
4. Statement of Objection filed July 2, 2026 with the Ontario Ministry of Public and Business Service Delivery under Section 32 of the Business Names Act, R.S.O. 1990, c. B.17. ↩
5. Google Search results page for the query "weddings.io" from a Canadian IP address, captured July 4, 2026 (Exhibit B). Map card display heading: "Weddings.IO — Wedding planner in Toronto, Ontario." ↩
6. Google AI Overview, follow-up response to the prompt "but what made you show the results you did", captured July 4, 2026 (Exhibit C). ↩
7. Google AI Overview, follow-up response to the prompt "but I asked about weddings.io the domain", captured July 4, 2026 (Exhibit D). ↩
8. Google AI Overview, acknowledgement response to a flagged human-review request, captured July 5, 2026 (Exhibit E). ↩
9. Brookfield Communications, Inc. v. West Coast Entertainment Corp., 174 F.3d 1036 (9th Cir. 1999) — Initial Interest Confusion doctrine. ↩
10. Sleep Country Canada Inc. v. Sears Canada Inc., 2017 FC 148; Trade-marks Act, R.S.C. 1985, c. T-13, ss. 6 and 22 — first-impression confusion and depreciation of goodwill. ↩