One of the new capabilities of SharePoint 2013 is the native support for Search Engine Optimization of public-facing websites. This article provides an overview of available capabilities as well as some architectural considerations.
SEO – you can’t do without it
When building public-facing websites you could assume that eventually your site will get indexed but it’s probably a better idea to ensure that your content will appear high in the organic search results. Search Engine Optimization (SEO) is the craft of optimizing public-facing websites for indexing by search engines.
From SEO perspective there are a number of things that you can do to improve the ranking of your content in organic search results. Some of them have to do with the content but there are a number of technology-related such as XML sitemaps or meta tags that you can use as well.
SEO and SharePoint 2010
Although SharePoint 2010 was a great and highly extensible platform for building public-facing websites, it didn’t offer any out of the box support for Search Engine Optimization of websites. To close the gap in the past two years we have built here at Mavention a number of solutions that can help you extend your public-facing website with SEO capabilities. Using solutions such as Mavention XML Sitemap, Mavention Meta Fields or Mavention Robots.txt you could add the missing functionality to SharePoint 2010 and get more out of your public-facing website built in SharePoint 2010.
SEO in SharePoint 2013
One of the new WCM-related capabilities in SharePoint 2013 is native support for Search Engine Optimization. Following is the overview of what SEO functionality SharePoint 2013 offers.
SEO Properties for Publishing Pages
SharePoint 2013 allows you to provide SEO Properties for your Publishing Pages. On a Publishing Page you can open the Ribbon, activate the Page tab and then from the Manage group, open the options under the Edit Properties button and choose the Edit SEO Properties option.
This will take you to the SEO Properties page where you can manage SEO-related data of your page.
The great thing is that all of those properties are stored as Site Columns so you can retrieve them in code but you can also have them made available in search if you’re using Cross-Site Collection Publishing.
The following SEO Properties can be set on a Publishing Page:
- Title (Title field): page title on the page and in the navigation
- Browser Title (SeoBrowserTitle field): page title in the title bar of the browser. Also used in organic search results
- Meta Description (SeoMetaDescription field): meta description. Used sometimes in organic search results
- Keywords (SeoKeywords field): meta keywords. Rarely used by public search engines
- Sitemap Priority (SitemapPriority field). Used when generating XML Sitemap
- Sitemap Change Frequency (SitemapChangeFrequency field). Used when generating XML Sitemap
- Exclude from Internet Search Engines (RobotsNoIndex field). If set renders meta robots noindex
All underlying Site Columns and UI are installed by the SearchEngineOptimization Feature (ID: 17415B1D-5339-42F9-A10B-3FEF756B84D1) which is activated for Publishing Sites by default.
SEO Properties for Terms
One of the new capabilities of SharePoint 2013 is Managed Navigation where you can define the navigation of your website using a Term Set. The same SEO properties as available on Publishing Pages can be set on Terms. The difference is that the values are stored in Local Custom Properties of each Term. Following is the mapping of SEO Properties and Custom Local Term Properties:
- Browser Title: _Sys_Seo_PropBrowserTitle
- Meta Description: _Sys_Seo_PropDescription
- Keywords: _Sys_Seo_PropKeywords
- Sitemap Priority: _Sys_Seo_PropSitemapPriority
- Sitemap Change Frequence: _Sys_Seo_PropSitemapUpdateFrequency
- Exclude from Internet Search Engines: _Sys_Seo_PropSitemapNoIndex
Canonical URLs
An important step in optimizing your website for search engines is specifying the canonical URL. The canonical URL is the URL that uniquely identifies the content of the page and which is stored in the index of search engines. By properly configuring canonical URLs you can prevent duplicated content from being indexed.
SharePoint 2013 automatically generates for you the canonical URL. The only thing that you might want to configure are the query string parameters that you want to exclude from the canonical URLs. This can be configured in the Site Collection SEO Settings.
Site Collection SEO Settings
Aside from specifying SEO Properties for particular Publishing Pages and Terms, SharePoint 2013 allows you to define meta tags on the Site Collection-level. Those are very useful for example if you need to verify the ownership of your website with web analytics services on the Internet.
Site Collection SEO Settings can be configured through Site Settings > Site Collection Administration > Search engine optimization settings.
On the SEO Settings page you can specify custom meta tags that will be added to all pages as well as you can define query string parameters that should be excluded from canonical URLs.
Rendering SEO Properties
After SEO Properties have been configured, some of them are rendered in the HTML to be processed by search engines while crawling the content. Rendering of SEO Properties is being done by a number of delegate controls that are activated by the SearchEngineOptimization Feature. All those controls are associated with the AdditionalPageHead Delegate Control so you want to ensure that you have it present on your Master Page if you want to use the standard SharePoint 2013 SEO capabilities on your website.
Following is the overview of Delegate Controls responsible for rendering SEO properties on the page. All of those controls are located in the Microsoft.SharePoint.Publishing assembly in the Microsoft.SharePoint.Publishing.WebControls namespace.
- Browser Title: SeoBrowserTitle
- Meta Description: SeoMetaDescription
- Keywords: SeoKeywords
- Exclude From Internet Search Engines: SeoNoIndex
- Canonical URL: SeoCanonicalLink
- Custom Meta Tags (defined at Site Collection-level): SeoCustomMeta
XML Sitemap
One of the great gaps in SharePoint 2010 was the lack of a mechanism that would generate XML Sitemap. By submitting an XML Sitemap to search engines you can help them discover content on your website.
SharePoint 2013 provides native support for generating XML Sitemaps. In order to have an XML Sitemap generated for your website you first have to enable the Search Engine Sitemap Site Collection Feature. This will register the Site Collection with the Search Engine Sitemap job Timer Job which by default runs daily and generates an XML Sitemap for every Site Collection that has been registered with that Timer Job.
The Search Engine Sitemap job generates not only the XML Sitemap itself but also modifies the robots.txt file where it adds the link for the XML Sitemap file so that it can be easily discovered by search engines.
Friendly URLs
One of the great improvements in SharePoint 2013 for Web Content Management it the separation of URLs and site hierarchy. Using Managed Navigation you can now define the structure of your site and by tagging the content with the right terms you can ensure that the content will be published at the right location in your website.
Using Managed Navigation allows you to use friendly URLs: URLs without /pages/ and .aspx. Additionally Welcome Pages of Webs are served from the web URL so you will see neither /pages/default.aspx nor 302 Temporarily Moved redirects anymore!
Architectural Considerations
The Search Engine Optimization capabilities of SharePoint 2013 can help you improve the ranking of your content in organic search results. There are however a few things that you should take into account while designing for SEO in your public-facing website on SharePoint 2013.
It’s all or nothing
Search Engine Optimization functionality of SharePoint 2013 is provided as a single functional unit. When you enable the SearchEngineOptimization Feature you will deploy all Site Columns, enable the UI and activate all Delegate Controls. By default there is no way for you to choose which components you would like to use. One way to work around this limitation would be to create your own Feature to for example enable only specific Delegate Controls.
It’s internal
In SharePoint 2013 Preview the SEO capabilities are not extensible. All of the API is internal and cannot be used in your solutions. With that it’s impossible to modify or extend any of the default behavior and should you need it, you would have to build everything from scratch yourself.
Rendering SEO Properties
All SEO Properties are rendered using Delegate Controls associated with the AdditionalPageHead Delegate Control. If you want to have your SEO Properties rendered you have to ensure that this Delegate Control is present in your Master Page.
Browser Title
The Browser Title SEO Property is rendered using the SeoBrowserTitle control. After this control retrieves the Browser Title, it will look for the PlaceHolderPageTitle Content Placeholder and replace all its content with the Browser Title! This means that if you want to use hierarchical titles on your website, you have add parent hierarchy in the Master Page outside the PlaceHolderPageTitle Content Placeholder for the SeoBrowserTitle not to overwrite it.
XML Sitemap
For the XML Sitemap to be generated it requires anonymous access on the Default Zone of the Site Collection for which it’s generating the XML Sitemap. Additionally in SharePoint 2013 Preview there is a bug with generating the URLs. While building the XML Sitemap the Timer Job replaces the URL of the Default Zone of the Site Collection by the URL of the Internet Zone which, if not explicitly set, falls back to the SPSite.Url property. Because the SPSite.Url property doesn’t contain a trailing slash the replaced URL doesn’t contain a slash after the host name and before the path name which results in an invalid URL.
Friendly URLs
Publishing Pages that have friendly URLs can still be requested using their physical URLs. If not dealt with properly this can lead to content duplication, particularly as in SharePoint 2013 Preview the canonical URL changes alongside and renders the physical URL of the page.
Summary
SharePoint 2013 provides native support for Search Engine Optimization of public-facing websites for Internet Search Engines. In this article I have showed you what the new SEO capabilities are, how they work and how you can benefit of them when building public-facing websites on SharePoint 2013.
July 22nd, 2012 at 4:33 pm
Waldek,
Fantastic content as always, thanks for sharing the new WCM capabilities native to SP2013!
Ryan
September 9th, 2012 at 1:02 pm
Well written Waldek, I always like reading your blog as you manage to make complicated stuff come across understandable.
Thanks,
Maarten
September 13th, 2012 at 7:51 am
Thank you!
September 24th, 2012 at 7:27 am
good feature. nicely explained. Thanks
October 13th, 2012 at 9:30 am
Hi
Great Post. do you know where the sitemap xml file is generated and if it is possible to generate the site map using Managed metadata navigation?
October 14th, 2012 at 8:39 pm
The XML Sitemap is generated as an XML file in the root of your Site Collection. It supports Managed Navigation out of the box.
October 15th, 2012 at 10:29 am
I cannot find it. the only file i can find is robots.txt
What is the path for the sitemap.xml
Is there any possible configurations to manage the output of the site map file?
Thanks
October 15th, 2012 at 3:44 pm
No, there is no configuration and the file is always generated in the same place. Since you cannot find the file I suggest you take a look at the ULS log to find if there are any errors in the process of generating the XML Sitemap.
October 18th, 2012 at 4:34 pm
i have discovered it is failing because i have host header in the web application. is it wired that this feature doesn't work host headers?!! which is a typical scenario for public facing site
While getting public site Url, unable to use SPSite.GetUrls(). Using fallback Url: 'The site collection is not in host header mode.' 9cbcd79b-cb03-4036-b38b-a2abadd46472
CatalogConfig.ReadFromPropertyBag; Catalog configurations don't exist for site collection
October 20th, 2012 at 12:56 pm
I wouldn't say it's a typical scenario because the configuration really depends on what you are trying to achieve and as well as I've seen customers using dedicated Web Applications I've also seen many using Host Named Site Collections. Remember that you are using preview software and there might be bugs. If you have a possibility I'd suggest you file the bug. This will help you ensure that everything work as expected once SharePoint is released.
October 29th, 2012 at 6:53 pm
Great Post.
There are a couple of issues I found with 2010, are these still present in 2013?
-does SharePoint still generate lots of pages you don’t want in the SERPs (auth pages, list pages etc) or does it easily allow you to exclude them?
-can you remove the home.aspx from the home page so it is just /?
Some of these new features will make my life a bit easier. Thanks for a detailed post.
October 29th, 2012 at 6:57 pm
1. Yes, although there are many ways in which you could prevent those pages from being picked up by search.
2. Yes, it's out of the box and you don't have to do anything for this.
December 9th, 2012 at 9:28 pm
Hi,
Thanks for knowledge sharing.
I have a book.xml with 3 books records in SP 2013 document lib. How to crawl this xml as a single-2 records means 3 doc should index.
I tried but its indexing xml as a single record. XML e.g.
SP search
FAST search
SP Guide
December 10th, 2012 at 1:15 pm
Have you seen this article: http://blogs.msdn.com/b/xml_connector_for_sharepoint_2013/archive/2012/10/01/xml-connector-for-sharepoint-2013.aspx?
January 28th, 2013 at 5:12 pm
I have the following problem. A client is using sharepoint. When I visit the website and don't accept cookies, and get an endless 302 moved loop, delivered by the files InternalError.asp. It tries to set a certain uniquesig I guess. If I refresh a couple of times, I also get a 500 error.
I assume it has something to do with UAG and found this article which perfectly describes the problem i'm having:
http://blogs.technet.com/b/ben/archive/2011/10/25/uag-and-stateless-clients.aspx
I cannot spider the website with Screaming Frog of other automated software because of this issue. The thing is, Google has indexed it perfectly without problems. Would this be a case of IP delivery, or can Google handle these cookies suddenly?
Unfortunately I cannot reveal the clients name or URL.
Thanks in advance,
January 29th, 2013 at 7:53 am
Yes, I have seen this situation as well, where UAG was causing infinite loop with cookies disabled in browser. I'm not sure about how Google retrieves pages and which web capabilities (and to what extent) such as cookies and JavaScript it supports. When it comes to using external software you might be limited by their support of cookies, but if you're building code yourself you can definitely get this to work. The only thing that you need to do is to ensure that you're passing the cookies received from UAG on the first request with every consecutive request.
January 29th, 2013 at 5:12 pm
Yeah, I know. The lack of cookie-support is causing the external software to fail its crawl. I was just wondering if you knew any cases like this that caused indexing issues with Google.
I guess Google is perfectly capable of handling cookies these days ;-)
March 7th, 2013 at 10:15 am
I tried to generate sitemap.xml
and my site map look like
http://seoproperties:2001/sitemap0.xml
http://seoproperties:2001/sitemap_mobile0.xml
in log I get these errors
SiteServicesAddins.ReadFromPropertyBag: Site services addins don't exist for site collection
CatalogConfig.ReadFromPropertyBag; Catalog configurations don't exist for site collection
March 7th, 2013 at 1:32 pm
What is your question exactly?
March 7th, 2013 at 1:39 pm
My question is my sitemap is not generating properly.
I edited SEO Properties of my Home.aspx page in Pages library and checked in with Publish.
Then I run Search Engine Sitemap Job. but i can't find my Home.aspx in sitemap.xml
Configuration I did,
Services Running: All except Load Balancing
Site template: Publishing Portal
Site Coll Feature Activated: SEO.
and make Search Engine Sitemap job to run every Hour
March 7th, 2013 at 1:41 pm
The XML Sitemap generation process uses Search to generate the XML Sitemap. Have you crawled your site and verified that your pages have been indexed?
March 7th, 2013 at 1:44 pm
yes I started Full Crawl and then running Search Engine Sitemap job.
March 15th, 2013 at 12:12 pm
Hi,
Finally understand the issue when i had a meeting with one SEO guy. Problem is in sitemap.xml it shows the sitemap url where the actual sitemap stores in my example, Actual sitemap stores in http://seoproperties:2001/sitemap0.xml
and sitemap.xml shows sitemapindex tag.
Thanks for this great information.
March 15th, 2013 at 12:29 pm
Hi Waldek Mastykarz,
Yesterday I found this (Link given Below) post and i saw that i can give seo properties to metadata in term store management. But unluckily i was not able to see SEO Properties option in my Term store management. Am I missing any features?
http://www.shailwx.com/2012/07/sharepoint-2013-real-world-branding-part-3-navigation/
March 18th, 2013 at 7:57 am
This article refers to the UI of the beta version of SharePoint 2013. In RTM this UI has been moved to the Ribbon. To edit the SEO properties of the particular term, navigate in the browser to the page associated with that term, and then from the Ribbon, open the drop-down list under the Edit Properties button and click the Edit SEO Properties option.
March 18th, 2013 at 8:23 am
Thanks for the info. But my main goal is to set Sitemap Priority. Which i am not able to set using Edit SEO Properties.
March 18th, 2013 at 8:25 am
Unfortunately the ability to set the Sitemap priority has been removed in SP2013 RTM.
March 26th, 2013 at 3:15 pm
Hi. Have you discovered a way that when using managed metadata navigation to expose the SEO properties (description, keywords etc) on the page layout so they are editable inline? All the field names u have suggested above return blank.
March 27th, 2013 at 5:35 pm
Unfortunately not. Depending on what type of navigation you're using those properties end up either as fields or as properties. So far I haven't managed to find a workable alternative around the standard behavior.
March 28th, 2013 at 12:32 pm
Ok thanks. When using managed navigation I expected the keywords and metatags to attach to the terms in the term store but I could not see the custom properties attached. They are also not stored in the site columns. I think a custom control solution may be required. Thanks for the reply. :)
March 28th, 2013 at 1:12 pm
They are stored as properties on the terms but since those properties are prefixed with '_Sys' they are not visible in the UI. You should be able to see them using PowerShell though.
March 30th, 2013 at 5:59 am
Hello
I Generated Sitemap thanks for this info. But Sitemap is not generated in proper way means as per metadata hierarchy. All Pages comes in straight way not in hierarchy. So having problem in showing SiteMap page using this sitemap functionality. Is there any workarround for that?
March 30th, 2013 at 11:30 pm
Two questions: are you using Managed or Structural Navigation and if you're using Managed Navigation have you enabled on all pages the property to hide the physical URL from search?
April 1st, 2013 at 7:51 am
Managed navigation and yes Hide the physical URL is hidden from search…
April 2nd, 2013 at 6:00 am
Do you see Friendly URLs or Physical URLs in your XML Sitemap?
April 2nd, 2013 at 6:17 am
i am seeing Physical URLs in sitemap0.xml
April 2nd, 2013 at 6:23 am
And if you open the contents of the sitemap0.xml, what do you see there?
April 2nd, 2013 at 6:48 am
I can see below mentioned xml
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<!–Generated: 2013-04-01T15:52:48–>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>http://sp2013-03:6666/en-in/Pages/UploadResume.aspx</loc>
<lastmod>2013-03-19T07:30:11Z</lastmod>
</url>
April 2nd, 2013 at 6:50 am
Is this the only URL that you are seeing? If so, it would seem that you haven't configured search properly to have your site crawled. XML Sitemap depends on SharePoint 2013 Search so in order for your pages to appear in the XML Sitemap they must be indexed by search.
April 2nd, 2013 at 7:17 am
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<!–Generated: 2013-04-01T15:52:48–>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>http://sp2013-03:6666/en-in/Pages/UploadResume.aspx</loc>
<lastmod>2013-03-19T07:30:11Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Pages/sitemap.aspx</loc>
<lastmod>2013-03-16T08:14:54Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/News-Events/Pages/News-2.aspx</loc>
<lastmod>2013-03-11T13:42:12Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/News-Events/Pages/News-1.aspx</loc>
<lastmod>2013-03-11T13:42:12Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Web-Application-Development.aspx</loc>
<lastmod>2013-03-12T18:23:46Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Software-Testing.aspx</loc>
<lastmod>2013-03-11T12:24:27Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Software-Development.aspx</loc>
<lastmod>2013-03-12T10:47:43Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Social-Media-Optimization.aspx</loc>
<lastmod>2013-03-12T10:47:42Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Search-Engine-Optimization.aspx</loc>
<lastmod>2013-03-12T10:47:42Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Reputation-Management.aspx</loc>
<lastmod>2013-03-12T10:47:42Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Product-Development0312-9454.aspx</loc>
<lastmod>2013-03-12T18:20:52Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Product-Development.aspx</loc>
<lastmod>2013-03-12T18:20:52Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/PPC-Mangaement.aspx</loc>
<lastmod>2013-03-12T18:20:51Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Portal-Development.aspx</loc>
<lastmod>2013-03-12T18:20:51Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Offshore-Development.aspx</loc>
<lastmod>2013-03-12T18:20:51Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/New-application-development.aspx</loc>
<lastmod>2013-03-12T18:20:51Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Legacy-Migration.aspx</loc>
<lastmod>2013-03-12T18:20:50Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Existing-development-enhancement.aspx</loc>
<lastmod>2013-03-12T18:20:50Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Enterprise-Services.aspx</loc>
<lastmod>2013-03-12T18:20:50Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Enterprise-Content-Management.aspx</loc>
<lastmod>2013-03-12T18:20:50Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Engineering-Services.aspx</loc>
<lastmod>2013-03-12T18:20:49Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/End-user-services.aspx</loc>
<lastmod>2013-03-12T18:20:49Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Embedded-Systems.aspx</loc>
<lastmod>2013-03-12T18:20:49Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Desktop-%EF%BC%86-Systems-Management.aspx</loc>
<lastmod>2013-03-12T18:20:49Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Desing-Solution.aspx</loc>
<lastmod>2013-03-12T18:20:49Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Data-Center-Services.aspx</loc>
<lastmod>2013-03-12T18:20:48Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Customized-Application-Development.aspx</loc>
<lastmod>2013-03-12T18:20:48Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Content-Management-Systems.aspx</loc>
<lastmod>2013-03-12T18:20:48Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Content-Management–Collaboration.aspx</loc>
<lastmod>2013-03-12T18:20:47Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Collaborative-Application.aspx</loc>
<lastmod>2013-03-12T18:20:47Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Cloud-Computing.aspx</loc>
<lastmod>2013-03-12T18:20:47Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Business-IT-Services.aspx</loc>
<lastmod>2013-03-12T18:20:46Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Business-Intelligence-and-Analytics.aspx</loc>
<lastmod>2013-03-12T18:20:46Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Business-continuity-and-resiliency-services.aspx</loc>
<lastmod>2013-03-12T18:20:46Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Business-Application-Services.aspx</loc>
<lastmod>2013-03-12T18:20:46Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Applications-On-Cloud.aspx</loc>
<lastmod>2013-03-12T18:20:45Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Application-Lifecycle-Management-Services.aspx</loc>
<lastmod>2013-03-12T18:20:45Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Application-Integration-Services.aspx</loc>
<lastmod>2013-03-12T18:20:45Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/ITServices/Pages/Application-Development-and-maintenance.aspx</loc>
<lastmod>2013-03-12T18:20:45Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/windows-azure-sdk.aspx</loc>
<lastmod>2013-03-12T18:18:02Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/windows-azure-portal.aspx</loc>
<lastmod>2013-03-12T18:18:02Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/windows-azure-platform.aspx</loc>
<lastmod>2013-03-12T18:18:01Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/windows-azure-development.aspx</loc>
<lastmod>2013-03-12T18:18:01Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/windows-azure-cloud.aspx</loc>
<lastmod>2013-03-12T18:18:01Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/Windows-Azure.aspx</loc>
<lastmod>2013-03-12T18:18:00Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/SharePoint-Consulting.aspx</loc>
<lastmod>2013-03-12T18:18:00Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/SAP.aspx</loc>
<lastmod>2013-03-12T18:18:00Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/Professional-Services-Automation-(PSA).aspx</loc>
<lastmod>2013-03-12T18:18:00Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/Oracle.aspx</loc>
<lastmod>2013-03-12T18:17:59Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/Mobile-office-web-app.aspx</loc>
<lastmod>2013-03-12T18:17:59Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/Microsoft-Dynamics-SL-(Solomon).aspx</loc>
<lastmod>2013-03-12T18:17:58Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/Microsoft-Dynamics-RMS.aspx</loc>
<lastmod>2013-03-12T18:17:58Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/Microsoft-Dynamics-NAV-(Navison).aspx</loc>
<lastmod>2013-03-12T18:17:58Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/Microsoft-Dynamics-GP-(Great-Plains).aspx</loc>
<lastmod>2013-03-12T18:17:57Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/Microsoft-Dynamics.aspx</loc>
<lastmod>2013-03-12T18:17:57Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/GEO-location.aspx</loc>
<lastmod>2013-03-12T18:17:57Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/enterprise-resource-planning.aspx</loc>
<lastmod>2013-03-12T18:17:57Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/Enterprise-content-management.aspx</loc>
<lastmod>2013-03-12T18:17:57Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/DNS-Management.aspx</loc>
<lastmod>2013-03-12T18:17:56Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/Digital-Business.aspx</loc>
<lastmod>2013-03-12T18:17:56Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/Desktop-applications.aspx</loc>
<lastmod>2013-03-12T18:17:56Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/Case-Management.aspx</loc>
<lastmod>2013-03-12T18:17:56Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/Business-technology-consulting.aspx</loc>
<lastmod>2013-03-12T18:17:56Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/Business-Intelligence-Solution.aspx</loc>
<lastmod>2013-03-12T18:17:55Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/Business-Applications.aspx</loc>
<lastmod>2013-03-12T18:17:55Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/Branding-Strategies.aspx</loc>
<lastmod>2013-03-14T13:10:43Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/Asset-Management.aspx</loc>
<lastmod>2013-03-12T18:17:55Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/BusinessSolutions/Pages/Agile-methodology.aspx</loc>
<lastmod>2013-03-12T18:17:54Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Web-Research-Services.aspx</loc>
<lastmod>2013-03-12T11:38:22Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Virtual-Assistant-Services.aspx</loc>
<lastmod>2013-03-12T11:38:21Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Utilities-BPO.aspx</loc>
<lastmod>2013-03-12T18:24:06Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Transition-management.aspx</loc>
<lastmod>2013-03-12T18:24:06Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Transcription-Services.aspx</loc>
<lastmod>2013-03-12T18:24:06Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Tools-and-processes.aspx</loc>
<lastmod>2013-03-12T18:24:06Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Procurement-BPO.aspx</loc>
<lastmod>2013-03-12T18:24:05Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Outcome-based-model.aspx</loc>
<lastmod>2013-03-12T18:24:05Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Network-BPO.aspx</loc>
<lastmod>2013-03-12T18:24:05Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Market-Research-Services.aspx</loc>
<lastmod>2013-03-12T18:24:04Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/MANAGED-IT-SERVICES.aspx</loc>
<lastmod>2013-03-12T18:24:04Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Legal-Process-Outsourcing-LPO.aspx</loc>
<lastmod>2013-03-12T18:24:04Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Insurance-BPO.aspx</loc>
<lastmod>2013-03-12T18:24:04Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Infrastructure-Outsourcing.aspx</loc>
<lastmod>2013-03-12T18:24:03Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Health-Administration-BPO.aspx</loc>
<lastmod>2013-03-12T18:24:03Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Global-Delivery.aspx</loc>
<lastmod>2013-03-12T18:24:03Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Full-IT-outsourcing.aspx</loc>
<lastmod>2013-03-12T18:24:02Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Financial-Accounting,-Bookkeeing-Services.aspx</loc>
<lastmod>2013-03-12T18:24:02Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Finance-and-Accounting-BPO.aspx</loc>
<lastmod>2013-03-12T18:24:02Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Exchange-Server-Hosting.aspx</loc>
<lastmod>2013-03-12T18:24:02Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Email-Filtering.aspx</loc>
<lastmod>2013-03-12T18:24:01Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Document-Scanning-Services.aspx</loc>
<lastmod>2013-03-12T18:24:01Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Document-Indexing-Services.aspx</loc>
<lastmod>2013-03-12T18:24:01Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Disaster-RecoveryBusiness-Continuity.aspx</loc>
<lastmod>2013-03-12T18:24:01Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Desktop–Server-Deployment.aspx</loc>
<lastmod>2013-03-12T18:24:01Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Data-Processing-Services.aspx</loc>
<lastmod>2013-03-12T18:24:00Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Data-Entry-Services.aspx</loc>
<lastmod>2013-03-12T18:24:00Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Data-Conversion-Services.aspx</loc>
<lastmod>2013-03-12T18:24:00Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Capacity-Services.aspx</loc>
<lastmod>2013-03-12T18:24:00Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Business-Process-Outsourcing.aspx</loc>
<lastmod>2013-03-12T18:24:00Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Outsourcing/Pages/Bundled-Outsourcing.aspx</loc>
<lastmod>2013-03-12T18:23:59Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Pages/Search.aspx</loc>
<lastmod>2013-03-13T04:50:45Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Pages/Partners.aspx</loc>
<lastmod>2013-03-14T06:21:05Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Pages/Media-Room.aspx</loc>
<lastmod>2013-03-12T14:17:23Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Pages/Locations.aspx</loc>
<lastmod>2013-03-12T14:17:23Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Pages/Investor-Relation.aspx</loc>
<lastmod>2013-03-12T14:17:22Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Pages/Core-Values.aspx</loc>
<lastmod>2013-03-12T14:17:22Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Pages/Contact-Us.aspx</loc>
<lastmod>2013-03-13T03:58:21Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Pages/Company-Overview.aspx</loc>
<lastmod>2013-03-12T14:17:22Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Pages/Clients.aspx</loc>
<lastmod>2013-03-14T06:20:42Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Pages/Banner-Check.aspx</loc>
<lastmod>2013-03-11T12:12:57Z</lastmod>
</url>
<url>
<loc>http://sp2013-03:6666/en-in/Pages/About-Us.aspx</loc>
<lastmod>2013-03-12T14:17:21Z</lastmod>
</url>
</urlset>
April 2nd, 2013 at 7:24 am
Have you configured Friendly URLs for all those pages?
April 2nd, 2013 at 7:41 am
yes, I did configured friendly URLs for each…
April 2nd, 2013 at 7:55 am
Have you verified that the pages are available using the friendly URLs and have you recrawled your site?
April 2nd, 2013 at 8:13 am
Yes checked several times (as have managed navigation) and crawled it many times too
April 2nd, 2013 at 8:29 am
Have you configured to hide the physical URLs from search on every single page?
April 2nd, 2013 at 8:48 am
yes…
April 2nd, 2013 at 8:54 am
That's odd. Have you tried resetting your search index? What results are you getting if you trying to search for a page: are you getting the Physical URL or the Friendly URL?
April 2nd, 2013 at 9:12 am
Will try reset after some time and when I search I get the same URL as Sitemap.