Create a project-specific URL matching key

Define equivalence before normalizing URL exports

Joining Google Search Console exports against CRM or analytics URLs often fails on superficial differences: http:// vs https://, leading www., uppercase characters, or a trailing slash /.

The illustrated policy lowercases the entire string, removes the scheme and leading www., then one trailing slash. Preserve the original URL alongside this derived key.

Illustrative matching-key formula

Place IFERROR directly around TEXTAFTER(u, "://") so schemeless URLs ("arte-soft.com/docs") pass through untouched.

=LET(u, LOWER(TRIM(A2)), p, IFERROR(TEXTAFTER(u, "://"), u), w, IF(LEFT(p, 4)="www.", MID(p, 5, LEN(p)), p), IF(RIGHT(w, 1)="/", LEFT(w, LEN(w)-1), w))

Remove only trailing slash while keeping protocol

This only removes one trailing slash; use it when that change matches your explicit comparison policy.

=LET(u, TRIM(A2), IF(RIGHT(u, 1)="/", LEFT(u, LEN(u)-1), u))

Inputs and interpretation

Paths and queries can be case-sensitive. HTTP/HTTPS, www/non-www and slash/no-slash paths can identify different resources. Do not use this lossy key to generate canonical URLs, security decisions or navigation destinations. Queries, fragments, credentials and unusual URL forms need structured URL parsing.

Further reading

• Microsoft Support — TEXTAFTER function