Welcome to the Q&A Forum
Browse the forum for helpful insights and fresh discussions about all things SEO.
Are you using a CMS, or some inhouse solution? If it is a CMS, in many cases you should be able to update that CMS so that the 2 links are generated but the page itself isn't generated twice.
Another option if 2 pages must exist, would be to set a canonical on both pages to the 1 main location for the content, while using a pushstate on the url to manipulate the browser into the main pathing. Although the more I think about that one, it may not be a 100% viable option.
Wanted to pass along a specific use-case that I'm thinking through in the technical setup for a client.
Site: http://www.abc.com is an ecommerce company that offers the ability to white-label a site so an affiliate can join and get access to the site, and ultimately get a cut of whatever is sold through that affiliate.
So I join the site and get access to scott.xyz.com and can handle my business through that. From a technical standpoint, this is the proposed technical setup of the site.
Questions
Thanks!
Scott
It's a very good question and definetly an option although at this time it isn't a viable option since the company isn't interested in a change to the overall legacy architecture which has all the content separated as I stated above. There is the desire to keep the tabs as specific targetable content as they are all specific deeper dives into the product and not necessarily the types of content that you pointed out above (specs, shipping, etc). It's more of a travel product where there is an itinerary, property, room type options (all of which are chosen later in a booking).
Though the index numbers aren't all that impressive, the sites had a number of previous architectural and duplication issues that are finally beginning to clear up and normalize. There is a belief that the cleaning of ur parameters, canonicalizations, etc that has happened will improve those index numbers.
Thano you for the suggestion, it's definitely appreciated and something I've considered although as I mentioned I'm not sure if it is a direction I'll be able to convince them on.
This isn't a unique problem but an e-commerce client has product information on a page, with separate tabs that have been historically loaded with a new page, which have been indexed.
All of the content shares a common product top section (summary of information) but has unique canonical url definitions, meta information, etc. The individual content tabs are all part of a larger grouping, which is why their index level is considerably less than the actual product page. As the client grows and updates this historical practice, one of the implementation options is making the content available on the page via an Ajax load.
The desire would be to maintain the ability to search for content1, content2, etc at that level and not spread the juice throughout all the main product pages. My question is what would the best setup be to maintain the historical ability to target the content individually via Search, while updating the UI/UX for a better customer experience? If the ajax route is the way to go, what are all the tasks necessary to properly handle without creating a separate duplicate pathing? Some of the tasks that I've outlined would be
Using pushState to update the url when the tab is changed
Is there an ability to also update canonicals & meta information?
what else am I missing? Any guidance would be great as Id love to get some thoguhts on the matter.
Thanks!
Recently a module was built into the homepage to pull in content from an outside source via Ajax and I'm curious about the overall crawability of the content.
In WMT, if I fetch & render the content it displays correctly, but if I view source all I am seeing is the empty container. Should I take additional steps so that the actual AJAX content displays in my source code, or am I "good" since the content does display correctly when I fetch & render?