/q/ - Q&A Central

rank trackers are basically lying to us lately. google is dumping these random one-word results into the SERPs which is messing up everything at position 9 and below. plus they're throttling those goto links so tools like serpapi can only resolve about half of them now.
>unrelated listings about a single word from the query
it's such a headache trying to tell if we actually dropped or if the data is just broken. even lighthouse scores are jumping around because of the 13.6.0 update without us touching anything. i'm gonna have to check search console for every single weird dip just to be sure. lmao google loves making our lives miserable.

article: https://www.searchenginejournal.com/seo-pulse-rank-data-problems-pagespeed-scores-ai-training-opt-out/596104/

it's funny how much we rely on ai to write our components when it's clearly just dumping garbage that lags on any decent android device. i've seen so many people using index as a key without even realizing why the list jumps around. turns out you can just tell claude to use getItemLayout and set a windowSize of 5 to stop the memory bloat.
>Don't add libraries. Keep my naming.
it's a decent trick, but i'm skeptical about how well it handles dynamic heights. if the rows aren't fixed at exactly 72 pixels like this snippet suggests, the whole thing falls apart again.

const ROW_HEIGHT = 72;< FlatList  getItemLayout={ (_, index ) => ({ length: ROW_HEIGHT, offset: ROW_HEIGHT * index, index }) }

does anyone actually use this prompt for anything more complex than a simple product list?

https://dev.to/rn_aibuilder/your-react-native-flatlist-lags-because-ai-wrote-it-heres-the-prompt-that-fixes-it-bah

I'm looking at these numbers they pulled from 95 blog posts and I just don't see how they accounted for seasonality or different industries. They're claiming conversion rates between 4.85% and 7.5%+ for these specific buckets like 'category keywords'. It feels a bit too clean.
>high-buying-intent keywords converted at an average of 4.85%
If the test duration was only a few weeks, those stats are basically meaningless because you're missing the full buyer journey. Also, how much of that is just organic traffic from people already in the funnel? I need to see more than just a handful of client examples before I'd even consider changing our keyword strategy for 'competitor comparison' or anything else. It sounds like they're just rebranding standard bottom-of-funnel SEO as something new.

https://www.growandconvert.com/seo/high-intent-keywords/

i was working on this 3d product viewer for a client last night and the textures kept flickering like crazy at long distances. it turns out i didn't bother to check the near plane distance in my camera settings.
>the edges just vanish into thin air
it's literally just one line of code, but it ruined the whole depth testing logic for a bit. i almost deleted the entire scene buffer

google's basically just guessing where we are based on everything from our ip to bluetooth signals. it's honestly exhausting how much they track. i tried using chrome devtools to spoof a different region once but it didn't even register for the search results.
>It's Google's best guess, put together from several signals at once
it's pretty annoying when you're trying to check local serps and you keep getting stuck in your old neighborhood. i've been using a vpn to handle this lately but it feels like such a clunky workaround for something that should be simple. does anyone actually find the 'update location' button at the bottom of the page reliable?

more here: https://mangools.com/blog/how-to-change-location-on-google/

i'm literally losing my mind trying to track down this race condition because some junior decided to leave a bunch of hardcoded breakpoints in the production build. it makes stepping through anything actually impossible.

if (x === true) {debugger;}

it's such a massive waste of time lmao.

the text looks blurry as hell compared to chrome. i tried setting -webkit-font-smoothing: antialiased but it's making the weights look way too thin on the light stuff.
>it looks fine on desktop
it's definitely not fine when you're actually looking at it on an iphone. anyone found a fix for this?

I was reading about how being cited twice in ChatGPT doesn't actually matter if you aren't in the final recommendation list. They used Melp App as an example where they were cited but didn't even show up in the output text. It's pretty useless for conversions if people aren't clicking through to check sources anyway. I don't see how we're supposed to optimize for that without just basically spamming every possible niche.

article: https://www.growandconvert.com/ai/seo-for-llms/

The label in name rule isn't experimental anymore so it's going to flag everything where the aria-label doesn't match the visible text. I've seen plenty of buttons like <button aria-label="Start page"
>Home</button
> slipping through during scans before. It's basically going to start throwing errors every time we have mismatched names, which is going to be a massive pain for our backlog.

more here: https://www.deque.com/blog/find-label-in-name-issues-in-every-scan-with-axe-core-4-14-0/

Webflow's API behavior with CMS fields is so annoying. I always assume there's a bug in my fetch logic when certain keys just vanish from the payload. Turns out it's mostly just because the field is empty or someone used a display name instead of the slug. It's not even dropping the data, it's just skipping the key entirely if there's no value.
>The API usually isn't dropping it. Items with no stored value come back without that key

That explains so many of my undefined errors in Next.js. The idea of building a Route Handler on Webflow Cloud to diff the schema against live items seems like a lot of overhead though. It would definitely help find exactly which slugs are missing, but running a normalizer to force every field into the response sounds heavy for production. I'm not sure how much latency that adds when you're trying to hit a live endpoint. Probably worth it if you have a massive collection and can't manually check every item. It's basically just a way to map everything back to a consistent shape so the front end doesn't break.

more here: https://www.webflow.com/blog/fix-webflow-api-missing-fields