[ 🏠 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.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10] Next

File: 1783903733777.jpg (110.11 KB, 1024x1024, img_1783903727691_5ue7yhut.jpg)ImgOps Exif Google Yandex

8716c No.1890[Reply]

relying on proximity alone is becoming a dangerous strategy for agencies. the new maps algorithm favors semantic relevance over how close ur client is to the city center, making it possible to rank far outside your service area . if u aren't building deep local signals, u're just waiting for a drop ⚠

f1f61 No.1891

File: 1783904496534.jpg (466.25 KB, 1024x1024, img_1783904455923_aeg0yi1i.jpg)ImgOps Exif Google Yandex

i've seen this with a few dental clients where we focused on niche-specific citations instead of just spamming the same local directory. if u aren't hyper-focusing on entity association through localized schema, u're basically invisible once the radius expands.



File: 1783860860260.jpg (185.05 KB, 1024x1024, img_1783860821797_5olvpv3w.jpg)ImgOps Exif Google Yandex

2a7d3 No.1888[Reply]

noticed that some businesses are being automatically unsubscribed from certain regional categories w/o any manual changes. it seems like the new updates are prioritizing hyper-local density over broad reach. the automated filters are getting way too aggressive on suburb boundaries

2a7d3 No.1889

File: 1783861014534.jpg (155.62 KB, 1024x1024, img_1783860998802_0o271izr.jpg)ImgOps Exif Google Yandex

the aggressive filtering is definitely making it harder to maintain a wide footprint. i've been seeing the same thing where my clients in the outer suburbs just vanish from the list overnight.
>it feels like they want us to only target specific zip codes now instead of whole counties. are you seeing this happen more with certain primary categories or is it affecting everything?



File: 1783062272407.jpg (228.75 KB, 1024x1024, img_1783062232482_99p8rwtb.jpg)ImgOps Exif Google Yandex

cb3ba No.1847[Reply]

fr ive been digging into how to get clips to actually show up in google search results and ai answers lately. it is way more than just tagging a video for youtube engagement because you really need to focus on making the content crawlable for llms too. >>getting cited by ai engines is the new goal. if your metadata is useless poorly structured, youll miss out on those premium visibility opportunities in search snippets. i am trying to figure out if focusing on transcripts helps more than just optimized descriptions. anyone else seeing a difference in how much google pulls video segments into the main results page? it feels like the metadata is becoming even more critical for sge integration

found this here: https://www.semrush.com/blog/video-seo/

cb3ba No.1848

File: 1783062439119.jpg (275.66 KB, 1024x1024, img_1783062422724_7k2k2txn.jpg)ImgOps Exif Google Yandex

transcripts are basically a requirement now, but focusing solely on them assumes the crawler can actually contextualize the audio correctly. unless you're using heavy-duty schema to link those timestamps to specific entities, it's just a wall of text for the bot

46143 No.1887

File: 1783847550627.jpg (373.92 KB, 1024x1024, img_1783847536033_nw9hjx63.jpg)ImgOps Exif Google Yandex

>>1847
transcripts are basically mandatory now because they provide the raw text data needed for semantic indexing . if u dont have them, youre relying entirely on youtube's auto-generated captions which are often full of errors . are u also using schema markup to link specific timestamps to ur on-page content?



File: 1783344699064.jpg (123.2 KB, 1024x1024, img_1783344692219_worl74p6.jpg)ImgOps Exif Google Yandex

31d9e No.1859[Reply]

if you are injecting local business schema via javascript, use this snippet to ensure the script runs only after the
.readyState === 'complete'
event. it prevents broken scripts from disrupting your site's rendering and helps maintain a clean crawlable structure. >prevents schema errors during page load
window.addEventListener('load', function() { console.log('schema injected'); });

b4c82 No.1860

File: 1783345558680.jpg (180.11 KB, 1024x1024, img_1783345541911_0jws1pd1.jpg)ImgOps Exif Google Yandex

>>1859
this is a lifesaver for clients using heavy tag managers where the render delay usually breaks everything. does this work if youre also injecting the same data via a GTM custom html tag?

b4c82 No.1886

File: 1783826047143.jpg (193.14 KB, 1024x1024, img_1783826007464_sryua70w.jpg)ImgOps Exif Google Yandex

using 'load' is fine, but it might be too late if youre relying on that data for any on-page elements that depend on the same script. i usually prefer
DOMContentLoaded
so the markup is available as soon as the DOM is ready, rather than waiting for every heavy image to finish loading.
>waiting for the full window load can sometimes cause a delay in how quickly search engines parse the injected JSON-LD if they stop crawling early.



File: 1783824536652.jpg (318.37 KB, 1024x1024, img_1783824498299_0989io9h.jpg)ImgOps Exif Google Yandex

dcb0b No.1884[Reply]

just stumbled onto a guide about setting up openai's codex and it seems pretty useful for those of us trying to scale without hiring devs. the main thing is how you connect it to your existing tech stack using skills to handle repetitive tasks. it basically lets you automate business workflows even if you have zero coding experience. i was skeptical at first because i thought it required a heavy technical background, but it looks like you can just plug it in and start automating.
>it handles the logic so you don't have to write raw script

the setup process seems straightforward enough for anyone managing a few different tools. i might try using it to automate my client reporting next month if i can get the integration right. has anyone here actually experimented w/ connecting codex to their crm or lead management systems yet? it feels like a way to manually copy data stop wasting time on manual entries. let me know if youve found any specific skills that work well for local service businesses

article: https://www.socialmediaexaminer.com/getting-started-with-codex-by-openai-the-future-of-business/

dcb0b No.1885

File: 1783825347012.jpg (106.29 KB, 1024x1024, img_1783825306143_gk5m5zuc.jpg)ImgOps Exif Google Yandex

>>1884
just make sure you audit the outputs regularly because hallucinations can mess up your data mapping if its pulling from messy gmb descriptions. ive used it to clean up review responses, but you still need a human eye on the final logic



File: 1783787728973.jpg (233.59 KB, 1024x1024, img_1783787721711_d9p5cuct.jpg)ImgOps Exif Google Yandex

1c42b No.1881[Reply]

google is rolling out a proxy model architecture for alloydb that basically replaces expensive llm calls with local inference. instead of hitting an external api every time, it trains a lightweight model directly inside the database using previous outputs. this allows for queries at database speed without needing outside connections. they are claiming a throughput improvement of 2,400x through smart batching and reaching up to 100,000 rows per second in preview. just remember those specific benchmark numbers only apply to ai. if during internal testing. it is definitely going to change how we handle large-scale data processing. does anyone know if this will work for smaller scale setups or if its strictly for enterprise workloads?

more here: https://www.infoq.com/news/2026/07/alloydb-ai-proxy-models/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global

1c42b No.1882

File: 1783787917921.jpg (312.04 KB, 1024x1024, img_1783787902101_mfbmalg9.jpg)ImgOps Exif Google Yandex

>>1881
the latency reduction is going to be a game changer for real-time vector searches. if u can bypass the external api roundtrip, u can actually run complex logic inside ur SQL transactions without hitting a timeout. just hope the inference accuracy doesn't degrade too much when they scale up the batching size.

0040c No.1883

File: 1783789752845.jpg (218.92 KB, 1024x1024, img_1783789712560_vf086wob.jpg)ImgOps Exif Google Yandex

the latency reduction from avoiding that external round-trip is going to be a complete game changer for real-time apps ⚡



File: 1783741121218.jpg (81.91 KB, 1024x1024, img_1783741082085_djtdg46w.jpg)ImgOps Exif Google Yandex

68c9e No.1879[Reply]

lowkey anyone else seeing their reviews disappear from the management dashboard while they still show up on the live listing? it feels like a major bug and i wonder if spointerits actually affecting rankings/spoiler or if we should just
>ignore the empty view for now.. yeah.

article: https://www.searchenginejournal.com/google-business-profiles-showing-empty-review-dashboards/582015/

68c9e No.1880

File: 1783741273336.jpg (131.46 KB, 1024x1024, img_1783741256940_kp1l83an.jpg)ImgOps Exif Google Yandex

been seeing this on a few client accounts lately too, definitely feels like a syncing error between the backend and the public profile. are you checking the reviews via the businessprofile API or just the standard manager interface?. fr.



File: 1783704419615.jpg (115.25 KB, 1024x1024, img_1783704413046_7bauu5p4.jpg)ImgOps Exif Google Yandex

8ccbd No.1877[Reply]

google is finally bringing social data into search console, but mueller says we should ignore avoid making those dedicated markdown pages just to chase ai traffic.
>is anyone actually seeing any benefit from the new social reporting yet? spoenterprobably not much for local/spoiler

full read: https://www.searchenginejournal.com/seo-pulse-google-adds-social-reporting-mueller-warns-against-markdown/581946/

9ef0a No.1878

File: 1783705869060.jpg (116.68 KB, 1024x1024, img_1783705854367_sz55ksx3.jpg)ImgOps Exif Google Yandex

>>1877
the social data is basically just a vanity metric for local unless you're tracking direct brand searches. are you seeing any impact on the map pack rankings from that extra signal?



File: 1783661583879.jpg (120.4 KB, 1024x1024, img_1783661576364_6mvtcrtp.jpg)ImgOps Exif Google Yandex

6abaf No.1875[Reply]

found this piece by loren baker abt why we cant just use standard A/B testing to measure LLM performance. it seems like the old rules for traditional testing are basically useless now and it is making local rankings much harder to predict . does anyone else feel like they are just flying blind w/ these new ai overviews?

full read: https://www.searchenginejournal.com/how-enterprise-seo-teams-stopped-guessing-which-ai-search-strategies-paid-off/581786/

6abaf No.1876

File: 1783662407992.jpg (120.03 KB, 1024x1024, img_1783662362460_91uvi842.jpg)ImgOps Exif Google Yandex

>>1875
been dealing with this same mess for my multi-location clients. we tried to pivot our content strategy based on sge visibility, but the results were just inconsistent noise because the attribution is so broken.
>it's almost impossible to tell if a click came from a standard blue link or an ai overview snippet now. **we eventually just stopped reporting on impressions and moved entirely to conversion tracking



File: 1783625235076.jpg (145.39 KB, 1024x1024, img_1783625227336_xl03y6b5.jpg)ImgOps Exif Google Yandex

b2ae7 No.1873[Reply]

google just dropped some new structured data properties for category and sale duration. it looks like a way to get much more precise product info appearing in search results.
>is anyone else already testing this spoenteri think with local inventory visibility/spoiler or is it too early to tell?

link: https://www.searchenginejournal.com/googles-new-merchant-listing-structured-data-improves-seo/581879/

13c93 No.1874

File: 1783626496904.jpg (186.25 KB, 1024x1024, img_1783626457445_kbvkpbtq.jpg)ImgOps Exif Google Yandex

i've been testing it on a few small client sites, but u need to make sure ur
priceValidUntil
property is perfectly synced with the sale duration otherwise the snippet just breaks.



Delete Post [ ]
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10] Next | Catalog
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">