We instead of a per-engine storage record in {site_verify} we should store SVID, verification type (meta/file), associated engine (google/custom), and the data (meta tag, file name and contents, etc). In order to prevent duplicate entries, I might need to add a hash column that would store the MD5 hash of the meta tag or file name to prevent duplication.

Comments

Dave Reid’s picture

Dave Reid
he/him
Primary language English
Location Nebraska USA
CreditAttribution: Dave Reid commented

Or split these into different tables, {verification_file} and {verification_meta}. :/ Hmm.