Sitemap - Add Manual

Vito Giovannetti

• September 11, 2020 22:44

Hi, We realized that the subdomain sitemap.xml wont work since we host off a different domain in AWS.

We haven't used Server Sync so we attempted to manually update the SiteMap.xml 

When we added it to Google Search Console. We bumped into the following errors.

What suggestions do you have for us. It would be great to export the xml each time we update and export the project.

0

• 

  Sandra Prunici

  • September 14, 2020 09:36

  Hi,

  Could you please check if you followed all the steps from this article?
  Thanks!

  Best regards,
  Sandra

  0
• 

  Vito Giovannetti

  • September 14, 2020 15:05

  Yes, this was the main article we followed. 
  
  However, because we can sync Brizy Cloud to our custom domain. It gives a sitemap that is only for Brizy Subdomain.
  
  What we did was manually change the domain on each line to work for our custom domain site map.
  
  Do you understand the challenge we are having now?
  
  
  

  0
• 

  Sandra Prunici

  • September 15, 2020 10:41

  Hi,

  It is a bit strange. Did you generate the sitemap.xml from the https://treasured.ca/sitemap.xml or from the URL of the Brizy Cloud project? Could you please inform us if you will find this problem again? 
  Thanks!

  Best regards,
  Sandra

  0
• 

  Vito Giovannetti

  • September 15, 2020 11:57

  Hi Sandra, 

  We first generated the sitemap.xml from the URL of the Brizy Cloud project (sub.domain). 

  Then we manually edited contents of the sitemap.xml to match our public domain (treasured.ca) 

  We need to make edits we were uncertain about to make Google Console accept the Sitemap.xml
  
  But now Google is recognizing issues crawling on some pages. 

  Can you help us generate the correct SiteMap.xml ?

  

   

  0
• 

  Sandra Prunici

  • September 15, 2020 14:23

  Hi, Vito,

  You have to generate the sitemap.xml when you already published the site on the treasured.ca. 
  For example you have to access this link https://treasured.ca/sitemap.xml and you will access the sitemap of the site. After this follow the next steps from this article https://support.brizy.io/hc/en-us/articles/360041720332-Sitemap-XML.

  Best regards,
  Sandra

  0
• 

  Vito Giovannetti

  • September 16, 2020 15:25

  Hi Sandra, 

  We are not hosting Treasured.ca on Brizy Cloud. We are hosting Treasured.ca on AWS S3. 

  In the past, when we exported our project from Brizy Cloud, the export does not have a sitemap.xml
  
  Therefore when we update our website on S3. We cant search an pull and update sitemap.xml as highlight in the article. 

  Does this make sense?

  0
• 

  Sandra Prunici

  • September 17, 2020 08:45

  Hi,

  Wait, I'm a bit confused. :) Could I ask you why do you can't generate the sitemap? Yes, we offer the sitemap for the Brizy Cloud sites but if you used the Server Sync (I gues you used this method because you said that the treasured.ca isn't hosted on Brizy Cloud but in the same time it has a custom domain) you have to generate the sitemap from the treasured.ca. It isn't correct to generate it from the Brizy Cloud and then to use this sitemap and add to the treasured.ca because they may be different. 

  Best regards,
  Sandra

  0
• 

  Vito Giovannetti

  • September 17, 2020 15:50

  Let me clarify 

  WE do not use Serve Sync, we can't run PHP. 

  We export HTML files and static host on AWS S3.
  
  When we export those files, the sitemap.xml is adapted to the subdomain that hosts the Brizy Cloud. 

  We could not find any automated way to generate this sitemap.xml, so we manually edited lines of the sitemap to adapt to our public page, Treasured.ca.
  
  However, when google search console, crawls it still spits back, errors. 
  
  Does this make sense? How do we address this issue?

  0
• 

  Sandra Prunici

  • September 17, 2020 16:28

  Hi,

  I mean the export HTML too, both Server Sync and Export HTML are user self-hosted publishing method. Therefore, what I said is available for export HTML publishing method too. Try to generate the sitemap.xml from  https://treasured.ca/sitemap.xml
  See here https://jmp.sh/WrlvHe1.

   

  0
• 

  Vito Giovannetti

  • September 18, 2020 01:01

  Hi Sandra,

  I am very very confused to say the least.... Please understand my issue.

  The instructions you have provided are not clear.

  1) I have export from Brizy Cloud.

  2) That folder does not include a sitemap
  
  3) When we upload static files, no sitemap is available or generated!!!!!!!!
  
  4) Thus we manually created one from the sub-domain on brizy, where we design the site.
  
  5) We then uploaded this manually edited sitemap to AWS S3 where the static sit is hosted.

  6) This manual way is not sustainable, when we are adding and refining pages weekly.
  
  7) If we upload the export directly to the static site and go to the URL your talking about (NOTHING EXISTS).
  
  8) As a result, we have to manually edit the one on brizy cloud with the subdomains, and add it to the exported folder before we upload the site to AWS

  9) This manually edited sitmap.xml has errors when google crawls it

  10) THUS we need a solution or more detailed instructions, on how to get a proper site map generated.

  Thanks in advance, your help is much appreciated

   

   

   

  0
• 

  Sandra Prunici

  • September 18, 2020 16:08

  Hi,

  I'm sorry. I confunded the lists. I discussed and concretised with one of our developers this detail and he said that at the moment for sites published with Export HTML and Server Sync method we don't generate the sitemap. We have it in our To-Do list and we will be added it in one of the future updates. 
  I'm sorry again for my mistake.
  Let us know if we can help you with something else.

  Best regards,
  Sandra

  0
• 

  Vito Giovannetti

  • September 18, 2020 16:10

  Thanks for the clarity Sandra, 
  
  You can help by explaining or producing a post that, shows how to manually edit the site map generated from the sub domain sitemap, to avoid errors. 

  0
• 

  Sandra Prunici

  • September 23, 2020 09:39

  Hi,

  I'm sorry but I think this is not possible. When the site is exported using one of the third-party publishing methods then we don't generate the sitemap and it can be affected/modified by the environment you added the site. Therefore we don't recommend to manually rewrite the sitemap you generated for the subdomain from Brizy Cloud. Soon we will add the sitemap for these publishing methods too and you will not face this problem.

  Thanks!

  Best regards,
  Sandra

  0
• 

  Hans De Graaf

  • November 13, 2023 09:10

  Hi, 3 years later and I still experience the same issues as in the thread above. At the same time, I get emails for voting on new functionalities. I would think it is logical to fix this omission in the product first. 

   

  0
• 

  Ariel H.

  • November 13, 2023 11:42

  Hi Hans,

  Thank you for reaching out to us.

  We understand your concern, and we've heard similar feedback from other users too. Rest assured, we have plans to tackle this issue in the upcoming updates. We're working on implementing a new approach that will resolve the problems related to syncing website content and automatically updating the sitemap.xml file.

  I apologize for the inconvenience.

  Best regards,
  Ariel H.

  0
• 

  Hans De Graaf

  • April 04, 2024 19:26
  • Edited

  Today I have experimented with different types of publishing options. When using server Sync method no sitemap is generated. I understand that. 
  
  But when you export to plain HTML, then now a sitemap is generated with references to the brizy subdomain version of my site. When I search for my most important keyword, both the site on my domain and the on the brizy website show up. This does hurt SEO because of duplicate content.
  
  I think it is very easy to solve this problem. Just add a field to enter the domain name (can be in the project settings OR as a popup when you hit the export to HTML button. And then ofcourse use that URL to build the right sitemap.xml. 
  
  For me, this kind of things really keep me from using Brizy Cloud and use other webbuilders instead.
  
  It's a long existing problems that hits many of your customers and the solution is so easy ....
  
  So, can we expect a solution now within, let's say, a month?
  
  FYI:  The SEO keyword is 'kerstzanger'.
  
  The website:  https://kerstzanger.nl
  
  The website referenced in the sitemap.xml:   https://kerstzanger.brizy.site
  
  The sitemap.xml content (from HTML export today, 04-04-2024):

  
  <?xml version="1.0" encoding="UTF-8"?><urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9
          http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd"><url><loc>https://kerstzanger.brizy.site/blog</loc><lastmod>2024-04-04T17:02:22+00:00</lastmod><changefreq>daily</changefreq><priority>1.0</priority></url><url><loc>https://kerstzanger.brizy.site/de-kerstzanger-boeken</loc><lastmod>2024-04-04T17:02:22+00:00</lastmod><changefreq>daily</changefreq><priority>1.0</priority></url><url><loc>https://kerstzanger.brizy.site/de-kerstzanger-contact</loc><lastmod>2024-04-04T17:02:22+00:00</lastmod><changefreq>daily</changefreq><priority>1.0</priority></url><url><loc>https://kerstzanger.brizy.site/de-kerstzanger-over</loc><lastmod>2024-04-04T17:02:22+00:00</lastmod><changefreq>daily</changefreq><priority>1.0</priority></url><url><loc>https://kerstzanger.brizy.site/de-kerstzanger-repertoire</loc><lastmod>2024-04-04T17:02:22+00:00</lastmod><changefreq>daily</changefreq><priority>1.0</priority></url><url><loc>https://kerstzanger.brizy.site/de-kerstzanger-tarieven</loc><lastmod>2024-04-04T17:02:22+00:00</lastmod><changefreq>daily</changefreq><priority>1.0</priority></url><url><loc>https://kerstzanger.brizy.site</loc><lastmod>2024-04-04T17:02:22+00:00</lastmod><changefreq>daily</changefreq><priority>1.0</priority></url></urlset>
  
  
  

  0
• 

  Ariel H.

  • April 05, 2024 10:51

  Hi Hans,

  My apologies for the inconvenience.

  We have also received a similar report, and we have escalated this issue to our senior support team for further investigation. It may take some time for them to look into this matter, but rest assured, we will reach out to you as soon as we receive an update from them.

  Best regards,
  Ariel H.

  0

Please sign in to leave a comment.