Submitting your Finalsite sitemap to Google Search Console helps Google index all your public pages and improves discoverability. Every Composer site automatically maintains its own sitemap at yoursite.com/fs/pages/sitemap.xml. Schools with a single domain submit one sitemap; districts with multiple school sites or domains submit one sitemap for each. This article walks through both routes in five steps.
đź’ˇQuick answers
- Where is your Finalsite sitemap URL? At your domain followed by /fs/pages/sitemap.xml; it is automatically maintained by Composer and does not need to be manually updated.
- Do I submit one sitemap or several? Submit one sitemap per website. A single school (or a handful of sites) submits one sitemap for each site. A district with many school sites or subdomains submits each school's sitemap separately; the district sitemap does not include the school sites.
- What must be completed before submitting a sitemap? Your domain must be verified through Google Search Console; see the "Configure Google Search Console" article if not yet done. Districts should verify a Domain property so that all school subdomains are covered at once.
- Submitting the sitemap in Google Search Console? In the Sitemaps section of the left navigation, enter fs/pages/sitemap.xml in the Add a new sitemap field and click Submit. (For a Domain property, enter the full sitemap URL instead.)
- What does a "Couldn't fetch" status mean? Google was temporarily unable to access the sitemap; wait overnight and check again. If it persists after 24 hours, contact your Project Management or Support team.
- Where do you monitor sitemap status after submitting? In the Sitemaps section of Google Search Console, where success/failure messages and ongoing indexing insights are displayed.
Google Search Console lets you monitor and manage how your site shows up in Google search results. A key part of that visibility is your sitemap: a structured XML file that gives Google a clear view of all the public pages on your site, including how they’re organized and related.
This article will walk you through submitting your sitemap to Search Console, an essential step toward improving your site's discoverability and search performance. Steps 1, 2 and 4 have expandable sections for Route A and Route B, so open the one that fits your organization.
Which route applies to you?
A sitemap only describes the pages on the domain where it lives. That means Google needs a sitemap submitted for every domain or subdomain you want indexed.
Route A: Single school or a few sites
- Typical setup: One website, or a small number of sites (for example, a school and a separate foundation site).
- Sitemaps to submit: One per site.
- Property type: A URL-prefix property is fine.
-
Sitemap field entry:
fs/pages/sitemap.xml
Route B: District with multiple domains
-
Typical setup: A district site plus individual school sites on subdomains (
school.district.org) and/or separate domains (schoolname.org). - Sitemaps to submit: One per site: the district site and every school site.
- Property type: A Domain property for all subdomains of one root domain, and a separate property for any school on its own root domain.
-
Sitemap field entry: The full URL for each school, such as
https://school.district.org/fs/pages/sitemap.xml
If you are not sure which applies, count your public website addresses. If you have more than a handful, or schools have their own web addresses, follow Route B.
In this article
- Step 1: Retrieve your public sitemap URL(s)
- Step 2: Confirm that you have verified your domain through Google
- Step 3: Access Google Search consoleÂ
- Step 4: Submit your sitemap(s)
- Step 5: Monitor sitemap status
Step 1: Retrieve your public sitemap URL(s)
Directly access your sitemap by using a simple link format. Each domain’s sitemap lives at a specific URL:
- Replace [yourdomain] with the actual domain you're working with.
This XML file is automatically maintained by Composer and provides search engines with up-to-date page listings.
You have one sitemap URL for each site. Open each one in your browser to confirm it loads.
Each school site has its own sitemap, and the district sitemap does not list school pages. Make a list of every site's sitemap URL before you begin. For example:
-
https://www.district.org/fs/pages/sitemap.xml(district site) -
https://lincoln.district.org/fs/pages/sitemap.xml(school on a subdomain) -
https://roosevelt.district.org/fs/pages/sitemap.xml(school on a subdomain) -
https://www.eastsideacademy.org/fs/pages/sitemap.xml(school on its own domain)
Open each URL to confirm it loads. If a school's sitemap does not load, contact your Project Management or Support team before continuing.
Step 2: Confirm that you have verified your domain through Google
If you have not already verified your domain through Google, please start on this article: Configuring Google Search Console.Â
Verify each site as its own property.
Choose the property type that matches how your domains are set up:
-
Domain property (recommended): A single Domain property for
district.orgcovers the district site and every subdomain (lincoln.district.org,roosevelt.district.org, and so on), so you verify once. Domain properties are verified with a DNS record, so you will need access to your DNS settings or help from whoever manages them. -
Separate properties for separate root domains: A school that uses its own domain (such as
eastsideacademy.org) is not covered by the district's Domain property and must be verified on its own. - URL-prefix properties: If you cannot use DNS verification, verify each school's address as its own URL-prefix property.
Step 3: Access Google Search consoleÂ
- Visit Google Search Console at https://search.google.com/search-console/welcome.
- Log in using the Google account that has access to your Search Console properties.
- Once logged in, click the main menu and use the dropdown arrow to select your website as the Property.
- If you have many sites, use the search instead.
- If the site has not already been added, click on Add property and follow the instructions detailed in the article: Configuring Google Search Console.
Step 4: Submit your sitemap(s)
Repeat these steps for each site.
- From the property overview screen, click on Sitemaps in the left-hand navigation.
- In the provided Add a new sitemap field, enter
fs/pages/sitemap.xmlthen click Submit.
Submit a sitemap for the district site and for every school site, using the list you made in Step 1.
- Select the property that covers the site you are submitting for (the district's Domain property, or the school's own property), then click Sitemaps in the left-hand navigation.
- In the Add a new sitemap field:
- If you are in a URL-prefix property, enter
fs/pages/sitemap.xml. - If you are in a Domain property, enter the full sitemap URL for the school, for example
https://lincoln.district.org/fs/pages/sitemap.xml. A Domain property covers many hosts, so Google needs the complete address.
- If you are in a URL-prefix property, enter
- Click Submit.
- Repeat for each remaining school. In a Domain property, you can submit every subdomain's sitemap from the same Sitemaps screen. Schools on their own root domain are submitted in their own property.
District submission checklist
- District site sitemap submitted
- A sitemap submitted for every school site on a subdomain
- A sitemap submitted, in its own property, for every school site on a separate domain
- Each submission shows a status of Success in the Sitemaps report
Important Note
If you see a "Couldn't fetch" status, wait overnight.
Google periodically rechecks availability. If the issue persists after 24 hours, contact your Project Management or Support team for assistance.
Step 5: Monitor sitemap status
After submission, monitor the sitemap status to ensure Google successfully indexes it. The interface will update with success/failure messages and ongoing indexing insights.
Districts should check the Sitemaps report for each property periodically, since a school's status can differ from the district's. When a new school site is launched, repeat Steps 2 through 4 for that site.
For more information, reach out to Google Support.