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
-
Spammers created bad links to old hacked domain, now redirected to our new domain. Advice?
My client had an old site hacked (let's call it "myolddomain.com") and the hackers created many links in other hacked sites with links such as http://myolddomain.com/styless.asp?jordan-12-taxi-kids-cheap-T8927.html The old myolddomain.com site was redirected to a different new site since then, but we still see over a thousand spam links showing up in the new site's Search Console 404 crawl errors report. Also, using the links: operator in google search, we see many results of spam links. Should we be worried about these bad links pointing to our old site and redirecting to 404s on the new site? What is the best recommendation to clean them up? Ignore? 410s? Other? I'm seeing conflicting advice out there. The old site is hosted by the client's previous web developer who doesn't want to clean anything up on their end without an ongoing hosting contract. So beyond turning redirects on or off, the client doesn't want to pay for any additional hosting. So we don't have much control over anything related to "myolddomain.com". 😞 Thanks in advance for any assistance!
Technical SEO | | usDragons0 -
Redirect root domain to www
I've been having issues with my keyword rankings with MOZ and this is what David at M0Z asked me to do below. Does anyone have a solution to this? I'm not 100% sure what to do. Does it hurt ranking to have a domain at the root or not? Can I 301 redirect a whole site or do I have to do individual pages. "Your campaign is looking for rankings for the www version of the campaign but the URL resolves as a root domain. This would explain the discrepancy. Since there is no re-direct between the two, you can have brickmarkers.com 301 re-direct to www.site.com which will prevent you from re-creating your campaign to track the root domain. Once the re-direct is in place it will take a while for Google to show the www version in the results in which your campaign rankings will be accurate." Thanks
Technical SEO | | SeaDrive0 -
Subdomain vs Main Domain Penalties
We have a client who's main root.com domain is currently penalized by Google, but the subdomain.root.com is appearing very well. We're stumped - any ideas why?
Technical SEO | | Prospector-Plastics0 -
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 -
Subdomain and Domain Rankings
I have read here that domain names with keywords might add a boost to your search rank For instance using a completely inane example monkey-fights.com might get a boost compared to mfl.com (monkey fighting league) when searching for "monkey fights" There seems to be a hot debate as to how much bonus the first domain might get over the second, but leaving that aside for the moment. Question 1. Would monkey-fights.mfl.com get the same kind of bonus as a root domain bonus? Question 2. If the answer to 1 above was yes would a 301 redirect from the suddomain URL to root domain URL retain that bonus I was just thinking on how hard it is to get root domains these days that are not either being squatted on etc. and if this might be a way to get the same bonus, or maybe subdomains are less bonus prone and so it would be a waste of time Thanks
Technical SEO | | bThere0 -
How to remove a sub domain from Google Index!
Hello, I have a website having many subdomains having same copy of content i think its harming my SEO for that site since abc and xyz sub domains do have same contents. Thus i require to know i have already deleted required subdomain DNS RECORDS now how to have those pages removed from Google index as well ? The DNS Records no more exists for those subdomains already.
Technical SEO | | anand20100 -
Using hyphenated sub-domains or non-hyphenated sub-domains? What is the question! I Any takers?
For our corporate business level domain, we are exploring using a hyphenated sub-domain foir a project. Something like www.go-figure.extreme.com I thought from a user perspective it seems cluttered. The domain length might also be an issue with the new Algorithm big G has launched in recent past. I know with past experience, hyphenated domains usually take longer to index, as they are used by spammers more frequently and can take longer to get out of the supplementary index. Our company site has over 90 million viewers / year, so our brand is well established and traffic isn't an issue. This is for a corporate level project and I didn't have the answer! Will this work? anyone have any experience testing this. Any thoughts will help! Thanks, Rob
Technical SEO | | RobMay0 -
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
