Search Engine Tip: Prevent Duplicate Content By Removing Wildcard Subdomain From DNS

If you have a website, it is important to only publish it in one place. The underlying reason is that Google and other search engines do not like it if they find the same information in multiple places (so-called duplicate content).

How is that possible if you do not intentionally copy pages to other places?

One possibility is that your website can be accessed via multiple URLs. For example, we will give you a temporary URL if the domain has not yet been moved or is in the air. In addition, the DNS is set up so that you can come to your site via any subdomain. If you use WordPress you already set the website URL via Settings> General. If visitors are received on another (sub) domain, WordPress will immediately send the visitor to the correct domain.

If you now know which domain your website should be active on, then in many cases you can prevent your website from being accessed in several ways by a few simple steps (of course use your own domain instead of example.com below):

  1. Log in to the account center https://my.codeorange.co.th/login
  2. Select the domain that you want to set;
  3. Look under “Manage Subdomains” (and dig into your memory) and write down the subdomains that you use;
  4. Select “Name Servers”;
  5. See if you find a line with an asterisk and an A, something like this: * .example.com A 1.2.3.4 3600
  6. Write down the IP of the line with the asterisk (or take a screenshot), then you can easily undo it later by creating a new line with the same data. You also need the IP address in step 8;
  7. If you do see this rule, check-in the browser whether www.example.com but also www123.example.com , for example, remain in the browser with identical content, without redirecting the visitor to the main domain;
  8. So if you can put a number of different URLs in the browser and they all display the same website, it is better that you delete the line with the asterisk.
    Note  that if you have other subdomains in use (see step 3), they will stop working if you delete the line with the asterisk. To prevent this, you can add the subdomains to the Name Server settings by creating one or more A records with the same IP as the asterisk (as you noted in step 6).

After changing the Name Server data, it may take a while for the changes to work. Internet providers can sometimes remember the data up to a day later. Therefore, for testing after step 8, it is better to use subdomains that you have not previously entered in the browser.

Better DNS settings make everyone happy. So get started and if you have any questions, we are always there for you.

PS: From mid-February 2017, the * record is no longer automatically created for new orders and name server records are automatically added and deleted when creating/deleting subdomains via “Manage Subdomains”.

PPS: For more advanced use you can also indicate to search engines which of the identical pages is the actual source, by means of “canonicalization”, see also: https://support.google.com/webmasters/answer/66359?hl=en

How to Optimize Site Performance for Core Web Vitals

By Rutger | June 8, 2021

There are many factors that affect website rankings, one of which is, site performance. How does your site perform in terms of speed and accessibility? Just this month  Google established a new user experience metric called Core Web Vitals. Core Web Vitals aims to put the most optimized website in terms of performance on top of…

Firefox’s new Site Isolation Security Architecture

By Rutger | May 28, 2021

Online there are plenty of untrustworthy websites that could overpass the initial security in your primary browser. Which is why Firefox developed a new Site Isolation Security. With the main purpose of preventing malicious websites from accessing or stealing information from your accounts on other websites.  The process of site Isolation security is separating web…

WordPress Proposes Blocking Google’s FLoC

By Rutger | April 25, 2021

In the recent announcement from WordPress, they state that they are treating Google’s new FLoC tracking technology as a security concern and may block it by default on WordPress sites. Google’s Federated Learning of Cohorts (FLoC) received a lot of criticism concerning privacy. “FLoC is meant to be a new way to make your browser…

Am I FLoCed? A New Site to Test Google’s Invasive Experiment

By Rutger | April 5, 2021

 Am I FLoCed is one of an effort to uncover the invasive practices of the adtech industry—Google included. It is a new site where you can check if you are being subjected to the latest advertising experiment, FLoC. What is FloC? Federated Learning of Cohorts or FLoC is Google’s new advertising technology intended to replace…

DuckDuckGo Browser and Extension

By Rutger | February 25, 2021

DuckDuckGo describes itself as “the search engine that doesn’t track you.” Although DDG is better known for its privacy-focused search engine, the company has expanded into making its own Privacy Browser app for Android and IOS. The DDG Privacy Browser has the speed you need, the browsing features you expect (like tabs & bookmarks), and…

The Search Engine That Doesn’t Track You

By Rutger | February 11, 2021

THERE’S A NEW battleground in the browser wars: user privacy. Just recently, we published an article about Brave browser and how effective its tracker blocking technologies. So here’s another talk of the town privacy-focused search engine that will help you enjoy the internet without having to worry about leaving a digital footprint.  What is DuckDuckGo?…

Mozilla Firefox 85.00 is Here!

By Rutger | January 30, 2021

The popular open-source web browser Mozilla Firefox finally released version 85.00. With significant updates including the much-awaited major privacy enhancement called network partitioning. Check out the major improvements and what’s been added and changed for the latest Firefox 85.00. What’s new? The Adobe’s popular software Flash Player is no longer supported by Firefox 85. “There is…

Update: Let’s Encrypt Extends Support for Android 7 or Older Devices for Three Years

By Rutger | January 13, 2021

Back in November, Let’s Encrypt an open certificate authority announced an end to its partnership with Identrust and to “Standing on Our Own Two Feet – Let’s Encrypt”. The supposed part ways will cause compatibility issues with Android 7.1.1 or older to not be able to access HTTPS websites.  In its new announcement, Let’s Encrypt has…

Apple and Cloudflare team up to stop your ISP from seeing which websites you visit

By Rutger | December 16, 2020

Apple and Cloudflare team up to develop a new internet protocol called “Oblivious DNS-over-HTTPS,” or “ODoH,” which can prevent Internet Service Providers (ISP) from knowing which websites you visit. When visiting a website the request sent can be logged and tells your ISP which websites you visited, down to the hostnames and subdomains. This information…

Standing on Our Own Two Feet – Let’s Encrypt

By Rutger | November 13, 2020

[Update] Let’s Encrypt Extends Support for Android 7 or Older Devices for Three Years Let’s Encrypt announced its partnership with IdenTrust will come to an end by September 1, 2021. Except for its own root certificate, Let’s Encrypt has been using a cross-signed certificate from IdenTrust. The decision to part ways is dubbed as the…