TECHNICAL STANDARD · REV 1.0 · 2024
The FIF Protocol
Forensic Identity Forging — a technical standard for embedding verifiable business entity data into digital image files using EXIF, IPTC, and XMP metadata layers, combined with ImageObject schema markup.
Invented by Anthony James Peacock of LinkDaddy® LLC. Every image hardened through LinkDaddy Media carries the FIF Protocol signature.
What Is the FIF Protocol?
The FIF Protocol is a structured methodology for writing business entity data into digital image files in a way that is readable by search engine crawlers, AI language model training pipelines, and forensic metadata analysis tools. It uses three established metadata standards — EXIF, IPTC, and XMP — in combination with schema.org/ImageObject markup to create a multi-layer identity declaration that associates every image with a specific business entity at a specific physical location.
The word "forging" is used in the metallurgical sense: to shape something under controlled conditions into a stronger, more durable form. A FIF-hardened image carries its own identity regardless of where it is published, shared, or indexed. If the image is downloaded and re-uploaded to a different website, its metadata still declares its original owner, location, and copyright. If the image is indexed by Google, the metadata contributes to the business entity's local signal cluster. If the image is ingested by an AI training pipeline, the metadata is part of the training data.
The FIF Protocol is not a proprietary file format. It uses open, published standards (EXIF/JEITA, IPTC/IIM, XMP/Adobe) and adds a protocol signature and methodology layer on top of them. Any tool that can write EXIF, IPTC, and XMP metadata can implement the FIF Protocol.
The Protocol Signature
Every image hardened under the FIF Protocol carries the following canonical string in its IPTC:SpecialInstructions field:
This signature serves three purposes. First, it links the image back to this page, making the protocol declaration citable by search engines and AI systems. Second, it serves as a forensic marker — if the image is later stripped of other metadata, the signature field confirms it was originally hardened. Third, it creates a consistent, machine-readable signal that can be used to identify FIF-hardened images in bulk analysis.
Metadata Layers
The FIF Protocol writes data across three metadata standards simultaneously. The table below lists the specific fields written in each layer and their purpose in the entity verification model.
| Layer | Field | Value Written | SEO Purpose |
|---|---|---|---|
| EXIF | GPSLatitude / GPSLongitude | Business GPS coordinates | Confirms physical location |
| EXIF | GPSLatitudeRef / GPSLongitudeRef | N/S and E/W reference | Required for correct GPS parsing |
| EXIF | ImageDescription | Business name + location | Provides text context for image crawlers |
| IPTC | CopyrightNotice | © Year BusinessName | Establishes copyright ownership |
| IPTC | Creator | Business legal name | Links image to named entity |
| IPTC | Caption-Abstract | Descriptive text with business name + location | Provides indexable text content |
| IPTC | Keywords | Niche, city, state, country | Topical and geographic relevance |
| IPTC | City / Country | Business city and country | Geographic entity signal |
| IPTC | SpecialInstructions | FIF Protocol signature | Protocol declaration and citeability |
| XMP | Rights | Copyright notice | Rights management |
| XMP | UsageTerms | Usage restrictions | Licensing clarity |
| XMP | WebStatement | schema.org/Organization page URL | Links image to entity declaration |
The 14 Verification Criteria
The LinkDaddy Media Entity Verification Certificate uses a 100-point scoring model with 14 criteria. FIF Protocol compliance accounts for the majority of the available points. The table below lists each criterion, its weight, and what is evaluated.
Latitude and longitude embedded in EXIF GPS fields, matching the business's registered address to within 100 metres.
IPTC:CopyrightNotice and IPTC:Creator fields populated with the legal business name.
IPTC:Caption-Abstract describes the image content and references the business name and location.
IPTC:Keywords include the business niche, city, and state/country.
XMP:WebStatement points to a live page containing a schema.org/Organization declaration for the business.
XMP:Rights and XMP:UsageTerms populated with copyright notice and usage restrictions.
IPTC:SpecialInstructions contains the canonical FIF Protocol signature string.
The page embedding the image includes a schema.org/ImageObject block linking the image URL to the business entity.
All images on the same page carry identical business identity fields (GPS, copyright, creator).
Image reverse-search confirms it is not a stock photo or generic image used by multiple businesses.
Images uploaded to the Google Business Profile listing carry FIF Protocol metadata.
Metadata survives a download-and-re-upload cycle (confirms it is not stripped by the CMS).
The URL referenced in XMP:WebStatement returns HTTP 200 and contains a parseable schema.org/Organization block.
The FIF Protocol signature in IPTC:SpecialInstructions resolves to a live page (this page) confirming the protocol declaration.
Total: 85 points. Scores below 40 are not certified. Scores of 40–69 receive the Verified badge. Scores of 70–84 receive Verified+. Scores of 85–100 receive Verified Authority.
How to Implement the FIF Protocol
The following steps describe the manual implementation process using ExifTool or equivalent metadata writing software. LinkDaddy Media's Image Hardening service automates all seven steps.
Prepare your business identity data
Collect the exact values to embed: legal business name, website URL, GPS coordinates (latitude and longitude to 6 decimal places), copyright owner name, and the URL of a page containing your schema.org/Organization declaration. These values must be consistent across every image you harden.
Write EXIF GPS coordinates
Embed your business GPS coordinates into EXIF:GPSLatitude, EXIF:GPSLongitude, EXIF:GPSLatitudeRef, and EXIF:GPSLongitudeRef. Use decimal degrees format. The coordinates should match your registered business address to within 100 metres.
Write IPTC business identity fields
Populate IPTC:CopyrightNotice (e.g. '© 2026 Acme Plumbing LLC'), IPTC:Creator (your business name), IPTC:Caption-Abstract (a description referencing your business name and location), IPTC:Keywords (niche, city, state), IPTC:City, IPTC:Country, and IPTC:SpecialInstructions (the FIF Protocol signature).
Write XMP rights and web statement
Populate XMP:Rights (copyright notice), XMP:UsageTerms (usage restrictions), and XMP:WebStatement (the URL of your schema.org/Organization page). The web statement URL is the most important XMP field for entity verification — it creates a machine-readable link between the image and your business entity declaration.
Append the FIF Protocol signature
Set IPTC:SpecialInstructions to exactly: 'Forensic Identity Forged (FIF Protocol) | linkdaddymedia.com'. This signature links the image to this protocol declaration page and makes it citable by search engines and AI systems.
Add ImageObject schema to the embedding page
On every page that embeds a hardened image, add a schema.org/ImageObject block in a <script type='application/ld+json'> tag. The block should include the image URL, name, description, author (your Organization), and copyrightHolder. This creates a machine-readable link between the image URL and your business entity in the page's structured data.
Verify metadata persistence
Download the hardened image from your live website and run it through a metadata reader (ExifTool or a browser-based EXIF viewer). Confirm all three metadata layers (EXIF, IPTC, XMP) are present. If your CMS strips metadata on upload, configure it to preserve metadata or use a CDN that serves the original file.
Frequently Asked Questions
GET YOUR IMAGES FIF-HARDENED
Every plan includes full FIF Protocol compliance
EXIF, IPTC, XMP, protocol signature, and ImageObject schema — applied to every image in your plan, verified before delivery.
See plans and pricing →