Skip to content

Article 16 min read

XML Sitemap: What Google Reads, What It Ignores, and What Shouldn't Be on the List

by Daniel Sócrates published

On September 14, 2026, we searched for “sitemap xml” on Google. The search ran on Google in Brazil, where we are based. At the top, the AI Overview came up in English, even on the Portuguese interface. It gets the file limits right: 50,000 addresses and 50 MB. 1

Scroll down the page. A Brazilian marketing guide, last updated in 2017, says the file cannot go over 10 MB. 2 That limit did exist. The protocol moved to 50 MB in November 2016. 3 A Portuguese-language post from November 2025 says the sitemap tells Google the priority and update frequency of each page. 2 Google writes that it ignores both fields. 4

None of these texts was written in bad faith. The protocol changed, the documentation changed, and the published text stayed where it was. That is why this piece works with the official pages open, checked on September 14, 2026.

What a sitemap is, and why it is only a hint

In the piece on SEO for WordPress, I compared the sitemap to the tenant directory in a building lobby. The delivery driver does not have to knock on every door to learn who lives there.

Now finish the scene. The driver gets the directory and keeps walking the halls. He decides the order, the time, and how many doors he visits today. The directory helps, and the driver picks the route.

Google describes the file the same way. The sitemap gives information about the pages and files on the site, and the relationships between them. 5 It says which pages you consider important, when they changed, and which versions exist in other languages. 5 Search engines read the file to crawl the site more efficiently. 5

The sentence that shapes the rest is on the submission page. Google may not download the file, and may not use the list for crawling. 4 This is called a hint, and the word is Google’s own. 4

The file helps the crawler discover addresses. It does not guarantee that all of them will be crawled and indexed. 5 How often the crawler comes back to the site, and what brings it back, is in the piece on crawling and crawl budget.

When Google says a sitemap helps

Google’s page on sitemaps gives three cases where you might need the file. 5

  1. A large site. The more pages, the harder it is to make sure each one gets a link from another. Some new pages may go undiscovered. 5
  2. A new site, with few links from outside. The crawler moves across the web by following links from pages it has already crawled. If nobody points to you, it may not get there. 5
  3. A site with lots of video and images, or one that appears in Google News. The file carries extra information about that media. 5

The same page says when you might not need one. 5 A small site, with about 500 pages or fewer, counting only the ones that need to be in search results. A site where every important page can be reached through links from the homepage. And a site without much media or news to show in search. 5

Even so, the text closes in favor of the file. In most cases, a site benefits from having one. 5 And anyone on WordPress, Wix, or Blogger probably has one already, without lifting a finger. 5

My takeaway is simple. The sitemap pays off most where internal linking falls short.

The protocol and the file limits

Think of a standard shipping label at the post office. Everyone fills in the same fields, and any branch can read it. The XML sitemap follows a public form like that, created in 2005. 6 This is called the sitemaps protocol, and it lives at sitemaps.org. 3

The file opens and closes with the <urlset> tag. Each page goes inside a <url>, and each <url> carries a <loc> with the address. Everything else is optional. 3 The file must be UTF-8 encoded, and the addresses go in full, with https and the domain. 3 4

Google accepts three formats. XML, an RSS or Atom feed, and a plain text list with one address per line. It writes that it has no preference. 4 XML is the most versatile, because it takes extensions for images, video, news, and versions in other languages. 4

The limits, and the sitemap index

Each file holds up to 50,000 addresses or 50 MB uncompressed. Past that, you split it. 3 4 The size cap used to be smaller. The Internet Archive copy of the protocol from November 2, 2016, said 10 MB. The copy from December 1 already said 50 MB. 3

Picture an accordion file with many pockets. A label on the front lists the pockets, and each pocket holds its own papers. When the site goes past the limit, each file becomes a pocket, and a separate file lists them all. This is called a sitemap index.

The index uses the <sitemapindex> tag and lists up to 50,000 sitemaps. 3 7 The listed files have to live on the same site, in the index’s folder or below it. 7 One index cannot list another index, and Search Console flags it as an error. 8 Each site can submit up to 500 index files in Search Console. 7

You can split even below the limit. Google points out that this helps you track each sitemap in Search Console. 4

An example, made up

The example below is made up. The domain example.com is reserved for documentation and belongs to no one. 9

bloco para copiar
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://www.example.com/</loc>
  </url>
  <url>
    <loc>https://www.example.com/pintura-de-fachada/</loc>
    <lastmod>2026-09-10</lastmod>
  </url>
</urlset>

There are two addresses. The first carries only the <loc>, the minimum the protocol requires. The second also carries the <lastmod>, the date the page last changed. 3 On September 14, I checked the file against the official schema published at sitemaps.org. It passed with no errors. 10

Two fields that many people add are missing, <priority> and <changefreq>. They were left out on purpose, and the reason comes next.

What Google reads and what it ignores

The sentence takes up one line of the documentation: “Google ignores <priority> and <changefreq> values.” 4 In 2023, Google’s blog repeated that it still does not use those two fields at all. 6

The protocol itself had already warned us. Priority goes from 0.0 to 1.0, and the default is 0.5. 3 The text says it is not likely to influence your position in the results. And that giving every page a high priority is not likely to help. 3 The native WordPress sitemap, since version 5.5, lists only the address, because search engines do not typically read the other fields. 11

The <lastmod> has a different fate. Think of the “last revised” date printed in an owner’s manual. If every reprint stamps that day’s date, readers learn to ignore the stamp. In a sitemap, that stamp is the date of the last modification.

Google uses the <lastmod> when it is consistently and verifiably accurate. For example, when it matches the last change on the page itself. 4 The date should mark the last significant change: main text, structured data, or links. Updating the copyright year in the footer does not count. 4

The 2023 blog post was more blunt. If the page changed seven years ago and the date says yesterday, at some point Google stops believing you. 6 The same post says it is fine to leave the date out when the system cannot tell, as on the homepage or a category list. 6

How to get the sitemap to Google

The documentation lists three routes. 4

The Sitemaps report in Search Console. You paste the address and submit. The report shows when the crawler read the file and any errors in the reading. 4 8 Submitting requires owner permissions. Without them, you can declare the file in robots.txt. 8

The Search Console API, for anyone who submits through code. 4

The robots.txt file, with a line that starts with Sitemap: and carries the full address. Google finds it the next time it reads robots.txt. 4 The line applies to any crawler, and the file accepts several, with no limit. 3 4 The rest of that file, and what it really blocks, is in the piece on robots.txt.

One detail ties the routes together. The Sitemaps report shows only what was submitted through it or through the API. A sitemap declared only in robots.txt does not show up there, even though Google reads it. 8 The sitemap filter in the Page indexing report counts both routes. 12

The route that closed: the ping

There was a fourth route. The protocol describes a notification address: the site calls the search engine and passes along the sitemap’s address. 3 This is called a ping.

On June 26, 2023, Google announced the end of its ping. The stated reason: the vast majority of those submissions led to spam. 6 The endpoint would stop working in six months and start responding with a 404. 6 Today the post opens with a notice that the deprecation is complete. 6

I did not find the exact shutdown date in the documentation. On September 14, 2026, I tested Google’s ping address. The response was a 404. 13 The post says an old plugin that still calls the ping causes no problem. It just does nothing useful. 6

Resubmitting, deleting, and what does not help

After the first read, Google comes back to the sitemap at its own pace, independent of the site’s crawl. 8 Resubmitting is for big changes to the file. Otherwise, the help page says to let Google follow its regular schedule. 8

Deleting a sitemap from the report does not erase the memory either. Google does not forget the file or the addresses it listed. 8 To stop the crawler from visiting, the help page points to three ways out: a robots.txt rule, removing the file, or a noindex rule. 8

The Sitemaps report, column by column

For each submitted file, the report shows the type, the submission date, and the last read. 8 The status has three values. Success, when Google read it with no errors. Has errors, when it read only part of it. And Couldn’t fetch, when it never reached the file. 8

The column that misleads the most is Discovered pages. It counts the addresses parsed from the file. The help page says there is no guarantee they have been or will be crawled and indexed. 8 To find out how many made it into the index, filter the Page indexing report by that sitemap. 8 12

When the status is Couldn’t fetch, the help page lists the causes. 8 The file is blocked in robots.txt. The address is wrong and returns a 404. There is a pending manual action on the site. The server is down. Or there is low crawl demand for the file. 8

The mistake of listing what shouldn’t be there

Back to the lobby. Now the directory lists someone who moved out, an apartment that was torn down, and a tenant who asked not to be bothered. The driver wastes time at each door. And he learns to distrust the directory.

Google asks for the addresses you want to see in search results. 4 Building the file means saying which addresses you prefer to show, the canonical ones. 4 The page on canonical URLs adds that every page listed in the sitemap is suggested as canonical. 14 Three kinds of address clash with that request.

The address that redirects. A page with a redirect does not get indexed. Only the destination can be. 12 In practice, listing the source asks Google to treat as canonical an address that sends the visitor away. The help page suggests swapping those addresses for the ones that should actually be crawled. 8 Where a redirect fails silently is in the piece on 301 redirects.

The address that returns a 404. The help page recommends fixing the 404s in your own links and in your sitemap. 12 The rest can be normal, if the page was removed with no replacement. 12

The address with noindex. The sitemap asks for indexing, and the page asks to stay out. The help page lists this case among the causes of a spike in indexing errors. The same goes for a page blocked in robots.txt or behind a login. 12

There is also the same request down two paths: the sitemap points to one address and the canonical tag to another, for the same page. Google says not to do this. 14 That case has its own piece, on the canonical tag.

Our own case: the old sitemap and the new one

The old site, on August 31, 2026

Our company site in Brazil, seogenome.com, ran on WordPress until early September 2026. In the diagnosis of August 31, the sitemap had three problems. 15

First, anyone who typed /sitemap.xml got a success response with an empty file. The real sitemap lived at /wp-sitemap.xml. 15 Second, the robots.txt pointed to no sitemap at all. 15 Third, the sitemap listed 19 /go/ addresses, created by a link shortener plugin. Each one existed only to respond with a 301 and send the visitor elsewhere. 15

By the yardstick of the previous section, those were 19 canonical requests for addresses that redirect. 14 15 How they got onto the list is told in the piece on WordPress.

In Search Console, two old sitemaps had been registered since March 16, 2026. One was /wp-sitemap.xml, with 47 addresses. The other, /br/wp-sitemap-posts-page-1.xml, had 19. 16 With the new site live on September 2, the first returned a 404 and the second a 301. Both came out of the report, and the new sitemap was submitted the same day. 16

Taking them out of the report does not make Google forget the old addresses. 8 In my reading, what settles each old address is its own redirect.

The new site, generated in the build

The new site, built in Astro, generates the sitemap with every publish, inside the build itself. 10 Nobody types the list. The generator finds the pages by the same rule that decides what is live. 10 A scheduled page stays out until its day. This piece was written on September 14, 2026, and scheduled. By that rule, it only joins the list on its publication day. 10

The <lastmod> was left out on purpose. The code writes the date only when the page has a recorded update. Stamping the build date would make every page look changed with every publish. 10 It is the owner’s manual stamp, applied to our own site.

On September 14, 2026, I checked the live file. 10

What I checkedWhat I found
Address/sitemap.xml, a single file, no index
robots.txta Sitemap: line pointing to it
Addresses listed91, in Portuguese and English, with the language pairs
Size32,626 bytes
Response for each address91 returned 200, with no redirect along the way
noindexnone
<lastmod>none, because no page has a recorded update
Canonical87 point to themselves; 4 point to another domain

The four exceptions were the partners’ pages, in Portuguese and in English. Each one names the partner’s personal site as canonical. It was the same request down two paths from the previous section, covered in the canonical tag piece. 10 14 We fixed it the same day: pages with an external canonical came out of the file, which now lists 87 addresses.

Search Console read the same file. Through the API, it was submitted on September 2 and last read on September 12. It had 90 addresses, zero errors, and zero warnings. 10 By the 14th, the file already listed 91. Google rereads at its own pace, and the gap shows it. 8 10

The API also returns a field for pages indexed per sitemap. Its documentation says the field is deprecated and should not be used. 17

The fifteen-minute check

Have your site’s address ready and Search Console open.

  1. Open robots.txt. Type yourdomain.com/robots.txt and look for the Sitemap: line. Without it, the file may exist with no one ever told about it. 4
  2. Open the address on that line. If it is an index, open one of the sitemaps it lists. 7
  3. Count the addresses. More than 50,000 in one file calls for a split. 3
  4. Test a sample. Take ten addresses and check the response for each one. Redirects and 404s come off the list. 8 12
  5. Look for noindex. Open the source code of three listed pages and search for the word noindex. 12
  6. Read the <lastmod>. Compare the date on three pages with their last real change. 4 In my reading, the same date on every page, today’s, is usually the generator’s stamp.
  7. Leave <priority> and <changefreq> alone. Google does not read either one. 4 Do not spend time tuning them.
  8. Open the Sitemaps report. Check the status, the last read, and whether the registered address is the one that responds today. 8
  9. Filter indexing by the sitemap. In the Page indexing report, pick the sitemap and read the reasons for the pages left out. 12

The whole technical ground, from indexing to speed, is in technical SEO.

From now on, when someone says the sitemap will get Google to index the site, you will ask for two things. The last read in the Sitemaps report. And the indexing report filtered by that file.

The first step fits in right now. Open yourdomain.com/robots.txt, look for the Sitemap: line, and open the address it points to.

Frequently asked questions

Does every site need an XML sitemap?

Google says a small site, with about 500 pages or fewer and well linked internally, might not need one. 5 A large site, a new one, or one with lots of media tends to gain from it. In most cases, according to the same page, a site benefits. 5

Does submitting the sitemap make Google index the pages?

There is no guarantee. Submitting is a hint, and Google may not download the file or use the list for crawling. 4 The Discovered pages column does not tell you how many were indexed either. 8

Does the priority tag in a sitemap help ranking?

Not on Google. The documentation says it ignores <priority> and <changefreq>. 4 The protocol itself says priority is not likely to influence your position in the results. 3

How many URLs fit in one sitemap?

Up to 50,000 addresses or 50 MB uncompressed per file. 3 4 Beyond that, split it into several files and list them all in a sitemap index. 7

Does Google’s sitemap ping still work?

No. Google announced its end on June 26, 2023, with a six-month deadline. 6 On September 14, 2026, the address returned a 404 in my test. 13 What remains is Search Console, the API, and robots.txt. 4

Do I need to resubmit the sitemap for every new page?

No. After the first read, Google comes back to the file at its own pace. 8 The help page saves resubmission for big changes to the sitemap. 8

Notes and sources

  1. Live reading of the Google Brazil results page for “sitemap xml,” September 14, 2026, at https://www.google.com.br/search?q=sitemap+xml&hl=pt-BR&gl=br&pws=0, in the author’s own browser tab. The search ran on Google in Brazil, where we are based, with the interface in Portuguese. The AI Overview, labeled “Visão geral criada por IA,” came up in English: “An XML sitemap is a file that lists a website’s essential pages so search engines like Google can find and crawl them efficiently”, with the section “Key Limits” (“Up to 50,000 entries per file”, “Maximum of 50MB uncompressed”, and a sitemap index beyond that). Organic results in order: Google for Developers (“What Is a Sitemap”), XML Sitemaps Generator, RD Station, digital.gov, English Wikipedia, Mirago, sitemaps.org, i-cherry, and a YouTube video. The same day, the Semrush snapshot, Brazil database, recorded 720 searches a month for the phrase, with ten organic results among guides, generators, and other sites’ sitemap files, none on another subject. Accessed September 14, 2026.
  2. SEO Genome survey, September 14, 2026, of texts from the first page in the previous note, downloaded and read the same day. RD Station, “Sitemap XML: tudo o que você precisa saber” (XML sitemap: everything you need to know), published September 12, 2012, and updated October 11, 2017, https://www.rdstation.com/blog/marketing/o-que-e-sitemap-xml/: “É um arquivo XML simples, que não pode ter mais de 50.000 URLs (e 10MB)” (it is a simple XML file that cannot have more than 50,000 URLs, and 10MB) and “o Google não consegue trabalhar com Sitemaps que possuem mais de 10mb de tamanho” (Google cannot work with sitemaps larger than 10mb). i-cherry, “Sitemap.xml: o que é, para que serve e boas práticas” (Sitemap.xml: what it is, what it is for, and best practices), November 26, 2025, https://blog.i-cherry.com.br/sitemap-xml: the sitemap “indica as páginas prioritárias e mostra com que frequência o conteúdo é atualizado” (points out the priority pages and shows how often the content is updated). Mirago, September 22, 2024, https://www.mirago.com.br/sitemap/, records that “O campo prioridade atualmente não é utilizado pelo Google” (the priority field is not currently used by Google). Accessed September 14, 2026.
  3. Sitemaps.org, “Sitemaps XML format,” https://www.sitemaps.org/protocol.html, page marked “Last Updated: Monday, November 21, 2016”; and Internet Archive copies of the same page from November 2, 2016, https://web.archive.org/web/20161102154805/http://www.sitemaps.org/protocol.html, and from December 1, 2016, https://web.archive.org/web/20161201082313/https://www.sitemaps.org/protocol.html. Accessed September 14, 2026. Passages from the current page: “The file itself must be UTF-8 encoded”; the file must open with <urlset>, have one <url> per address and one <loc> in each, and “All other tags are optional”; “each Sitemap file that you provide must have no more than 50,000 URLs and must be no larger than 50MB (52,428,800 bytes)”; “Sitemap index files may not list more than 50,000 Sitemaps”; on priority, “Valid values range from 0.0 to 1.0”, “The default priority of a page is 0.5”, “not likely to influence the position of your URLs in a search engine’s result pages”, and “assigning a high priority to all of the URLs on your site is not likely to help you”; on the robots.txt line, “This directive is independent of the user-agent line”; and submission through <searchengine_URL>/ping?sitemap=sitemap_url. The November 2, 2016, copy says “no larger than 10MB (10,485,760 bytes)”; the December 1 copy, “no larger than 50MB (52,428,800 bytes)”.
  4. Google Search Central, “Build and submit a sitemap,” https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap, page last updated July 8, 2026; Portuguese version, “Criar e enviar um sitemap” (Build and submit a sitemap), updated July 15, 2026. Accessed September 14, 2026. Passages: “Google doesn’t have a preference” among the formats; “XML sitemaps are the most versatile of the sitemaps formats”; “All formats limit a single sitemap to 50MB (uncompressed) or 50,000 URLs”; splitting “may be useful if you want to track the search performance of each individual sitemap in Search Console”; “Use fully-qualified, absolute URLs in your sitemaps”; “Include the URLs in your sitemap that you want to see in Google’s search results”; “you’re telling search engines about which URLs you prefer to show in search results. These are the canonical URLs”; “Google ignores <priority> and <changefreq> values”, in the Portuguese version “O Google ignora os valores <priority> e <changefreq>”; “Google uses the <lastmod> value if it’s consistently and verifiably (for example by comparing to the last modification of the page) accurate”, with a significant change to the main content, the structured data, or the links, and “an update to the copyright date is not”; “submitting a sitemap is merely a hint: it doesn’t guarantee that Google will download the sitemap or use the sitemap for crawling URLs on the site”, in the Portuguese version “O envio de um sitemap é apenas uma dica”; and the submission routes (the Sitemaps report, “This will allow you to see when Googlebot accessed the sitemap and also potential processing errors”, the Search Console API, and the line “Sitemap: https://example.com/my_sitemap.xml” in robots.txt, with “We will find it the next time we crawl your robots.txt file” and “there’s no limit to the number of sitemaps you can include in your robots.txt file”).
  5. Google Search Central, “Learn about sitemaps,” https://developers.google.com/search/docs/crawling-indexing/sitemaps/overview, page last updated December 10, 2025; Portuguese version, “Saiba mais sobre sitemaps” (Learn about sitemaps), updated December 18, 2025. Accessed September 14, 2026. Passages: “A sitemap is a file where you provide information about the pages, videos, and other files on your site, and the relationships between them. Search engines like Google read this file to crawl your site more efficiently”; the file tells “which pages and files you think are important”, “when the page was last updated and any alternate language versions”; “it doesn’t guarantee that all the items in your sitemap will be crawled and indexed. However, in most cases, your site will benefit from having a sitemap”; the list “You might need a sitemap if” (a large site, a new site with few external links, lots of media content, or presence in Google News); the list “You might not need a sitemap if”, with “about 500 pages or fewer” and “Only pages that you think need to be in search results count toward this total”; and “If you’re using a CMS such as WordPress, Wix, or Blogger, it’s likely that your CMS has already made a sitemap available to search engines and you don’t have to do anything”.
  6. Gary Illyes, “Sitemaps ping endpoint is going away,” Google Search Central Blog, June 26, 2023, https://developers.google.com/search/blog/2023/06/sitemaps-lastmod-ping. Accessed September 14, 2026. The page now opens with the notice “The sitemaps ping endpoint deprecation is complete.” Passages: “The Sitemaps Protocol was introduced in 2005”; “in the case of Google Search, the vast majority of the submissions lead to spam”; “the endpoint will stop functioning in 6 months”; the pings “will result in a 404 error”; “Any existing code or plugins which use this endpoint will not cause problems for Google Search”, “but using the endpoint will also not do anything useful”; “if your page changed 7 years ago, but you’re telling us in the lastmod element that it changed yesterday, eventually we’re not going to believe you anymore”; “In these cases it’s fine to leave out lastmod for those pages”, on the homepage and category pages; and “Google still doesn’t use the changefreq or priority elements at all.”
  7. Google Search Central, “Manage your sitemaps with a sitemap index file,” https://developers.google.com/search/docs/crawling-indexing/sitemaps/large-sitemaps, page last updated December 10, 2025. Accessed September 14, 2026. Passages: the <sitemapindex> root; “A sitemap index file may have up to 50,000 loc tags”; “Sitemaps that are referenced in the sitemap index file must be in the same directory as the sitemap index file, or lower in the site hierarchy”; and “You can submit up to 500 sitemap index files for each site in your Search Console account.”
  8. Search Console Help, “Sitemaps report,” https://support.google.com/webmasters/answer/7451001, English and Portuguese versions. Accessed September 14, 2026. Passages: “You must have owner permissions on a property to submit a sitemap using the Sitemaps report. If you don’t have owner permissions, you can list the sitemap in your robots.txt file instead”; “Google will continue to recrawl the sitemap at a pace independent of the site crawl schedule”; “If you make big changes to a sitemap, you might want to resubmit”, and otherwise “let Google follow its regular crawling schedule”; “Deleting a sitemap removes the sitemap from this report, but Google won’t forget the sitemap or any URLs listed in it”, with robots.txt, removing the file, and noindex in a response header as ways out; “It does not show any sitemaps discovered through a robots.txt reference or other discovery methods”; the statuses “Success”, “Has errors”, and “Couldn’t fetch”; “There is no guarantee that a page URL discovered in a sitemap has been or will be crawled or indexed by Google. You can filter the Page indexing report by sitemap”; the causes of fetch failure (a robots.txt block, a manual action, a wrong URL with a 404, a general error, and “low crawl demand for the sitemap”); “We suggest that you replace any redirect URLs in your sitemaps with the URLs that should actually be crawled”; and the error “Nested sitemap indexes”, “A sitemap index file can’t list other sitemap index files”. The Portuguese version, which warns “Esta página pode ter conteúdo que foi traduzido com tecnologia de IA” (this page may contain content translated with AI technology), labels them “Processado,” “Contém erros,” “Não foi possível buscar o sitemap,” and “Páginas encontradas.”
  9. IANA, “Example Domains,” https://www.iana.org/help/example-domains, revision of May 13, 2017. Accessed September 14, 2026. Passages: domains such as example.com are maintained “for documentation purposes” and are not “available for registration or transfer”, based on RFC 2606 and RFC 6761.
  10. SEO Genome measurement and record, September 14, 2026. By curl, without following redirects: https://seogenome.com/sitemap.xml at 200, application/xml, 32,626 bytes, 91 <url> entries, no <lastmod>, with the pt-BR and en language pairs; the 91 URLs requested one by one, all at 200 directly, none with noindex, 87 with a canonical equal to their own URL and 4 with a canonical on another domain (/quem-somos/daniel-socrates/ and /en/about/daniel-socrates/ to https://danielsocrates.com.br/, /quem-somos/polly-melo/ and /en/about/polly-melo/ to https://pollymelo.com.br/); https://seogenome.com/robots.txt with the line “Sitemap: https://seogenome.com/sitemap.xml”; /sitemap-index.xml and /wp-sitemap.xml at 404. After the same-day fix, the live file listed 87 <url> entries. Generator code read in the site repository (src/pages/sitemap.xml.ts): the list comes from the pages and pieces under the same publication rule as the routes, a pending piece does not enter, and the date only appears when there is a recorded update, because stamping the build date would make every page look changed with every publish. Search Console API reading, property https://seogenome.com/, read-only: sitemap https://seogenome.com/sitemap.xml submitted on September 2, 2026, at 20:46 UTC, last read on September 12, 2026, at 14:44 UTC, 90 URLs submitted, 0 errors and 0 warnings. The example in the text was validated against the schema https://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd, with no errors. Accessed September 14, 2026.
  11. Pascal Birchler, “New XML Sitemaps Functionality in WordPress 5.5,” Make WordPress Core, July 22, 2020, https://make.wordpress.org/core/2020/07/22/new-xml-sitemaps-functionality-in-wordpress-5-5/. Accessed September 14, 2026. Passage: changefreq and priority are “not typically consumed by search engines, which is why WordPress only lists the URL itself”.
  12. Search Console Help, “Page indexing report,” https://support.google.com/webmasters/answer/7440203. Accessed September 14, 2026. Passages: “All submitted pages - Show only URLs listed in a sitemap or sitemap index that was submitted using either the Sitemaps report or a robots.txt file on your site”; “Page with redirect: This is a non-canonical URL that redirects to another page. As such, this URL will not be indexed”; “we recommend fixing only 404 errors that you link to yourself or list in a sitemap”; the acceptable 404 “for a page that you’ve removed and have no replacement for”; and, among the causes of an error spike, “you might have submitted a sitemap that includes URLs that are blocked for crawling by robots.txt, noindex, or a login requirement”.
  13. SEO Genome test, September 14, 2026: request to https://www.google.com/ping?sitemap=https%3A%2F%2Fwww.example.com%2Fsitemap.xml, HTTP 404 response. The documentation updates page, https://developers.google.com/search/updates, has no entry about the ping. Accessed September 14, 2026.
  14. Google Search Central, “How to specify a canonical URL with rel=“canonical” and other methods,” https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls, page last updated July 10, 2026. Accessed September 14, 2026. Passages: “All pages listed in a sitemap are suggested as canonicals”; “Sitemap inclusion: A weak signal”; and “don’t specify one URL in a sitemap, but a different URL for that same page using rel=“canonical"".
  15. SEO Genome internal record, “Diagnóstico do site seogenome.com” (seogenome.com site diagnosis), August 31, 2026. Method: authenticated WordPress REST API, a crawl of the 22 published URLs, a reading of the sitemaps, Search Console, and Google Analytics 4. Findings used: /sitemap.xml with a 200 response and empty content; the real sitemap at /wp-sitemap.xml; robots.txt with no sitemap declaration; 19 /go/ addresses, generated by the Linker plugin with a 301, listed in wp-sitemap-posts-linker-1.xml.
  16. SEO Genome, migration record for seogenome.com, September 2, 2026 (client record). Old sitemaps registered in Search Console since March 16, 2026: /wp-sitemap.xml, with 47 URLs submitted, at 404 after the switchover, and /br/wp-sitemap-posts-page-1.xml, with 19, at 301; both removed from the report, and /sitemap.xml submitted and processed the same day.
  17. Search Console API, “Sitemaps” resource, https://developers.google.com/webmaster-tools/v1/sitemaps. Accessed September 14, 2026. On the indexed field: “contents[].indexed”, “Deprecated; do not use.” The value returned for the seogenome.com sitemap was not used.

Want to see SEO Genome more often on Google? Add it as a preferred source.

Daniel Sócrates

Founder and CEO of SEO Genome

Author of AI Search Optimization. Writes about what the company applies in client work.

danielsocrates.com.br

Let us look at what the machine understands about your company

A diagnostic conversation, with no slide deck. You bring your website address. We bring what Google and the AI assistants already know about it today.

Talk to us on WhatsApp