<b>SOP: Smartlink naming and tagging convention</b>

<b>SOP: Smartlink naming and tagging convention</b>

Purpose: make any smartlink readable at a glance six months later when you've built 200 of them.

Name pattern: <code>vertical_geo_source_version</code>
Example: <code>dating_t1_fb_v3</code>

☐ Step 1 — Lock the field order and never reorder it. Sorting depends on consistency.
☐ Step 2 — Use the same source codes everywhere: fb, gg, tt, push, native. No synonyms.
☐ Step 3 — Bump the version on every routing-logic change, never edit in place silently.
☐ Step 4 — Tag with the date created and the owner. Orphaned smartlinks are how dead offers keep running.
☐ Step 5 — Keep a single index sheet: name, purpose, last edited, status.

The convention is worthless if one person ignores it. Enforce it on every new link.

Review the index monthly and archive anything dark for 30 days.