The Google Search Console creates URLs that are not in my sitemap, and then complains that these pages are broken

You have a wrong idea of ​​what a sitemap is.

The sitemap is used to monitor the crawling of the site by the search engine bot. The sitemap and crawling a site are two different and independent things. Google continues to search your site independently of the sitemap. The sitemap is used to check if Google can properly crawl your site. For example, if pages are found in your sitemap and Google has not seen the page, Google may add the page to the fetch queue to include.

The opposite is not true. If a page is not found in the sitemap, Google will not remove it from the index. Why? Because Google found it by crawling the site.

What you seem to believe is that the sitemap is the absolute authority Google uses to identify which pages exist on a particular site. That's not the case. The crawl is. The sitemap only helps Google to know if You can properly crawl your site, and if not, what pages Google is missing that should be added to the fetch queue.

Your expectation that Google will stop trying to access pages because these pages are no longer in your sitemap is wrong. Sitemaps are cached and checked at regular intervals. Why? Because it is a testing process.

You have a real problem that you need to solve.

You return a 500 error for pages that were not found. This is bad. Your website should return a 404 Not Found error. The 500 error is a system error and is treated as temporary by Google. If your site returns a 404 error, Google will still try the page a few times over a period of time, until it finds that the page no longer exists. If possible, you want to output a 410 Removed error for pages that you have removed. If this is too much work or not possible, the 404 will mean the same over time.

You must fix your 500 error.

Google Search Console creates URLs that do not exist in my Sitemap, and then complains that these pages are broken

You have a wrong idea of ​​what a sitemap is.

The sitemap is used to monitor the crawling of the site by the search engine bot. The sitemap and crawling a site are two different and independent things. Google continues to search your site independently of the sitemap. The sitemap is used to check if Google can properly crawl your site. For example, if pages are found in your sitemap and Google has not seen the page, Google may add the page to the fetch queue to include.

The opposite is not true. If a page is not found in the sitemap, Google will not remove it from the index. Why? Because Google found it by crawling the site.

What you seem to believe is that the sitemap is the absolute authority Google uses to identify which pages exist on a particular site. That's not the case. The crawl is. The sitemap only helps Google to know if You can properly crawl your site, and if not, what pages Google is missing that should be added to the fetch queue.

Your expectation that Google will stop trying to access pages because these pages are no longer in your sitemap is wrong. Sitemaps are cached and checked at regular intervals. Why? Because it is a testing process.

You have a real problem that you need to solve.

You return a 500 error for pages that were not found. This is bad. Your website should return a 404 Not Found error. The 500 error is a system error and is treated as temporary by Google. If your site returns a 404 error, Google will still try the page a few times over a period of time, until it finds that the page no longer exists. If possible, you want to output a 410 Removed error for pages that you have removed. If this is too much work or not possible, the 404 will mean the same over time.

You must fix your 500 error.

Google Search Console – Where can I put my sitemap in my directory structure under Laravel? It is 404 in the root directory

If you look at your directory structure, there seems to be as many (all?) Files in the root of the document as you have uploaded sitemap.xml) are not accessible – all return 404 Not Found when publicly accessed.

It looks like this is a Laravel app and you may write everything in the new one /public Subdirectory (a typical usage pattern with Laravel). In that case you should move sitemap.xml (and any other files that should be publicly accessed) /public Subdirectory.

To confirm this, we would have to see the contents of your root .htaccess File. (Please edit your question to record this.)

TO UPDATE: Your .htaccess File confirms the above.

RewriteRule ^$ public/ (L)
RewriteRule (.*) public/$1 (L)

From your .htaccess File in the document root we can see that all Requests are rewritten in the /public Subdirectory. So a request for example.com/sitemap.xml is rewritten internally to example.com/public/sitemap.xml,

This means that your document root "effectively" /home/winnerrs/public_html/publicNot /home/winnerrs/public_htmlas you first thought.

You have to move that sitemap.xml File from the public_html Directory for public_html/public Directory.

seo – change picture name or create a picture sitemap? Or both?

The Environment is a classifieds site offering products with descriptions, titles and photos. With the exception of images, all data is stored in a MySQL database.

Although there are friendly titles of classifieds and it is relatively easy to link to them, all images are saved with randomly generated names (something like d6as897d6ad67a5s7da8d56sa7d.jpg).

The question is, for SEO, PAGE RANKING and SERP, which is the best and why?

  • Change the image names from random characters to classified titles.
  • Create image sitemap;
  • Both.

What are the advantages and disadvantages? And why not choose the other options? Are there any other alternatives that I have not mentioned here?

SEO – How can I index Sitemap of my website?

I would like to optimize the sitelink on my website via the search console / webmaster

I want to search on google that certain menus appear. For example, menus, a, menu b and menu c

I'm looking for some references. To be able to set using the search console, only a sitemap.xml is required, which is searched first

So I accessed this https://www.xml-sitemaps.com/. I enter my domain and click on the start button. After the process is complete, I downloaded the Sitemap file

my question is if i upload the xml file directly to my hosting? or do I have to edit it first to determine which menus to display when entering keywords in Google?

update:

My xml as follows:







  https://www.mywebsite.com/
  2019-10-13T23:46:01+00:00
  1.00

...

  https://www.mywebsite.com/menu-a
  2019-10-13T23:46:01+00:00
  0.80

...

  https://www.mywebsite.com/menu-b
  2019-10-13T23:46:01+00:00
  0.64




There are 2000 lines of code, but here are just a few

SEO – Google can not retrieve a large sitemap with 50,000 URLs and is not rendered by browsers

My sitemap contains 50,000 URLs / 7.8 MB and the following URL syntax:




 https://www.ninjogos.com.br/resultados?pesquisa=vestido, maquiagem,   2019-10-03T17:12:01-03:00 
 1.00 


The problems are:

• The search console reports that the sitemap could not be read.

• Sitemap loading takes 1 hour and Chrome stops working.

Enter image description here

• In Firefox, the sitemap was downloaded in 1483 ms and fully loaded after 5 minutes.

Things that I have done without success:

• Disable GZip compression.

• Delete my .htaccess file;

• Create a test sitemap with 1 KB URLs and the same syntax, and send it to Search Console. However, the sitemap with 50 KB URLs still displays "" that no sitemap can be retrieved.

Enter image description here

• An attempt was made to directly check the URL, but an error occurred and you are asked to try again later while the 1KB URLs worked.

• An attempt was made to validate the sitemap on five different websites (YANDEX, ETC), and all worked without error / warning

Any light?

Office 365 – How does the main menu of a modern SharePoint site become a dynamic sitemap?

I'm creating a modern SharePoint site as a documentation site for our end users. We want to create a basic hierarchy of folders and pages, and possibly pages with child pages.

📁Sales
    📄Creating a Lead
    📄Creating a Proposal
        📄Adjusting Prices
📁Administration
    📄Resetting Your Password

These are not just Word documents or other files in a directory, but modern SharePoint pages. My questions about building and maintaining this hierarchy are:

  1. How do I create nested pages, regardless of whether they are subordinate to a folder / section or another page? We do not want a flat list of pages.
  2. How do I display this hierarchy in the form of a sitemap in the main menu navigation? dynamic without having to manually create this hierarchy and edit it each time a new page is created?