Please check if you have any nodes below /content/mysite/us/en, which are not of type Page ?

In your use case, it seems like component behavior is dynamic, ie. the component fetches data from some backend service and renders it.  There are multiple ways to handle such cases: Lazy loading of your component, using AJAX. Make sure to uncache this AJAX request to always get latest content from ...

If you are using AEM on-prem setup, Bulk Editor [1] can solve your problem.   Another option you can try is Bulk Editing page properties [2]   [1] https://experienceleague.adobe.com/docs/experience-manager-65/administering/operations/bulk-editor.html?lang=en [2] https://experienceleague.adobe.com/do...

There are no detailed level auditing of user actions, You can use versioning for governance purpose.    AEM OOB provides audit logs [1] for events that qualify for audit logging.   ACS commons audit log search interface [2] can be used, which allows administrators to easily search the AEM Audit Log...

Hello @arvindpandey    Such blobs kind of data (JSON Payload in this case) can be stored under /var folder.   Please make sure to implement a fallback, like if JSON data is not available under /var, make a real-time API call and save it under /var.   ~ Mohit

Hello Sanjana   Use AEM Search Core component [1] for search implementation.    [1] https://experienceleague.adobe.com/docs/experience-manager-core-components/using/components/quick-search.html?lang=en 

This question and solution are not related to AEM. You can use Google GEOCoder API to query, see below links for reference https://stackoverflow.com/questions/52501111/google-maps-api-query-with-only-zip-code-provides-incorrect-results 

You can use tools like localtunnel [1] / ngrok [2] to expose your localhost over the internet. But be careful as it's easy to exploit localhost due to lake of security. Make sure to apply security checklist [3]   [1] https://theboroer.github.io/localtunnel-www/ [2] https://ngrok.com/  [3] https://ex...

In that case, raise a support request for this issue.

This is strange, have you tried replicating this on a fresh aem instance with a demo site ?