I don't see how my reply is rude. I told you the truth about the approach you're using and suggested better alternatives. I also never said what you're doing is "dumb". That's something you said yourself. I simply said it is the least reliable way to automate stuff. And that's true. It is. Perfectly fine that you didn't know that. Now you do, and hopefully will try to avoid using OCR when alternatives are available from now on.
Now, you can use Extract data from web page if you have several results in the page, or Get details of element in web page if there's only one element in the page and you want to verify the result. The samples you provided lead to only a single search result in all cases, so you might as well use Get details of element in web page and capture the element. Should work fine.
If you want to click on the item, you can also build a custom selector for the UI element you want to click on. I've right-clicked on the element and selected "Inspect" to view it in the developer tools of my browser (Chrome in my case) and here's what the element looks like:
It actually has the text there, and this could be used in the selector. When I captured the element to click on, it actually automatically captured the text:
You can then edit the selector and pass in a variable there for the text. If you use that in a Press button in web page action, it will press on the item with the address you're looking for.
I've tested and verified it to work.
-------------------------------------------------------------------------
If I have answered your question, please mark it as the preferred solution. If you like my response, please give it a Thumbs Up.
I also provide paid consultancy and development services using Power Automate. If you're interested, DM me and we can discuss it.
