Country of the website on confirmed URLs

Hi!
I think it will be nice and convenient to have the country column in the list of verified URLs. If the GSA can identify the country (based on the domain tld and others), it is helpful for people who do not work with xxx, xxx, xxx URLs to avoid certain tlds / hosts. I know this is possible while posting, but I think it may be useful to reorient some websites / languages.
I'm not sure if it's easy or not, but the data is already collected at checkout (last checked).
What do you think?

How do I remove the attached string from image and Javascript URLs?

I have a Drupal 8 website. I have installed the Advagg module. The URL for the JavaScript file is appended with a string.

  • https://example.com/libraries/superfish/superfish.js?pzw4cp
  • https://example.com/libraries/superfish/superfish.js?pzy2r8
  • https://example.com/libraries/superfish/superfish.js?pzzsmo
  • https://example.com/sites/default/files/js/optimized/js_rKIkMy4-wmUaGP59iZKW9XJMLcVwjsfB0SXmAPmdK1I.sEln9qPOr9xw2O4-sGx2Wja5YU2bXGxwxG

The same applies to the URLs of the uploaded images. Sometimes the browser will not display the image if the URL contains this string. When I remove the string, the image is displayed. The Google search console reports such files as malware.

How do I remove these strings from the end of the URL?

URLs – Create 600 links to separate files on Google Drive

For a climate change education project, I have to create 600 links pointing to 600 separate files on Google Drive. I have the list of all 600 shared URLs for the files, but I do not see how I can assign these URLs to the links on my WordPress website without manually copying / pasting them.

Is there a way (plugin, python library etc) to perform this task as an automated batch?

Thanks in advance for your help.

Friendly greetings,
André.

How should I structure my URLs for both SEO and localization?

There are many acceptable ways to structure your website for SEO and internationalization. Everyone has advantages and disadvantages.

Top level domains

Buy the same domain name from multiple top-level country domains like example.com. example.es and example.de,

advantages

  • Full support from Google. You can add the sites to Google Webmaster Tools. There you have the opportunity to tell Google how they are targeted.
  • Often preferred by users who like content published on the TLD for their country
  • The domain name itself can be located. Many international users may respond poorly to English words or an English-sounding domain name. This may be particularly important for languages ​​that do not use a Latin alphabet.
  • Supports localization by country. You can have different sites like example.co.uk and example.com.au Target group in different countries. Websites may contain duplicate content with minor spelling differences and still rank well. In fact, several well-located Web sites in the same language may rank higher than a single Web site in that language.
  • Hosting can be located by pointing to a web server in the destination country.

disadvantage

  • Expensive and time consuming to buy many domains. Especially if you are dealing with squatters.
  • Cookies can not be shared in multiple locales, which means that users must sign in to each site separately.
  • Not a good option for language localization only, as many languages ​​have multiple countries and no country TLD can be the language code. Also in cases where the TLD does not match the language code esSearch engines can assume that the website is only suitable for users from Spain, not for all Spanish speakers.

subdomains

Buy a single domain and use subdomains like en.example.com, and es.example.com

advantages

  • Full support from Google.
  • Supports localization by country or by language.
  • Hosting can be located by pointing DNS to a web server near the user.
  • Simple and cost-effective implementation compared to purchasing multiple domains.
  • Cookies can be used in all locales, so users can log in more seamlessly with just one login.

disadvantage

  • No way to localize the domain name itself
  • This may be less local to users than a top-level domain.

subdirectories

Buy a single domain and use subdirectories like example.com/en/, and example.com/es/

advantages and disadvantages

  • Same as subdomains, except that there is a DNS record that excludes hosting your site in multiple countries for different locales.

Techniques that are NOT recommended

  • filename: Use different file names like index_en.html and index_de.html, This technique is not fully supported by Google. For example, there is no way to set targeting in Webmaster Tools.
  • URL parameters: Using URL Parameters Like lang=en, It is not recommended for the same reason that other filenames are not recommended.
  • Take over the language heading: Automatic language switching based on Accept-Language Header.
    • For many users this header is not set correctly. This is especially true for users traveling abroad who may be using a friend's computer or an internet café. This is also often the case for international users who install an English web browser and have sufficient English language skills but prefer content in a different language.
    • Google has just announced that Googlebot will send it Accept-Language Header and Crawl from different geographic locations. However, Google still recommends using separate URLs for content in different languages.
    • You can the Accept-Language A header that indicates that users may prefer a different version of the site by displaying a message if the site they are visiting does not match that one Accept-Language Header.
  • Geographic IP addresses: Automatic language switching based on the geographical location of the IP address.

On-page markup

If you support multiple languages, you should be well versed in using language metadata.

Use the lang attribute in the html Label:


Use alternate links to the same page in other languages ​​as suggested by Google:



 

Alternatively, this information can be stored in Sitemap files.

Tell Google about your website

You should add any language (or locale) of your site to Google Webmaster Tools. This can be done for top-level domains, for subdomains, or for subdirectories.

If your site is country targeted, you should use Webmaster Tools to set the site's orientation. Navigate to "Configuration" -> "Settings" -> "Geographic Destination" and select the correct country from the drop-down list.

The Google Search Console creates URLs that are not in my sitemap, and then complains that these pages are broken

You have a wrong idea of ​​what a sitemap is.

The sitemap is used to monitor the crawling of the site by the search engine bot. The sitemap and crawling a site are two different and independent things. Google continues to search your site independently of the sitemap. The sitemap is used to check if Google can properly crawl your site. For example, if pages are found in your sitemap and Google has not seen the page, Google may add the page to the fetch queue to include.

The opposite is not true. If a page is not found in the sitemap, Google will not remove it from the index. Why? Because Google found it by crawling the site.

What you seem to believe is that the sitemap is the absolute authority Google uses to identify which pages exist on a particular site. That's not the case. The crawl is. The sitemap only helps Google to know if You can properly crawl your site, and if not, what pages Google is missing that should be added to the fetch queue.

Your expectation that Google will stop trying to access pages because these pages are no longer in your sitemap is wrong. Sitemaps are cached and checked at regular intervals. Why? Because it is a testing process.

You have a real problem that you need to solve.

You return a 500 error for pages that were not found. This is bad. Your website should return a 404 Not Found error. The 500 error is a system error and is treated as temporary by Google. If your site returns a 404 error, Google will still try the page a few times over a period of time, until it finds that the page no longer exists. If possible, you want to output a 410 Removed error for pages that you have removed. If this is too much work or not possible, the 404 will mean the same over time.

You must fix your 500 error.

Google Search Console creates URLs that do not exist in my Sitemap, and then complains that these pages are broken

You have a wrong idea of ​​what a sitemap is.

The sitemap is used to monitor the crawling of the site by the search engine bot. The sitemap and crawling a site are two different and independent things. Google continues to search your site independently of the sitemap. The sitemap is used to check if Google can properly crawl your site. For example, if pages are found in your sitemap and Google has not seen the page, Google may add the page to the fetch queue to include.

The opposite is not true. If a page is not found in the sitemap, Google will not remove it from the index. Why? Because Google found it by crawling the site.

What you seem to believe is that the sitemap is the absolute authority Google uses to identify which pages exist on a particular site. That's not the case. The crawl is. The sitemap only helps Google to know if You can properly crawl your site, and if not, what pages Google is missing that should be added to the fetch queue.

Your expectation that Google will stop trying to access pages because these pages are no longer in your sitemap is wrong. Sitemaps are cached and checked at regular intervals. Why? Because it is a testing process.

You have a real problem that you need to solve.

You return a 500 error for pages that were not found. This is bad. Your website should return a 404 Not Found error. The 500 error is a system error and is treated as temporary by Google. If your site returns a 404 error, Google will still try the page a few times over a period of time, until it finds that the page no longer exists. If possible, you want to output a 410 Removed error for pages that you have removed. If this is too much work or not possible, the 404 will mean the same over time.

You must fix your 500 error.

java – Parameters for MercadoPago API return URLs

I am trying to integrate the MercadoPago API into my Java / Spring project, and there are some issues when I return to the application after the payment has been made.

In my java code, I define the return URLs as follows:

public Preference preference(Usuario usuario) throws  MPException, MPConfException {
...
    String successUrl = "http://localhost:8080/mercadopago/process_order";
    String pendingUrl = "http://localhost:8080/mercadopago/process_order";
    String failureUrl = "http://localhost:8080/cart";
    preference.setBackUrls(new BackUrls(successUrl, pendingUrl, failureUrl));
...
}

When I run the application and try to make a payment, the process is done normally, and I come to the last screen with the payment confirmation http://localhost:8080/mercadopago/process_order I am referred http://localhost:8080/process_order,

I also want to pass two parameters along with this URL: user_id and transaction_id (the latter must contain a marketPage-generated transaction ID?) For my application.

Does anyone know how to change the code above to tell that these parameters will be redirected along with the URL? How does MercadoPago forward these parameters (via POST or GET)? How do I get the transaction id generated by MercadoPago in the above method?

ps.: The HTML code that starts the purchase is:

  

URLs – Special domain for a page

I have a WP installation example.com and want to have secondary.com to show content from example.com/b (b is a page) but keep secondary.com in the url (not secondary.com/b)

I've tried this approach: https://stackoverflow.com/a/35272993/2095642

I've shown both domains on a directory, I use this in my wp-config.php:

//this works, enables both domains to show the same wp installation
define('WP_SITEURL', 'http://' . $_SERVER('HTTP_HOST'));
define('WP_HOME', 'http://' . $_SERVER('HTTP_HOST'));

and that in my .htaccess:

#this works, changes example.com/b url to secondary.com
RewriteCond %{HTTP_HOST} example.com$
RewriteRule ^b/(.*)$ https://www.secondary.com/$1 (L,QSA,R=302)

#this doesn't take effect and shows homepage on secondary.com
#I want it to keep only secondary.com in URL but show page /b/.
RewriteCond %{HTTP_HOST} secondary.com/?$
RewriteRule ^$ /b/ (L,QSA)

The second rule works the way it should when referencing a non-WP directory – preserves the URL but displays the directory index. However, if you point to a wp page path, this is not the case.

Thank you so much!