Domain masking: why it hurts SEO and what to use instead

Domain masking, also called frame forwarding or cloaked redirection, is a setup where your domain stays in the browser's address bar while the page content is actually loaded from a completely different address. Technically it is a tiny HTML page holding a single full-screen iframe. Visitors see a short, memorable name in the address bar and everything looks fine. Search engines, however, see an almost empty page, which is exactly why masking is one of the most damaging choices you can make for SEO.

What a masked domain really serves

When you pick "forward with masking" in domain settings, a wrapper page is generated for the domain. Its code looks roughly like this, and it contains none of your real content:

<!DOCTYPE html>
<html>
<head>
  <title>Mebel Toshkent</title>
</head>
<body style="margin:0">
  <iframe src="https://mebel-dokon.konstruktor-sayt.com/"
          style="border:0;width:100%;height:100vh"></iframe>
</body>
</html>

A crawler reading this page finds a title and one frame URL. The text, products, prices and contact details live on another domain, and the crawler attributes them to that domain. The nice domain you paid for has nothing of its own to index, so it cannot compete in search results.

Why search engines treat masking badly

Content is credited to the other URL

Google and Yandex associate content with the URL where it actually resides. The framed page is treated as a separate document, so rankings and link equity accumulate there. You promote your short domain on other sites, social media and ads, yet much of the SEO value of those links is lost because they point to a page without content.

Every page is stuck on one address

With masking, the address bar shows the home page URL no matter where the visitor navigates. Inner pages such as "Sofas" or "Delivery" have no visible URL under your domain. Search engines cannot list them under your name, shared product links land on the home page.

Duplicate content and confusion

When identical content is reachable at two addresses, the search engine has to choose the canonical one itself. It usually picks the original, so the builder's technical subdomain shows up in results instead of your brand.

Problems beyond SEO

Most modern sites refuse to be displayed inside other pages, using the X-Frame-Options header or the CSP frame-ancestors directive. If the target site does this, visitors to the masked domain get a blank white screen, and owners often miss it because their own browser shows a cached copy. If the wrapper is served over plain HTTP, browsers may flag forms as insecure. Responsive layouts frequently break inside frames on phones, double scrollbars appear, and analytics misreport traffic sources.

A real-world example: a furniture shop in Tashkent

A small furniture shop in Tashkent built its site on a free website builder with a long technical subdomain. The owner bought a neat .uz domain and, to save time, pointed it at the builder with masking. Months later the domain was printed on flyers, shown on Instagram and on maps, but searches like "sofa prices Tashkent" still returned the builder subdomain, or nothing at all. Then the builder disabled framing in a security update, and for several days the domain showed an empty page.

The fix came in two steps: masking was replaced with a 301 redirect, and later the site moved to its own hosting with the domain pointed directly at the server. Inner pages got their own URLs, and search engines began treating the brand domain as the primary address.

What to use instead

Option 1: a permanent 301 redirect

If the second domain is just an extra name, such as a typo variant or an old brand, redirect it to the main domain with a 301. On Apache, use .htaccess:

RewriteEngine On
RewriteCond %{HTTP_HOST} ^(www\.)?eski-domen\.uz$ [NC]
RewriteRule ^(.*)$ https://asosiy-domen.uz/$1 [R=301,L]

On Nginx a separate server block is enough, and $request_uri preserves the path:

server {
    listen 80;
    server_name eski-domen.uz www.eski-domen.uz;
    return 301 https://asosiy-domen.uz$request_uri;
}

Option 2: connect the domain to the site itself

The proper solution is for the site to run on your domain directly: the site lives on hosting and the domain points to that server through DNS, either an A record or nameservers. Most website builders also support connecting a custom domain, which is real hosting under your name rather than masking. On sayt.uz hosting the domain is attached to the account from the cabinet and a free SSL certificate is issued automatically, so no iframe is needed.

Option 3: a canonical tag

If identical content truly must be available on two domains, add a canonical tag pointing to the main URL on every page. It tells search engines which copy to index, although a 301 remains the stronger signal.

How to check your current setup

A single terminal command tells you whether a domain is masked or properly redirected. A 301 status with a Location header means a real redirect; a 200 with only an iframe in the source means masking:

curl -I http://eski-domen.uz/katalog
curl -s http://eski-domen.uz/ | grep -i iframe

In a browser, choose "View page source": a few lines with a single iframe mean your domain is empty for search engines. Masking is acceptable only for throwaway cases where search does not matter. For a business site, online store or clinic it hides your brand from search, and your domain should be the real home of your content, not a mask over someone else's address.