Skip to content

Commit 70a36de

Browse files
authored
chore(gatsby-plugin-sitemap): Clarify language on entryLimit (#32113)
1 parent 2bf8c0d commit 70a36de

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

packages/gatsby-plugin-sitemap/README.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,8 @@ plugins: [`gatsby-plugin-sitemap`]
2222
Above is the minimal configuration required to have it work. By default, the
2323
generated sitemap will include all of your site's pages, except the ones you exclude.
2424

25+
You then can point your service (e.g. Google Search Console) at `https://www.example.com/sitemap/sitemap-index.xml`.
26+
2527
## Recommended usage
2628

2729
You probably do not want to use the defaults in this plugin. Here's an example of the default output:
@@ -57,7 +59,7 @@ The options are as follows:
5759

5860
- `output` (string = `/sitemap`) Folder path where sitemaps are stored.
5961
- `createLinkInHead` (boolean = true) Whether to populate the `<head>` of your site with a link to the sitemap.
60-
- `entryLimit` (number = 45000) Number of entries per sitemap file, a sitemap index and multiple sitemaps are created if you have more entries.
62+
- `entryLimit` (number = 45000) Number of entries per sitemap file. A sitemap index (as `sitemap-index.xml`) will always be created and multiple sitemaps are created for every `entryLimit` increment (e.g under 45000 entries only `sitemap-0.xml` will be created).
6163
- `excludes` (string[] = []) An array of paths to exclude from the sitemap. While this is usually an array of strings it is possible to enter other data types into this array for custom filtering. Doing so will require customization of the [`filterPages`](#filterPages) function.
6264
- `query` (GraphQL Query) The query for the data you need to generate the sitemap. It's required to get the site's URL, if you are not fetching it from `site.siteMetadata.siteUrl`, you will need to set a custom [`resolveSiteUrl`](#resolveSiteUrl) function. If you override the query, you may need to pass in a custom [`resolvePagePath`](#resolvePagePath), [`resolvePages`](#resolvePages) to keep everything working. If you fetch pages without using `allSitePage.nodes` query structure you will definitely need to customize the [`resolvePages`](#resolvePages) function.
6365
- [`resolveSiteUrl`](#resolveSiteUrl) (function) Takes the output of the data query and lets you return the site URL. Sync or async functions allowed.

0 commit comments

Comments
 (0)