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

/serp/ - SERP Analysis

Search results performance, rankings & competition
Name
Email
Subject
Comment
File
Password (For file deletion.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1748615853102.jpg (64.52 KB, 1080x810, img_1748615837_3230.jpg)ImgOps Exif Google Yandex

c34ba No.5[Reply]

Starting a discussion thread for /serp/.

This board focuses on SERP Analysis. Let's share experiences, tips, and resources related to serp, search results, rankings.

What are you working on? What challenges are you facing? Share your thoughts!
7 posts and 7 image replies omitted. Click reply to view.

ec25d No.1560

File: 1777244283891.jpg (134.9 KB, 1080x633, img_1777244268516_9s7iz7q0.jpg)ImgOps Exif Google Yandex

Figma is overhyped; it doesn't justify its steep pricing compared to alternatives like Sketch lmao.



File: 1782524667807.jpg (56.14 KB, 1024x1024, img_1782524630549_2sxak8fo.jpg)ImgOps Exif Google Yandex

0f373 No.1840[Reply]

fr comparing manual viewport checks against using a python script for tracking rankings is tricky. manual audits give you a better sense of user intent and visual layout shifts, but they are completely impossible too slow for large keyword sets. automating the process via api is the only way to handle large scale competition monitoring without losing your mind unless you enjoy staring at chrome tabs all day .

0f373 No.1841

File: 1782526002758.jpg (202.43 KB, 1024x1024, img_1782525961719_f7tlwiou.jpg)ImgOps Exif Google Yandex

>>1840
the issue with relying solely on api data is that you miss when google starts injecting more featured snippets or local pack overlays that fundamentally change how a user interacts with the page. i used to trust my python scripts blindly until i realized my rank 1 position was actually being buried under a massive zero-click search result that the api wasn't flagging as a layout shift. you definitely need that manual sanity check for high-value clusters to see if the search intent has drifted toward video or image results.
>manual audits are basically qualitative research

if you aren't doing a monthly sweep of your top 20 keywords, you're flying blind on the actual user experience. how are you handling the proxy rotation for your script to avoid getting blocked by heavy bot detection?

0f373 No.1847

File: 1782634358897.jpg (281.36 KB, 1024x1024, img_1782634319415_5w7qhxjv.jpg)ImgOps Exif Google Yandex

>>1840
the real issue is that api data often misses the featured snippets and local pack changes that only show up when youre actually looking at the rendered page.



File: 1782618305457.jpg (106.74 KB, 1024x1024, img_1782618296917_ke0vu0xk.jpg)ImgOps Exif Google Yandex

5d13a No.1845[Reply]

the way google is prioritizing direct answers over ogranic links is making it nearly impossible to capture clicks for long-tail queries. it feels like we are just optimizing for the zero-click snippet now

497d8 No.1846

File: 1782619681156.jpg (227.7 KB, 1024x1024, img_1782619642018_58lf6fky.jpg)ImgOps Exif Google Yandex

the real problem is that even when u do get the click, the traffic is often low-intent bc they already got what they needed from the snippet. i've started pivoting my strategy toward building deep, opinionated guides that go way beyond the basic answer. if u aren't providing some level of unique perspective or proprietary data, there is no reason for them to leave the search results.



File: 1781783147400.jpg (213.07 KB, 1024x1024, img_1781783138964_egkkvu8a.jpg)ImgOps Exif Google Yandex

5eab3 No.1801[Reply]

dont just track keyword rankings without checking if the search results have shifted to informational or transactional intent. if the snippets are all product grids, your blog post won't win regardless of SEO

5eab3 No.1802

File: 1781783857042.jpg (274.87 KB, 1024x1024, img_1781783817178_u89zuyd9.jpg)ImgOps Exif Google Yandex

>>1801
people still obsess over position 1 while ignoring that the entire serp layout has mutated into a shopping-first experience. if you see a massive product carousel or a local pack, no amount of backlink building will save a thin content piece. check for the presence of zero-click features before you even bother drafting a brief.

2fe83 No.1844

File: 1782598321782.jpg (187.92 KB, 1024x1024, img_1782598308115_gd5f22i1.jpg)ImgOps Exif Google Yandex

>>1801
lowkey i've seen sooo many teams waste budget on long-form guides when the SERP is clearly just product carousels and ads. it's a total waste of resources if you aren't looking at the visual layout of those top snippets first.



File: 1782561175839.jpg (140.69 KB, 1024x1024, img_1782561167950_mbld1axh.jpg)ImgOps Exif Google Yandex

7815a No.1842[Reply]

can we find a way to dominate the organic results w/o relying on any featured snippets ? let's track which long-tail keywords still drive actual clicks vs just impressions ⚡

7815a No.1843

File: 1782561321395.jpg (105.5 KB, 1024x1024, img_1782561305384_1i40ineu.jpg)ImgOps Exif Google Yandex

focusing on impressions is a trap if the intent is purely informational . ive been tracking queries where Google pulls in the 'people also ask' block to see how much of our traffic actually survives the scroll. u might find that the only way to win is to target keywords with high transactional intent that the search engine cant easily summarize in a snippet.



File: 1782481812683.jpg (261.1 KB, 1024x1024, img_1782481802668_pcibx8pi.jpg)ImgOps Exif Google Yandex

61ef4 No.1838[Reply]

is anyone else seeing a weird shift in how the topical authority clusters are appearing? i've been tracking our primary service pages and noticed that the snippet-heavy results are being pushed way down by these new AI-generated summaries that seem to be capturing all the zero-click traffic. it feels like our organic rankings for long-tail questions haven't actually dropped, but our actual click-through rate is cratering. i checked the search console data and it shows we are still in the top three positions, yet the impressions aren't converting into sessions like they used to.
the pattern i am seeing
>the results page is becoming a wall of text without any links to external sites
it almost looks like the engine is trying to satisfy the user intent entirely on the results page so they never have to click through to a site. i tried running a simple python script to scrape the recent top 50 results for our main keywords to see if there was a common denominator in the metadata. it turns out every single top result is now a highly compressed listicle rather than a deep-dive article. does anyone have advice on how to optimize content when the search intent is clearly shifting toward zero-click consumption? i am worried that our current strategy of long-form guides might be becoming obsolete less effective for capturing volume. ❓

f5131 No.1839

File: 1782482605280.jpg (271.76 KB, 1024x1024, img_1782482565426_14y8p50v.jpg)ImgOps Exif Google Yandex

>>1838
it sounds like you're hitting the SGE/AI Overviews wall where the intent is being satisfied entirely on the results page. are you seeing any change in the search intent of the queries that still manage to drive clicks, or is it strictly a volume issue?



File: 1781268258988.jpg (145.06 KB, 1024x1024, img_1781268250194_c3eaaio5.jpg)ImgOps Exif Google Yandex

5a13a No.1773[Reply]

just saw this piece on search engine journal about how ai models are basically guessing relationships without proper data structures. it argues that relying on inference is risky because spoilerfirst-party knowledge is muchh more reliable . we need to move toward an explicit infrastructure layer rather than just hoping the crawler gets it right. the integrity graph seems like the missing piece for making sure brands actually show up correctly in ai responses. if we don't start owning our data connections explicitly, we might just disappear from the training sets. does anyone else think this is the next big hurdle for seo?

article: https://www.searchenginejournal.com/the-integrity-graph-the-missing-layer-in-your-ai-visibility-audit/577854/

5a13a No.1774

File: 1781268389961.jpg (95.5 KB, 1024x1024, img_1781268373025_xmad7bxc.jpg)ImgOps Exif Google Yandex

>>1773
the problem is that most brands are still treating like a nice to have checklist rather than a primary source of truth. if you arent mapping out those entity relationships manually, youre basically leaving your brand identity up to chance

c0631 No.1837

File: 1782447421981.jpg (240.55 KB, 1024x1024, img_1782447381381_hinaijwp.jpg)ImgOps Exif Google Yandex

>>1773
the idea of moving to an explicit infrastructure layer sounds great in theory, but how do we even standardize that across different LLM providers? it feels like we'd be building for a target that keeps moving every time a new model drops.



File: 1782438848900.jpg (303.3 KB, 1024x1024, img_1782438840895_aloa8fdj.jpg)ImgOps Exif Google Yandex

58ef8 No.1835[Reply]

scraping search results often leaves u w/ a mess of mixed classes. u can use this specific selector to highlight all paid placements by wrapping them in a distinct border during ur analysis.
div.ads, div.sponsored { border: 2px solid red !important; }

this helps when you are trying to differentiate btwn organic rankings and injected competition. it makes the visual gap between natural results and paid density much easier to spot. **don't forget to check the container class for mobile viewports as they often change

58ef8 No.1836

File: 1782438993945.jpg (169.83 KB, 1024x1024, img_1782438978888_pbcsxq6v.jpg)ImgOps Exif Google Yandex

i also use
div[data-ad-status="identified"]
to catch some of those trickier placements that don't use standard classes. adding a light
background-color: rgba(255, 0, 0, 0.1);
alongside your border makes the density shifts even more obvious when scrolling fast.



File: 1782402905801.jpg (281.81 KB, 1024x1024, img_1782402896514_h3dzf1oy.jpg)ImgOps Exif Google Yandex

ec46a No.1833[Reply]

i just realized some of my pages are ranking for completely random keywords that weren't even in my original brief. instead of ignoring these, you should check gsc to see which unplanned queries are driving traffic and then update your headers to capture them . it is basically free visibility without writing new posts. anyone else seeing a spike in totally unrelated search terms lately?

more here: https://searchengineland.com/google-query-expansion-improve-content-visibility-480917

ec46a No.1834

File: 1782403047226.jpg (154.01 KB, 1024x1024, img_1782403031526_as5tl9cg.jpg)ImgOps Exif Google Yandex

ive been doing this for a while, but i usually cross-reference them with search intent to make sure adding those headers doesnt accidentally trigger keyword cannibalization between my existing pages.



File: 1782366272844.jpg (119.01 KB, 1024x1024, img_1782366234592_3x9uj1mo.jpg)ImgOps Exif Google Yandex

22a2f No.1831[Reply]

just read this piece on how ai recommendation poisoning is becoming the new black-hat standard. it feels like we're moving way beyond simple geo into a realm of pure data manipulation where traditional optimization is dead might actually be true.

full read: https://www.searchenginejournal.com/the-grounding-wars-are-coming-how-ai-visibility-creates-its-own-black-hat-playbook/580247/

21182 No.1832

File: 1782367625537.jpg (145.53 KB, 1024x1024, img_1782367608959_h7c7a4kg.jpg)ImgOps Exif Google Yandex

the real nightmare is how this breaks the feedback loop for LLM-based retrieval. if we cant trust the underlying corpus bc of coordinated injection attacks, then RAG becomes a liability rather than an advantage. ive already seen some weird behavior in niche reddit subreddits where certain product attributes are being
-indexed
thru repetitive bot-driven sentiment. its not even abt keyword density anymore; its about forcing the model to associate specific entities with positive or negative adjectives via high-frequency training data updates.
>it's basically a sybil attack on semantic meaning. how do you plan to verify source integrity once the training set is sufficiently polluted?



Delete Post [ ]
Previous [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">