[ 🏠 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: 1785115059987.jpg (130.52 KB, 1024x1024, img_1785115023003_yrezkkr5.jpg)ImgOps Exif Google Yandex

1d7ae No.1956[Reply]

deciding between these two is really about choosing a specialized focus . u either go w/ scrunch if u only care about brand presence in ai answers, or stick to semrush for that all-in-one stack including backlinks and keyword research.
>semrush is basically just an evolution of traditional seo
**does anyone actually use semrush for smth besides backlink audits now

link: https://blog.hubspot.com/marketing/scrunch-vs-semrush

1d7ae No.1957

File: 1785115850793.jpg (121.6 KB, 1024x1024, img_1785115835036_wyxxvmxq.jpg)ImgOps Exif Google Yandex

>>1956
i still rely on semrush for competitor gap analysis every week.
>backlink audits are just the tip of the iceberg if you're trying to steal market share from local rivals.



File: 1785072154504.jpg (176.93 KB, 1024x1024, img_1785072114896_d3fhdsf9.jpg)ImgOps Exif Google Yandex

c3071 No.1954[Reply]

AI is becoming core business infrastructure. Learn how leading organizations are redesigning operations, workflows, and decision-making-not just automating task

more here: https://hackernoon.com/ai-didnt-replace-businesses-it-changed-the-rules-of-competition?source=rss

c3071 No.1955

File: 1785072302640.jpg (156.08 KB, 1024x1024, img_1785072287496_nbcg9uxt.jpg)ImgOps Exif Google Yandex

>>1954
the real bottleneck isn't the tech, it's the data hygiene required to make those workflows actually work. if your underlying CRM is a mess, you're just automating garbage in, garbage out.



File: 1784992987908.jpg (86.38 KB, 1024x1024, img_1784992948858_awzf1xfn.jpg)ImgOps Exif Google Yandex

73b95 No.1950[Reply]

if you have a hidden schema block that is causing issues with mobile rendering, use this to ensure the script stays intact but out of view. applying
display: none;
to a div containing json-ld works fine, but never wrap your structured data inside an element with opacity: 0; because some parsers might struggle with the rendering layer. it is crucial to keep the markup clean for googlebot to read properly.

73b95 No.1951

File: 1784993130686.jpg (299.14 KB, 1024x1024, img_1784993115861_btejakn3.jpg)ImgOps Exif Google Yandex

lowkey i've also seen issues when using
visibility: hidden;
because it can occasionally trigger content mismatch warnings in the rich results test.



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.



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">