It appears NetSuite Support is not understanding this case. They've converted this case to Enhancement request 159979. The enhancement request reads: “Support for the new canonical link standard to eliminate duplicate content penalties for pages with the same content but different navigation“ Below is what I've replied to…

If I understand that correctly, we are not penalized for duplicate content, but we may get lower rankings because of link bleed. Do I have that correct? You are correct!

Stephan, We are in the same boat. We sell items from the same family but different height, width, light color, etc. I opted to go for what I thought was a better user experience and flexibility in marketing. I decided to create one page for each item.

8. Currently on pagination, the URL listed on the page would be something like this: /s.nl/c.482623/n.1/sc.7/category.41/.f?range=91,98,98 then a 301 redirect would occur immediately to the friendly URL. It would be great to skip the system URL and just present the friendly. I cannot imagine how many 301 redirects would be…

What I did was simply block google from crawing those pages with robots.txt -- not ideal, but better than a duplicate filter. The big downside is if you have an item which is only listed on page 2 of a category, it could have a challenge getting indexed. Even if you put a item URL in an XML site map, Google has stated that…

NetSuite case: 1211514 How did I miss this and fail to undersand the impact? This will cause issues with SEO results and usability. For the parameter, ?range=1%2C45%2C50 If the number of items in that category changes, up or down, the parameter will change: +1 = ?range=1%2C45%2C51 -1 = ?range=1%2C45%2C49 This creates two…

First, I understand pagination of categories is extremely difficult! That said, pagination models which were ok for search engine marketing in prior years are no longer acceptable. The search engines are raising the bar and shopping cart vendors much exceed that bar. As I see it, there are 5 options: 1) NetSuite makes a…

Canonical is not designed for this. Agreed! The enhancement should not even talk about the canonical reference, it just needs to 301 redirect (permanent) to update the total amount. That gets google to update their index, and stop referencing the invalid amount. This will also automatically handle future updates without…

6. can be done with robots.txt very easily. Agreed, below is the robots.txt: Disallow: /*sort1desc* #Sorts on item lists Questions: 1) Does Bing support it? 2) Is robots.txt the best way to handle it? Also canonical on the category / tab level should also solve this issue.

None of those are acceptible options. The only acceptible "fix" or "change" is appending the page number to the page title. Done. a 301 to fix incorrect "totals" in the URL is icing on the cake. Thats ALL that needs to be done. Canonical is not ment for different pages and content, google will just ignore the canonical…

Can anyone think of a way to add the following?: <META NAME="ROBOTS" CONTENT="NOINDEX, FOLLOW"> To the head section whenever the category page does one of the following: 1) Page forward / back 2) Sort Please let me know.

...JSESSONID is appended to all images, even if the user agent is a bot. That invalidates the cache... WOW -- great catch. I saw the JSESSIONID on the URL for the images but did not think about the impact on the cache on the user browser.

...attach you to the defect Defect 175288 ... I've created a support case and requested it be attached to defect 175288.

Ok, so support has decided to close 160747 as a duplicate of 159979. Point being, vote for 159979. If you previously voted for 160747 then confirm you vote moved to 159979.

The NetSuite case number is 930312. I am convinced that the proper implementation of this would create great spider food.

...We have products that show up at site.com/catalog/product and site.com/product, putting site.com/product as the canonical is useless because the site.com part is removed, leaving just the trailing /product. So to google, if its in the category page it will appear as if the site.com/catalog/product is the canonical, and…

What is the big deal? I've received some emails asking why canonical URL is important for Support KB, Topic and Solution. The obvious reason is that duplicate content and "link juice" bleed make it difficult to get proper ranking for specific pages. The not so obvious reason is my overall business goal for KB, Topic and…

100% definitive via support. There is not a canonical URL for the KB / topics / solutions. Please vote for enhancement 132027 which is for descriptive URL's for KB / topics / solutions. Not sure how I am going to band aid this. The issue is not so much the duplicate content but rather the "link juice" bleed caused by…

I've been told that google does not index NS pages with a query string at the end (www.mysite.com/item?sc=2&category=5587), but what about other people linking to you... if other webmasters link to these URLs, will it count as a link for the query-stringless page that is indexed by google (www.mysite.com/item) and will it…

...I've been checking it daily for several weeks and it hasn't changed... -T Tom - you might consider a weekly study or even a bi-weekly study; the results just will not appear that fast. Google is way to smart to make the changes that apparent for fear of manipulation.

Does this mean that now we are on 2010.1 we can make duplicate pages without any fear of penalisation now? Paul, IMHO there would be no penalty for 3-8 duplicate pages created by multiple URL's pointing to the same product. That said, it does create "internal link juice" bleed. The benefit of the canonical URL is to…

So I just got two pieces of hubba bubba. ;-) I guess the only way to handle this is to create one master KB, then place all topics inside that KB. Then try to use the canonical URL meta tag and set all of the topic's canonical to the "Master". Would anyone have any thoughts / ideas on this?

*** Bump *** Would someone from NetSuite address this? In the URL's below, I am guessing that the id represents the internal id of the solution which the kb represents the internal id of the kb the solution has been attached. http://www.DOMAIN.com/s.nl/ctype.KB/it.I/id.10/KB.209/.f…

Do a search in the users group for robots.txt. There has been quite a discussion on this topic. Netsuite should handle most of the parameters for you. This is our Robots.txt: ----------------------------------------------------------- #Block Googlebot-Image User-agent: Googlebot-Image Disallow: / User-agent: * #Disallow:…

There's a NS Knowledge base now? When? How? Lists | Support A good example can be found at http://www.htd.com/info/faq. They have done a great job of this.

...with url components like sc=1 and such. Refurbups, Have you seen many of these types of URL's showing in the search engines? Our site has a couple but not enough to worry me. sc=1 would not be presented to the spiders as Netsuite strips the parameters when it sees the User Agent is a known bot. This behavior started in…

...We are a little concerned if a NetSuite site will rank well with our competitors... Yeah it is always a challenge to compete with well funded competitors. That disclosure aside, there is nothing MAJOR preventing a NetSuite site from having a number one listing. I know this because my site has been #1 before. It is not…

does anyone one know how they seem to have custom layouts/templates on the knowledge base? I have been told this is not possible as the knowledge base inherits the default site templates. Unless they have made the site default template availabel for knowledge base and given every other category a different template? hmm…

<link rel="canonical" href="/Pittsburgh-Steelers-Super-Bowl-XLIII-Champs-Terrible-Beach-Towel" /> Dave, Just checked the page, unfortunately the jsessionID is showing: <link rel="canonical"…

Yes, well there isn't anything I can do about the session IDs, right? Honestly, I have not messed with it much BUT in my opinion, netsuite should be removing the jsessionid. I have not tested it on your site but it is my guess.