Where to place Google Search description on VUE app?

By -

We have developed a vue app with support for different languages. For such, we use the dictionaries of i18n.

Also, on "/public/index.html", we have added the descritions we expect to read on the google search page with the tags:

 <meta property="og:title" content="....">

But what we see on google is:

Google search screen

So my questions are:

  1. How can we set the right values?
  2. Do we have to request somehow to google to update the values in case those were taken before our update?

Thanks

--------------- EDIT 1 -------------------

Every string on the app, it check the indexes on a dictionary: BF_PRICING_CARD... If It does not exist, the default behaviour is to print/echo the string of the key

About the og:title: tags. We are using this set:

<meta name="title" content="bla bla"> 
<meta name="author" content="bla">
<meta name="description" content="bla bla bla">
<meta name="keywords" content="bla bla bla bla bla">

--------------- EDIT 2 ------------------- <title>bla blag</title>

The URL does not change. The language is detected on the browser and then passed to the app as a JS variable to take the right dictionary.

  1. Can the issue be that when Google index it, we do not have any translation available for its robot?


from Recent Questions - Stack Overflow https://ift.tt/2ZzsUQo
https://ift.tt/2ZtsUl6

Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk.
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch").build();     TransportClient client = new P
Read more