First define what belongs in the sitemap
Collect content that people should be able to find: service pages, guides and standalone articles. Exclude drafts, the workspace, technical duplicates and outdated addresses that have already been replaced by a permanent version. Align the list with canonical URLs and navigation.
Check the sitemap as a real external resource. It must return a sitemap rather than the homepage HTML because of a catch-all routing rule. If you use a sitemap index, open the nested files too. An empty successful server response does not confirm that new articles are actually listed.
An accurate date is more useful than changing it every day
Google recommends an accurate lastmod corresponding to a significant page change. Replacing the year in the footer is not an update to the main content. Google ignores priority and changefreq values. There is therefore no point assigning every page maximum priority in the hope of speeding things up.
For a practical example, a guide’s working method for verifying a website changes. After publication, update that page’s date, not every article in the library. If the information has not changed, there is no need to rewrite its date every night. Keep the timestamp’s source in your publishing system so subsequent checks can be explained.
Submission and verification are different actions
With a search engine connected, submit the sitemap address through a supported method and save the result. Then review which URLs have been discovered and which have received their own status. Checking the file, accepting the sitemap and including a page in the index are different events.
If an error occurs, check the exact host, protocol, sitemap accessibility and listed addresses. If an article is not yet published or leads to a noindex page, resubmitting the sitemap will not fix the cause. Repeat a notification after a genuine change to its contents or page list, not just to get a green check mark.
How to work in AURA GEO
AURA managed publications have their own sitemap and library. Connected Google/Bing services let the agent submit available sitemaps and read the resulting receipts. The client website’s main sitemap depends on its publishing rules and authorized CMS or repository access.
Ask the agent to show the actual sitemap address and the new article inside it. The outcome is an accurate content list and a saved submission, not a promised deadline for appearing in AI answers.
Conditions and limitations
- A sitemap does not guarantee crawling or indexing.
- The client’s main website may have its own sitemap generator.
Explore the details
The sitemap contains the required primary addresses and the actual submission result is saved.
Check pages and sitemaps