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
-
301 Redirect back to original domain
We have a site, domainA.com and we split part of the site off into it's own site a couple of years ago as domainB.com. All urls from DomainA were 301 redirected to DomainB, but with a different folder structure. For business reasons, we now shuttering domainB and rolling it back into domainA. For the 301 redirects for urls that were on the original domainA, should I overwrite them to the new folder structure directly from the original urls? In other words: 301 redirect domainA.com/oldstructure to domainA.com/newstructure rather than: Existing 301 redirect domainA.com/oldstructure to domainB.com/newstructuretopic with a new 301 redirect to domainA.com/newstructuretopictopic
Technical SEO | | ang0 -
Should I be concerned about Google indexing an old domain if the listings redirect to the new domain?
I noticed this about Moz's old domain SEOMoz.org. If the URLs from the old domain are redirecting, is there any reason to be concerned about an old domain still appearing to be indexed by Google? See here: https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=site%3Aseomoz.org Links to seomoz.org are listed, but if you click them they redirect to moz.com. Is this anything to be concerned about or is everything operating as expected?
Technical SEO | | 352inc0 -
Domain Structure - without www.
I'm working on a new project and we would prefer to not use the www. - for name/branding reasons. Are there any SEO ramifications from setting the domain without the www and using 301 redirects for all home page extensions to forward to -> domain.com(without the www)? Furthermore, we will be hosting many profiles on this site and would like to structure them for optimal SEO. Would there be an issue with using sub domains - user.domain.com, or would sub directories be more optimal? Thank you in advance!
Technical SEO | | NickMacario0 -
Updating Domain Yearly for Branding Purposes?
We host an event every year which updates it's branding to include the year (Ex. Acme 2013, Acme 2014, etc.). We used to use the branded domains (acme2012.com) to redirect to the event microsite on off of our main content site (ex. acme2012.acme.com). Just this year our event managers decided host the event on it's own domain, separating it from the content site. So it is now acme2013.com. Their strategy is to update the domain every year to include the current year, so next year the domain would be acme2014.com. I understand the use of the domain for marketing purposes but I feel like it could be hurting our SEO by doing this. Should we revert to our original strategy or is this okay with the proper setup? I should note that because this is an event promotion site, the site template and content updates every year.
Technical SEO | | accessintel0 -
Undo a 301 or Starting New Domain?
Hi Guys & Gals, I have a question I'd appreciate your input on. Quick History
Technical SEO | | Nobody1560986989723
When I first started in web design it was just me and a couple of clients. I had a website based on my name on the domain moxby.org.uk. The only 'SEO' work done on it was a bit of on-site work, various links based on forum and blog activity I was involved in (genuine involvement not crappy link building) and of course, building websites with a credit in the footer. When we got serious about the business we considered and finally put in place a new website, new branding and 301'd old URLs to their shiny new location on the new domain: _summitweb.net _(put in place about 12 months ago) Ranks were pretty much maintained and until recently we ranked well locally (still figuring the fallout from the last week or so's changes). The Question I would like to build a personal website, well I'm going to anyway. But as it's a personal/showcase website I need a personal URL for it and my natural choice would be my old url moxby.org.uk. However it is not that simple because summitweb.net is benefitting from redirected links and I don't want to harm our business' rankings just to reclaim a personal URL. So... is there benefit or would it be to my detriment to undo the 301 and build a website on moxby.org.uk or would it, in fact, just make more sense to buy a new domain and have a clean slate?0 -
Duplicate Content: Canonicalization vs. Redirects
Hi all, I have a client that I recently started working with whose site was built with the following structure: domain.com
Technical SEO | | marisolmarketing
domain.com/default.asp Essentially, there is a /default.asp version of every single page on the site. That said, I'm trying to figure out the easiest/most efficient way to fix all the /default.asp pages...whether that be 301 redirecting them to the .com version, adding a canonical tag to every .asp page, or simply NOINDEXing the .asp pages. I've seen a few other questions on here that are similar, but none that really say which would be the easiest way to accomplish this without going through every single page... Thanks in advance!0 -
Is Buying Domains Good For SEO? Can I 301 redirect domains to an Original website?
I have a friend that purchased multiple domains related to their website. Each of these domains have the back ground of the original website and irrelevant content on them. Is is possible to redirect the various domains to certain pages on the original website. For example if the website is www.shoes.com and they purchased domains such as www.leathermensshoes.com and a few others related to the website. Is it SEO friendly to link the domains purchased to the original website?
Technical SEO | | TSpike10 -
Considering redirecting or canonicalization - Best Practice
Hi, I'm having a techinical problem and I would like advise on the effects this is having on my SEO efforts. My old site www.oldsiteexample.com (live for about 8 years) Directs to my new site www.example.com which is fine BUT When I type me new website into the tool bar both sides are found & do not direct to one domain; www.example.com & example.com (both the same site) What is the best practice here? Direct my new non www to my new www site considering my old website directs to the www. Advise & the SEO affects this is having my website would be greatly appreciated, thank you.
Technical SEO | | Socialdude0