Hot answers tagged

8

Yes, you can. But it's not configurable. You need to override SitemapGenerator located in Sitecore.XA.Feature.SiteMetadata library. Most of the things are marked there as protected virtual so you shouldn't have problems with achieving what you want in your implementation. At the end just replace SXA implementation with your one in the DI container. This ...


8

I have done this before by using a custom handler to provide the sitemap. In the handler I used the SearchAPI to pull a list of all items that are derived from a _Sitemap template and that have the field in that template (Hide from Sitemap) set to false. The output of the handler is stored in the Sitecore HtmlCache, so on a publish the cache is cleared and ...


4

Have you tried the Ultimate Sitemap module? I'm not sure if you can schedule tasks for it out of the box to be honest. But I think you can get that with the Automated publisher module as well. I myself have tried the Ultimate Sitemap module and liked it to perform tasks like you described.


4

We have done this for several clients. I have added the alternate tags to the sitemap but that caused the sitemap to be too large and I didn't want to create multiple sitemaps. So we added the tag in the header. Then created a sitemap of just the English content because English was the default language. This way Google will be able to get to all the ...


4

During my journey with Sitecore starting from version 6.4, until now, I couldn't find a Sitecore feature that can build Sitemap XML for you automatically. You have few options: Use one of the Market place modules like Sitecore XML. It is an open source so you can extend it if required Upload your Sitemap XML file on media library and build your own IIS ...


3

If the different domains map 1 to 1 with a site node and those site nodes have different root paths then this should help. You should be able to make an extension method that finds the context site based on the root path like the following: public static SiteInfo GetSite(this Item source) { return Factory.GetSiteInfoList().FirstOrDefault( site =>...


2

I had to explicitly allow xml files using the Sitecore FilterUrlExtensions setting: <configuration xmlns:patch="http://www.sitecore.net/xmlconfig/"> <sitecore> <pipelines> <preprocessRequest> <processor type='Sitecore.Pipelines.PreprocessRequest.FilterUrlExtensions, Sitecore.Kernel'> <param desc="...


2

You can use redirect module : https://marketplace.sitecore.net/Modules/301_Redirect_module.aspx?sc_lang=en Github repository where you can get the code and to modify it: https://github.com/Chris-Castle/301RedirectModule On the redirect module you have the option to create rules for redirecting your requests to other landing pages.


2

TL;DR I think you forgot to extend Page template with appropriate field (_Sitemap) Current status Right now SXA (10 and lower) doesn't support officially Sitemap feature in JSS sites. There is no feature parity between SXA and JSS. Both are technically separate types of sites which have different set of scaffolding actions. You can compare what modules/...


2

From what I can see, sitemap.xml host is generated in the following order: If targetHostName site property is not empty, it's used. If hostName property doesn't contain wildcards (*) or multiple hostnames (joined with |), it's used. Otherwise request host name is used. The only scenario which would generate blank host name is when both targetHostName and ...


2

bgsi/public/group_scheme/index.jsp Sounds like Java Server Pages. Sitecore is based on .Net and doesn't use this page extension. That is why I assume that it could be added by some external sitemap(it is a built-in feature of SXA). I suggest you check external sitemap settings for your SXA website: Open Settings item under your root SXA website Look for &...


1

If you take a look at the current implementation of the SitemapGenerator service in Sitecore.XA.Feature.SiteMetadata.dll, there is a method GetFullUrl which renders the url in the sitemap protected virtual string GetFullLink(Item item, SitemapLinkOptions options) { string itemUrl = LinkManager.GetItemUrl(item, options.UrlOptions); return ...


1

I believe the reason why this was happening was because of SXA bug 393910: https://dev.sitecore.net/Downloads/Sitecore%20Experience%20Accelerator/10x/Sitecore%20Experience%20Accelerator%201000/Release%20Notes This is fixed in SXA version 10.0.0.


1

SXA supports multiple languages Sitemap from SXA 1.6- check the release notes here for more details- The SEO Sitemaps aggregate all the available sites under a single hostname, and support multiple languages 494598 9788 In your case you can customized the Sitemap XML generator for your SXA version, follow the below steps: 1) Create a new class that ...


1

Having done this in the past for a customer, we implemented a small bit of code on the layout that would find all versions published in other languages and build out link attributes in the header, like so: <link rel="alternate" hreflang="nl-NL" href="http://www.mycompany.nl/company/careers" /> <link rel="alternate" hreflang="pt-BR" href="http://...


Only top voted, non community-wiki answers of a minimum length are eligible