Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
Cross Canonicalization for domains with same menu
-
I have a client who took 3 pages from its main website and made them into their own domains. So that now, for example,
www.mainsite.com/page
redirects to
www.page.comThis is so users can be given access to the content on that specific page with ease.
Now, www.page.com has the same menu items as www.mainsite.com, so that users who select the menu items on www.page.com will be circled back to the main site.But this means that there are now different URLs for these pages.
ie:
On www.mainsite.com there is: www.mainsite.com/menu-item
(the content resides here)And on www.page.com there is: www.page.com/menu-item
(Which is basically "scaffolding" to support the page and a means to get around, so to speak.This is to make any and all pages accessible at either domain. ) I have only seen this type of URL on the Moz campaign crawl. In the real world, when a user selects a menu item from the www.page.com, it will circle back to www.mainsite.com/menu-itemSEO-wise, should I use cross-canonicalization to point www.page.com/menu-item to www.mainsite.com/menu-item? Or would this be splitting hairs since these are only seen on the Moz crawl?
-
@Shrine-SEO-Gal said in Cross Canonicalization for domains with same menu:
I have a client who took 3 pages from its main website and made them into their own domains. So that now, for example,
www.mainsite.com/page
redirects to
www.page.com
This is so users can be given access to the content on that specific page with ease.
Now, www.page.com has the same menu items as www.mainsite.com, so that users who select the menu items on www.page.com will be circled back to the main site.
But this means that there are now different URLs for these pages.
ie:
On www.mainsite.com there is: www.mainsite.com/menu-item
(the content resides here)
And on www.page.com there is: www.page.com/menu-item
(Which is basically "scaffolding" to support the page and a means to get around, so to speak.This is to make any and all pages accessible at either domain. ) I have only seen this type of URL on the Moz campaign crawl. In the real world, when a user selects a menu item from the www.page.com, it will circle back to www.mainsite.com/menu-item
SEO-wise, should I use cross-canonicalization to point www.page.com/menu-item to www.mainsite.com/menu-item? Or would this be splitting hairs since these are only seen on the Moz crawl?For SEO, using cross-canonical tags would help consolidate authority and avoid potential duplication issues, even though the structure is primarily for navigation and redirecting users to the main site. Adding canonicals from
www.page.com/menu-itemtowww.mainsite.com/menu-itemsignals to search engines that the main version resides on the main site, which is helpful in the long term.Since these URLs show up only in Moz crawls, this isn’t an urgent issue, but canonicalization helps clarify the content's primary source if search engines eventually pick up on
www.page.com/menu-item. You might also want to set up redirects on these scaffold URLs if they don’t need to be indexed separately, which can further ensure consistency.
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Help: buy domain from Tradenames.com?
Hello to all, I'm Silvia. I am writing to ask if any of you know this site: tradenames.com. It is a domains broker. They contacted my client and would like to sell the .com business domain (my client currently has the .it). Does anyone know them? Thanks you for your help.
Technical SEO | | advmedialab0 -
Images on sub domain fed from CDN
I have a client that uses a CDN to fill images, from a sub domain ( images.domain.com). We've made sure that the sub domain itself is not blocked. We've added a robots.txt file, we're creating an image sitemap file & we've verified ownership of the domain within GWT. Yet, any crawler that I use only see's the first page of the sub domain (which is .html) but none of the subsequent URL's which are all .jpeg. Is there something simple I'm missing here?
Technical SEO | | TammyWood0 -
Correct linking to the /index of a site and subfolders: what's the best practice? link to: domain.com/ or domain.com/index.html ?
Dear all, starting with my .htaccess file: RewriteEngine On
Technical SEO | | inlinear
RewriteCond %{HTTP_HOST} ^www.inlinear.com$ [NC]
RewriteRule ^(.*)$ http://inlinear.com/$1 [R=301,L] RewriteCond %{THE_REQUEST} ^./index.html
RewriteRule ^(.)index.html$ http://inlinear.com/ [R=301,L] 1. I redirect all URL-requests with www. to the non www-version...
2. all requests with "index.html" will be redirected to "domain.com/" My questions are: A) When linking from a page to my frontpage (home) the best practice is?: "http://domain.com/" the best and NOT: "http://domain.com/index.php" B) When linking to the index of a subfolder "http://domain.com/products/index.php" I should link also to: "http://domain.com/products/" and not put also the index.php..., right? C) When I define the canonical ULR, should I also define it just: "http://domain.com/products/" or in this case I should link to the definite file: "http://domain.com/products**/index.php**" Is A) B) the best practice? and C) ? Thanks for all replies! 🙂
Holger0 -
Umlaut in domain
Hi, My client wants to expand it's business to Germany and logically we need a domain name to match. We've found a great one and regsiterd several variants to it. However I just found out that in Germany it is possible (while here it's not) to register a domain with an umlaut. My question is: will google assign more value to: schädlinge.de than schadlinge.de when users search for schädlinge? If yes, how large will the difference be? (I will use an umlaut in the title etc) Kind regards,
Technical SEO | | media-surfer
Jason.0 -
.ca and. com domains
Hello, currently the main site im working on is a .com, but have the .ca version purchased from register.com. should i have this setup to redirect to the .com site. will google see these as dup content. We have the .ca for our canadian customers but both sites are identical. Thank you
Technical SEO | | TP_Marketing0 -
Any way around buying hosting for an old domain to 301 redirect to a new domain?
Howdy. I have just read this QA thread, so I think I have my answer. But I'm going to ask anyway! Basically DomainA.com is being retired, and DomainB.com is going to be launched. We're going to have to redirect numerous URLs from DomainA.com to DomainB.com. I think the way to go about this is to continue paying for hosting for DomainA.com, serving a .htaccess from that hosting account, and then hosting DomainB.com separately. Anybody know of a way to avoid paying for hosting a .htaccess file on DomainA.com? Thanks!
Technical SEO | | SamTurri0 -
What is the best method to block a sub-domain, e.g. staging.domain.com/ from getting indexed?
Now that Google considers subdomains as part of the TLD I'm a little leery of testing robots.txt with something like: staging.domain.com
Technical SEO | | fthead9
User-agent: *
Disallow: / in fear it might get the www.domain.com blocked as well. Has anyone had any success using robots.txt to block sub-domains? I know I could add a meta robots tag to the staging.domain.com pages but that would require a lot more work.0 -
301 Redirect vs Domain Alias
We have hundreds of domains which are either alternate spelling of our primary domain or close keyword names we didn't want our competitor to get before us. The primary domain is running on a dedicated Windows server running IIS6 and set to a static IP. Since it is a static IP and not using host headers any domain pointed to the static IP will immediately show the contents of the site, however the domain will be whatever was typed. Which could be the primary domain or an alias. Two concerns. First, is it possible that Google would penalize us for the alias domains or dilute our primary domain "juice"? Second, we need to properly track traffic from the alias domains. We could make unique content for those performing well and sell or let expire those that are sending no traffic. It's not my goal to use the alias domains to artificially pump up our primary domain. We have them for spelling errors and direct traffic. What is the best practice for handling one or both of these issues?
Technical SEO | | briankb0