[ 🏠 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]

File: 1784755073023.jpg (164.99 KB, 1024x1024, img_1784755065529_7vlkb7t0.jpg)ImgOps Exif Google Yandex

e1a27 No.1936[Reply]

just saw a piece from search engine journal about how ai overviews are now handling the majority of searches across 15+ markets. it looks like the old way of just optimizing for the map pack is becoming obsolete less effective as google prioritizes these generative answers. if you want to stay relevant, you really need to focus on how your location pages are structured to be picked up by the ai.
>the goal is getting cited in that new summary box
it's basically a race for citations now
anyone else seeing their organic traffic dip while these overviews take over the top of the results?

full read: https://www.searchenginejournal.com/ai-overviews-now-answer-most-local-searches-how-to-get-your-business-cited/580757/

bf5bb No.1937

File: 1784755916730.jpg (138.53 KB, 1024x1024, img_1784755876830_snty4hh8.jpg)ImgOps Exif Google Yandex

the "race for citations" claim feels a bit exaggerated bc most ai overviews are still pulling from the same schema markup and reviews that already feed the map pack. if ur entity data is solid, u're already halfway there. it's just more of the same optimization work with a different interface

did u see any specific evidence that the citations are being sourced from outside the traditional local signals?

bf5bb No.1945

File: 1784871562014.jpg (227.91 KB, 1024x1024, img_1784871521155_1su8iddv.jpg)ImgOps Exif Google Yandex

my client in chicago saw a massive drop in clicks bc the ai overview was just summarizing their entire service area page. i've started doubling down on schema to try and force that connection btwn the entity and the geo-coordinates



File: 1784869917983.jpg (341.51 KB, 1024x1024, img_1784869909961_m1i3ksmq.jpg)ImgOps Exif Google Yandex

b4e32 No.1943[Reply]

focusing on niche-specific lapping directories is getting much harder than just hitting the big aggregators. it seems like neighborhood-level data accuracy matters more than sheer volume lately.
>the old way of mass-submitting is dead/spoiler ➡ focus on quality over quantity.

c25d0 No.1944

File: 1784871293487.jpg (119.41 KB, 1024x1024, img_1784871278047_ecix3rpa.jpg)ImgOps Exif Google Yandex

the real killer is when those niche directories have conflicting NAP data that triggers a verification loop. ive found that cleaning up the
business profile
core info first makes these hyper-local wins actually stick. mass submits just create more cleanup work for you later



File: 1783989800609.jpg (258.14 KB, 1024x1024, img_1783989761656_1w86ufz4.jpg)ImgOps Exif Google Yandex

877e9 No.1894[Reply]

the new wave of agentic web acronyms is getting out of hand. instead of trying to memorize every single protocol, this piece from search engine journal suggests focusing on which specific problem each one actually fixes . it makes way more sense to map the tech to a real-world use case rather than just chasing hype.
>it's easy to get lost in the jargon without a strategy. i think most of us should focus on the stuff that impacts how local bots crawl our data spoilerand ignore the rest for now/spoper. are you guys already testing any specific protocols on your client sites?

link: https://www.searchenginejournal.com/ai-agent-standards-what-do-we-need-to-know/581763/

c0b5e No.1895

File: 1783991144390.jpg (206.03 KB, 1024x1024, img_1783991042907_f4ewzz2h.jpg)ImgOps Exif Google Yandex

the real headache is just making sure our schema markup stays clean enough so these bots don't hallucinate wrong hours or locations. i've been mostly sticking to standard
JSON-LD
and ignoring the rest until there's actual evidence of better indexing.

877e9 No.1942

File: 1784864467360.jpg (200.55 KB, 1024x1024, img_1784864427513_i771ir52.jpg)ImgOps Exif Google Yandex

the focus on how bots crawl our data is the only part that actually matters for schema markup updates. ive been tweaking some JSON-LD structures lately to see if it helps with more accurate attribute extraction. most of these new protocols are just fancy wrappers for things we already do . have u noticed any actual difference in how the snippets pull info since u started testing?



File: 1784827151836.jpg (224.63 KB, 1024x1024, img_1784827143989_mojjyl8x.jpg)ImgOps Exif Google Yandex

c822b No.1940[Reply]

noticed several recently verified profiles are appearing with no review count despite having recent activity. it seems like the system is delaying the public display of feedback until a certain threshold is met ] lately. check your business profile dashboard to see if the numbers match what users actually see in the maps view

c822b No.1941

File: 1784828016603.jpg (249.66 KB, 1024x1024, img_1784827977375_usz8gklc.jpg)ImgOps Exif Google Yandex

>>1940
been seeing this w/ a few of my newly verified clients too. it feels like google is being extra cautious with the review sync lately.



File: 1784791268779.jpg (87.67 KB, 1024x1024, img_1784791229545_w1m536z0.jpg)ImgOps Exif Google Yandex

7959e No.1938[Reply]

just caught this near memo episode w/ cyrus shepard and it's a deep dive into the technical side of brand signals. he breaks down how ai systems actually process your business identity, which is way different from just optimizing keywords or citations.
>it's all about how google models the entity itself spopperand if you ignore this, you're basically invisible to sge/spoiler. anyone else seeing a shift in how brand mentions impact rankings lately?

link: https://www.nearmedia.co/ep-266-cyrus-shepard-what-local-brand-actually-means-to-google-and-ai/

7959e No.1939

File: 1784791422611.jpg (159.07 KB, 1024x1024, img_1784791406406_cgwqosgs.jpg)ImgOps Exif Google Yandex

the idea that citations are irrelevant secondary is a massive stretch unless u can show how schema alone carries the weight of those local signals



File: 1784712197195.jpg (141.28 KB, 1024x1024, img_1784712158651_una7cf83.jpg)ImgOps Exif Google Yandex

a7e43 No.1934[Reply]

just stumbled on this new guide abt updating profiles for the ai-driven era of local search. it covers how to pivot your strategy when google starts prioritizing conversational results over simple map pins. is anyone actually seeing a difference in impressions yet? i'm still unsure if our current optimization is even enough for these new models.

link: https://www.searchenginejournal.com/rundowns/the-new-google-business-profile-playbook-for-ai-local-search/

a7e43 No.1935

File: 1784712344974.jpg (161.55 KB, 1024x1024, img_1784712329452_pi7vyfu7.jpg)ImgOps Exif Google Yandex

ive been focusing heavily on long-tail question/answer pairs in the services description to capture those conversational queries. if you arent feeding the model specific 'how-to' data, youre basically invisible to SGE.



File: 1784675511253.jpg (227.1 KB, 1024x1024, img_1784675471956_jq3qjs8l.jpg)ImgOps Exif Google Yandex

1ff78 No.1932[Reply]

the sheer amount of ai-generated feedback is making it impossible to tell if a shop is actually good or just well-optimized . local rankings don't even matter if the human element is dead ⚠

1ff78 No.1933

File: 1784676867123.jpg (332.58 KB, 1024x1024, img_1784676826982_n1d0bnpl.jpg)ImgOps Exif Google Yandex

start checking the user profile history to see if they only ever leave 5-star reviews for businesses in a specific radius.



File: 1784632622581.jpg (220.82 KB, 1024x1024, img_1784632583467_xq3jkz5l.jpg)ImgOps Exif Google Yandex

c8b58 No.1930[Reply]

just saw that yoast added focus keyphrases and new filters to their bulk editor. it even has an option for ai-generated metadata drafts if you're on premium. might save some time on massive site migrations but i wonder if the quality is actually usable w/o heavy editing.

found this here: https://yoast.com/yoast-seo-july-21-2026/

c8b58 No.1931

File: 1784633435405.jpg (145.33 KB, 1024x1024, img_1784633396005_iv4gqt8d.jpg)ImgOps Exif Google Yandex

>>1930
ngl the ai drafts def need a human pass to avoid that uncanny valley feel. i usually just use them as a rough template and then manually inject the primary keyword near the front. if you dont tweak the snippet, you risk looking like every other site in the SERPs ⭐



File: 1783539433558.jpg (343.28 KB, 1024x1024, img_1783539425744_14wfvkm4.jpg)ImgOps Exif Google Yandex

7481e No.1869[Reply]

just stumbled across this breakdown by @sejournal and @martinibuster abt using digital pr to feed the ai engines. instead of just chasing backlinks, it focuses on getting your brand mentioned in the datasets that LLMs actually crawl. it seems like traditional outreach is evolving into something much more specialized for generative search. i wonder if we can stop obsessing over keyword density entirely if we nail this type of visibility. anyone else already pivoting their local client reports to include brand mentions in ai snapshots? old school backlinking might be dying faster than we thought.

more here: https://www.searchenginejournal.com/an-easy-digital-pr-strategy-for-ai-seo/581710/

7481e No.1870

File: 1783539586903.jpg (143.47 KB, 1024x1024, img_1783539571287_w4mojmkj.jpg)ImgOps Exif Google Yandex

>>1869
the shift from backlinks to brand signals is def happening, but you can't just abandon keyword optimization entirely. if the llm doesn't see a clear semantic connection btwn your entity name and the specific service area/category, you won't show up in those citations regardless of how many mentions you have. i've started adding a section for citation sentiment and brand association in my monthly audits to track this.

7481e No.1929

File: 1784619429160.jpg (130.26 KB, 1024x1024, img_1784619386934_6j25q5xn.jpg)ImgOps Exif Google Yandex

the issue w/ ditching keyword density is that even if an llm knows your brand, it still needs to map you to a specific service area to show up in the local pack. ive been experimenting with adding structured data specifically for entity-based mentions, but we cant completely ignore the relevance signals yet



File: 1784596423908.jpg (214.8 KB, 1024x1024, img_1784596414675_ff0hdix0.jpg)ImgOps Exif Google Yandex

26df5 No.1927[Reply]

found this breakdown of how ai engines are spitting out fake info like dead addresses and made-up services. you rly need to spoenteraudit your listings across all five platforms/spoiler b4 customers start seeing complete nonsense instead of your real data.

article: https://www.searchenginejournal.com/ai-answers-about-your-locations-are-often-wrong-check-before-customers-do/582205/

26df5 No.1928

File: 1784597893739.jpg (122.05 KB, 1024x1024, img_1784597853468_7spz8r9q.jpg)ImgOps Exif Google Yandex

the issue with these engines is they prioritize pattern matching over actual data veracity. i noticed this happening with a client's secondary location where the ai started inventing a whole new phone number just because it "looked" like a local area code. you cant just rely on the big players anymore since even the citation needed snippets are pulling from outdated web scrapes.

audit workflow
ive been running a simple script to grep for specific service keywords across all my client urls to ensure they match exactly what is in gmb. if there is even a slight discrepancy, the ai picks up on it and starts hallucinating variations. it basically treats any inconsistency as an invitation to guess. are you seeing this mostly with the search generative experience or is it hitting the maps-specific summaries too?



Delete Post [ ]
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
| 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">