How should citation tracking handle URLs with tracking parameters?

Definition: Citation tracking should preserve the raw source URL observed in an answer alongside a normalized page identifier used to group equivalent links. Tracking parameters are query fields used to label referrals or campaigns; removing them from a grouping identifier requires a rule that preserves parameters identifying different content.

Key facts

• RFC 3986, section 3.4, defines the query as data that helps identify a resource together with the path.
• As of 17 October 2026, Google's campaign URL documentation describes utm_source, utm_medium and utm_campaign as campaign fields whose values reach Analytics when a referral link is clicked.
• Google Search Central's canonicalisation documentation, updated 10 July 2026, describes redirects and rel="canonical" annotations as strong canonical signals.

What normalization does RFC 3986 support?

Normalization transforms a URL into a consistent form for comparison. RFC 3986, section 6.1, explains that equivalence depends on the application's purpose and that comparison methods must avoid false positives: incorrectly treating different resources as equivalent.

Section 6.2.2.1 permits lowercasing the scheme and host. Other components are assumed to be case sensitive unless the scheme defines otherwise. Section 6.2.2.2 permits decoding percent-encoded unreserved characters, which are letters, digits and the characters -, ., _ and ~.

A conservative citation grouping policy therefore keeps unrecognized query fields. It removes a parameter only after its tracking-only role is established for the relevant site. Blanket query deletion, sorting unfamiliar query fields, and lowercasing the whole URL fall outside this policy. The policy should record its rules and a revision identifier so earlier observations can be regrouped consistently after a change.

Which fields should a citation record preserve?

Google's campaign URL documentation provides an example containing utm_source=summer-mailer, utm_medium=email and utm_campaign=summer-sale. Its parameter values are case sensitive.

For citation tracking, a practical record keeps the exact observed link in raw_url and computes normalized_page_id separately. The following illustrative record uses Google's example URL and assumes the site serves equivalent content when these campaign fields are removed:

{
  "raw_url": "https://www.example.com/?utm_source=summer-mailer&utm_medium=email&utm_campaign=summer-sale",
  "normalized_page_id": "https://www.example.com/",
  "removed_parameters": ["utm_source", "utm_medium", "utm_campaign"]
}

This is a proposed recording format. The raw field preserves the campaign labels for inspection; the derived field supports grouping page references. Each observation should retain its answer reference and collection time so grouping leaves the underlying evidence available. Reports should state whether they count observed links or distinct normalized page identifiers.

A grouping transformation belongs in the reporting layer. It leaves the stored source link intact, including its original parameter values.

How should canonical signals affect grouping?

A canonical URL is the representative URL for duplicate or very similar pages. Google's canonicalisation documentation describes a canonical element in the HTML head that identifies a representative page. It also describes sitemap inclusion as a weaker signal than redirects or canonical annotations.

A tracker can record the fetched destination and declared canonical URL as separate evidence fields, with the time of the check. Any grouping based on that evidence should retain the original link and identify the rule used. Google's canonical signals concern its search processing; applying them to citation reports is an explicit measurement choice.

When a declared canonical and the content comparison conflict, the conservative policy keeps separate identifiers pending review. This avoids merging distinct cited material solely because a page declares a canonical target.

Related terms

• Canonical URL
• Citation tracking
• UTM parameters
• HTTP redirects

FAQ

Should you remove every query parameter?

Keep unfamiliar parameters until their role is established. RFC 3986, section 3.4, includes query data in resource identification, so query removal requires an application-specific grouping rule.

Should you preserve fragment identifiers?

Preserve the fragment, the portion introduced by #, in the raw link. Section 3.5 of the same RFC explains that a fragment can identify a portion or subset of a resource; a page-level grouping rule can omit it from the derived identifier while retaining that reference detail.

Does a declared canonical replace the observed citation URL?

Keep both fields. Google's documentation treats canonical annotations as signals, and preserving the observed URL keeps the citation record auditable when grouping rules change.

Sources

1. IETF, "RFC 3986: Uniform Resource Identifier (URI): Generic Syntax", January 2005
2. Google Search Central, "How to specify a canonical URL with rel="canonical" and other methods", updated 10 July 2026
3. Google Analytics Help, "URL builders: Collect campaign data with custom URLs", accessed 17 October 2026

---

Check how a page reads to answer engines. Open the GEO score analyzer