Avoid SEO problems with multiple domains (like in Now)

cianespablo · 8 September 2019 10:40

Hello,

Are there any option to control the Automatic Aliasing and avoid indexed by Google??

In this moment I think is under important SEO problems with this deployment

I think it is not possible to hide or even not allow to index all staging sites on each deployment. On other hand with Github integration is event worst.

For example in same production web you have 3 alias:

Your public production domain verified with ZEIT DNS: mydomain.com
Your proyect: proyect-name.username.now.sh
Your git branch: proyect-name-git-master.username.now.sh

And of course more staging urls and more git branch alias with other versions of the same web and maybe indexed all at the same time with no control…

In this moment I think is not a good solution to production If we dont have control of that

luisherranz · 9 September 2019 06:48

Hi @cianespablo, thanks for your post and welcome to the community

Automatic aliasing is a feature of Zeit Now, not of Frontity. So I recommend you to ask the same question in their support forums: https://spectrum.chat/zeit

To avoid SEO problems with multiple domains make sure to always use canonical tags in your <head> pointing to the right domain. Take a special look at the section 6 of this article, “Canonicalize cross-domain duplicates”: https://moz.com/learn/seo/canonicalization

cianespablo · 10 September 2019 11:52

thanks for your quick response

with more time we will see other development options where we have more control

luisherranz · 14 October 2019 13:18

I just want to do a quick update in this topic.

@zhandosweb pointed out in here that plugins like Yoast automatically manage the canonical tags of your WP theme, so there’s probably a better solution to avoid duplicate content:

1. Use a plugin to password protect your front-end, like explained by @ShaGui here:

More info in this topic: 3 questions from a newbie

2. Use `Redirection` to redirect all your front-end traffic to your Frontity site:

3 questions from a newbie

Another viable option is to add 301 redirections with the Redirection plugin.

You have to

Add new redirection.

Choose the REGEX option.

Use this source URL that matches any url that is not wp-admin , wp-json , wp-login …
^(\/(?!wp-(json|admin|login|signup|content|comments-post\.php|cron\.php)).*)
Use your Frontity domain as Target URL, followed by $1 , which is the pathname and query:
https://mars.frontity.org$1
I’ve just tested it in https://test.frontity.io and works great (it is disabled now).

More info in this topic: 3 questions from a newbie

Finally, we will add options to do this in our upcoming PHP plugin:

kasper · 17 February 2021 22:47

Hi @luisherranz,

I used solution nr 2 (Use Redirection to redirect all your front-end traffic to your Frontity site) here, is this still the best pracice?

-Kasper

luisherranz · 18 February 2021 08:30

Yes, that’s perfectly fine

Avoid SEO problems with multiple domains (like in Now)

1. Use a plugin to password protect your front-end, like explained by @ShaGui here:

2. Use Redirection to redirect all your front-end traffic to your Frontity site:

2. Use `Redirection` to redirect all your front-end traffic to your Frontity site: