metatag | plugin allows you to automatically provide | Meta Tags library

If there is a proper mock for the pageDbService.data$. the code bellow should be enough:

Instead use the following to add an opengraph meta tag with the product sku on single products:

If I understood your problem correctly, you can't retrieve the value selected in the select "time"?

If this is the case it is because you forgot to indicate values to the options.

See the code below {VALUE_HERE}

OK, I solved it.

The issue was with one of the components named MetaTags:

MetaTags.jsx

Your label in the facet should be mode="BOOST" if you want to restrict to a structured data field within the scope of your engine.

I don't think you can parse a json with comments by using dict() function or by using json lib, i would recommend using a third party json parse lib, you can find tons of them online and im not sure 100% about the __jp0(); if you can parse it if you removed the comment i.e the __jp0(JSON);

If a page refresh makes an API call, then that API call is accounted for quota usage.

Now, you say that your page refreshes at a rate of one Video.list API endpoint call per minute.

Therefore, during a full day (24 hours), you'll have 24 * 60 = 1440 calls to Videos.list.

According to the official specification of Videos.list, each call to this endpoint has a quota cost of 1 unit.

Consequently, if only accounting for 1440 calls to Videos.list, the quota cost of your page refreshing amounts to 1440 units. That's well below the allocated daily quota of 10000 units.

This implies also that the API will by no means consider you a spammer.

All good, this seems to do what is needed:

Since you didn't post any code I can only give general advice.

1. Look if there's a hidden API that retrieves the data you're looking for. Load the page in Chrome. Inspect with F12 and look under Network tab. Click CTRL + F and you can search for the text you see on screen which you want to collect. If you find any file under the Network tab that contains the data as json, that is more reliable since the backend of a webpage will change less frequent than the frontend.

2. Be less specific with selectors. Instead of doing body > .content > #datatable > .row::text you can change to #datatable > .row::text. Then your spider will be less likely to break on small changes.

3. Handle errors with try except so to stop the whole parse function from ending if you're expecting some data might be inconsistent.