Mobile app version of vmapp.org
Login or Join
Rivera981

: Multiple domains, 'one' server I'm almost completing an online service where people can link their domain to. Think Squarespace/Wix/Weebly type. Visitors enter customerdomain.com that leads to mywebapp.com

@Rivera981

Posted in: #CanonicalUrl #Domains #MultipleDomains #Seo #WebHosting

I'm almost completing an online service where people can link their domain to. Think Squarespace/Wix/Weebly type.
Visitors enter customerdomain.com that leads to mywebapp.com but keeps customerdomain.com/page in the addressbar and forward that to mywebapp.com/page. There is only one leading domain, content is technically accessible through both domains. Sites are dynamically identified by the domain name and generated without frames.

Currently I'm using a Alias Pointer and using the canonical tag pointing to customerdomain.com for SEO, and this technically works fine..

But I'd like to allow for SSL, subdomains, email hosting for each domain and keep in mind that my client or I will own the domain(s). Ultimately I'd like to automate adding domain names within the webapp by my customers.

How will this affect my (customers') SEO serving hundreds of sites through 'one' webapp? is Canonical enough? Other technical setup? More IP adresses? How much per IP?

10.01% popularity Vote Up Vote Down


Login to follow query

More posts by @Rivera981

1 Comments

Sorted by latest first Latest Oldest Best

 

@Cofer257

The rule for indexing is to ask 'Where is the content?' and 'What's the fastest route to it?'

Cross domain canonicalisation is treated like a soft redirect. You state that content is served from webapp.com/page but the URI remains domain.com/page. If you're using an iFrame pointing to webapp.com/page, Google will see it as a link and index the linked content's address. If you use a cross domain canonical tag, it might index domain.com/page.

You can canonicalise a page to another but it remains a suggestion - not a directive. If the content on each page is similar, Google may decide to merge their indexes and 'think' of them as the same page. If the content is very different then it will ignore your suggestion completely.

The only way to force it to index another page is a 301 redirect. This acts as a harder directive. It also changes the request URI.

Here's a simple flow for you to follow:


If you ask a question of Google, where is the content that will answer it?
Is the URI for that content the one that is going to show up as indexed?
Will the server mess with that URI if a user clicks on it?
Is the content going to appear dynamic (different every time)?


These are the questions Google's algorithm will ask in order to find the shortest path from it's index to the content. Any attempt to subvert that in a way that lengthens that path or diverts it, and Google will either adapt or drop the index link.

IP addresses make no difference if you're attempting to index everything under a single domain. Google was originally trained to see subdomains as entirely separate sites and it still has issues interpreting if a subdomain is part of the main site or not. Think xxx.wordpress.com - where each hosted site has it's own subdomain. wordpress.com has no impact on these subdomains whatsoever.

Quick edit: Where IP address would come into SEO is if you wanted different domains to benefit each other without being seen as part of the same C-block (indicates a lazy PBN running from the same Network). This isn't relevant as you're using the same domain name - which categorically tells Google all the sites are from the same network.

10% popularity Vote Up Vote Down


Back to top | Use Dark Theme