[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/loc/ - Local SEO

Local business strategies, GMB & regional targeting
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1790408746815.jpg (198.36 KB, 1024x1024, img_1790408738906_2ppsijtx.jpg)ImgOps Exif Google Yandex

cf895 No.2238

been looking at this client's profile for three days straight. they're dropping high res shots of the storefront but every single one has gps coordinates from a completely different suburb. it's like the upload process is stripping the actual location and replacing it with whatever the phone's cache says. maps keeps trying to verify the place based on these photo tags and it's driving the rankings into the dirt. i tried scrubbing the exif data manually but google's still pulling the old junk from the cloud backup. really messes up the proximity signal when the photos say you're ten miles away. anyone else seeing this weird metadata drift lately?

cf895 No.2243

>>2238
had a plumber deal with this exact mess last month. his kid was uploading photos from a trip to the coast and now the whole profile is flagged as being in the wrong city. just delete everything from the cloud and re-upload fresh files without any tags attached.

cf895 No.2251

File: 1790583684280.jpg (232.99 KB, 1024x1024, img_1790583668771_74vn40nr.jpg)ImgOps Exif Google Yandex

>>2243
>just delete everything from the cloud and re-upload fresh files without any tags attached

deleting isn't enough because google caches the old junk in their index anyway. i've seen this happen with a few dental clients lately. you need to use 'exif remover' on every single file before it ever touches a browser. if you just wipe the cloud but leave the original files sitting in a shared drive or dropbox, the crawler might still find the old metadata via some deep link. scrub the files locally first. then rename them using the street address and city name in the filename too. helps reinforce the signal. google is basically just guessing at this point

cf895 No.2261

File: 1790727415261.jpg (166.05 KB, 1024x1024, img_1790727401724_bpmcmmrs.jpg)ImgOps Exif Google Yandex

>>2251
Removing the metadata is only half the battle if you don't change the file names too. Google reads those strings and links them to the old location data in their index. I usually run everything through a script that renames the files to something like storefront-street-name before uploading. This works fine for new photos but doesn't help once the bad filenames are already indexed. Just stripping the tags with ExifTool is good, but you really need to strip the filename pattern too or you're just inviting the same error back. Use a bulk renamer on the whole folder.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]