Detailed explanation of wechat applet page configuration and sitemap configuration parameters

Configuration page

app.json Some configurations in , It also supports the configuration of a single page , It can be found on the corresponding page .json File to configure the performance of this page .

The configuration items in the page will be overwritten on the current page app.json The same configuration item in .

The content of the document is a JSON object , It has the following properties ：

Configuration item

attribute	type	The default value is	describe	Minimum version
navigationBarBackgroundColor	HexColor	#000000	Navigation bar background color , Such as #000000
navigationBarTextStyle	string	white	Navigation bar Title Color , Support only black / white
navigationBarTitleText	string		Navigation bar title text content
navigationStyle	string	default	Navigation bar style , Only the following values are supported ： default Default style custom Custom navigation bar , Just keep the capsule button in the upper right corner .	iOS/Android Wechat client 7.0.0,Windows Wechat client does not support
backgroundColor	HexColor	#ffffff	Background color of window
backgroundTextStyle	string	dark	The drop-down loading The style of , Support only dark / light
backgroundColorTop	string	#ffffff	The background color of the top window , only iOS Support	Wechat client 6.5.16
backgroundColorBottom	string	#ffffff	The background color of the bottom window , only iOS Support	Wechat client 6.5.16
enablePullDownRefresh	boolean	false	Whether to open the current page drop-down refresh . See Page.onPullDownRefresh
onReachBottomDistance	number	50	Distance from the bottom of the page when the pull-up event is triggered , Unit is px. See Page.onReachBottom
pageOrientation	string	portrait	Screen rotation settings , Support auto / portrait / landscape See Respond to changes in the display area	2.4.0 (auto) / 2.5.0 (landscape)
disableScroll	boolean	false	Set to true The whole page cannot scroll up and down . Only valid in page configuration , Cannot be in app.json Set in
usingComponents	Object	no	page Custom components To configure	1.6.3
initialRenderingCache	string		page Initial render cache To configure , Support static / dynamic	2.11.1
style	string	default	Enable new component styles	2.10.2
singlePage	Object	no	Single page mode related configuration	2.12.0
restartStrategy	string	homePage	Restart policy configuration	2.8.0
handleWebviewPreload	string	static	control Time to preload the next page . Support static / manual / auto	2.15.0
visualEffectInBackground	string	no	When cutting into the background of the system , Hide page content , Protect user privacy . Support hidden / none, If the page is set separately, the global configuration will be overwritten , See Global configuration	2.15.0
enablePassiveEvent	Object or boolean	no	Whether the event listener is passive, If the page is set separately, the global configuration will be overwritten , See Global configuration	2.24.1

• notes ： Not all app.json The configurations in can be overwritten on the page or specified separately , Only options included in this document .
• notes ：iOS/Android client 7.0.0 The following versions ,navigationStyle Only in app.json Enter into force .

Configuration example

{
  "navigationBarBackgroundColor": "#ffffff",
  "navigationBarTextStyle": "black",
  "navigationBarTitleText": " Wechat interface function demonstration ",
  "backgroundColor": "#eeeeee",
  "backgroundTextStyle": "light"
}

---

sitemap To configure

  Wechat has now opened the search in the applet , Developers can use sitemap.json To configure , Or manage the background page collection switch to configure whether wechat index is allowed for its applet page . When developers allow wechat indexing , Wechat will take the form of a crawler , Index the page content of the applet . When the user's search term triggers the index , The page of the applet will probably be displayed in the search results . When a crawler visits a page in an applet , Will carry specific user-agent：mpcrawler And Scene value ：1129. It should be noted that , If the page data found by the app crawler is inconsistent with the real user's presentation , Then the page will not enter the index .

In the applet root directory sitemap.json This file is used to configure whether the applet and its page can be indexed by wechat , The content of the document is a JSON object , without sitemap.json , All pages are allowed to be indexed by default ;sitemap.json It has the following properties ：

Configuration item

attribute	type	Required	describe
rules	Object[]	yes	Index rule list

rules

rules The configuration item specifies the index rule , Each rule is a JSON object , Properties are shown below ：

attribute	type	Required	The default value is	Value	Value description
action	string	no	"allow"	"allow"、"disallow"	Whether the pages that hit the rule can be indexed
page	string	yes		"*"、 The path of the page	* Represents all pages , Cannot be used as a wildcard
params	string[]	no	[]		When page The list of page parameter names that may be used when the page specified by the field is matched by this rule （ Without parameter value ）
matching	string	no	"inclusive"	Reference resources matching Value description	When page When the page specified in the field is matched by this rule , This parameter describes params How to match
priority	Number	no			priority , The larger the value, the earlier the rule is matched , Otherwise, it will match from top to bottom by default

matching Value description

value	explain
exact	When the parameter list of the applet page is equal to params when , Rules hit
inclusive	When the parameter list of the applet page contains params when , Rules hit
exclusive	When the parameter list of the applet page is different from params When the intersection is empty , Rules hit
partial	When the parameter list of the applet page is different from params When the intersection is not empty , Rules hit

Configuration example

Example 1

{
  "rules":[{
    "action": "allow",
    "page": "path/to/page",
    "params": ["a", "b"],
    "matching": "exact"
  }, {
    "action": "disallow",
    "page": "path/to/page"
  }]
}

• path/to/page?a=1&b=2 => Priority index
• path/to/page => Not indexed
• path/to/page?a=1 => Not indexed
• path/to/page?a=1&b=2&c=3 => Not indexed
• Other pages will be indexed

Example 2

{
  "rules":[{
    "action": "allow",
    "page": "path/to/page",
    "params": ["a", "b"],
    "matching": "inclusive"
  }, {
    "action": "disallow",
    "page": "path/to/page"
  }]
}

• path/to/page?a=1&b=2 => Priority index
• path/to/page?a=1&b=2&c=3 => Priority index
• path/to/page => Not indexed
• path/to/page?a=1 => Not indexed
• Other pages will be indexed

Example 3

{
  "rules":[{
    "action": "allow",
    "page": "path/to/page",
    "params": ["a", "b"],
    "matching": "exclusive"
  }, {
    "action": "disallow",
    "page": "path/to/page"
  }]
}

• path/to/page => Priority index
• path/to/page?c=3 => Priority index
• path/to/page?a=1 => Not indexed
• path/to/page?a=1&b=2 => Not indexed
• Other pages will be indexed

Example 4

{
  "rules":[{
    "action": "allow",
    "page": "path/to/page",
    "params": ["a", "b"],
    "matching": "partial"
  }, {
    "action": "disallow",
    "page": "path/to/page"
  }]
}

• path/to/page?a=1 => Priority index
• path/to/page?a=1&b=2 => Priority index
• path/to/page => Not indexed
• path/to/page?c=3 => Not indexed
• Other pages will be indexed

notes ： No, sitemap.json All pages can be indexed by default

notes ：{"action": "allow", "page": "*"} Is the default rule with the lowest priority , Not explicitly specified "disallow" Are indexed by default

---