Navigate by heading broken on Google in Mac OS Ventura 13.5.1

I’m not on the Mac beta so can’t help here.
However, while it’s fine to check with others here, I would advise against waiting for others’ verification to log the bug. There could be differences with your configuration that cause the issue for you but not someone else, but it’s still a bug for your configuration so should be logged.
Many thanks,
Dave

What I've noticed is that it's any object navigation forward after using heading nav: after landing, moving up by heading or anything else works, but moving forward is trapped, regardless of rotor setting. But, with quickNav turned on, h weirdly appears to still work. I just switched my search engine away from Google Search and problem seems to be solved. Not doing it on Bing or Duck Duck Go in my brief test. Was just about to throw my Mac out the window (without opening the window first). Still plenty of reasons to do that, of course, so I'm keeping my options open.

I'm having the same problem today and reported it to Apple a few minutes ago. You indicated OSX 13.5.1, but the version I installed today is 13.5.2.

I hope they solve this issue before the release of OSX 14 because it is really annoying. Another thing that I noticed with this update is that the issue with the "Safari not Responding" message, which was almost solved in my Mac, now it is really annoying again.

with quick nav turned on, go to a webpage with a lot of images. hit G to move to the next one, and your stuck. unless you do Shift+G witch goes the other way around.

This is not a Safari issue but rather, as others have mentioned, an issue with Google Search specifically as it only began happening (at least for me) within the last 48 hours, and I am running the latest macOS Sonoma beta instead of Ventura or other releases. The same issue occurs in Google Chrome and other browsers on macOS as well. Hopefully Google will revert the change that is causing this problem.

First they screw up YT now this? I thought it was me, until I realized I didn't have an adult beverate at my elbow, in other words, I was about to write I had an issue when others have it also. google, the hell? Oh since i'm on the topic, here's how to work around YT. First, type your quary into the search bar. After that, turn down the volume, wait probably half a minute or more. Turn it up, navigate to the search filter vO space. Then navigate by heading, press four. You can then go right to find upload date. Hope that helped.

I just noticed this problem as well. Like others have said, this seems to only a problem with Google. I find that the Headings get stuck whether I am using Quick Nav or not. I get around this by using the Headings rotor to navigate.
Hope this gets fixed soon.

Also other Google products such as Google Books and Google Scholar they are all presenting the same behavior. Now we have to struggle with a new bug for years to come.

Disabling JavaScript solves the problem for me, at least on Search (haven't tried other Google products). If you don't have the Developer menu turned on, do that in Safari settings, then the Developer pull-down has the JavaScript option. I went into system settings and assigned the cmd+j shortcut to toggle it on and off. AFAIK, the option is buried deeper in the Google Chrome settings.
Added bonus: turning off javascript takes away a lot of annoying crap. The shortcut brings the functionality back when needed.
This has happened with Google before, as I recall. They fixed it fairly quickly (or Apple did in the next update--I don't remember).

Thanks. I disabled Java Script, and the problem is solved. It even solved the second problem I noticed that eevery every time I clicked on a link of the Google search results, I was getting the "Safari is not responding" message.

That is, unless you want a lot of other things to break, things that you weren't expecting. For the uninitiated, JavaScript powers much of the web, and in this case much of Google, and hinders many a website once it's disabled. If you ever wondered why this option was in a developer-focused menu of all places, then perhaps this is why. It's meant primarily for developers testing their web applications to ensure a graceful fallback is available should JavaScript for some reason be unavailable during an end user's browsing session.

This is back to working as expected for me today.

Hopefully it's the same for others too.

You can phone google there and talk to someone.

I'm on windows and probably always will be, yes it has some issues but not like this.